> Actually, orinoco-exp could be used as a test bed for monitor mode,
> scanning, hermesap, ... and merge it back to the standard orinoco as it
> probes to work right. For now it should be a test bed for USB support :)
[snip]
> > If you are going to create a separate driver, you should rename the
> > module. I wouldn't bother with separate modules. Just link hermes,
> > orinoco and orinoco_usb to one driver, say orinoco-usb.
>
> No, I want to stay as similar to standard orinoco as possible to make
> merging easier.
OK, I understand you are suggesting to fork an experimental branch. Then
I suggest that we stop this discussion in LKML and return to orinoco-devel
to discuss the situation.
There is nothing wrong with the fork if all other ways to keep the code
together have been exhausted. But since this wasn't discussed in the
orinoco-devel mailing list, I think it's too early to fork.
One thing we haven't considered is restructuring the code to separate
common and different parts of the USB and the non-USB drivers.
The firmware issue has been solved in the 2.5 kernels, so it shouldn't
prevent David from including your code.
-- Regards, Pavel Roskin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/