Especially that there are so many driver to choose from, and
each is broken in some unique way.
> > 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?
I asked him a couple of times, but so far nothing. He is
working hard on various issues in the driver.
> Any idea if the other drivers are getting updates too, like airo?
I think the CVS has a new version, including change to the
monitoring mode, but airo list is pretty quiet lately. airo.c is
pretty stable and bug free, so updates are not critical. I still need
to finish to convert it to the new API.
> 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.
Yes, you are right, it has been in 2.5.X for only two months,
which is quite short.
> Jeff
Have fun...
Jean
-
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/