Skip to contentSkip to conversation

Compat-wireless N900

DISCUSSION George 6 participants 26 messages Oct 14, 2010 – Oct 25, 2010

lore
Share & tools
lore

George

author
#0 lore raw

Hi all,

I'm trying to use compat-wireless to upgrade my n900 wireless driver. N900 is using WL1251 wireless driver and the omap1 kernel version used it 2.6.28.

The issue is that 2.6.28 does not have implemented many issues for nl80211 netlink family which I wanted to test on my n900.

I have recompiled the kernel to make cfg80211 and mac80211 modules, so I can use compat-wireless. After that I have compiled compat-wireless by selecting the driver family I need. All done under scratchbox.

# scripts/driver-select wl12xx
# make KLIB=/lib/modules/2.6.28-myversion \
   KMODPATH_ARG=/lib/modules/2.6.28-myversion
# make  KLIB=/lib/modules/2.6.28-myversion \
   KMODPATH_ARG=/lib/modules/2.6.28-myversion install

After that I have installed the new kernel and the drivers in the n900 and the system starts. uname -a reports I'm using my custom kernel.

The problem is that the wireless modules are not working as expected and I cannot get access to my wifi networks. Actually bluetooth is not working as well, as far as I have tested.

dmesg reports --> http://pastebin.com/xskKcGnE

I have hightlighted the lines that seems to be reflecting what is not working. So it seems that on startup it is trying to upload the former wl12xx.ko module. Then I decided to manually upload the new modules to check them out.

$ sudo gainroot
# modprobe wl1251_spi
# ifconfig -a
---- no wlan0 iface ----
# iwconfig
---- no wireless devices ----

I have also tried with wl1251_sdio driver but I have the same problem. dmesg doesn't report any error while uploading these drivers, but I don't know why not a new wireless interface is not created.

BTW, the firmware is in /lib/modules/firmware so it is in a place that can be found. Do I have to change something?

What files do I need to reconfigure as to get the kernel to point to the correct driver upon booting? How do I create a new wireless interface if the driver is uploaded properly but the interface is not created? Any other issue that you find I'm not doing correctly?

Any help is welcome.

Regards,
George

#1 lore raw
Quoted 19 lines · George

Hi all,

I'm trying to use compat-wireless to upgrade my n900 wireless driver. N900 is using WL1251 wireless driver and the omap1 kernel version used it 2.6.28.

The issue is that 2.6.28 does not have implemented many issues for nl80211 netlink family which I wanted to test on my n900.

I have recompiled the kernel to make cfg80211 and mac80211 modules, so I can use compat-wireless. After that I have compiled compat-wireless by selecting the driver family I need. All done under scratchbox.

# scripts/driver-select wl12xx
# make KLIB=/lib/modules/2.6.28-myversion \
    KMODPATH_ARG=/lib/modules/2.6.28-myversion
# make  KLIB=/lib/modules/2.6.28-myversion \
    KMODPATH_ARG=/lib/modules/2.6.28-myversion install
Quoted 8 lines

After that I have installed the new kernel and the drivers in the n900 and the system starts. uname -a reports I'm using my custom kernel.

The problem is that the wireless modules are not working as expected and I cannot get access to my wifi networks. Actually bluetooth is not working as well, as far as I have tested.

dmesg reports --> http://pastebin.com/xskKcGnE

