usb-id 0df6:0036 not yet in kernel 2.6.29-rc2

[Giuseppe Calà]

Hi,
I have just downloaded the last kernel source hoping that the bus-id of my Sitecom WL-603 had been inserted in zd_usb.c but it's not so even if in my previouses message in this mailinglist I have reported a successful compilation and a correct working of this device with the zd1211rw driver. Just in case my previous posts were completely ignored now a quote of one of them:

****************
I have added the new usb-id (0df6:0036) to zd_usb.c (zd1211b section) and
recompiled the kernel (2.6.27-9.19 from ubuntu repo). So the device is
recognized correctly and works fine.

One more info:

$ dmesg | grep 'zd1211b\? chip'
[   49.410219] zd1211rw 1-4:1.0: zd1211b chip 0df6:0036 v4810 high 00-0c-f6
AL2230_RF pa0 g--N-

so this device combines a AL2230 RF transceiver chip.

This should be enough for adding the Sitecom WL-603 bus-id in the kernel
driver.

*******************

Regards.

[Hin-Tak Leung-3]

I have gone through the process of getting code changes into the linux kernel so it is relatively straight forward to do that if it isn't already done by somebody else on the list. But
(1) I think I asked maybe somebody else if a new chip id is 1211 or 1211b -
for such simple changes it is easier for everybody concerned to add a few in a single patch than etc.
(2) you need to sign-off on it and you need to write down your real name, not "jiveaxe".
(3) when it gets accepted to wireless-testing, it will still take some time and go through some people before it gets to Linus, so you check for the latest change in the driver not in rc's, but in wireless-testing. There are merge-windows where changes are accepted by Linus - basically I am saying that whatever change you submit now will not make it in time for 2.6.29. Maybe 2.6.30 or 2.6.31 is your expectation.

So, if you want to proceed, follow the patch submission guidelines yourself at http://linuxwireless.org/, or write down you real name and I'll do it for you.

--- On Mon, 19/1/09, jiveaxe <jiveaxe@...> wrote:

> Hi,
> I have just downloaded the last kernel source hoping that
> the bus-id of my
> Sitecom WL-603 had been inserted in zd_usb.c but it's
> not so even if in my
> previouses message in this mailinglist I have reported a
> successful
> compilation and a correct working of this device with the
> zd1211rw driver.
> Just in case my previous posts were completely ignored now
> a quote of one of
> them:
>
> ****************
> I have added the new usb-id (0df6:0036) to zd_usb.c
> (zd1211b section) and
> recompiled the kernel (2.6.27-9.19 from ubuntu repo). So
> the device is
> recognized correctly and works fine.
>
> One more info:
>
> $ dmesg | grep 'zd1211b\? chip'
> [   49.410219] zd1211rw 1-4:1.0: zd1211b chip 0df6:0036
> v4810 high 00-0c-f6
> AL2230_RF pa0 g--N-
>
> so this device combines a AL2230 RF transceiver chip.
>
> This should be enough for adding the Sitecom WL-603 bus-id
> in the kernel
> driver.
>
> *******************
>
> Regards.

     

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Giuseppe Calà]

Thank you,
now the problem of the real name should be gone.

Best regards

[Hin-Tak Leung]

--- On Mon, 19/1/09, Giuseppe Calà <jiveaxe@...> wrote:

> Thank you,
> now the problem of the real name should be gone.
>
> Best regards

You should have gotten some automatic notification e-mails about the patches being sent out. Apologies for sending it three times... kernel patches are required to be formatted precisely and sent through git. git is not the easiest-to-use tool in the world :-).
It is very powerful, and well worth the time to learn to use it though.

Good luck and enjoy the connectivity. I don't think there should be any issue for such a simple change (when it is sent in the correct format in the correct way to the correct people...), so you could expect the change to be in 2.6.30; whehther it will go into 2.6.29 or 2.6.29.X is up to others' decision.



 



     

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Giuseppe Calà]

Ok Hin-Tak,
thanks for your patience.

Giuseppe

Hin-Tak Leung wrote:

--- On Mon, 19/1/09, Giuseppe Calà <[e-mail]> wrote:

> Thank you,
> now the problem of the real name should be gone.
>
> Best regards

You should have gotten some automatic notification e-mails about the patches being sent out. Apologies for sending it three times... kernel patches are required to be formatted precisely and sent through git. git is not the easiest-to-use tool in the world :-).
It is very powerful, and well worth the time to learn to use it though.

Good luck and enjoy the connectivity. I don't think there should be any issue for such a simple change (when it is sent in the correct format in the correct way to the correct people...), so you could expect the change to be in 2.6.30; whehther it will go into 2.6.29 or 2.6.29.X is up to others' decision.



 



     

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs