lkml.org 
[lkml]   [2008]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Oops report for the week preceding June 16th, 2008
    On Tue, 17 Jun 2008, Greg KH wrote:

    > On Tue, Jun 17, 2008 at 05:33:56PM +0200, Ingo Molnar wrote:
    > > IMO we are not learning and are repeating history once again, as the
    > > Nouveau situation is building up towards a similar "we didnt merge it in
    > > time" pain point. From kernel-2.6.25.6-24.fc8.src.rpm:
    > >
    > > -rw-r--r-- 1 root root 513639 2008-05-22 04:31 nouveau-drm.patch
    > >
    > > 39 files changed, 13960 insertions(+), 5 deletions(-)
    > >
    > > Nouveau has been started in 2006, about two years ago. It's a lot less
    > > painful (not the least it is a lot faster as well) if such things are
    > > developed gradually in mainline.
    >
    > Not to dispute your original claim of wanting to merge drivers earlier,
    > but a lot of the time, there are good reasons why the code doesn't get
    > merged.
    >
    > As recently pointed out by the nouveau driver authors on the xorg
    > mailing list, they don't want the driver to be added to the main
    > kernel.org tree yet as they feel that their userspace/kernelspace
    > inteface is not complete and will change in the future.

    That's the same reason the wireless drivers didn't get merged sooner, with
    the slight difference that they were waiting on the new 802.11 stack's
    interface to stabilize, rather than their own interface.

    On the other hand, it would be good if there were a way to include
    unstable APIs in the mainline kernel so that they could get some exposure
    before they're set in stone, and that would also eliminate that reason for
    keeping drivers out so long.

    -Daniel
    *This .sig left intentionally blank*


    \
     
     \ /
      Last update: 2008-06-17 20:47    [W:9.575 / U:0.636 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site