At first sight it seem that you have some mismatch issues, Try to compile the maemo 2.6.28 kenrel without the wireless modules or replace the wireless modules by the compat-wireless ones. (normally the compat-wireless modules should take the precedence but as it seem here, it didn't work)

by the way, are you aware of the meego 2.6.35 kernel, it might not be complete yet, but may solve some of your problems.

Denis.

author
#2 lore raw
Quoted 9 lines · Denis 'GNUtoo' Carikli
Quoted 8 lines · George

Hi all,

I'm trying to use compat-wireless to upgrade my n900 wireless driver. N900 is using WL1251 wireless driver and the omap1 kernel version used it 2.6.28.

The issue is that 2.6.28 does not have implemented many issues for nl80211 netlink family which I wanted to test on my n900.

What I want is to get iw and nl80211 working properly so I can use netlink sockets to get all the information. Currently I cannot do anything as every iw command reports operation not supported.

Quoted 17 lines
Quoted 17 lines

I have recompiled the kernel to make cfg80211 and mac80211 modules, so I can use compat-wireless. After that I have compiled compat-wireless by selecting the driver family I need. All done under scratchbox.

# scripts/driver-select wl12xx
# make KLIB=/lib/modules/2.6.28-myversion \
     KMODPATH_ARG=/lib/modules/2.6.28-myversion
# make  KLIB=/lib/modules/2.6.28-myversion \
     KMODPATH_ARG=/lib/modules/2.6.28-myversion install

After that I have installed the new kernel and the drivers in the n900 and the system starts. uname -a reports I'm using my custom kernel.

The problem is that the wireless modules are not working as expected and I cannot get access to my wifi networks. Actually bluetooth is not working as well, as far as I have tested.

Quoted 6 lines
Quoted 1 line

dmesg reports --> http://pastebin.com/xskKcGnE

At first sight it seem that you have some mismatch issues, Try to compile the maemo 2.6.28 kenrel without the wireless modules or replace the wireless modules by the compat-wireless ones. (normally the compat-wireless modules should take the precedence but as it seem here, it didn't work)

If I compile the kernel withouth the wireless modules then they are not going to be recognized and compat-wireless will complain that .config that kernel was compiled without wireless.

On the other hand, what do you mean by replacing the wireless modules? just cut and paste from compat-wireless.

The issue is that 2.6.28 has nl80211, cfg80211 and mac80211 on their very stages. I think what will solve my problem is just updating those modules, but for that I have to change also the driver.

Besides that, the main problemm, as some guys pointed in the IRC channel, is that wl1251 driver is spi and they need something about the board interfaces.

Quoted 2 lines

by the way, are you aware of the meego 2.6.35 kernel, it might not be complete yet, but may solve some of your problems.

Yes I'm aware of that. I have compiled the kernel and try to load it on the n900 with maemo rootfs and ... crashes.

Actually I have meego (mmc rootfs) also running on my N900 and wireless drivers work perfect. The problem is that the gui and develepment SDK and toolchains are still underdevelopment and I cannot then use something like the maemo scratchbox.

I have compiled an small application directly on the n900 with meego, but for larger applications it is not viable.

Quoted 9 lines

Denis.

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw
In reply to Denis 'GNUtoo' Carikli
Quoted 23 lines · Denis 'GNUtoo' Carikli
Quoted 22 lines · George

Hi all,

I'm trying to use compat-wireless to upgrade my n900 wireless driver. N900 is using WL1251 wireless driver and the omap1 kernel version used it 2.6.28.

The issue is that 2.6.28 does not have implemented many issues for nl80211 netlink family which I wanted to test on my n900.

I have recompiled the kernel to make cfg80211 and mac80211 modules, so I can use compat-wireless. After that I have compiled compat-wireless by selecting the driver family I need. All done under scratchbox.

# scripts/driver-select wl12xx
# make KLIB=/lib/modules/2.6.28-myversion \
    KMODPATH_ARG=/lib/modules/2.6.28-myversion
# make  KLIB=/lib/modules/2.6.28-myversion \
    KMODPATH_ARG=/lib/modules/2.6.28-myversion install

After that I have installed the new kernel and the drivers in the n900 and the system starts. uname -a reports I'm using my custom kernel.

Quoted 6 lines
Quoted 5 lines

The problem is that the wireless modules are not working as expected and I cannot get access to my wifi networks. Actually bluetooth is not working as well, as far as I have tested.

dmesg reports --> http://pastebin.com/xskKcGnE

At first sight it seem that you have some mismatch issues,

Agreed, try:

for i in mac80211 cfg80211 wl1251_spi; do modprobe -l $i; done

This will show you where its picking up the modules upon load. If you see some disagreement with paths, that's the issue. Compat-wireless relies on stuffing them on your /lib/modules/$(uname -r)/updates/ directory and in order for these modules to take precedence over the /lib/modules/$(uname -r)/kernel/ modules we rely on a file in /etc/depmod.d/ which tells depmod to prefer updates first. For example on an ubuntu box you get:

mcgrof@tux ~ $ cat /etc/depmod.d/ubuntu.conf
search updates ubuntu built-in

Luis

author
#4 lore raw
Quoted 44 lines · Luis R. Rodriguez
Quoted 23 lines · Denis 'GNUtoo' Carikli
Quoted 22 lines · George

Hi all,

I'm trying to use compat-wireless to upgrade my n900 wireless driver. N900 is using WL1251 wireless driver and the omap1 kernel version used it 2.6.28.

The issue is that 2.6.28 does not have implemented many issues for nl80211 netlink family which I wanted to test on my n900.

I have recompiled the kernel to make cfg80211 and mac80211 modules, so I can use compat-wireless. After that I have compiled compat-wireless by selecting the driver family I need. All done under scratchbox.

# scripts/driver-select wl12xx
# make KLIB=/lib/modules/2.6.28-myversion \
     KMODPATH_ARG=/lib/modules/2.6.28-myversion
# make  KLIB=/lib/modules/2.6.28-myversion \
     KMODPATH_ARG=/lib/modules/2.6.28-myversion install

After that I have installed the new kernel and the drivers in the n900 and the system starts. uname -a reports I'm using my custom kernel.

Quoted 6 lines
Quoted 5 lines

The problem is that the wireless modules are not working as expected and I cannot get access to my wifi networks. Actually bluetooth is not working as well, as far as I have tested.

dmesg reports --> http://pastebin.com/xskKcGnE

At first sight it seem that you have some mismatch issues,

Agreed, try:

for i in mac80211 cfg80211 wl1251_spi; do modprobe -l $i; done

This will show you where its picking up the modules upon load. If you see some disagreement with paths, that's the issue. Compat-wireless relies on stuffing them on your /lib/modules/$(uname -r)/updates/ directory and in order for these modules to take precedence over the /lib/modules/$(uname -r)/kernel/ modules we rely on a file in /etc/depmod.d/ which tells depmod to prefer updates first. For example on an ubuntu box you get:

Quoted 3 lines

mcgrof@tux ~ $ cat /etc/depmod.d/ubuntu.conf
search updates ubuntu built-in

I have tried using even insmod and the modules load perfectly but the wlan device doesn't show up. In dmesg nothing is displayed except for the cfg80211 and when I rmmod the module wl1251 (wl1251: removed or similar)

I'm still wondering what the hell I have to do.

TA

#5 lore raw
Quoted 2 lines · George

I have tried using even insmod and the modules load perfectly but the wlan device doesn't show up.

Then that likely means you are not loading the right module.

Quoted 4 lines

In dmesg nothing is displayed except for the cfg80211 and when I rmmod the module wl1251 (wl1251: removed or similar)

I'm still wondering what the hell I have to do.

Are you sure you have the right module?

Luis

author
#6 lore raw
Quoted 5 lines · Luis R. Rodriguez
Quoted 2 lines · George

I have tried using even insmod and the modules load perfectly but the wlan device doesn't show up.

Quoted 8 lines

Then that likely means you are not loading the right module.

Quoted 4 lines

In dmesg nothing is displayed except for the cfg80211 and when I rmmod the module wl1251 (wl1251: removed or similar)

I'm still wondering what the hell I have to do.

Are you sure you have the right module?

Yes. The driver is the wl1251 family. As I said in previous posts and from what some guys in the IRC channel tried to guess, it seems that the problem might be in that the spi interface is specific for any device, and in the n900 might be different from the one implemented in compat-wireless.

I'm a bit suprised about this fact, but they know more than I.

TA

Quoted 6 lines

Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#7 lore raw
Quoted 14 lines · George
Quoted 13 lines · Luis R. Rodriguez
Quoted 3 lines · George

I have tried using even insmod and the modules load perfectly but the wlan
device doesn't show up.

Then that likely means you are not loading the right module.

Quoted 4 lines

In dmesg nothing is displayed except for the cfg80211 and when I rmmod the
module wl1251 (wl1251: removed or similar)

Quoted 8 lines
Quoted 3 lines
Quoted 1 line

I'm still wondering what the hell I have to do.

Are you sure you have the right module?

Yes. The driver is the wl1251 family. As I said in previous posts and from what some guys in the IRC channel tried to guess, it seems that the problem might be in that the spi interface is specific for any device, and in the n900 might be different from the one implemented in compat-wireless.

Heh, nope.

Quoted 1 line

I'm a bit suprised about this fact, but they know more than I.

Or, we had not yet accommodated yet for the fact that the wl1251 driver was split out into its own directory from the original wl12xx/ directory and no one ever sent a patch to fix this on compat-wireless. I just fixed this on today's compat-wireless, so you can try that around noon PST time when the new tarball will be generated. Ah but there are some pcmcia crap compile issues, we just have to remove pcmcia support, well not now, I have other stuff to do.

I welcome patches if someone gets to it.

Luis

author
#8 lore raw
Quoted 28 lines · Luis R. Rodriguez
Quoted 14 lines · George
Quoted 13 lines · Luis R. Rodriguez
Quoted 3 lines · George

I have tried using even insmod and the modules load perfectly but the wlan
device doesn't show up.

Then that likely means you are not loading the right module.

Quoted 4 lines

In dmesg nothing is displayed except for the cfg80211 and when I rmmod the
module wl1251 (wl1251: removed or similar)

Quoted 8 lines
Quoted 3 lines
Quoted 1 line

I'm still wondering what the hell I have to do.

Are you sure you have the right module?

Yes. The driver is the wl1251 family. As I said in previous posts and from what some guys in the IRC channel tried to guess, it seems that the problem might be in that the spi interface is specific for any device, and in the n900 might be different from the one implemented in compat-wireless.

Heh, nope.

Quoted 1 line

I'm a bit suprised about this fact, but they know more than I.

Quoted 7 lines

Or, we had not yet accommodated yet for the fact that the wl1251 driver was split out into its own directory from the original wl12xx/ directory and no one ever sent a patch to fix this on compat-wireless. I just fixed this on today's compat-wireless, so you can try that around noon PST time when the new tarball will be generated. Ah but there are some pcmcia crap compile issues, we just have to remove pcmcia support, well not now, I have other stuff to do.

Thanks for that. Tomorrow at work I will try to test it out and get back to you if something happens ;)

Quoted 1 line

I welcome patches if someone gets to it.

I'm sorry but my knowdledge of the system is from a higher level of abstraction. Otherwise I will be soooo please of helping you out.

Again. Thanks.
Jorge

Quoted 6 lines

Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

author
#9 lore raw
Quoted 30 lines · George
Quoted 29 lines · Luis R. Rodriguez
Quoted 15 lines · George
Quoted 14 lines · Luis R. Rodriguez
Quoted 2 lines · George

I have tried using even insmod and the modules load perfectly but the wlan device doesn't show up.

Then that likely means you are not loading the right module.

Quoted 4 lines

In dmesg nothing is displayed except for the cfg80211 and when I rmmod the module wl1251 (wl1251: removed or similar)

I'm still wondering what the hell I have to do.

Quoted 7 lines
Quoted 1 line

Are you sure you have the right module?

Yes. The driver is the wl1251 family. As I said in previous posts and from what some guys in the IRC channel tried to guess, it seems that the problem might be in that the spi interface is specific for any device, and in the n900 might be different from the one implemented in compat-wireless.

Heh, nope.

Quoted 1 line

I'm a bit suprised about this fact, but they know more than I.

Quoted 8 lines
Quoted 8 lines

Or, we had not yet accommodated yet for the fact that the wl1251 driver was split out into its own directory from the original wl12xx/ directory and no one ever sent a patch to fix this on compat-wireless. I just fixed this on today's compat-wireless, so you can try that around noon PST time when the new tarball will be generated. Ah but there are some pcmcia crap compile issues, we just have to remove pcmcia support, well not now, I have other stuff to do.

I have downloaded compat-wireless-2010-10-17.tar.bz2 and have compiled the code with no problem. I have seen the changes you've made creating modules wl1251, spi and sdio.

I have run modprobe spi to upload the modules (also tried sdio) and no way. dmesg doesn't include any message. Below is the one after unloading the modules and uploading them again:
rmmod spi wl1251 mac80211 cfg80211 compat_firmware_class
modprobe spi

Quoted 1 line
Quoted 1 line

wl1251: unloaded
cfg80211: Calling CRDA to update world regulatory domain

Quoted 1 line
Quoted 1 line

Below is the output for lsmod. As you can see modules are up and running, but when I execute ifconfig -a no wlan0 device shows up.

Nokia-N900:~# lsmod | grep spi
spi                     4352  0
wl1251                 75840  1 spi
mac80211              212984  2 spi,wl1251
crc7                    1216  1 spi
Nokia-N900:~# lsmod | grep compat
compat_firmware_class     8896  1 wl1251
compat                 10496  2 mac80211,cfg80211
v4l1_compat            12100  1 videodev
compat_ioctl32           832  1 fmtx_si4713
Nokia-N900:~# lsmod | grep wl12
wl1251                 75840  1 spi
compat_firmware_class     8896  1 wl1251
mac80211              212984  2 spi,wl1251
cfg80211              148904  2 wl1251,mac80211

Any help on that? Sorry but I'm somehow desesperate and don't know what to do. Actually I'm thinking on not using compat-wireless and nl80211 and get back to wireless-extensions.

CU
Jorge

Quoted 21 lines

Thanks for that. Tomorrow at work I will try to test it out and get back to you if something happens ;)

