Messages in this thread | | | Date | Wed, 23 Nov 2016 23:23:35 +0100 | From | Pavel Machek <> | Subject | Re: wl1251 & mac address & calibration data |
| |
Hi!
> > > As wl1251.ko does not accept mac_address as module parameter, such > > > modprobe hook does not help -- as there is absolutely no way from > > > userspace to set or change (permanent) mac address. > > > > Quoting modprobe.d manual: > > > install modulename command... > > > > > > This command instructs modprobe to run your > > > command instead of inserting the module in the > > > kernel as normal. The command can be any shell > > > command: this allows you to do any kind of > > > complex processing you might wish. [...] > > I know. But this do not allow me to send mac address to kernel -- as > kernel does not support such command yet (reason for my first > question).
Plus, this does not really work for cases where wl1251 is not a module.
> > You can hook up a script that cooks up wl1251-nvs.bin (caldata, > > macaddr) and then insmod the actual wl1251.ko module. Or you can just > > cook up the nvs on first device boot and store it in /lib/firmware > > (possibly overwriting the "generic" wl1251 from linux-firmware). > > This is what I would like to prevent -- overwriting (possible readonly) > system files with some device specific. It is really bad idea!
Agreed.
"ifconfig hw ether XX" normally sets the address. I guess that's ioctl? And I guess we should use similar mechanism for permanent address.
Best regards,
Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html [unhandled content-type:application/pgp-signature] | |