LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "J.R. Mauro" <jrm8005@gmail.com>
Cc: Greg KH <gregkh@suse.de>, Moritz Muehlenhoff <jmm@debian.org>,
	linux-kernel@vger.kernel.org
Subject: Re: staging: me4000 and relation to other data acquisition devices
Date: Fri, 31 Oct 2008 08:00:38 -0700	[thread overview]
Message-ID: <20081031150037.GA9314@kroah.com> (raw)
In-Reply-To: <3aaafc130810300842h5a764903i61bfa5817c0fb493@mail.gmail.com>

On Thu, Oct 30, 2008 at 11:42:36AM -0400, J.R. Mauro wrote:
> On Thu, Oct 30, 2008 at 11:23 AM, Greg KH <gregkh@suse.de> wrote:
> > On Thu, Oct 30, 2008 at 10:25:30AM -0400, J.R. Mauro wrote:
> >> Ok. I emailed a few of them. The ones I omitted either didn't have a
> >> clear homepage/maintainer, had already sent a patch to the kernel, or
> >> explicitly stated no intentions of going into mainline.
> >
> > Which ones were in the last 2 categories?
> 
> The Alix driver seemed to be sent in already: http://lkml.org/lkml/2008/8/19/279
> 
> The ov51x-jpeg driver's homepage mentions that there is a driver
> already, but it doesn't do jpeg compression, since that kind of
> shouldn't be done in the kernel. The out-of-tree driver does do the
> compression in the kernel, but the author doesn't think it should go
> into mainline. Or something like that.
> 
> >
> >> Maybe you could send me the Spreadsheet O' Drivers if you need more help?
> >
> > Yeah, I think I'll move this to a google docs file or somehow merge it
> > with the information on the linuxdriverproject.org wiki.  Give me a few
> > days.
> 
> A google spreadsheet would be great for me. Maybe you could do both?
> 
> >
> >> I've also been wondering: should we contact the maintainers of the big
> >> distros and make them aware of staging and have them work with us to
> >> get whatever out-of-tree stuff they have more centralized? I don't
> >> know if it's a good idea, but it could be. And if it is, I have no
> >> idea where to start.
> >
> > I've already looked at what the following distros include in their
> > kernel package:
> >        - Fedora
> >        - openSUSE
> >        - Ubuntu
> > so I have them on my list, and is where I took a number of the existing
> > staging drivers from.
> >
> > If you could poke around other distro's kernels (like Mandrake and any
> > other you can think of) and find out what they include, that would e
> > great.
> 
> Ok. I'll talk to distros not mentioned above and hopefully add
> anything I find to the forthcoming spreadsheet.

I've gone through the suse, fedora, ubuntu, and gentoo kernels and added
everything that I have found (gentoo had a _lot_ of external kernel
modules in their packaging system) to the wiki at:
	http://www.linuxdriverproject.org/twiki/bin/view/Main/OutOfTreeDrivers

I also dumped all of my spreadsheet information into here as well, as it
didn't make sense to try to categorize it that way.

So, feel free to clean up, and organize that wiki page with whatever
else you have found.  Some of it still is not organized (like the huge
list at the end of the page) and there might be duplicates as well.

Thanks a lot for helping out.

greg k-h

  reply	other threads:[~2008-10-31 15:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 15:49 Shawn Bohrer
2008-10-28 16:34 ` Greg KH
2008-10-28 17:33   ` Randy Dunlap
2008-10-28 18:14     ` Greg KH
2008-10-29 15:12       ` Wolfgang Beiter
2008-10-30  0:02         ` Greg KH
2008-10-29 18:57       ` Moritz Muehlenhoff
2008-10-30  0:37         ` J.R. Mauro
2008-10-30  0:46           ` Richard Holden
2008-10-30  1:42           ` Greg KH
2008-10-30 14:25             ` J.R. Mauro
2008-10-30 15:23               ` Greg KH
2008-10-30 15:42                 ` J.R. Mauro
2008-10-31 15:00                   ` Greg KH [this message]
2008-10-31 15:10                     ` J.R. Mauro
2008-10-30  1:43         ` Greg KH
2008-10-29 17:37   ` Shawn Bohrer
2008-10-30  0:04     ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081031150037.GA9314@kroah.com \
    --to=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=jmm@debian.org \
    --cc=jrm8005@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: staging: me4000 and relation to other data acquisition devices' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).