Alan Jenkins wrote:
Are you concerned about the module loading as well, or only "ifconfig up" as quoted above?
I'm not into the technical details. The argumentation is: "Somebody put it there, probably there's a reason for it." So if we care about backward compatibility with mixed systems, we should research when the quirks became obsolete.
Why do we assume 2.6.30 is ok? Is there an important feature/bugfix in it? Or is this more of a heuristic, in that no-one is able (or willing?) to run etch userspace on such a new kernel?
The choice was mostly arbitrary (in my personal experience, ath5k didn't cause any troubles after 2.6.30.1). I'm clearly not competent, here.
Kind regards, Thiemo -- +-----------------------------------+--------------------------+ | Dipl.-Phys. Thiemo Nagel | | | Technische Universitaet Muenchen | Room PH1 3276 | | Physik-Department E18 | | | James-Franck-Strasse | Phone +49 89 289-12379 | | D-85747 Garching | Fax +49 89 289-12570 | +-----------------------------------+--------------------------+ _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
