Re: umac.ko for 2.6.26

2008-08-22 Thread Kalle Valo
ext Gregoire Gentil [EMAIL PROTECTED] writes:

 [  274.247192] umac: module license 'Proprietary' taints kernel.
 [ 1328.262176] sm_drv_spi_probe
 [ 1328.262237] sm_drv_netdev_create
 [ 1328.262298] Registering WLAN platform device
 [ 1328.262847] Creating WLAN sysfs
 [ 1328.463775] sm_drv_statistics 
 [ 1328.465545] cx3110x: chip variant STLC4550.
 [ 1328.465606] sm_drv_fetch_firmware
 [ 1328.465606] firmware: requesting 3826.arm
 [ 1328.708282] sm_drv_fetch_firmware: file 3826.arm (31284 bytes)
 [ 1328.708343] cx3110x: firmware version 2.13.0.0.a.22.8.
 [ 1328.708740] cx3110x: driver version 2.0.15 loaded.
 [ 1370.573364] GET RANGE
 [ 1370.573455] cx3110x: WARNING SoftMAC not initialized, chip not booted (get 
 oid 0x1712)

 The last message means that lp-sm_initialization = 0. Indeed,
 sm_drv_spi_initialize is not reached. sm_drv_spi_wq which
 calls sm_drv_spi_initialize, seems also never reached - so
 no ifconfig! -:( I checked that INIT_WORK(lp-work,sm_drv_spi_wq);
 is reached inside sm_drv_spi_probe.

 So why don't we get this first crucial interrupt?
 Kalle? A little bit of help? ;-)

Sorry, can't help you.

-- 
Kalle Valo
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: umac.ko for 2.6.26

2008-08-18 Thread Gregoire Gentil
On Sun, 2008-08-17 at 17:03 -0400, Gregoire Gentil wrote: 
 Faheem,
 
 Thanks for the tip. I tried it and it worked. I can insmod both umac and
 cx3110x in 2.6.26 and it looks fine in dmesg:
 
 cx3110x: chip variant STLC4550
 cx3110x: firmware version 2.13.0.0.a.22.8.
 cx3110x: driver version 2.0.15 loaded.
 
 But then I get multiple errors:
 
 ifconfig wlan0 up reports SIOCSIFFLAGS: Cannot assign requested
 address
 
 iwlist wlan0 scan doesn't work
 
 and in dmesg, I get many:
 cx3110x: WARNING SoftMAC not initialized, chip not booted
 
 I compiled cx3110x from
 http://repository.maemo.org/pool/maemo4.1/free/c/cx3110x-module-src/cx3110x-module-src_2.0.15-1.tar.gz
 against my 2.6.26 kernel. I had to modify the code in two locations:
 
 - in sm_drv_spi_io.c, replace SA_INTERRUPT by IRQF_DISABLED
 - in sm_drv.c, remove the line where mac.raw is assigned
 
 
 Any idea? Has anyone successfully tried what I'm doing now?
A little bit more of information from dmesg with the full
debug flag in cx3110x:

[  274.247192] umac: module license 'Proprietary' taints kernel.
[ 1328.262176] sm_drv_spi_probe
[ 1328.262237] sm_drv_netdev_create
[ 1328.262298] Registering WLAN platform device
[ 1328.262847] Creating WLAN sysfs
[ 1328.463775] sm_drv_statistics 
[ 1328.465545] cx3110x: chip variant STLC4550.
[ 1328.465606] sm_drv_fetch_firmware
[ 1328.465606] firmware: requesting 3826.arm
[ 1328.708282] sm_drv_fetch_firmware: file 3826.arm (31284 bytes)
[ 1328.708343] cx3110x: firmware version 2.13.0.0.a.22.8.
[ 1328.708740] cx3110x: driver version 2.0.15 loaded.
[ 1370.573364] GET RANGE
[ 1370.573455] cx3110x: WARNING SoftMAC not initialized, chip not booted (get 
oid 0x1712)

The last message means that lp-sm_initialization = 0. Indeed,
sm_drv_spi_initialize is not reached. sm_drv_spi_wq which
calls sm_drv_spi_initialize, seems also never reached - so
no ifconfig! -:( I checked that INIT_WORK(lp-work,sm_drv_spi_wq);
is reached inside sm_drv_spi_probe.

So why don't we get this first crucial interrupt?
Kalle? A little bit of help? ;-)

Grégoire


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: umac.ko for 2.6.26

2008-08-17 Thread Kalle Valo
ext Gregoire Gentil [EMAIL PROTECTED] writes:

 Hello,

