> FWIW, waiting for the merge window is generally frowned upon. > If at all possible you should submit patches now or ASAP so > that Jeff and I have a reasonable chance to review them and > they can make their way into -mm for some testing BEFORE the > merge window opens. Yeah, but I'm still very much unfinished. It can: * detect the card * setup the IO window * setup the ISR * download helper firmware * download real firmware * react to some (not ALL!) interrupts But, for example, it can not: * send commands to the device (I'm close, but not yet there) * receive results from the device (dito) * receive data from the device (hey, even skb's are new to me) * send data to the device So, in short: the driver isn't yet usable in any way. And so I doubt you would want to see my current skeleton :-) I referred to the merge window because I doubt that I'll get my code early enought into a submitable form -- and if I can't it submit to YOU before the merge window closes, then you can't put it upstream either. And so it might be that the libertas_cs code will end up in 2.6.24, not 2.6.23. And Dan even mentioned 2.6.22, which is out-of-the-question, because a new driver is hardly a fix. So, my plan is to submit the driver (or the patchset for the driver) to either libertas-dev or wireless-dev as soon as I get my first association to an AP via it. We can than think if the driver should be added to some GIT tree. From then on I'll start sending incremental patches. Do you think that makes sense? - 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
