Re: wl1251 & mac address & calibration data

Hi! > >> But overwriting that one file is not possible as it next update of > >> linux-firmware package will overwrite it back. It break any normal usage > >> of package management. > >> > >> Also it is ridiculously broken by design if some "boot" files needs to > >> be overwritten to

Re: wl1251 & mac address & calibration data

* Kalle Valo [161220 09:12]: > Tony Lindgren writes: > > > * Kalle Valo [161220 03:47]: > >> Arend Van Spriel writes: > >> > >> > On 18-12-2016 13:09, Pali Rohár wrote: > >> > > >> >> File

Re: wl1251 & mac address & calibration data

Tony Lindgren writes: > * Kalle Valo [161220 03:47]: >> Arend Van Spriel writes: >> >> > On 18-12-2016 13:09, Pali Rohár wrote: >> > >> >> File wl1251-nvs.bin is provided by linux-firmware package and contains >> >>

Re: wl1251 & mac address & calibration data

On Tuesday 20 December 2016 17:56:58 Tony Lindgren wrote: > * Kalle Valo [161220 03:47]: > > Arend Van Spriel writes: > > > On 18-12-2016 13:09, Pali Rohár wrote: > > >> File wl1251-nvs.bin is provided by linux-firmware package and > > >>

Re: wl1251 & mac address & calibration data

* Kalle Valo [161220 03:47]: > Arend Van Spriel writes: > > > On 18-12-2016 13:09, Pali Rohár wrote: > > > >> File wl1251-nvs.bin is provided by linux-firmware package and contains > >> default data which should be overriden by model specific

Re: wl1251 & mac address & calibration data

Arend Van Spriel writes: > On 18-12-2016 13:09, Pali Rohár wrote: > >> File wl1251-nvs.bin is provided by linux-firmware package and contains >> default data which should be overriden by model specific calibrated >> data. > > Ah. Someone thought it was a good idea

Re: wl1251 & mac address & calibration data

On 18-12-2016 13:09, Pali Rohár wrote: > On Sunday 18 December 2016 12:54:00 Arend Van Spriel wrote: >> On 18-12-2016 12:04, Pali Rohár wrote: >>> On Sunday 18 December 2016 11:49:53 Arend Van Spriel wrote: On 16-12-2016 11:40, Pali Rohár wrote: > On Friday 16 December 2016 08:25:44

Re: wl1251 & mac address & calibration data

On Sunday 18 December 2016 12:54:00 Arend Van Spriel wrote: > On 18-12-2016 12:04, Pali Rohár wrote: > > On Sunday 18 December 2016 11:49:53 Arend Van Spriel wrote: > >> On 16-12-2016 11:40, Pali Rohár wrote: > >>> On Friday 16 December 2016 08:25:44 Daniel Wagner wrote: > On 12/16/2016 03:03

Re: wl1251 & mac address & calibration data

On 18-12-2016 12:04, Pali Rohár wrote: > On Sunday 18 December 2016 11:49:53 Arend Van Spriel wrote: >> On 16-12-2016 11:40, Pali Rohár wrote: >>> On Friday 16 December 2016 08:25:44 Daniel Wagner wrote: On 12/16/2016 03:03 AM, Luis R. Rodriguez wrote: > For the new API a solution for

Re: wl1251 & mac address & calibration data

On Sunday 18 December 2016 11:49:53 Arend Van Spriel wrote: > On 16-12-2016 11:40, Pali Rohár wrote: > > On Friday 16 December 2016 08:25:44 Daniel Wagner wrote: > >> On 12/16/2016 03:03 AM, Luis R. Rodriguez wrote: > >>> For the new API a solution for "fallback mechanisms" should be > >>> clean

Re: wl1251 & mac address & calibration data

On 16-12-2016 11:40, Pali Rohár wrote: > On Friday 16 December 2016 08:25:44 Daniel Wagner wrote: >> On 12/16/2016 03:03 AM, Luis R. Rodriguez wrote: >>> For the new API a solution for "fallback mechanisms" should be >>> clean though and I am looking to stay as far as possible from the >>>

Re: wl1251 & mac address & calibration data

On Friday 16 December 2016 08:25:44 Daniel Wagner wrote: > On 12/16/2016 03:03 AM, Luis R. Rodriguez wrote: > > For the new API a solution for "fallback mechanisms" should be > > clean though and I am looking to stay as far as possible from the > > existing mess. A solution to help both the old

Re: wl1251 & mac address & calibration data