Hi,

 I'm experimenting with 2.6.26 on N810. I have successfully compiled
 cx3110x but I need umac.ko. How can I get this proprietary module
 compiled for 2.6.26? (Obviously, I can't insmod the 2.6.21 version).

You simply can't. But we are very aware of the problem and are trying
solve it somehow.

I'm not aware of any hack about how to load the 2.6.21 version but
Poky has some linker tricks, you might want to check that. Also there
was discussion on cx3110x-devel about struct net_device changes.

-- 
Kalle Valo
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: umac.ko for 2.6.26

2008-08-17 Thread Faheem Pervez
Hi,

A bit of a dirty trick, but have you tried loading umac.ko in a hex editor
and changing the string vermagic=2.6.21-omap1?

I managed to recompile cx3110x against my preempt kernel by using the mamona
patch for cx3110x and a dummy_umac.c file from 0.8.1 + binary_umac.o
(renamed umac.ko from my initfs)

Regards,
Faheem

On Sun, Aug 17, 2008 at 2:27 AM, Gregoire Gentil [EMAIL PROTECTED]wrote:

 Hello,

 I'm experimenting with 2.6.26 on N810. I have successfully compiled
 cx3110x but I need umac.ko. How can I get this proprietary module
 compiled for 2.6.26? (Obviously, I can't insmod the 2.6.21 version).

 Thanks in advance,

 Gregoire


 ___
 maemo-developers mailing list
 maemo-developers@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-developers

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


umac.ko for 2.6.26

2008-08-16 Thread Gregoire Gentil
Hello,

I'm experimenting with 2.6.26 on N810. I have successfully compiled
cx3110x but I need umac.ko. How can I get this proprietary module
compiled for 2.6.26? (Obviously, I can't insmod the 2.6.21 version).

Thanks in advance,

Gregoire


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: umac.ko

2007-12-12 Thread Kalle Valo
ext [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
 I also very much would like this to work with packet injection,

Me too.

 and be able to modify the source completely for other reasons.

I also would like you to be able to modify the source code, no doubt
about that. I'm a strong supporter of Open Source and I'm certain that
having an open WLAN driver would benefit both the community and Nokia.

But as life in general, things are not that simple. It's not that we
just need to decide that we will have an open driver. There are
various aspects and requirements involved, and all them need to solved
before an open driver would be reality.

 So in this case can't we just get the full data sheet for the chip 
 and we're off to the races. Program it to do anything we need. 
 Third party manu. so I'm assuming the full data sheet is not top 
 secret...?

Only public data sheet I'm aware of is here:

http://www.st.com/stonline/products/literature/bd/12063/stlc4550.htm

But that's not going to help you at all.

If we could publish a complete data sheet of the WLAN chip in Nokia
tablets, we would have done that a long time ago. Heck, I would have
even written the driver on my free time if that would have been
possible. The problems here are not technical, but something else.

-- 
Kalle Valo
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: umac.ko

2007-12-11 Thread davidruff
 En/na Kalle Valo ha escrit:
 ext Luca Olivetti luca[at]ventoso.org writes:

 En/na Kalle Valo ha escrit:
 ext Alex Iliadis alex[at]immunityinc.com writes:

 [packet injection]

 Is there a way that we can modify the source of the umac.ko 
module supplied
 with the N810 or N800?
 The answer is plain and simple no. The umac.ko module is 
proprietary
 and the source code is not available. Sorry.
 But somebody has access to that sources, so he or she could add 
this
 often requested feature, right?

 I find that very unlikely. If you can come with a good business 
_and_
 use case, I might reconsider taking this to higher-ups. But the
 reasons would have to be really good.

Mmh, so I guess that ranking better on
http://www.aircrack-ng.org/doku.php?id=compatibility_drivers 
wouldn't be
enough.
Too bad, since by looking at other patches it shouldn't be a big 
effort.
Well, now that usb host mode is possible there are other 
alternatives,
though I fear that my ralink usb adapter needs something more than 
100ma
to work.

Bye
-- 
Luca

I also very much would like this to work with packet injection, and 
be able to modify the source completely for other reasons.  Though 
I know assembly I've never programmed off a data sheet, I certainly 
could.

So in this case can't we just get the full data sheet for the chip 
and we're off to the races. Program it to do anything we need. 
Third party manu. so I'm assuming the full data sheet is not top 
secret...?

thanks



--
Free Information On How We can Help With Your Patent. Click Here.
http://tagline.hushmail.com/fc/Ioyw6h4fKEtigOIrPxHUNYW3N0DHsxzAIlGEluR44X6awrxmvIWAF5/

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: umac.ko

2007-12-11 Thread Brian Waite
On Tuesday 11 December 2007, [EMAIL PROTECTED] wrote:
  En/na Kalle Valo ha escrit:
  ext Luca Olivetti luca[at]ventoso.org writes:
  En/na Kalle Valo ha escrit:
  ext Alex Iliadis alex[at]immunityinc.com writes:
 
  [packet injection]
 
  Is there a way that we can modify the source of the umac.ko
 
 module supplied
 
  with the N810 or N800?
 
  The answer is plain and simple no. The umac.ko module is
 
 proprietary
 
  and the source code is not available. Sorry.
 
  But somebody has access to that sources, so he or she could add
 
 this
 
  often requested feature, right?
 
  I find that very unlikely. If you can come with a good business
 
 _and_
 
  use case, I might reconsider taking this to higher-ups. But the
  reasons would have to be really good.
 
 Mmh, so I guess that ranking better on
 http://www.aircrack-ng.org/doku.php?id=compatibility_drivers
 wouldn't be
 enough.
 Too bad, since by looking at other patches it shouldn't be a big
 effort.
 Well, now that usb host mode is possible there are other
 alternatives,
 though I fear that my ralink usb adapter needs something more than
 100ma
 to work.
 
 Bye
 --
 Luca

 I also very much would like this to work with packet injection, and
 be able to modify the source completely for other reasons.  Though
 I know assembly I've never programmed off a data sheet, I certainly
 could.

 So in this case can't we just get the full data sheet for the chip
 and we're off to the races. Program it to do anything we need.
 Third party manu. so I'm assuming the full data sheet is not top
 secret...?
A full data sheet will do you no good for wireless devices. Wireless devices 
employ a HAL (hardware abstraction layer) that is meant to restrict people 
from doing un-regulated things with the chip. People like the FCC require 
some level of assurance that the distributor is not providing hardware that 
can be used outside its tested parameters. Basically, I would not bother 
unless you are pretty deep into reverse engineering. 
Thanks
Brian



 thanks



 --
 Free Information On How We can Help With Your Patent. Click Here.
 http://tagline.hushmail.com/fc/Ioyw6h4fKEtigOIrPxHUNYW3N0DHsxzAIlGEluR44X6a
wrxmvIWAF5/

 ___
 maemo-developers mailing list
 maemo-developers@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-developers
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: umac.ko

2007-12-07 Thread Kalle Valo
ext Luca Olivetti [EMAIL PROTECTED] writes:

 I find that very unlikely. If you can come with a good business _and_
 use case, I might reconsider taking this to higher-ups. But the
 reasons would have to be really good.

 Mmh, so I guess that ranking better on
 http://www.aircrack-ng.org/doku.php?id=compatibility_drivers
 wouldn't be enough.

Sorry, that's not enough. Fixing bugs and improving performance is far
more important.

-- 
Kalle Valo
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: umac.ko

2007-12-06 Thread Kalle Valo
ext Luca Olivetti [EMAIL PROTECTED] writes:

 En/na Kalle Valo ha escrit:
 ext Alex Iliadis [EMAIL PROTECTED] writes:

[packet injection]

 Is there a way that we can modify the source of the umac.ko module supplied 
 with the N810 or N800? 
 
 The answer is plain and simple no. The umac.ko module is proprietary
 and the source code is not available. Sorry.

 But somebody has access to that sources, so he or she could add this 
 often requested feature, right?

I find that very unlikely. If you can come with a good business _and_
use case, I might reconsider taking this to higher-ups. But the
reasons would have to be really good.

-- 
Kalle Valo
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: umac.ko

2007-12-06 Thread Luca Olivetti
En/na Kalle Valo ha escrit:
 ext Luca Olivetti [EMAIL PROTECTED] writes:
 
 En/na Kalle Valo ha escrit:
 ext Alex Iliadis [EMAIL PROTECTED] writes:
 
 [packet injection]
 
 Is there a way that we can modify the source of the umac.ko module 
 supplied 
 with the N810 or N800? 
 The answer is plain and simple no. The umac.ko module is proprietary
 and the source code is not available. Sorry.
 But somebody has access to that sources, so he or she could add this 
 often requested feature, right?
 
 I find that very unlikely. If you can come with a good business _and_
 use case, I might reconsider taking this to higher-ups. But the
 reasons would have to be really good.

Mmh, so I guess that ranking better on 
http://www.aircrack-ng.org/doku.php?id=compatibility_drivers wouldn't be 
enough.
Too bad, since by looking at other patches it shouldn't be a big effort.
Well, now that usb host mode is possible there are other alternatives, 
though I fear that my ralink usb adapter needs something more than 100ma 
to work.

Bye
-- 
Luca

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: umac.ko

2007-12-05 Thread Luca Olivetti
En/na Kalle Valo ha escrit:
 ext Alex Iliadis [EMAIL PROTECTED] writes:
 
 Is there a way that we can modify the source of the umac.ko module supplied 
 with the N810 or N800? 
 
 The answer is plain and simple no. The umac.ko module is proprietary
 and the source code is not available. Sorry.

But somebody has access to that sources, so he or she could add this 
often requested feature, right?

Bye
-- 
Luca

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers