From: Pavel Machek <pavel@suse.cz>
To: "Altobelli, David" <david.altobelli@hp.com>
Cc: "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:21:52 +0200 [thread overview]
Message-ID: <20080708072152.GD1761@elf.ucw.cz> (raw)
In-Reply-To: <CF70AA892F109448AEA269483B3A983903BB8CEA25@G1W1215.americas.hpqcorp.net>
On Mon 2008-07-07 17:37:18, Altobelli, David wrote:
> Pavel Machek wrote:
> > Hi!
> >
> >>>> A driver for the HP iLO/iLO2 management processor, which allows
> >>>> userspace programs to query the management processor. Programs can
> >>>> open a channel to the device (/dev/hpilo/dXccbN), and use this to
> >>>> send/receive queries.
> >>>
> >>> What kind of queries? Is there documentation somewhere?
> >>
> >> Generally, it can get data out of the management processor - things
> >> like basic iLO configuration (users, nic, etc), handle SNMP traffic,
> >> flashing iLO, and some others.
> >>
> >> Unfortunately, there isn't yet any available documenation.
> >
> > Ok, I guess we should have documentation "what does it do" and "what
> > protocol does it speak" before we can think about merging.
>
> I really hope that isn't the case.
Telling us "what does it do" seems like good start.
> However, I do think there is value in merging the driver without docs.
> Having drivers in tree is often stated as a goal, because of the obvious
> security and API/ABI disadvantages to out of tree drivers.
You know, we'd prefer to have kernel<->user ABI documented. With this
driver... we don't.
What does /dev/hpilo/* do? Beep speakers? Control fans? Launch atomic
bombs? What will happen on cat /bin/bash > /dev/hpilo/dXccbN? Does
that depend on concrete machine? Is it acceptable for this
functionality not to be abstracted out? (Kernel should provide hw
abstraction, right?)
> If this can't be merged, then we continue to ship an out of tree driver,
> which no one (us, distros, customers) likes. We pester our partners to
> support this driver, or include it, or what have you. We get slowly
> out of date, and bugs creep in, or our package breaks on upstream kernels.
> To me, it seems like merging the driver is the better path.
Docs for kernel<->user ABI does not seem like too much to ask.
If you wrote a driver, I don't think it is unreasonable for me to ask
"how to use that driver".
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-07-08 7:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 16:00 [PATCH][resubmit] HP iLO driver 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
2008-07-08 5:32 ` Ray Lee
2008-07-08 7:21 ` Pavel Machek [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20080708072152.GD1761@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=david.altobelli@hp.com \
--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