Add vt6656 driver to drivers/staging.
Quoted 4 lines · Dan Williams
The only fixes that drivers are getting in staging now are
netdev_ops, whitespace cleanups, and trivial fixes. Nobody is actually rewriting the Ralink or Via staging drivers to use mac80211, which is what's needed for them to be merged. Given that they are going nowhere, are
Only rtl8187se and wlan-ng don't have a mac80211 port.
mac80211 drivers:
agnx -> http://git.sipsolutions.net/agnx.gitat76_usb -> replacement already in kernel.org code at drivers/net/wireless/at76c50x-usb.[ch]
otus -> replacement already in kernel.org code at drivers/net/wireless/ar9170/
rt2860 -> rt2800pci.[ch] http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git
rt2870 -> rt2800usb.[ch] http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git
rt3070 -> rt2800usb.[ch] http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git
rtl8187se -> ???
stlc45xx -> replacement already in kernel.org code at drivers/net/wireless/p54/p54spi*
winbond -> http://code.google.com/p/winbondport/
wlan-ng -> ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/FAQ ???
I hope rt2800pci/usb to be included *ASAP*, because rt2800usb supports more than 1oo USB devices and rt2800pci is included in a lot of laptops(ask Torvalds [1] [2])
[1] http://marc.info/?l=linux-netdev&m=121799144422863&w=2
[2] http://marc.info/?l=linux-kernel&m=123187052023831&w=2
regards,
Signature · 1 line
Polycommander, Erkowit, Urquiola, Andros Patria, Cason, Aegean Sea, Prestige, ...
Quoted 11 lines · Xose Vazquez Perez
Quoted 4 lines · Dan Williams
The only fixes that drivers are getting in staging now are
netdev_ops, whitespace cleanups, and trivial fixes. Nobody is actually rewriting the Ralink or Via staging drivers to use mac80211, which is what's needed for them to be merged. Given that they are going nowhere, areOnly rtl8187se and wlan-ng don't have a mac80211 port.
mac80211 drivers:
Quoted 10 lines
agnx -> http://git.sipsolutions.net/agnx.git
at76_usb-> replacement already in kernel.org code at drivers/net/wireless/at76c50x-usb.[ch]
otus -> replacement already in kernel.org code atdrivers/net/wireless/ar9170/
rt2860 -> rt2800pci.[ch] http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git
rt2870 -> rt2800usb.[ch] http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git
rt3070 -> rt2800usb.[ch] http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git
rtl8187se -> ???
stlc45xx -> replacement already in kernel.org code atdrivers/net/wireless/p54/p54spi*
winbond -> http://code.google.com/p/winbondport/
wlan-ng -> ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/FAQ ???
Thanks for the summary.
Note, whenever a "real" wireless driver goes into the tree that obsoletes any of the staging drivers, please let me know and I'll instantly remove it.
Right now the otus code is staying because the ar9170 developers want it to.
But what about at76_usb? stlc45xx? Do they now have workable drivers to replace them in the tree today? If so, _please_ let me know.
As for the other drivers, here's what I know:
rtl8187se - a varient of rtl818x, someone just needs to do the work to add the proper parts to the existing driver. I tried, and it wasn't obvious how to do this :(
wlan-ng - this is being cleaned up by community members for eventual inclusion in the main tree. It only supports a single type of USB device.
winbond - community members are cleaning it up as well.
Quoted 6 lines
I hope rt2800pci/usb to be included *ASAP*, because rt2800usb supports more than 1oo USB devices and rt2800pci is included in a lot of
laptops(ask Torvalds [1] [2])[1] http://marc.info/?l=linux-netdev&m=121799144422863&w=2
[2] http://marc.info/?l=linux-kernel&m=123187052023831&w=2
That would be great to have in, what's keeping it from happening?
thanks,
greg k-h
Quoted 9 lines · Greg KH
Note, whenever a "real" wireless driver goes into the tree that obsoletes any of the staging drivers, please let me know and I'll instantly remove it.
Right now the otus code is staying because the ar9170 developers want it to.
But what about
at76_usb? stlc45xx? Do they now have workable drivers to replace them in the tree today? If so, _please_ let me know.
I have received a report that at76_usb has worked better than at76c50x-usb. Also p54spi implementation is quite new and not that much tested.
If it's ok for you, I would like to have both at76_usb and stlc45xx in the staging area for some time still. I will let you know when they can be removed.
Signature · 1 line
Kalle Valo
Quoted 10 lines
I have received a report that
at76_usbhas worked better than at76c50x-usb. Also p54spi implementation is quite new and not that much tested.If it's ok for you, I would like to have both
at76_usband stlc45xx in the staging area for some time still. I will let you know when they can be removed.--
Kalle Valo
Kalle, what is the primary location for stlc45xx sources then? I see that version in staging is pretty old.
Signature · 1 line
Max
Quoted 9 lines · Max Filippov
Quoted 7 lines
I have received a report that
at76_usbhas worked better than at76c50x-usb. Also p54spi implementation is quite new and not that much tested.If it's ok for you, I would like to have both
at76_usband stlc45xx in the staging area for some time still. I will let you know when they can be removed.Kalle, what is the primary location for stlc45xx sources then?
I have been thinking about using staging the primary location. What do you think?
Quoted 1 line
I see that version in staging is pretty old.
Yeah, I have been planning to patch bomb Greg at some point with all the patches from the stlc45xx git tree. It's just that n800 support is currently broken in 2.6.30-rc1 from linux-omap tree :(
Signature · 1 line
Kalle Valo
Quoted 4 lines
Quoted 1 line
Kalle, what is the primary location for stlc45xx sources then?
I have been thinking about using staging the primary location. What do you think?
Partly agree: drivers/staging is better than gitorious and there are more potential testers than at [email protected]. But I don't realize what is the purpose to have two drivers for one hw? p54spi IMHO only lacks firmware restart feature now. And most of the p54 code is used collectively by the pci, usb and spi, so it is probably more tested than stlc45xx.
Signature · 1 line
Max
Quoted 7 lines · Max Filippov
Quoted 4 lines
Quoted 1 line
Kalle, what is the primary location for stlc45xx sources then?
I have been thinking about using staging the primary location. What do you think?
Partly agree:
drivers/stagingis better than gitorious and there are more potential testers than at [email protected].
Good.
Quoted 4 lines
But I don't realize what is the purpose to have two drivers for one hw? p54spi IMHO only lacks firmware restart feature now. And most of the p54 code is used collectively by the pci, usb and spi, so it is probably more tested than stlc45xx.
p54spi is definitely the future. Christian and you have done great work to get p54spi working N800/N810.
Signature · 1 line
Kalle Valo
Hi,
Quoted 8 lines
Quoted 6 lines
I hope rt2800pci/usb to be included *ASAP*, because rt2800usb supports more than 1oo USB devices and rt2800pci is included in a lot of
laptops(ask Torvalds [1] [2])[1] http://marc.info/?l=linux-netdev&m=121799144422863&w=2
[2] http://marc.info/?l=linux-kernel&m=123187052023831&w=2That would be great to have in, what's keeping it from happening?
In short: A stable workable driver.
The rt2800usb driver is pretty far (at least on my testsetup), but still has problems with transmitting frames immediately after association.
As for rt2800pci that card still refuses to anything. The MCU registers simply refuses the initialize, the TX and RX refuse to do anything.
I have some help from Ralink on this, as well as some patches from others which have been merged. But I lack the time to really dive into these issues. I don't get much further then a guick glance every few days.
Ivo
Quoted 9 lines · Ivo van Doorn
Hi,
Quoted 7 lines
Quoted 6 lines
I hope rt2800pci/usb to be included *ASAP*, because rt2800usb supports more than 1oo USB devices and rt2800pci is included in a lot of
laptops(ask Torvalds [1] [2])[1] http://marc.info/?l=linux-netdev&m=121799144422863&w=2
[2] http://marc.info/?l=linux-kernel&m=123187052023831&w=2
Quoted 7 lines
Quoted 1 line
That would be great to have in, what's keeping it from happening?
In short: A stable workable driver.
The rt2800usb driver is pretty far (at least on my testsetup), but still has problems with transmitting frames immediately after association.
I read this as "it works, but some frames are lost immediately after association" -- is that right? FWIW, this sounds good enough to me to get it into the mainline kernel. _Please_ submit the rt2800usb driver for wireless-testing/linux-next ASAP!
John
Signature · 2 lines
John W. Linville Someday the world will need a hero, and you [email protected] might be all we have. Be ready.
Quoted 4 lines · John W. Linville
Quoted 3 lines · Ivo van Doorn
Hi,
Quoted 1 line
Quoted 1 line
I hope rt2800pci/usb to be included *ASAP*, because rt2800usb su=
pports
Quoted 8 lines
Quoted 8 lines
Quoted 7 lines
Quoted 5 lines
more than 1oo USB devices and rt2800pci is included in a lot of
laptops(ask Torvalds [1] [2])[1] http://marc.info/?l=3Dlinux-netdev&m=3D121799144422863&w=3D2
[2] http://marc.info/?l=3Dlinux-kernel&m=3D123187052023831&w=3D2That would be great to have in, what's keeping it from happening?
Quoted 8 lines
Quoted 5 lines
In short: A stable workable driver.
The rt2800usb driver is pretty far (at least on my testsetup), but still has problems with transmitting frames immediately after association.
I read this as "it works, but some frames are lost immediately after association" -- is that right?
It is not "Some frames" it is "All frames" you can't get a DHCP lease, or use a static IP and try to do anything.
Also 11n APs are not detected at all, which for a 11n client sounds very problematic.
Quoted 3 lines
FWIW, this sounds good enough to me
to get it into the mainline kernel. =A0_Please_ submit the rt2800usb driver for wireless-testing/linux-next ASAP!
If the above 2 problems aren't critical for merge, then I'll send the patches as soon as possible.
Ivo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Apr 21, 2009 at 12:30 PM, Ivo Van Doorn <[email protected]> wro= te:
Quoted 6 lines
Quoted 4 lines · John W. Linville
Quoted 3 lines · Ivo van Doorn
Hi,
Quoted 1 line
Quoted 1 line
I hope rt2800pci/usb to be included *ASAP*, because rt2800usb s=
upports
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
more than 1oo USB devices and rt2800pci is included in a lot of
laptops(ask Torvalds [1] [2])[1] http://marc.info/?l=3Dlinux-netdev&m=3D121799144422863&w=3D=
2
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
[2] http://marc.info/?l=3Dlinux-kernel&m=3D123187052023831&w=3D=
2
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
That would be great to have in, what's keeping it from happening?
In short: A stable workable driver.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
The rt2800usb driver is pretty far (at least on my testsetup), but still has problems with transmitting frames immediately after association.
I read this as "it works, but some frames are lost immediately after association" -- is that right?
It is not "Some frames" it is "All frames" you can't get a DHCP lease=
,
Quoted 1 line
or use a static IP and try to do anything.
To clarify a bit, this behavior summarizes the first minute after assoc= iation,
after that all frames queued in the past minute are bursted out in a si= ngle shot
and normal traffic is possible again.
Quoted 9 lines
Also 11n APs are not detected at all, which for a 11n client sounds very problematic.
Quoted 3 lines
FWIW, this sounds good enough to me
to get it into the mainline kernel. =A0_Please_ submit the rt2800usb driver for wireless-testing/linux-next ASAP!If the above 2 problems aren't critical for merge, then I'll send the patches as soon as possible.
Ivo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 24 lines · Ivo Van Doorn
Quoted 23 lines · Ivo Van Doorn
Quoted 20 lines · John W. Linville
Quoted 9 lines · Ivo van Doorn
Hi,
Quoted 7 lines
Quoted 6 lines
I hope rt2800pci/usb to be included *ASAP*, because rt2800usb supports more than 1oo USB devices and rt2800pci is included in a lot of
laptops(ask Torvalds [1] [2])[1] http://marc.info/?l=linux-netdev&m=121799144422863&w=2
[2] http://marc.info/?l=linux-kernel&m=123187052023831&w=2Quoted 7 lines
Quoted 1 line
That would be great to have in, what's keeping it from happening?
In short: A stable workable driver.
The rt2800usb driver is pretty far (at least on my testsetup), but still has problems with transmitting frames immediately after association.
I read this as "it works, but some frames are lost immediately after association" -- is that right?
Quoted 6 lines
Quoted 2 lines
It is not "Some frames" it is "All frames" you can't get a DHCP lease, or use a static IP and try to do anything.
To clarify a bit, this behavior summarizes the first minute after association, after that all frames queued in the past minute are bursted out in a single shot and normal traffic is possible again.
Ah, well in that case I'd say let's get it into at least wireless-testing.
John
Signature · 2 lines
John W. Linville Someday the world will need a hero, and you [email protected] might be all we have. Be ready.
Quoted 6 lines · Ivo Van Doorn
Quoted 4 lines · John W. Linville
Quoted 3 lines · Ivo van Doorn
Hi,
Quoted 1 line
Quoted 1 line
I hope rt2800pci/usb to be included *ASAP*, because rt2800usb =
supports
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
more than 1oo USB devices and rt2800pci is included in a lot o=
f
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
laptops(ask Torvalds [1] [2])[1] http://marc.info/?l=3Dlinux-netdev&m=3D121799144422863&w=3D=
2
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
[2] http://marc.info/?l=3Dlinux-kernel&m=3D123187052023831&w=3D=
2
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
That would be great to have in, what's keeping it from happening=
?
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
In short: A stable workable driver.
The rt2800usb driver is pretty far (at least on my testsetup), but still has problems with transmitting frames immediately after association.
I read this as "it works, but some frames are lost immediately afte=
r
Quoted 3 lines
Quoted 1 line
association" -- is that right?
=20
It is not "Some frames" it is "All frames" you can't get a DHCP lease=
,
Quoted 1 line
or use a static IP and try to do anything.
Is this permanent? Or does it start working at some point?
Quoted 2 lines
Also 11n APs are not detected at all, which for a 11n client sounds very problematic.
If 11g works then I think that is good enough to merge.
Quoted 2 lines
Quoted 2 lines
FWIW, this sounds good enough to me
to get it into the mainline kernel. =A0_Please_ submit the rt2800us=
b
Quoted 4 lines
Quoted 1 line
driver for wireless-testing/linux-next ASAP!
=20
If the above 2 problems aren't critical for merge, then I'll send the patches as soon as possible.
If there is no traffic at all then I guess it can still wait -- ping seems like a reasonable requirement. But 11n is not a requirement for merge.
John
--=20
John W. Linville Someday the world will need a hero, and you
[email protected] might be all we have. Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html