From: David Greaves <david@dgreaves.com>
To: Doug Warzecha <Douglas_Warzecha@dell.com>
Cc: michael_e_brown@dell.com, matt_domsch@dell.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.13-rc6] dcdbas: add Dell Systems Management Base Driver with sysfs support
Date: Thu, 25 Aug 2005 14:44:56 +0100 [thread overview]
Message-ID: <430DCB58.1090107@dgreaves.com> (raw)
In-Reply-To: <20050820225052.GA5042@sysman-doug.us.dell.com>
Doug Warzecha wrote:
>This patch adds the Dell Systems Management Base Driver with sysfs support.
>
>This patch incorporates changes based on comments from the previous posting.
>
>Summary of changes:
>
>* Changed permissions on sysfs files so that only owner can read.
>* Changed to use __uNN/__sNN types in structs.
>* smi_data_write will grow smi_data_buf if needed.
>* Renamed struct callintf_cmd to struct smi_cmd.
>* Renamed callintf_smi to smi_request.
>* Added 2 more supported values that were requested in smi_request_store.
>* Hold rtc_lock across SMI in host_control_smi.
>
>
>
Hi Doug
I've followed this thread as best I can and I have a query...
I have a Dell SC420
Is there a way (based around this patch) to allow users to enable and
set the auto-power-on BIOS feature?
(ie tell the BIOS to power on at 3:40am, power the system down, watch it
power up at 3:40am)
Normally I'd use 'nvram-wakeup' but it dosen't understand the Dell BIOS.
If so what I'd _like_ to do is send a patch to nvram-wakeup that tests
for this capability and uses it if it's there.
David
--
next prev parent reply other threads:[~2005-08-25 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 22:50 Doug Warzecha
2005-08-22 9:12 ` Pavel Machek
2005-08-25 13:44 ` David Greaves [this message]
2005-08-25 14:16 ` Michael E Brown
2005-08-25 2:00 Doug Warzecha
2005-08-25 3:09 ` Chris Wedgwood
2005-08-25 15:02 ` Doug Warzecha
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=430DCB58.1090107@dgreaves.com \
--to=david@dgreaves.com \
--cc=Douglas_Warzecha@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt_domsch@dell.com \
--cc=michael_e_brown@dell.com \
/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
Powered by JetHome