On Wednesday 28 February 2007 18:16, Johannes Berg wrote: > 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. Personally I think the amount of duplicated code will not be that bad, but I can make a better comparison when rt2x00lib is better used than currently is the case. > > 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. It goes a bit further than that, interrupt handling is done differently as well, and still a lot of checks during register intialization have to be performed about what to do when. Some functions, like channel selection, would have to be implemented twice due to the number of checks for each indivudual RF chipset. But to be honest, the last time I had looked into rt2400pci and rt2500pci merger was in the early days of rt2x00 when there wasn't a Linux wireless stack yet. Not even Intel had announced its stack yet. (rt2x00 started in 2004) so back then I had to try to extract the stack from the Ralink drivers. Personally I think that merging the 2 drivers would make the code too obscure to be easily understandable after the implementation of hardware encryption. But I could be wrong, as I haven't worked on the hardware encryption yet (getting things working without HW encryption is hard enough). So I think it is best to reinvestigate merging rt2400pci and rt2500pci, when both modules are working independently and hardware encryption work is being done. That will give the best comparison material for making a better decision. Ivo - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
