From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: Out of tree GPL serial tty driver help? Date: Fri, 26 Apr 2013 08:19:05 -0700 Message-ID: <20130426151905.GA27340@kroah.com> References: <51781A19.5030707@compro.net> <1366926071.3452.17.camel@thor.lan> <517A79E1.8060504@compro.net> <1366983913.3452.33.camel@thor.lan> <517A8EF1.8040006@compro.net> <20130426143526.GA15132@kroah.com> <517A98D6.2020701@compro.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-pb0-f49.google.com ([209.85.160.49]:44324 "EHLO mail-pb0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751381Ab3DZPTI (ORCPT ); Fri, 26 Apr 2013 11:19:08 -0400 Received: by mail-pb0-f49.google.com with SMTP id rp2so1191781pbb.36 for ; Fri, 26 Apr 2013 08:19:08 -0700 (PDT) Content-Disposition: inline In-Reply-To: <517A98D6.2020701@compro.net> Sender: linux-serial-owner@vger.kernel.org List-Id: linux-serial@vger.kernel.org To: Mark Hounschell Cc: Peter Hurley , linux-serial@vger.kernel.org, Mark Hounschell On Fri, Apr 26, 2013 at 11:10:14AM -0400, Mark Hounschell wrote: > >Also, any reason why these drivers aren't in the main kernel tree? If > >they were, all of this work would have been done for you :) > > > > Yes, I wish they were in the kernel. I've had to maintain them since > the 2.6 days because Digi just won't do it and their cards do what > we need quite well and are still current products. Ya, you can buy a > brand new one but the latest kernel supported is 2.6. I think Digi > at one point long ago may have tried the "in kernel" route but you > probably know more about that than I do. > > Since 2.6, the maintenance on these hasn't been to bad, until udev > came along. But I guess after 3.4 the tty layer is going through > quite some changes that I have yet to understand. And there will be lots more changes happening to it in the future. Why not submit the drivers now (after you get them working)? > Actually, we also have 3-4 of our own "out of kernel" GPL drivers > that I would love to see in the kernel. They are mature and only > require changes when something in the kernel changes. That's another > story though. Why not submit those as well? What's keeping you from doing this? thanks, greg k-h