From: david@lang.hm
To: Arjan van de Ven <arjan@infradead.org>
Cc: "Altobelli, David" <david.altobelli@hp.com>,
Pavel Machek <pavel@suse.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"greg@kroah.com" <greg@kroah.com>
Subject: Re: [PATCH][resubmit] HP iLO driver
Date: Mon, 7 Jul 2008 22:15:21 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0807072212450.12950@asgard.lang.hm> (raw)
In-Reply-To: <20080707214905.157be089@infradead.org>
On Mon, 7 Jul 2008, 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)
>>
>
> Hi,
>
> 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
> requirement, nor should it. I know that some other open source OSes do
> demand this, but Linux is not one of them. We explicitly accept drivers
> written with NDA docs, or drivers written by vendors.
> It's the code that talks.
> (and well written code is often worth more than the shoddy docs that we
> sometimes get)
sorry, I did not mean to imply that they code cannot be accepted, just to
point out that the 'secrets' that they are trying to protect are revealed
by the code anyway, and that someone will eventually need to do the work
to reverse-engineer some portion of the documentations, and that it's
best if it could come from the folks submitting it when they have the
origional documentation.
a driver with no docs is better then a closed source driver, but is not
nearly as good as a driver with docs.
David Lang
next prev parent reply other threads:[~2008-07-08 5:14 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 [this message]
2008-07-08 7:14 ` Pavel Machek
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=alpine.DEB.1.10.0807072212450.12950@asgard.lang.hm \
--to=david@lang.hm \
--cc=arjan@infradead.org \
--cc=david.altobelli@hp.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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®