mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, "Hans J. Koch" <hjk@linutronix.de>
Subject: Re: [PATCH 2/3] UIO: Documentation
Date: Wed, 08 Aug 2007 18:12:34 -0400	[thread overview]
Message-ID: <14166.1186611154@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 08 Aug 2007 23:36:00 +0200." <9a8748490708081436g23c8f01cga585d6612b380f16@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]

On Wed, 08 Aug 2007 23:36:00 +0200, Jesper Juhl said:

> Do we really want this?
> 
> In my oppinion we run the risk here of encouraging behaviour akin to
> what NVidia is doing - release a small kernel "glue" module and then
> keep the driver proper in a binary blob (in userspace, but still a
> binary blob).
> If the company goes out of business and take their driver source with
> them then users are left with a useless, un-debugable, un-maintainable
> binary blob.
> Don't we instead want to encourage/pressure people to release specs
> and/or source code for their hardware/drivers so open, modifiable
> drivers can be written?
> 
> This opens the door for people to start writing closed drivers. In the
> long run that seems to me like a bad deal for our users.

On the other hand, given that we've always said that closed-source stuff in
userspace is OK, the only way to not let *that* horse out of the barn is to
not merge UIO at all.

If you have UIO in the kernel talking to stuff in userspace, you're going to
have to deal with closed-source stuff at the userspace end of the pipe.

Unless somebody can come up with some great feat of sophistry to avoid that?

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2007-08-08 22:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 23:23 [GIT PATCH] UIO patches for 2.6.22 Greg KH
2007-07-18 23:26 ` [PATCH 1/3] UIO: Add the User IO core code Greg Kroah-Hartman
2007-07-18 23:26   ` [PATCH 2/3] UIO: Documentation Greg Kroah-Hartman
2007-07-18 23:26     ` [PATCH 3/3] UIO: Hilscher CIF card driver Greg Kroah-Hartman
2007-07-19 16:33       ` Jan Engelhardt
2007-07-19 19:28         ` Hans-Jürgen Koch
2007-07-19 20:02           ` Jan Engelhardt
2007-07-19 20:24             ` Hans-Jürgen Koch
2007-08-08 21:36     ` [PATCH 2/3] UIO: Documentation Jesper Juhl
2007-08-08 22:12       ` Valdis.Kletnieks [this message]
2007-08-08 23:03         ` Jesper Juhl
2007-08-09  7:19           ` Greg KH
2007-08-09 16:50             ` Jesper Juhl
2007-08-08 23:40         ` Alan Cox
2007-08-09 12:29           ` Hans-Jürgen Koch
2007-08-09 14:09             ` Alan Cox
2007-08-09 13:02         ` Hans-Jürgen Koch
2007-08-09 14:12           ` Alan Cox
2007-08-09 15:23             ` Hans-Jürgen Koch
2007-08-09  7:41       ` Hans-Jürgen Koch
  -- strict thread matches above, loose matches on Subject: below --
2007-05-08 14:04 [GIT PATCH] UIO patches for 2.6.21 Greg KH
2007-05-08 14:08 ` [PATCH 1/3] UIO: Add the User IO core code Greg Kroah-Hartman
2007-05-08 14:08   ` [PATCH 2/3] UIO: Documentation Greg Kroah-Hartman
2007-04-27 22:49 [GIT PATCH] UIO patches for 2.6.21 Greg KH
2007-04-27 22:50 ` [PATCH 1/3] UIO: Add the User IO core code Greg Kroah-Hartman
2007-04-27 22:50   ` [PATCH 2/3] UIO: Documentation Greg Kroah-Hartman
2007-05-01 23:42     ` Randy Dunlap
2007-05-02  8:41       ` Hans-Jürgen Koch
2007-05-02 20:52         ` Randy Dunlap
2007-05-02 22:00           ` Hans-Jürgen Koch
2007-05-02 23:37             ` Randy Dunlap
2007-05-03  5:37               ` Greg KH
2007-05-03  6:39                 ` Hans-Jürgen Koch
2007-05-04  9:37                   ` Hans-Jürgen Koch
2007-05-07 17:46                     ` Randy Dunlap
2007-05-07 20:01                       ` Hans-Jürgen Koch

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=14166.1186611154@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=jesper.juhl@gmail.com \
    --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

all inboxes | Powered by JetHome®