From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Mukund JB." <mukundjb@esntechnologies.co.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel interrupts disable at user level - RIGHT/ WRONG - Help
Date: Mon, 19 Dec 2005 17:42:49 +0000 [thread overview]
Message-ID: <1135014170.6051.19.camel@localhost.localdomain> (raw)
In-Reply-To: <3AEC1E10243A314391FE9C01CD65429B223248@mail.esn.co.in>
On Llu, 2005-12-19 at 17:45 +0530, Mukund JB. wrote:
> Dear Kernel Developers,
>
> I have a requirement of getting the CMOS details at the user level. I have identified the interfaces as /dev/nvram & /dev/rtc.
> But, the complete CMOS details are available to the user Applications as the driver does not provide the suitable interface to get the complete CMOS details.
Then you'll need to enhance the nvram or rtc driver to support the extra
bits you need. What doesn't it provide access to that you require >
next prev parent reply other threads:[~2005-12-19 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 12:15 Kernel interrupts disable at user level - RIGHT/ WRONG - Help Mukund JB.
2005-12-19 13:51 ` linux-os (Dick Johnson)
2005-12-19 17:42 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-20 6:57 Mukund JB.
2005-12-20 7:09 ` Dave Jones
2005-12-20 9:02 Mukund JB.
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=1135014170.6051.19.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mukundjb@esntechnologies.co.in \
/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