On Monday 12 February 2018 20:48:47 Luca Coelho wrote:
> On Tue, 2018-01-30 at 20:49 +0100, Pali Rohár wrote:
> > Hello,
>
> Hi Pali,
>
>
> > for almost 3 years I have a problem with Intel wifi card Centrino
> > Advanced-N 6235. Its firmware periodically
Hello,
for almost 3 years I have a problem with Intel wifi card Centrino
Advanced-N 6235. Its firmware periodically crash and in dmesg I'm seeing
a message "Microcode SW error detected".
Problem happens independently of kernel versions (I tried 3.8, 3.13,
3.18, 4.0, 4.9). Currently I'm using
On Friday 05 January 2018 02:45:10 Luis R. Rodriguez wrote:
> On Tue, Jan 02, 2018 at 08:23:45PM +0100, Pali Rohár wrote:
> > On Friday 10 November 2017 00:38:22 Pali Rohár wrote:
> > > This patch series fix processing MAC address for wl1251 chip found in
> > > Nokia
On Friday 10 November 2017 00:38:22 Pali Rohár wrote:
> This patch series fix processing MAC address for wl1251 chip found in Nokia
> N900.
>
> Changes since v1:
> * Added Acked-by for Pavel Machek
> * Fixed grammar
> * Magic numbers for NVS offsets are replaced by defines
&
On Friday 10 November 2017 21:26:01 Luis R. Rodriguez wrote:
> On Fri, Nov 10, 2017 at 12:38:27AM +0100, Pali Rohár wrote:
> > This function works pretty much like request_firmware(), but it prefer
> > usermode helper. If usermode helper fails then it fallback to direct
>
of patches as Pavel requested
Pali Rohár (6):
wl1251: Update wl->nvs_len after wl->nvs is valid
wl1251: Generate random MAC address only if driver does not have
valid
wl1251: Parse and use MAC address from supplied NVS data
wl1251: Set generated MAC address back to NVS data
firmwar
.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
Acked-by: Pavel Machek <pa...@ucw.cz>
---
drivers/net/wireless/ti/wl1251/main.c | 27 ++-
1 file changed, 18 insertions(+), 9 deletions(-)
diff --git a/drivers/net/wireless/ti/wl1251/main.c
b/drivers/net/wirele
If kmemdup fails, then wl->nvs_len will contain invalid non-zero size.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
Acked-by: Pavel Machek <pa...@ucw.cz>
---
drivers/net/wireless/ti/wl1251/main.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drive
This function works pretty much like request_firmware(), but it prefer
usermode helper. If usermode helper fails then it fallback to direct
access. Useful for dynamic or model specific firmware data.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
drivers/base/firmware_class.c
wl1251
correct mac address since beginning of chip usage.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
drivers/net/wireless/ti/wl1251/main.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/net/wireless/ti/wl1251/main.c
b/drivers/net/wireless/ti/wl1251/
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
drivers/net/wireless/ti/wl1251/Kconfig |1 +
drivers/net/wireless/ti/wl1251/main.c |2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ti/wl1251/Kconfig
b/drivers/net/wireless/ti/wl1251/Kconfig
index
-firmware repository,
contains MAC address 00:00:20:07:03:09. So this MAC address is marked as
invalid as it is not real device specific address, just example one.
Format of calibration NVS data can be found at:
http://notaz.gp2x.de/misc/pnd/wl1251/nvs_map.txt
Signed-off-by: Pali Rohár <pali
On Wednesday 17 May 2017 15:04:50 Johannes Berg wrote:
> On Wed, 2017-05-17 at 14:53 +0200, Pali Rohár wrote:
>
> > > In fact, why should the *driver* care either? IOW - why should
> > > "request_firmware_prefer_user()" even exist?
> >
> > There
ld generate some (random?).
So kernel driver should get NVS calibration data from userspace (which
know how where to get or how to prepare them) and in case userspace do
not have it, then we can try fallback to those example data (as people
reported us they can be useful instead of non-working WIFI
On Tuesday 31 January 2017 07:59:18 Tony Lindgren wrote:
> * Kalle Valo <kv...@codeaurora.org> [170130 22:36]:
> > Tony Lindgren <t...@atomide.com> writes:
> >
> > > * Pavel Machek <pa...@ucw.cz> [170127 11:41]:
> > >> On Fri 2017-01-27 17
On Monday 30 January 2017 18:53:09 Tony Lindgren wrote:
> * Pavel Machek <pa...@ucw.cz> [170127 11:41]:
> > On Fri 2017-01-27 17:23:07, Kalle Valo wrote:
> > > Pali Rohár <pali.ro...@gmail.com> writes:
> > > > On Friday 27 January 2017 14:26:22 Kall
On Friday 27 January 2017 17:23:07 Kalle Valo wrote:
> Pali Rohár <pali.ro...@gmail.com> writes:
>
> > On Friday 27 January 2017 14:26:22 Kalle Valo wrote:
> >> Pali Rohár <pali.ro...@gmail.com> writes:
> >>
> >> > 2) It was already
On Friday 27 January 2017 13:53:28 Arend Van Spriel wrote:
> On 27-1-2017 13:26, Kalle Valo wrote:
> > Pali Rohár <pali.ro...@gmail.com> writes:
> >
> >> On Friday 27 January 2017 13:49:03 Kalle Valo wrote:
> >>> Pali Rohár <pali.ro...@gmail.com>
On Friday 27 January 2017 14:26:22 Kalle Valo wrote:
> Pali Rohár <pali.ro...@gmail.com> writes:
>
> > On Friday 27 January 2017 13:49:03 Kalle Valo wrote:
> >> Pali Rohár <pali.ro...@gmail.com> writes:
> >>
> >> >> So
> >> >&g
On Friday 27 January 2017 13:49:03 Kalle Valo wrote:
> Pali Rohár <pali.ro...@gmail.com> writes:
>
> >> So
> >> for those other platforms there will be a delay waiting for user-mode
> >> helper to fail, before trying to get n
On Friday 27 January 2017 11:19:25 Arend Van Spriel wrote:
> On 27-1-2017 11:10, Pali Rohár wrote:
> > On Friday 27 January 2017 11:05:32 Arend Van Spriel wrote:
> >> On 27-1-2017 10:43, Pali Rohár wrote:
> >>> On Friday 27 January 2017 09:33:40 Kalle Valo wro
On Friday 27 January 2017 11:05:32 Arend Van Spriel wrote:
> On 27-1-2017 10:43, Pali Rohár wrote:
> > On Friday 27 January 2017 09:33:40 Kalle Valo wrote:
> >> Pali Rohár <pali.ro...@gmail.com> writes:
> >>
> >>> NVS calibration data fo
On Friday 27 January 2017 09:56:09 Kalle Valo wrote:
> Pali Rohár <pali.ro...@gmail.com> writes:
>
> > In case there is no valid MAC address kernel generates random one. This
> > patch propagate this generated MAC address back to NVS data which will be
> > upload
On Friday 27 January 2017 09:33:40 Kalle Valo wrote:
> Pali Rohár <pali.ro...@gmail.com> writes:
>
> > NVS calibration data for wl1251 are model specific. Every one device with
> > wl1251 chip has different and calibrated in factory.
> >
> > Not al
251, but for instance have no
> > > userspace helper the request to userspace will fail (after 60
> > > sec?) and try VFS after that. Maybe not so nice.
> >
> > Currently support for those devices is broken (like for N900) as
> > without proper NVS data they do not work correctly...
>
> Is it expected to work at all, perhaps with degraded performance /
> range? Because it seems to work for me.
Yes, some degraded performance or problems with connecting is expected.
And random MAC address at every boot. Plus some regulatory problems in
FCC countries.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Sunday 25 December 2016 21:15:40 Arend Van Spriel wrote:
> On 24-12-2016 17:52, Pali Rohár wrote:
> > NVS calibration data for wl1251 are model specific. Every one
> > device with wl1251 chip has different and calibrated in factory.
> >
> > Not all wl1251
VAL;
>
> You have two copies of these. Does it make sense to move it to helper
> function?
I'm thinking if checks is really needed. But probably moving it to
separate function is good idea.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Saturday 24 December 2016 19:14:21 Pavel Machek wrote:
> On Sat 2016-12-24 17:53:00, Pali Rohár wrote:
> > @@ -1581,10 +1598,16 @@ int wl1251_init_ieee80211(struct wl1251
> > *wl)
> >
> > wl->hw->queues = 4;
> >
> > + if (wl->nvs =
On Saturday 24 December 2016 19:08:54 Pavel Machek wrote:
> On Sat 2016-12-24 17:52:59, Pali Rohár wrote:
> > Before this patch driver generated random MAC address every time
> > when was doing initialization. And after that random MAC address
> > could be overwritten with
address.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
drivers/net/wireless/ti/wl1251/main.c | 27 ++-
1 file changed, 18 insertions(+), 9 deletions(-)
diff --git a/drivers/net/wireless/ti/wl1251/main.c
b/drivers/net/wireless/ti/wl1251/main.c
index 8971b64..c
In case there is no valid MAC address kernel generates random one. This
patch propagate this generated MAC address back to NVS data which will be
uploaded to wl1251 chip. So HW would have same MAC address as linux kernel
uses.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
drive
-firmware repository and
contains MAC address 00:00:20:07:03:09. So this MAC address is marked as
invalid as it is not real device specific address, just example one.
Format of calibration NVS data can be found at:
http://notaz.gp2x.de/misc/pnd/wl1251/nvs_map.txt
Signed-off-by: Pali Rohár <pali
This function works pretty much like request_firmware(), but it prefer
usermode helper. If usermode helper fails then it fallback to direct
access. Useful for dynamic or model specific firmware data.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
drivers/base/firmware_class.c
This patch series fix processing MAC address for wl1251 chip found in Nokia
N900.
Pali Rohár (6):
firmware: Add request_firmware_prefer_user() function
wl1251: Use request_firmware_prefer_user() for loading NVS
calibration data
wl1251: Update wl->nvs_len after wl->nvs is valid
In case kmemdup fails thne wl->nvs_len will contains invalid non-zero size.
This patch fixes it.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
drivers/net/wireless/ti/wl1251/main.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/
Nokia key/value format for nand
devices.
With this patch it is finally possible to load correct model specific NVS
calibration data for Nokia N900.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
drivers/net/wireless/ti/wl1251/Kconfig |1 +
drivers/net/wireless/ti/wl1251/main.c |
On Saturday 17 December 2016 12:14:50 Pali Rohár wrote:
> I will try to play with driver if it is really truth!
>
> I already looked into original TI's multiplatform HAL driver for
> wl1251 chip (big mess) and found there that there is wl1251 command
> to read mac address from
On Tuesday 20 December 2016 17:56:58 Tony Lindgren wrote:
> * Kalle Valo <kv...@codeaurora.org> [161220 03:47]:
> > Arend Van Spriel <arend.vanspr...@broadcom.com> writes:
> > > On 18-12-2016 13:09, Pali Rohár wrote:
> > >> File wl1251-nvs
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 wro
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 "fallbac
> On Sat, Dec 17, 2016 at 12:14:50PM +0100, Pali Rohár wrote:
> > > [1] http://notaz.gp2x.de/misc/pnd/wl1251/nvs_map.txt
> > In that description is something about STA mac address:
> >
019 02 //length
> > 01a 6d //STA_ADDR
On Saturday 17 December 2016 10:37:05 Sebastian Reichel wrote:
> Hi,
>
> On Fri, Dec 16, 2016 at 12:01:48PM +0100, Pali Rohár wrote:
> > Hi! Do you know format of wl1251 NVS calibration data file?
> >
> > I found that there is tool for changing NVS file for wl1
Resending email to new Gery's address...
On Friday 16 December 2016 12:01:48 Pali Rohár wrote:
> Hi! Do you know format of wl1251 NVS calibration data file?
>
> I found that there is tool for changing NVS file for wl1271 and newer
> chips (so not for wl1251!) at: https://github.com/
or not.
Default wl1251 NVS calibration file is available in linux-firmware:
https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ti-connectivity/wl1251-nvs.bin
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
on for this project is the get movement back in
> stuck discussion on the firmware loader API. Luis was very busy
> writing up all the details on the current situation and purely from
> the amount of documentation need to describe the API you can tell
> something is awry.
>
> Thanks,
> Daniel
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Friday 16 December 2016 03:03:19 Luis R. Rodriguez wrote:
> On Thu, Dec 15, 2016 at 2:12 PM, Arend Van Spriel
>
> <arend.vanspr...@broadcom.com> wrote:
> > On 15-12-2016 16:33, Pali Rohár wrote:
> >> On Thu Dec 15 09:18:44 2016 Kalle Valo <kv...@codeaurora.or
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 <kv...@codeaurora.org> wrote:
> >> (Adding Luis because he has been working on request_firmware()
> >> latel
On Thu Dec 15 09:18:44 2016 Kalle Valo <kv...@codeaurora.org> wrote:
> (Adding Luis because he has been working on request_firmware() lately)
>
> Pali Rohár <pali.ro...@gmail.com> writes:
>
> > > > So no, there is no argument against... request_firmware() in
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.
> &
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:
> &g
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:
> &g
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 h
ave
permanent mac address assigned.
We should assign permanent mac address before wlan0 of wl1251 is
registered into system.
--
Pali Rohár
pali.ro...@gmail.com
orary 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 sure here... Above ioctl ↑↑↑ is for changing temporary mac
address. But here we do not want to change permane
On Tuesday 22 November 2016 17:14:28 Michal Kazior wrote:
> On 22 November 2016 at 16:31, Pali Rohár <pali.ro...@gmail.com> wrote:
> > On Tuesday 22 November 2016 16:22:57 Michal Kazior wrote:
> >> On 21 November 2016 at 16:51, Pali Rohár <pali.ro...@gmail.com>
&
On Tuesday 22 November 2016 16:22:57 Michal Kazior wrote:
> On 21 November 2016 at 16:51, Pali Rohár <pali.ro...@gmail.com> 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
> &g
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 partitio
e again stored
in proprietary format and I can write userspace parser for it.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Wednesday 06 April 2016 13:30:22 Machani, Yaniv wrote:
> On Mon, Apr 04, 2016 at 15:39:44, Pali Rohár wrote:
> > > In linux-firmware repository [1] is missing AP firmware for TI
> > > wl1251 chip. There is only STA firmware wl1251-fw.bin which
> > > sup
On Sunday 20 March 2016 00:40:25 Pali Rohár wrote:
> Hi!
>
> In linux-firmware repository [1] is missing AP firmware for TI wl1251
> chip. There is only STA firmware wl1251-fw.bin which supports managed
> and ad-hoc modes.
>
> For other TI wilink chips there are -
On Monday 21 March 2016 12:35:32 Kalle Valo wrote:
> Pali Rohár <pali.ro...@gmail.com> writes:
>
> > In linux-firmware repository [1] is missing AP firmware for TI wl1251
> > chip. There is only STA firmware wl1251-fw.bin which supports managed
> > and ad-hoc mode
this pull request [2].
[1] -
https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ti-connectivity
[2] - http://thread.gmane.org/gmane.linux.kernel/1566500/focus=1571382
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Thursday 21 January 2016 15:48:14 Kalle Valo wrote:
> Pali Rohár <pali.ro...@gmail.com> writes:
>
> > On Thursday 14 January 2016 10:16:54 Pavel Machek wrote:
> >> On Wed 2016-01-13 23:32:47, Arend van Spriel wrote:
> >> > On 12/26/2015 12:45 PM, Pali Roh
On Thursday 14 January 2016 10:16:54 Pavel Machek wrote:
> On Wed 2016-01-13 23:32:47, Arend van Spriel wrote:
> > On 12/26/2015 12:45 PM, Pali Rohár wrote:
> > >Port the bt_coex_mode sysfs interface from wl1251 driver version included
> > >in the Maemo Fremantle ker
.
Signed-off-by: David Gnedt <david.gn...@davizone.at>
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
I'm resending this patch for review again as after two years there is no
nl80211 interface for bt coex and wl1251 on Nokia N900 needs it. Once
there will be common interface for b
for crypto DT stuff I already sent.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Monday 16 March 2015 22:01:43 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150316 13:59]:
On Monday 16 March 2015 16:29:39 Tony Lindgren wrote:
I believe the last pending issues is the support for
ATAG_REVISION in device tree mode as posted by Pali.
No. In DT boot
!
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
will be there again, userspace can provide
data).
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Monday 08 December 2014 21:57:21 Greg Kroah-Hartman wrote:
On Mon, Dec 08, 2014 at 05:47:30PM +0100, Pali Rohár wrote:
On Monday 08 December 2014 17:37:14 Greg Kroah-Hartman wrote:
On Mon, Dec 08, 2014 at 11:18:18PM +0800, Ming Lei wrote:
On Sat, Dec 6, 2014 at 9:02 PM, Pali Rohár
On Monday 08 December 2014 23:51:07 Dan Williams wrote:
Is the CAL data format generic to all wl1251 devices? Or is
the stuff in the CAL partition Nokia-specific?
Specific for Nokia devices.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message
On Tuesday 09 December 2014 00:42:17 Dan Williams wrote:
On Tue, 2014-12-09 at 00:23 +0100, Pali Rohár wrote:
On Monday 08 December 2014 23:51:07 Dan Williams wrote:
Is the CAL data format generic to all wl1251 devices? Or
is the stuff in the CAL partition Nokia-specific?
Specific
On Saturday 06 December 2014 13:49:54 Pavel Machek wrote:
On Thu 2014-11-27 07:58:40, Greg Kroah-Hartman wrote:
On Thu, Nov 27, 2014 at 04:22:58PM +0100, Pali Rohár wrote:
On Thursday 27 November 2014 16:16:55 Greg Kroah-Hartman wrote:
On Thu, Nov 27, 2014 at 03:43:23PM +0100, Pali Rohár
to use model specific data and if it fails
for some reasons then fallback to reading genetic data.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Thursday 27 November 2014 15:21:44 Ming Lei wrote:
On Thu, Nov 27, 2014 at 10:06 PM, Pali Rohár
pali.ro...@gmail.com wrote:
Hello,
wifi driver wl1251 needs NVS calibration data for working.
These data are loaded by driver via request_firmware from
userspace file: ti-connectivity
On Thursday 27 November 2014 16:16:55 Greg Kroah-Hartman wrote:
On Thu, Nov 27, 2014 at 03:43:23PM +0100, Pali Rohár wrote:
On Thursday 27 November 2014 15:21:44 Ming Lei wrote:
On Thu, Nov 27, 2014 at 10:06 PM, Pali Rohár
pali.ro...@gmail.com wrote:
Hello,
wifi driver
On Thursday 27 November 2014 16:14:48 Greg Kroah-Hartman wrote:
On Thu, Nov 27, 2014 at 03:43:23PM +0100, Pali Rohár wrote:
Which userspace helper programs for (automatic) firmware
loading are used? Can be udev configured to use own program
for loading firmware instead that udev integrated
77 matches
Mail list logo
