MrEngman
commented
6 years ago Finially managed to get the driver working with Raspbian kernel 4.14 on a Raspberry Pi.
Using code from port-to-4.13 I deleted the references to the vfs_read and vfs_write symbols using the patch
diff -Naurwb '--exclude=.git' genodeftest-Netgear-A6210/os/linux/rt_linux.c genodeftest-Netgear-A6210-4.14/os/linux/rt_linux.c
--- genodeftest-Netgear-A6210/os/linux/rt_linux.c 2017-12-01 01:32:22.730833865 +0000
+++ genodeftest-Netgear-A6210-4.14/os/linux/rt_linux.c 2017-12-01 01:33:59.010431737 +0000
@@ -701,7 +701,7 @@
mm_segment_t fs = get_fs();
set_fs(get_ds());
- ret = vfs_read(osfd, pDataPtr, readLen, &osfd->f_pos);
+ ret = 0;
set_fs(fs);
return ret;
}
@@ -713,7 +713,7 @@
mm_segment_t oldfs = get_fs();
set_fs(get_ds());
- ret = vfs_write(osfd, pDataPtr, writeLen, &osfd->f_pos);
+ ret = 0;
set_fs(oldfs);
return ret;
}The driver now compiles without the warning about vfs_read and vfs_write and I have the driver running with an Asus USB-N53_B1 on a Raspberry Pi 2B running Raspbian Stretch kernel 4.14.2
I've no idea what effect the patch may have in the long term but I've had the driver running for several hours without problems so far.
genodeftest
I compile a number of wifi modules for the Raspberry Pi kernel Raspbian including the mt7612 driver.
I am compiling the drivers on a Pi 3B. The other drivers I compile, 8188eu, 8192eu, 8812/21au and mt7610 compile and run OK after being patched for kernel 4.14. Just the mt7612 is causing issues. All the drivers including the mt7612 compile and run OK on Raspbian kernels 3.18, 4.0, 4.1, 4.4 and 4.9.
Raspbian is being updated to kernel 4.14 and I can no longer get the mt7612 driver to operate, although it compiles, as there are several warnings and the final one stops the driver loading and running.
The final warning when the module is created shows
I have hunted about on the internet and on github to see if I could find a fix for it but have not been able to.
I find the issue rather odd as although the two values are said to be undefined there is no warning while the file they appear in, os/linux/rt_linux.c, is being compiled.
When trying to load the driver I get the following error
and in dmesg
These errors appear to look like the two unknown symbols are being treated as though they are module addresses which seems totally wrong.
Full compiler output