From: Randy Dunlap <rdunlap@xenotime.net>
To: "Altobelli, David" <david.altobelli@hp.com>
Cc: 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: Tue, 8 Jul 2008 15:26:31 -0700 [thread overview]
Message-ID: <20080708152631.715092c5.rdunlap@xenotime.net> (raw)
In-Reply-To: <CF70AA892F109448AEA269483B3A983903BB8CF552@G1W1215.americas.hpqcorp.net>
On Tue, 8 Jul 2008 22:19:18 +0000 Altobelli, David wrote:
> Pavel Machek wrote:
> > Could you provide the list of commands (at least) so we can be more
> > concrete?
>
> Unfortunately, I don't believe that I can. We reviewed this internally,
> and the question of documentation was raised. The hardware teams did
> not approve disseminating the ABI. To be clear, we understand what we
> are doing by releasing the driver as GPLv2, the actual functionality
> of communicating with iLO was okayed for release. But releasing the
> specifics of what we can send was not approved.
Can you at least point people to the user manual etc. so they can see
what commands/functionality are/is available?
> > Yes, I believe we do want to have 30 commands it kernel, because it
> > will allow same userland to work on HP machines, AMD machines, etc...
>
> We sell AMD :)
>
> > (I assume management processors have pretty similar functionality
> > accross vendors, right?)
>
> I can't speak for other vendors.
>
> >> It seems much cleaner to keep the kernel interface simple and opaque
> >> (ie read/write), and handle the details of the commands in user
> >> space. From my limited understanding, I thought that was a common
> >> goal here: move what you can to userspace.
> >
> > We are not _that_ extreme. Yes, keep stuff in userspace is important,
> > but "hide hardware differences" is more important goal.
>
> That seems like a larger question/goal. Giving users some consistent
> interfaces to do stuff would be nice, but I'd really like to handle this
> driver on its own.
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
next prev parent reply other threads:[~2008-07-08 22:26 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
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 [this message]
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=20080708152631.715092c5.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--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®