lkml.org 
[lkml]   [2005]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [RFC][PATCH 2.6.13-rc6] add Dell Systems Management Base Driver (dcdbas) with sysfs support
Date
On Aug 15, 2005, at 19:38:49, Doug Warzecha wrote:
> On Mon, Aug 15, 2005 at 04:23:37PM -0400, Kyle Moffett wrote:
>> Why can't you just implement the system management actions in the
>> kernel
>> driver?
>
> We want to minimize the amount of code in the kernel and avoid
> having to
> update the driver each time a new system management command is added.

One of the recent trends in kernel driver development is to make as much
as possible accessible through standard tools (like with echo and cat
via
sysfs).

> The libsmbios project is being updated to use this code. http://
> linux.dell.com/libsmbios/main/. Using the libsmbios code, you
> will be able to set all of the options in BIOS F2 screen from Linux
> userspace. Also, libsmbios is looking at implementing a few other
> things
> like fan status. Libsmbios is 100% open-source (OSL/GPL dual
> license).

From my point of view, this driver could use sysfs almost entirely
and put
all of the hardware-manipulation code completely in kernel space, along
with the hardware detection code. You could have plain-text files in
/sys/bus/platform/dellbios/ that have all of the BIOS F2 options
accessible
to the admin from the command line, without special tools. (You could
always add an extra program that presents a BIOS-like interface)

> The power cycle feature of the system powers off the system for a few
> seconds and then powers the system back on without user intervention.
> shutdown() and reboot() don't provide that feature.

Please ensure that the code is only run on reboot (and maybe halt), but
definitely not in the poweroff code.

>> What exactly is smi_type used for? Please provide better
>> documentation
>> on how to use this and what it does.
>
> The method of generating a host control SMI is not exactly the same
> for
> each PowerEdge system listed in dcdbas.txt. host_control_smi_type
> tells
> the driver how to generate the host control SMI for the system in use.
> I'll update dcdbas.txt with the SMI type value associated with the
> systems
> listed in that file.

This is an _excellent_ reason why more of this should be in the kernel.
What happens if the wrong SMI is used? Shouldn't it be relatively easy
for the kernel to determine the correct SMI itself?

Thanks for your hard work!

Cheers,
Kyle Moffett

--
Unix was not designed to stop people from doing stupid things,
because that
would also stop them from doing clever things.
-- Doug Gwyn


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-08-16 03:47    [W:0.055 / U:0.332 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site