lkml.org 
[lkml]   [2008]   [Jul]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH][resubmit] HP iLO driver
On Tue 2008-07-08 14:48:00, Altobelli, David wrote:
> Pavel Machek wrote:
> > It probably does configure passwords on the management processor, for
> > example?
> >
> > And for that functionality, something like
> >
> > echo new_password > /sys/hpilo/admin/password
> >
> > would make sense, right? Except that your interface is more like "echo
> > ^%TEWFSGFSDF^%EW&^Tadmin^*&S^F&*SDYF*&SDYF*&YE*Wnew_password(*
> > &DF&S^DF*&DS^F*&S
> >> /dev/hpilo/d0ccb0", right? (And except that you consider exact
> > string to echo to change password "proprietary secret").
> >
> > We'd like to have the first interface, but unfortunately we do not
> > know enough about hpilo to even ask for better interface.
>
> Is the first interface really preferrable? How does that extend
> to commands that need to return data? Do we want to manage 30 different
> commands in the kernel? New functionality would require kernel
> updates.

Could you provide the list of commands (at least) so we can be more
concrete?

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...

(I assume management processors have pretty similar functionality
accross vendors, right?)

> 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.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html


\
 
 \ /
  Last update: 2008-07-08 23:51    [from the cache]
©2003-2011 Jasper Spaans