Messages in this thread | | | Date | Wed, 26 May 2004 22:47:30 +0200 | From | Francois Romieu <> | Subject | r8169 backport for 2.4.27-pre3 (was: Re: nforce2 keeps crashing with 2.4.27pre3) |
| |
Jeff Garzik <jgarzik@pobox.com> : [...] > I prefer to have the 2.4 and 2.6 drivers as close as possible to each > other, to reduce the maintenance burden. > > If the mainline r8169.c looks stable, then I would take that source and > backport it to 2.4.x.
Imho 2.6.6 seems a good candidate: - most of it has been fixed/tested for a few months before it was integrated; - to my surprize, it did not trigger a storm of bug reports after its integration; - its late features have no strong equivalent in 2.4 and even if _less_ tested, they have been tested and are isolated/simple (knock on wood). - the previous 2.4.x backport which were based on the same tree seemed sane.
I have made a single patch for it against 2.4.27-pre3: http://www.fr.zoreil.com/people/francois/misc/20040526-2.4.27-pre3-r8169.c-stable.patch
The relevant serie of patches is available at: http://www.fr.zoreil.com/linux/kernel/2.4.x/2.4.27-pre3-a
rsync does not crash, it survives link removal, packet storm and so (though it will complain from excess work in interrupt context as the patch does not include napi nor latest link/ethtool goodies). So I hope nothing trivially broken went in.
When you want this serie submitted by mail, just ask.
-- Ueimor - 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/
| |