lkml.org 
[lkml]   [2008]   [Feb]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...
    On Mon, Feb 18, 2008 at 01:08:33PM +0100, Andi Kleen wrote:
    > Greg KH <greg@kroah.com> writes:
    > >
    > > If Jeff does that, I still can't drop those PCI functions from the PCI
    > > core, which I desperatly want to do as they do not play nice with modern
    > > systems (meaning hotplug...).
    > >
    > > So either way, I think his patches should go in.
    >
    > Merging essentially untested patches does not seem like a good strategy.
    > And there is definitely still a large ISDN user base too.
    Only issue seems that this large ISDN user base is not very active
    in respect to Linux driver development.
    Or at least not judging from the missing responses to their
    mailing list and the limited traffic on said mailing list.

    Reading the isdn4linux it is obvious that the way forward are the
    mISDN code base so maybe that explains why noone steps up and
    test the patches of Jeff's.

    If noone in the isdn community step up and take some responsibility
    for the current isdn drivers in Linux then we should just delete them.
    If anyone cares they can always be forwardported or even better we can
    integrate the much more flexible mISDN solution.

    > My personal guess is that there are far more ISDN users than (non cardbus)
    > PCI/PCI-e hotplug users.

    My guess is that very very few uses ISDN in combination with a recent kernel.
    Hmm, wonder if it is more fun hacking isdn drivers than kbuild
    stuff and section mismatches ;-)

    Sam


    \
     
     \ /
      Last update: 2008-02-19 09:53    [W:2.768 / U:0.032 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site