Quoted 1 line

I welcome patches if someone gets to it.

I'm sorry but my knowdledge of the system is from a higher level of abstraction. Otherwise I will be soooo please of helping you out.

Again. Thanks. Jorge

Quoted 5 lines

Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html

-- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html

#10 lore raw
Quoted 77 lines · George
Quoted 33 lines · George
Quoted 31 lines · Luis R. Rodriguez
Quoted 16 lines · George
Quoted 14 lines · Luis R. Rodriguez
Quoted 2 lines · George

I have tried using even insmod and the modules load perfectly but the wlan device doesn't show up.

Then that likely means you are not loading the right module.

Quoted 4 lines

In dmesg nothing is displayed except for the cfg80211 and when I rmmod the module wl1251 (wl1251: removed or similar)

I'm still wondering what the hell I have to do.

Quoted 7 lines
Quoted 1 line

Are you sure you have the right module?

Yes. The driver is the wl1251 family. As I said in previous posts and from what some guys in the IRC channel tried to guess, it seems that the problem might be in that the spi interface is specific for any device, and in the n900 might be different from the one implemented in compat-wireless.

Heh, nope.

Quoted 1 line

I'm a bit suprised about this fact, but they know more than I.

Quoted 8 lines
Quoted 8 lines

Or, we had not yet accommodated yet for the fact that the wl1251 driver was split out into its own directory from the original wl12xx/ directory and no one ever sent a patch to fix this on compat-wireless. I just fixed this on today's compat-wireless, so you can try that around noon PST time when the new tarball will be generated. Ah but there are some pcmcia crap compile issues, we just have to remove pcmcia support, well not now, I have other stuff to do.

I have downloaded compat-wireless-2010-10-17.tar.bz2 and have compiled the code with no problem. I have seen the changes you've made creating modules wl1251, spi and sdio.

I have run modprobe spi to upload the modules (also tried sdio) and no way. dmesg doesn't include any message. Below is the one after unloading the modules and uploading them again:
rmmod spi wl1251 mac80211 cfg80211 compat_firmware_class modprobe spi

Quoted 1 line
Quoted 1 line

wl1251: unloaded
cfg80211: Calling CRDA to update world regulatory domain

Quoted 1 line
Quoted 1 line

Below is the output for lsmod. As you can see modules are up and running, but when I execute ifconfig -a no wlan0 device shows up.

Nokia-N900:~# lsmod | grep spi
spi                     4352  0
wl1251                 75840  1 spi
mac80211              212984  2 spi,wl1251
crc7                    1216  1 spi
Nokia-N900:~# lsmod | grep compat
compat_firmware_class     8896  1 wl1251
compat                 10496  2 mac80211,cfg80211
v4l1_compat            12100  1 videodev
compat_ioctl32           832  1 fmtx_si4713
Nokia-N900:~# lsmod | grep wl12
wl1251                 75840  1 spi
compat_firmware_class     8896  1 wl1251
mac80211              212984  2 spi,wl1251
cfg80211              148904  2 wl1251,mac80211
Quoted 3 lines

