public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Cox <adrian@humboldt.co.uk>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Erik Harrison <erikharrison@gmail.com>,
	davids@webmaster.com, eric@cisu.net,
	Christoph Hellwig <hch@lst.de>,
	linux-kernel@vger.kernel.org
Subject: Re: more files with licenses that aren't GPL-compatible
Date: Fri, 18 Jun 2004 10:08:31 +0100	[thread overview]
Message-ID: <1087549710.1547.14.camel@newt> (raw)
In-Reply-To: <20040616224949.GB7932@hh.idb.hist.no>

On Wed, 2004-06-16 at 23:49, Helge Hafting wrote:

> 1. don't _link_ the proprietary file into the kernel, ship firmware & logo
> as separate files along with the distro.  No problem.

USB serial drivers could be implemented in userspace given a 2.6 version
of Rogier Wolff's userspace serial patch:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0303.1/att-1075/01-patch-2.4.20.trueport-12-mrt

We currently have a lot of USB drivers in the kernel that could be 
implemented in userspace. I'm thinking of drivers/usb/image, misc, and
serial particularly. If there was a userspace API to do for video
capture what SANE does for scanners, drivers/usb/media would be mostly
unneeded as well.

If vendors noticed that this was possible, we'd probably get more binary
userspace drivers for USB devices. I pass no judgement here as to
whether this would be good or bad.

- Adrian Cox
Humboldt Solutions Ltd.



  reply	other threads:[~2004-06-18  9:13 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15 20:57 more files with licenses that aren't GPL-compatible Christoph Hellwig
2004-06-16  0:38 ` Eric
2004-06-16  1:27   ` Kyle Moffett
2004-06-16  4:11   ` David Schwartz
2004-06-16 20:34     ` Erik Harrison
2004-06-16 20:37       ` Christoph Hellwig
2004-06-16 21:21       ` David Schwartz
2004-06-16 22:45         ` Oliver Neukum
2004-06-16 23:45           ` David Schwartz
2004-06-17 14:09             ` Timothy Miller
2004-06-17 18:35               ` David Schwartz
2004-06-17 19:22                 ` Timothy Miller
2004-06-17  7:59           ` Christoph Hellwig
2004-06-17  8:43             ` Oliver Neukum
2004-06-17  8:47               ` Christoph Hellwig
2004-06-17 10:09             ` Martin Diehl
2004-06-17 10:14               ` Christoph Hellwig
2004-06-19 18:29               ` David Woodhouse
2004-06-17 14:04           ` Timothy Miller
2004-06-16 22:49       ` Helge Hafting
2004-06-18  9:08         ` Adrian Cox [this message]
2004-06-18 11:21           ` Kyle Moffett
  -- strict thread matches above, loose matches on Subject: below --
2004-06-16 23:47 Wichmann, Mats D
2004-06-17  1:18 ` Kyle Moffett
2004-06-18  6:29 Adam J. Richter
2004-06-17 15:44 ` Michael Poole
2004-06-17 17:09   ` Adam J. Richter
2004-06-17 19:14     ` Kyle Moffett
2004-06-17 20:51       ` Flavio Stanchina
2004-06-17 20:53         ` Kyle Moffett
2004-06-17 21:05         ` mdpoole
2004-06-17 21:10           ` Christoph Hellwig
2004-06-17 21:45           ` Flavio Stanchina
2004-06-17 20:22     ` mdpoole
2004-06-17 18:05 ` Greg KH
2004-06-17 19:54   ` Christoph Hellwig
2004-06-17 20:22     ` Greg KH
2004-06-17 20:30       ` Christoph Hellwig
2004-06-17 20:52         ` Greg KH
2004-06-18  6:56 Adam J. Richter
2004-06-18 11:09 ` mdpoole

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=1087549710.1547.14.camel@newt \
    --to=adrian@humboldt.co.uk \
    --cc=davids@webmaster.com \
    --cc=eric@cisu.net \
    --cc=erikharrison@gmail.com \
    --cc=hch@lst.de \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox