Very nice, thanks for forwarding this on.

As the license is BSD, that means we can place it in the kernel tree.
Do you all mind if I add it to the drivers/staging/ directory so you can
work on cleaning it up within the main kernel tree infrastructure?

thanks,

greg k-h
--

[ message continues ]

(cc'ing linux-wireless)

FYI, Hermes I hardware is already covered by the orinoco driver. WPA and firmware download functionality (which is supported by the Agere driver, but not orinoco in 2.6.27) is already in the wireless queue for 2.6.28.

This leaves Hermes-II (and USB?) hardware which orinoco does not support, but could if someone had access to a card for development.


Regards,

Dave.

--

[ message continues ]

TJ you can answer me using arvidjaar (at) newmail dot ru. Hopefully
one of them works. Re WPA2 - there is no information how to setup
CCMP/AES (even if firmware supports it); so no WPA2.


I do not mind but it is likely makes no sense for H-I now; and
I do not own H-II myself so cannot work on it. If we are focusing on
H-2/2.5, it would make more sense to make similar modifications to
7.22 driver set from Agere to avoid overlap with Orinoco.
firmware download functionality (which is supported by the Agere driver, bu=

Yes, I discovered this yesterday as well. Thank you!

How are you going to distribute firmware? You will need 9.x firmware from
original Agere driver; do I understand it correctly that it will come

As I initially wrote driver for internal consumption my mods supports
PCMCIA only.

Unfortunately I do not own Hermes-II device myself. I was asked recently
by Alexander who is owing such device and modification of Agere sources was
pretty trivial. I Cc to him; Aexander are you interested in aiding of
H-II driver development for mainstream?
[ message continues ]

I was hoping we could get it into David Woodhouses firmware tree. However I haven't had a response to my original message. I'll try again with a patch.


Dave.
--

[ message continues ]

Ok, let me know what you think is the best thing to do, and I'll be glad
to help you out with it.

thanks,

greg k-h
--

[ message continues ]

I tend to think that only for USB hardware do we need a new driver, and
that driver can share some things with both hostap and orinoco.  If at
all possible, lets integrate missing hardware support into _existing_
drivers instead of importing drivers of questionable quality.  I've seen
wlags49 before and it's not great.  Right now we don't have any viable
Orinoco USB driver, and while linux-wlan-ng was proposed, there's no way
we're taking a third 802.11 "stack" or the bits in those drivers that
overlap with existing drivers' hardware support.

Dan


--

[ message continues ]

I just added the wlan-ng usb driver (and stack) to the drivers/staging/
tree a few hours ago :)

So yes, we do need to do this kind of migration, at the moment I am
trying to track down all out-of-tree drivers that distros and users are
relying on to get them into staging/ and then we can work on cleaning
them up and moving them to the proper place in the kernel tree.

Sound good?

So, for this driver, should I do the same thing, as I don't think these
devices are covered by any other driver at the moment, right?

thanks,

greg k-h
--

[ message continues ]

Prism II USB devices are only covered by linux-wlan-ng, yes.

Dan


--

[ message continues ]