>1) Most Wireless LAN driver live outside the kernel. So, their
>evolution is somewhat decoupled to the kernel, so the earlier the
>patch goes it the better it is for those.
>
As you may have gathered from my last email, this is a bit annoying when
trying to find and stabalize a driver for a card you just got :)
> 2) David Gibson, maintainer of the Orinoco driver, told me
>that he would merge my new-API orinoco patches in his driver only when
>the new API would be in 2.4.x (as you may have noticed, he hasn't
>updated 2.5.X for a while). Chicken and Eggs.
>
Does that mean orinoco updates are coming for 2.5.x?
Any idea if the other drivers are getting updates too, like airo?
>I'm open to suggestions and will do what's best for
>everybody. What other people think ?
> But I feel now is a good time (as it seem that 2.4.19 will
>have to go through some stabilisation process).
>
My standard rule of thumb is turning out to be, deploy something
2.4.x-worthy in 2.5.x, wait a while, and then deploy it in 2.4.x. I
have no particular opinion about whether your patch should go in -right
now- but it seems like a fair patch for 2.4.x sooner or later.
Jeff
-
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/