mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Arjan van de Ven <arjan@infradead.org>
Cc: david@lang.hm, "Altobelli, David" <david.altobelli@hp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"greg@kroah.com" <greg@kroah.com>
Subject: Re: [PATCH][resubmit] HP iLO driver
Date: Tue, 8 Jul 2008 09:14:08 +0200	[thread overview]
Message-ID: <20080708071408.GC1761@elf.ucw.cz> (raw)
In-Reply-To: <20080707214905.157be089@infradead.org>

On Mon 2008-07-07 21:49:05, Arjan van de Ven wrote:
> On Mon, 7 Jul 2008 21:41:41 -0700 (PDT)
> david@lang.hm wrote:
> > umm, by merging the code a you reveal a lot of what they are
> > attempting to keep secret. what's to stop someone from reading the
> > code and writing the documentation?
> > 
> > that really should be someone at HP if you don't want to publish the 
> > exising documentation (since you are submitting the code)
> 
> I think you're being quite unreasonable here.
> In Linux we accept well written drivers even if there is no hardware
> docs. Sure we prefer them to be available, but is has never been a

This is not well-written driver. This is a layer that provides access
to hardware from userspace - AFAICT. But we are not told what hardware
does, nor how to control it.

Imagine a PC speaker "driver" that has two functions:

* write this to port 0x60

* write this to port 0x64

...and you don't get docs for the pc speaker. Only think that can use
your "driver" is proprietary binary. (Actually, in this case you are
not even told it is a pc speaker.)

I don't think that's acceptable...
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2008-07-08  7:13 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 16:00 David Altobelli
2008-06-23 17:32 ` Pekka Enberg
2008-06-24  4:05   ` Altobelli, David
2008-06-24  2:45 ` FUJITA Tomonori
2008-06-24  3:40   ` Altobelli, David
2008-06-24  4:19     ` FUJITA Tomonori
2008-06-27 19:14 ` Pavel Machek
2008-07-06 20:03   ` Altobelli, David
2008-07-07 16:06     ` Pavel Machek
2008-07-07 17:37       ` Altobelli, David
2008-07-08  4:41         ` david
2008-07-08  4:49           ` Arjan van de Ven
2008-07-08  5:15             ` david
2008-07-08  7:14             ` Pavel Machek [this message]
2008-07-08  5:32           ` Ray Lee
2008-07-08  7:21         ` Pavel Machek
2008-07-08  7:38           ` Pavel Machek
2008-07-08 14:48             ` Altobelli, David
2008-07-08 21:50               ` Pavel Machek
2008-07-08 22:19                 ` Altobelli, David
2008-07-08 22:26                   ` Randy Dunlap
2008-07-08 23:10                     ` Altobelli, David
2008-07-08 23:40                       ` Pavel Machek
2008-07-08 22:34                   ` Alan Cox
2008-07-08 23:08                   ` Pavel Machek
2008-07-08  8:02           ` Bruno Prémont
2008-07-08 10:37             ` Pavel Machek
2008-07-09 11:11 Martin Knoblauch
2008-07-09 14:47 ` Altobelli, David
2008-07-09 15:15 Martin Knoblauch
2008-07-09 15:41 ` Altobelli, David
2008-07-09 15:18   ` Alan Cox
2008-07-09 16:15 ` Randy Dunlap

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=20080708071408.GC1761@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=arjan@infradead.org \
    --cc=david.altobelli@hp.com \
    --cc=david@lang.hm \
    --cc=greg@kroah.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

Powered by JetHome