Open GoogleCodeExporter opened 9 years ago
Thanks for the report.
It seems they removed the create_proc_read_entry() in 3.10 :-/
In the meantime you can compile the driver without CONFIG_PROC_FS defined
(simplest way is to add an #undef CONFIG_PROC_FS to the vtunerc_prov.h)
/Honza
Original comment by jpetrous
on 9 Jul 2013 at 7:29
I did very quick patch, unfortunatelly I can't check it right now on running
kernel, so it can be broken in any way.
If you want to check asap, please use the attached patchfile and report
findings.
/Honza
Original comment by jpetrous
on 9 Jul 2013 at 11:37
Attachments:
the patch is ok
the build in ok
make -C /root/openbricks/build/build.x86_64.eglibc/linux-3.10
SUBDIRS=/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14
modules
make[1]: Entering directory
`/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/linux-3.10'
CC [M] /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc_main.o
CC [M] /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc_ctrldev.o
CC [M] /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc_proxyfe.o
LD [M] /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc.o
Building modules, stage 2.
MODPOST 1 modules
CC /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc.mod.o
LD [M] /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc.ko
make[1]: Leaving directory
`/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/linux-3.10'
many tanks
i have modify the patch for version 1.4 of vtuner
these is the file
Original comment by pierluca...@gmail.com
on 9 Jul 2013 at 12:31
Attachments:
Original issue reported on code.google.com by
pierluca...@gmail.com
on 8 Jul 2013 at 1:29