On Friday 16 December 2016 03:03:19 Luis R. Rodriguez wrote: > On Thu, Dec 15, 2016 at 2:12 PM, Arend Van Spriel > > wrote: > > On 15-12-2016 16:33, Pali Rohár wrote: > >> On Thu Dec 15 09:18:44 2016 Kalle Valo > >> wrote: > >>> (Adding Luis

Re: wl1251 & mac address & calibration data

On Thursday 15 December 2016 21:12:47 Arend Van Spriel wrote: > On 15-12-2016 16:33, Pali Rohár wrote: > > On Thu Dec 15 09:18:44 2016 Kalle Valo wrote: > >> (Adding Luis because he has been working on request_firmware() > >> lately) > >> > >> Pali Rohár

Re: wl1251 & mac address & calibration data

On 12/16/2016 03:03 AM, Luis R. Rodriguez wrote: For the new API a solution for "fallback mechanisms" should be clean though and I am looking to stay as far as possible from the existing mess. A solution to help both the old API and new API is possible for the "fallback mechanism" though -- but

Re: wl1251 & mac address & calibration data

On Thu, Dec 15, 2016 at 2:12 PM, Arend Van Spriel wrote: > On 15-12-2016 16:33, Pali Rohár wrote: >> On Thu Dec 15 09:18:44 2016 Kalle Valo wrote: >>> (Adding Luis because he has been working on request_firmware() lately) >>> >>> Pali Rohár

Re: wl1251 & mac address & calibration data

On 15-12-2016 16:33, Pali Rohár wrote: > On Thu Dec 15 09:18:44 2016 Kalle Valo wrote: >> (Adding Luis because he has been working on request_firmware() lately) >> >> Pali Rohár writes: >> > So no, there is no argument against... request_firmware()

Re: wl1251 & mac address & calibration data

On Thu Dec 15 09:18:44 2016 Kalle Valo wrote: > (Adding Luis because he has been working on request_firmware() lately) > > Pali Rohár writes: > > > > > So no, there is no argument against... request_firmware() in > > > > fallback mode with userspace

Re: wl1251 & mac address & calibration data

(Adding Luis because he has been working on request_firmware() lately) Pali Rohár writes: >> > So no, there is no argument against... request_firmware() in >> > fallback mode with userspace helper is by design blocking and >> > waiting for userspace. But waiting for some

Re: wl1251 & mac address & calibration data

On Thursday 24 November 2016 19:46:01 Aaro Koskinen wrote: > Hi, > > On Thu, Nov 24, 2016 at 04:20:45PM +0100, Pali Rohár wrote: > > Proprietary, signed and closed bootloader NOLO does not support DT. > > So for booting you need to append DTS file to kernel image. > > > > U-Boot is optional and

Re: wl1251 & mac address & calibration data

On Thu 2016-11-24 20:46:01, Aaro Koskinen wrote: > Hi, > > On Thu, Nov 24, 2016 at 04:20:45PM +0100, Pali Rohár wrote: > > Proprietary, signed and closed bootloader NOLO does not support DT. So > > for booting you need to append DTS file to kernel image. > > > > U-Boot is optional and can be

Re: wl1251 & mac address & calibration data

Hi, On Thu, Nov 24, 2016 at 04:20:45PM +0100, Pali Rohár wrote: > Proprietary, signed and closed bootloader NOLO does not support DT. So > for booting you need to append DTS file to kernel image. > > U-Boot is optional and can be used as intermediate bootloader between > NOLO and kernel. But

Re: wl1251 & mac address & calibration data

On Thursday 24 November 2016 19:11:39 Sebastian Reichel wrote: > Hi, > > On Thu, Nov 24, 2016 at 05:49:33PM +0100, Pali Rohár wrote: > > On Thursday 24 November 2016 17:08:30 Sebastian Reichel wrote: > > > On Thu, Nov 24, 2016 at 04:20:45PM +0100, Pali Rohár wrote: > > > > On Thursday 24 November

Re: wl1251 & mac address & calibration data

Hi, On Thu, Nov 24, 2016 at 05:49:33PM +0100, Pali Rohár wrote: > On Thursday 24 November 2016 17:08:30 Sebastian Reichel wrote: > > On Thu, Nov 24, 2016 at 04:20:45PM +0100, Pali Rohár wrote: > > > On Thursday 24 November 2016 16:13:17 Sebastian Reichel wrote: > > > > On Thu, Nov 24, 2016 at

Re: wl1251 & mac address & calibration data

On Thursday 24 November 2016 17:08:30 Sebastian Reichel wrote: > Hi, > > On Thu, Nov 24, 2016 at 04:20:45PM +0100, Pali Rohár wrote: > > On Thursday 24 November 2016 16:13:17 Sebastian Reichel wrote: > > > On Thu, Nov 24, 2016 at 09:33:29AM +0100, Pali Rohár wrote: > > > > On Thursday 24 November

Re: wl1251 & mac address & calibration data

Hi, On Thu, Nov 24, 2016 at 04:20:45PM +0100, Pali Rohár wrote: > On Thursday 24 November 2016 16:13:17 Sebastian Reichel wrote: > > On Thu, Nov 24, 2016 at 09:33:29AM +0100, Pali Rohár wrote: > > > On Thursday 24 November 2016 08:51:04 Pavel Machek wrote: > > > > > > "ifconfig hw ether XX"

Re: wl1251 & mac address & calibration data

Hi, On 24.11.2016 17:20, Pali Rohár wrote: In case when wl1251 is statically linked into kernel image, it is loaded and initialized before even userspace applications starts. Which leaves no option, but integrating libcal into kernel :). Ivo

