On Wed, 2007-02-28 at 18:07 +0100, Ivo van Doorn wrote: > That is where rt2x00lib is coming in. This is only a recent addition to rt2x00 > so not everything has moved in correctly. So you can expect more to be > merged into rt2x00lib. Yeah, I see that. > Merging rt2400pci and rt2500pci doesn't sound like a good idea to me, > once rt2x00lib has been optimally used most duplicate code is out, Well you'll still have a lot of the registration code etc. duplicated. > and merging those 2 could make the implementation of hardware encryption > for rt2500pci harder. rt2400pci is the only Ralink chip that is not capable of > hardware encryption. That I don't understand at all; if it's a 2400pci chip you just return early from the set_key() callback and thereby tell mac80211 to use sw crypto. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