Any help on that? Sorry but I'm somehow desesperate and don't know what to do. Actually I'm thinking on not using compat-wireless and nl80211 and get back to wireless-extensions.

Does your device use SDIO or SPI?

Luis

author
#11 lore raw
Quoted 78 lines · Luis R. Rodriguez
Quoted 77 lines · George
Quoted 33 lines · George
Quoted 31 lines · Luis R. Rodriguez
Quoted 16 lines · George
Quoted 14 lines · Luis R. Rodriguez
Quoted 2 lines · George

I have tried using even insmod and the modules load perfectly but the wlan device doesn't show up.

Then that likely means you are not loading the right module.

Quoted 4 lines

In dmesg nothing is displayed except for the cfg80211 and when I rmmod the module wl1251 (wl1251: removed or similar)

I'm still wondering what the hell I have to do.

Quoted 7 lines
Quoted 1 line

Are you sure you have the right module?

Yes. The driver is the wl1251 family. As I said in previous posts and from what some guys in the IRC channel tried to guess, it seems that the problem might be in that the spi interface is specific for any device, and in the n900 might be different from the one implemented in compat-wireless.

Heh, nope.

Quoted 1 line

I'm a bit suprised about this fact, but they know more than I.

Quoted 8 lines
Quoted 8 lines

Or, we had not yet accommodated yet for the fact that the wl1251 driver was split out into its own directory from the original wl12xx/ directory and no one ever sent a patch to fix this on compat-wireless. I just fixed this on today's compat-wireless, so you can try that around noon PST time when the new tarball will be generated. Ah but there are some pcmcia crap compile issues, we just have to remove pcmcia support, well not now, I have other stuff to do.

I have downloaded compat-wireless-2010-10-17.tar.bz2 and have compiled the code with no problem. I have seen the changes you've made creating modules wl1251, spi and sdio.

I have run modprobe spi to upload the modules (also tried sdio) and no way. dmesg doesn't include any message. Below is the one after unloading the modules and uploading them again:
rmmod spi wl1251 mac80211 cfg80211 compat_firmware_class modprobe spi

Quoted 1 line
Quoted 1 line

wl1251: unloaded
cfg80211: Calling CRDA to update world regulatory domain

Quoted 1 line
Quoted 1 line

Below is the output for lsmod. As you can see modules are up and running, but when I execute ifconfig -a no wlan0 device shows up.

Nokia-N900:~# lsmod | grep spi
spi                     4352  0
wl1251                 75840  1 spi
mac80211              212984  2 spi,wl1251
crc7                    1216  1 spi
Nokia-N900:~# lsmod | grep compat
compat_firmware_class     8896  1 wl1251
compat                 10496  2 mac80211,cfg80211
v4l1_compat            12100  1 videodev
compat_ioctl32           832  1 fmtx_si4713
Nokia-N900:~# lsmod | grep wl12
wl1251                 75840  1 spi
compat_firmware_class     8896  1 wl1251
mac80211              212984  2 spi,wl1251
cfg80211              148904  2 wl1251,mac80211
Quoted 7 lines
Quoted 3 lines

Any help on that? Sorry but I'm somehow desesperate and don't know what to do. Actually I'm thinking on not using compat-wireless and nl80211 and get back to wireless-extensions.

Does your device use SDIO or SPI?