Re: wl1251 & mac address & calibration data

On Thursday 24 November 2016 16:13:17 Sebastian Reichel wrote: > Hi, > > On Thu, Nov 24, 2016 at 09:33:29AM +0100, Pali Rohár wrote: > > On Thursday 24 November 2016 08:51:04 Pavel Machek wrote: > > > Hi! > > > > > > > > "ifconfig hw ether XX" normally sets the address. I guess that's > > > > >

Re: wl1251 & mac address & calibration data

On Thursday 24 November 2016 08:51:04 Pavel Machek wrote: > Hi! > > > > "ifconfig hw ether XX" normally sets the address. I guess that's > > > ioctl? > > > > This sets temporary address and it is ioctl. IIRC same as what ethtool > > uses. (ifconfig is already deprecated). > > > > > And I guess

Re: wl1251 & mac address & calibration data

Hi! > > "ifconfig hw ether XX" normally sets the address. I guess that's > > ioctl? > > This sets temporary address and it is ioctl. IIRC same as what ethtool > uses. (ifconfig is already deprecated). > > > And I guess we should use similar mechanism for permanent > > address. > > I'm not

Re: wl1251 & mac address & calibration data

On Wednesday 23 November 2016 23:23:35 Pavel Machek wrote: > 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

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... > > >

Re: wl1251 & mac address & calibration data

On 22-11-2016 18:05, Pali Rohár wrote: > On Tuesday 22 November 2016 17:14:28 Michal Kazior wrote: >> On 22 November 2016 at 16:31, Pali Rohár wrote: >>> On Tuesday 22 November 2016 16:22:57 Michal Kazior wrote: On 21 November 2016 at 16:51, Pali Rohár

Re: wl1251 & mac address & calibration data

On Tuesday 22 November 2016 17:14:28 Michal Kazior wrote: > On 22 November 2016 at 16:31, Pali Rohár wrote: > > On Tuesday 22 November 2016 16:22:57 Michal Kazior wrote: > >> On 21 November 2016 at 16:51, Pali Rohár > >> wrote: > >> > On Friday 11

Re: wl1251 & mac address & calibration data

On 22 November 2016 at 16:31, Pali Rohár wrote: > On Tuesday 22 November 2016 16:22:57 Michal Kazior wrote: >> On 21 November 2016 at 16:51, Pali Rohár wrote: >> > On Friday 11 November 2016 18:20:50 Pali Rohár wrote: >> >> Hi! I will open discussion

Re: wl1251 & mac address & calibration data

On Tuesday 22 November 2016 16:22:57 Michal Kazior wrote: > On 21 November 2016 at 16:51, Pali Rohár wrote: > > On Friday 11 November 2016 18:20:50 Pali Rohár wrote: > >> Hi! I will open discussion about mac address and calibration data for > >> wl1251 wireless chip again...

Re: wl1251 & mac address & calibration data

On 21 November 2016 at 16:51, Pali Rohár wrote: > On Friday 11 November 2016 18:20:50 Pali Rohár wrote: >> Hi! I will open discussion about mac address and calibration data for >> wl1251 wireless chip again... >> >> Problem: Mac address & calibration data for wl1251 chip on

Re: wl1251 & mac address & calibration data

On Friday 11 November 2016 18:20:50 Pali Rohár wrote: > Hi! I will open discussion about mac address and calibration data for > wl1251 wireless chip again... > > Problem: Mac address & calibration data for wl1251 chip on Nokia N900 > are stored on second nand partition (mtd1) in special