http://kerneltrap.org/node/view/3980
Marcelo Tosatti [interview] released 2.4.28-pre4 with few changes since -pre3 a month ago [story], "it contains a number of driver updates (pcnet, e1000, gdth, prism54), a network update from David, few more gcc3.4 warning fixes." He noted that no more new features are planned for the 2.4 stable kernel, "from now on [I] can change only what is necessary and let the 2.4 tree [rest] in peace :)"
What should be our policy toward 2.4? For example if 2.4 is now closed should we implement the drm-core model for it? What about new drivers? If 2.4 is closed these aren't going to be accepted.
This is a different question than fixing the drivers that are already in 2.4. We should still do that as we find problems.
Given that, it seems reasonable to not implement drm-core for 2.4. If we need to apply bug fixes to 2.4, we'll just have to figure out how to back-port them to the old arch.
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