Luis

I have tried both and none of them have worked.

Jorge

#12 lore raw
Quoted 4 lines · ext George
Quoted 3 lines · Luis R. Rodriguez
Quoted 3 lines

Any help on that? Sorry but I'm somehow desesperate and don't know what to do. Actually I'm thinking on not using compat-wireless and nl80211 and get back to wireless-extensions.

Getting back to wireless-extensions would certainly be a very desperate measure! :P

Quoted 5 lines
Quoted 3 lines

Does your device use SDIO or SPI?

Luis

I have tried both and none of them have worked.

On the N900 the wl1271 chip is connected via SPI.

I'll re-read this thread more carefully to see if I can spot anything that could help you.

Signature · 2 lines
Cheers,
Luca.
#13 lore raw
Quoted 12 lines · ext Luciano Coelho
Quoted 4 lines · ext George
Quoted 3 lines · Luis R. Rodriguez
Quoted 3 lines

Any help on that? Sorry but I'm somehow desesperate and don't know what to do. Actually I'm thinking on not using compat-wireless and nl80211 and get back to wireless-extensions.

Getting back to wireless-extensions would certainly be a very desperate measure! :P

Quoted 2 lines
Quoted 2 lines

Does your device use SDIO or SPI?

Quoted 8 lines
Quoted 3 lines
Quoted 1 line

Luis

I have tried both and none of them have worked.

On the N900 the wl1271 chip is connected via SPI.

I'll re-read this thread more carefully to see if I can spot anything that could help you.

First thing that came to my mind after re-reading the thread... Does the wl1251 driver work *without* compat-wireless? Where did you get the kernel that you have compiled?

My initial guess is that the SPI is not configured correctly so the probe function is never called in the wl1251_spi module and thus the interface is never created...

Signature · 2 lines
Cheers,
Luca.
author
#14 lore raw
Quoted 9 lines · Luciano Coelho
Quoted 8 lines · ext Luciano Coelho
Quoted 4 lines · ext George
Quoted 3 lines · Luis R. Rodriguez
Quoted 3 lines

Any help on that? Sorry but I'm somehow desesperate and don't know what to do. Actually I'm thinking on not using compat-wireless and nl80211 and get back to wireless-extensions.

Getting back to wireless-extensions would certainly be a very desperate measure! :P

I guess it is, evenmore when nl80211 is the present ;) But I'm running out of time and getting desperate ;)

Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines

Does your device use SDIO or SPI?

Luis

I have tried both and none of them have worked.

On the N900 the wl1271 chip is connected via SPI.

The chip is a wl1251, isn't it? wl1271 is n capable and n900 is not.

Quoted 5 lines
Quoted 2 lines

I'll re-read this thread more carefully to see if I can spot anything that could help you.

First thing that came to my mind after re-reading the thread... Does the wl1251 driver work *without* compat-wireless?

I don't now how to test the driver without compat-wireless. If you can explain it I will try. Do I have just to copy driver code on compat-wireless directly into my kernel source directory? I don't think that would work and probably complain, but I can try if this is the way.

Quoted 2 lines

Where did you get the
kernel that you have compiled?

The kernel is the official one for n900, kernel-2.6.28 (uname -a returns 2.6.28-omap1). I got it using scratchbox and downloading it with:

sb# apt-get source kernel

Then I have compiled it using:

sb# make EXTRAVERSION=-mine rx51_defconfig
sb# make EXTRAVERSION=-mine menuconfig
sb# make EXTRAVERSION=-mine bzImage modules
sb# make EXTRAVERSION=-mine modules_install

After that I have compiled on scratchbox compat-wireless package:

sb# cd compat-wireless-2010-10-17
sb# scripts/driver-select wl12xx
sb# make KLIB=/lib/modules/2.6.28-mine KMODPATH_ARG=/lib/modules/2.6.28-mine sb# make KLIB=/lib/modules/2.6.28-mine KMODPATH_ARG=/lib/modules/2.6.28-mine install

Then move the new set of modules to my n900

n900# mkdir -p /lib/modules/2.6.28-mine

# cd /lib/modules/2.6.28-mine
# scp -r updates/ kernel/ modules.* [email protected]:/lib/modules/2.6.28-mine

And then boot with the new kernel image

ubuntu$ sudo flasher-3.5 -l -b -k PATH_TO_KERNEL/kernel-2.6.28/arch/arm/boot/zImage

Quoted 3 lines

My initial guess is that the SPI is not configured correctly so the probe function is never called in the wl1251_spi module and thus the interface is never created...

I'm attaching a link to my .config file to check if you consider I have to activate any other stuff.

http://pastebin.com/sCnHzp3V

I would like to thank you all for the tremendous effort you are doing helping me out on this issue.

BR
Jorge

#15 lore raw
Quoted 9 lines · George
Quoted 8 lines · Luciano Coelho
Quoted 6 lines · ext Luciano Coelho
Quoted 4 lines · ext George
Quoted 2 lines · Luis R. Rodriguez

Does your device use SDIO or SPI?

Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line

   Luis

I have tried both and none of them have worked.

On the N900 the wl1271 chip is connected via SPI.

The chip is a wl1251, isn't it? wl1271 is n capable and n900 is not.

I think your problem is that the driver (in drivers/net/wireless/wl1251/spi.c) and spi_board_info (in arch/arm/mach-omap2/board-rx51-peripherals.c) names don't match (wl1251 vs wl12xx). Probably easiest to edit .modalias in board-rx51-peripherals.c and rebuild the kernel.

author
#16 lore raw
Quoted 16 lines · Grazvydas Ignotas
Quoted 15 lines · George
Quoted 13 lines · Luciano Coelho
Quoted 11 lines · ext Luciano Coelho
Quoted 7 lines · ext George
Quoted 3 lines · Luis R. Rodriguez

Does your device use SDIO or SPI?

Luis

I have tried both and none of them have worked.

On the N900 the wl1271 chip is connected via SPI.

Quoted 8 lines
Quoted 1 line

The chip is a wl1251, isn't it? wl1271 is n capable and n900 is not.

I think your problem is that the driver (in drivers/net/wireless/wl1251/spi.c) and spi_board_info (in arch/arm/mach-omap2/board-rx51-peripherals.c) names don't match (wl1251 vs wl12xx). Probably easiest to edit .modalias in board-rx51-peripherals.c and rebuild the kernel.

It seems getting closer ;)

After changing wl12xx for spi:wl1251 now modules are uploaded on startup.

However this is the output from lsmod | grep spi

spi                     4352  0
wl1251                 75840  1 spi
mac80211              256892  2 spi,wl1251
crc7                    1216  1 spi

As you can see spi module is not used :( and no interface is created. Still a way to go.

author
#17 lore raw
Quoted 30 lines · George
Quoted 16 lines · Grazvydas Ignotas
Quoted 15 lines · George
Quoted 13 lines · Luciano Coelho
Quoted 11 lines · ext Luciano Coelho
Quoted 7 lines · ext George
Quoted 3 lines · Luis R. Rodriguez

Does your device use SDIO or SPI?

Luis

I have tried both and none of them have worked.

On the N900 the wl1271 chip is connected via SPI.

Quoted 8 lines
Quoted 1 line

The chip is a wl1251, isn't it? wl1271 is n capable and n900 is not.

I think your problem is that the driver (in drivers/net/wireless/wl1251/spi.c) and spi_board_info (in arch/arm/mach-omap2/board-rx51-peripherals.c) names don't match (wl1251 vs wl12xx). Probably easiest to edit .modalias in board-rx51-peripherals.c and rebuild the kernel.

It seems getting closer ;)

After changing wl12xx for spi:wl1251 now modules are uploaded on startup.

Quoted 9 lines

However this is the output from lsmod | grep spi
spi 4352 0
wl1251 75840 1 spi
mac80211 256892 2 spi,wl1251
crc7 1216 1 spi

As you can see spi module is not used :( and no interface is created. Still a way to go.

I forgot also to mention that bluetooth in not working with new modules from compat-wireless

Quoted 6 lines

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#18 lore raw
In reply to George
Quoted 10 lines
Quoted 6 lines

I think your problem is that the driver (in drivers/net/wireless/wl1251/spi.c) and spi_board_info (in arch/arm/mach-omap2/board-rx51-peripherals.c) names don't match (wl1251 vs wl12xx). Probably easiest to edit .modalias in board-rx51-peripherals.c and rebuild the kernel.

It seems getting closer ;)

After changing wl12xx for spi:wl1251 now modules are uploaded on startup.

You should just use "wl1251", not spi:wl1251, so it becomes:

{

                .modalias               = "wl1251",
                .bus_num                = 4,
                .chip_select            = 0,
                .max_speed_hz           = 48000000,

...

author
#19 lore raw
Quoted 11 lines · Grazvydas Ignotas
Quoted 10 lines
Quoted 6 lines

I think your problem is that the driver (in drivers/net/wireless/wl1251/spi.c) and spi_board_info (in arch/arm/mach-omap2/board-rx51-peripherals.c) names don't match (wl1251 vs wl12xx). Probably easiest to edit .modalias in board-rx51-peripherals.c and rebuild the kernel.

It seems getting closer ;)

After changing wl12xx for spi:wl1251 now modules are uploaded on startup.

Quoted 8 lines

You should just use "wl1251", not spi:wl1251, so it becomes:

{

                 .modalias               = "wl1251",
                 .bus_num                = 4,
                 .chip_select            = 0,
                 .max_speed_hz           = 48000000,

...

Tried and got a similar behaviour as when using spi:wl1251.

I have also set the debug ALL mode to see if I get something that can help you out on finding the problem.

When uploading only wl1251 nothing appears in dmesg. But when uploading module spi, I got the following info: http://pastebin.com/ysdTSDnB

HTH

TA
Jorge

Quoted 5 lines

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#20 lore raw
Quoted 5 lines

I have also set the debug ALL mode to see if I get something that can help you out on finding the problem.

When uploading only wl1251 nothing appears in dmesg. But when uploading module spi, I got the following info: http://pastebin.com/ysdTSDnB

You need both wl1251 and spi. This is normal output, you should get wlan0 interface at this point.

author
#21 lore raw
Quoted 9 lines · Grazvydas Ignotas
Quoted 5 lines

I have also set the debug ALL mode to see if I get something that can help you out on finding the problem.

When uploading only wl1251 nothing appears in dmesg. But when uploading module spi, I got the following info: http://pastebin.com/ysdTSDnB

You need both wl1251 and spi. This is normal output, you should get wlan0 interface at this point.
--

Yes, that is what I was expecting from the begining but although phy0 should appear in /sys/class/ieee80211, this directory is empty :(

It seems that it tries to do something but it is not finally done. However, as you can see it seems there is no error (at least reported). Could it be that spi_read buf is almost everytime reading 00 00 00 00?

Another issue is that I have to manually upload the spi module as by default it only uploads wl1251 but not the spi. But this is not a big deal.

Again, thank you all for the help... You are almost there (I cannot say we as I've been only following your advices).

TA

#22 lore raw
Quoted 9 lines · George
Quoted 8 lines · Grazvydas Ignotas
Quoted 7 lines

I have also set the debug ALL mode to see if I get something that can help
you out on finding the problem.

When uploading only wl1251 nothing appears in dmesg. But when uploading module spi, I got the following info: http://pastebin.com/ysdTSDnB

Quoted 6 lines
Quoted 3 lines

You need both wl1251 and spi. This is normal output, you should get wlan0 interface at this point.
--

Yes, that is what I was expecting from the begining but although phy0 should appear in /sys/class/ieee80211, this directory is empty :(

Hm, maybe try enabling CONFIG_MAC80211_DEBUG* stuff in config.mk in compat_wireless.

author
#23 lore raw
Quoted 14 lines · Grazvydas Ignotas
Quoted 13 lines · George
Quoted 11 lines · Grazvydas Ignotas
Quoted 7 lines

I have also set the debug ALL mode to see if I get something that can help
you out on finding the problem.

When uploading only wl1251 nothing appears in dmesg. But when uploading module spi, I got the following info: http://pastebin.com/ysdTSDnB

You need both wl1251 and spi. This is normal output, you should get wlan0 interface at this point.
--

Quoted 6 lines
Quoted 2 lines

Yes, that is what I was expecting from the begining but although phy0 should appear in /sys/class/ieee80211, this directory is empty :(

Hm, maybe try enabling CONFIG_MAC80211_DEBUG* stuff in config.mk in compat_wireless.
--

I have done that and no extra messages appear besides the former ones :(

Any other idea :(

I have look at compat-2.6.28.c and in the comments it says that is for kernel 2.6.28. However it is not compiled as in the #ifdef it is said to be < 2.6.28. Is it right? I guess yes, but just for curiosity.

No other idea :(

#24 lore raw
In reply to George
Quoted 4 lines · George

It seems that it tries to do something but it is not finally done. However, as you can see it seems there is no error (at least reported). Could it be that spi_read buf is almost everytime reading 00 00 00 00?

If you get nothing but zeros back from the device, most likely that means that it's not powered up properly.

wl1251 chip on n900 is powered up by using a gpio line. I'm worried that the struct wl12xx_platform_data wl1251 wireless-compat driver expects (defined in /include/linux/wl12xx.h) doesn't match what the old maemo kernel provides. Unfortunately I can't remember anymore what the platform data was like in maemo kernels and there's no easy way for me to check that right now.

Signature · 1 line
Kalle Valo
author
#25 lore raw
Quoted 10 lines · Kalle Valo
Quoted 4 lines · George

It seems that it tries to do something but it is not finally done. However, as you can see it seems there is no error (at least reported). Could it be that spi_read buf is almost everytime reading 00 00 00 00?

If you get nothing but zeros back from the device, most likely that means that it's not powered up properly.

Quoted 7 lines

wl1251 chip on n900 is powered up by using a gpio line. I'm worried that the struct wl12xx_platform_data wl1251 wireless-compat driver expects (defined in /include/linux/wl12xx.h) doesn't match what the old maemo kernel provides. Unfortunately I can't remember anymore what the platform data was like in maemo kernels and there's no easy way for me to check that right now.

Thanks a lot for that hint. Now I'm involved in another issue but when I have more time I will look at those .h, but don't expect too much from me as I'm not expert but just user.

Thanks a lot.