From: Arjan van de Ven <arjan@infradead.org>
To: Dan Carpenter <error27.lkml@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to read BIOS information
Date: Fri, 12 May 2006 22:02:19 +0200 [thread overview]
Message-ID: <1147464139.3173.58.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <b263e5900605100132m62cbfe16yda4213c97ae363e@mail.gmail.com>
On Wed, 2006-05-10 at 01:32 -0700, Dan Carpenter wrote:
> Arjan van de Ven:
> > But that's the best you can do.
> > (well you could grovel through the acpi tables just like the kernel
> > does, but you really don't want to do that from userspace)
>
> Obviously that would be tricky in this case. But in general it seems
> like writing an acpi table parser should be doable. Couldn't you
> just search through /dev/mem like dmidecode does? What's the
> difficult part?
the difficult part is in all the exceptions, quirks and special rules
the kernel uses (like "don't trust this table if acpi is off", and the
rules for acpi to not get enabled at runtime are highly complex and
continuously evolving).
next prev parent reply other threads:[~2006-05-12 20:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 14:14 Madhukar Mythri
2006-05-08 14:36 ` Richard Mittendorfer
2006-05-08 14:54 ` Madhukar Mythri
2006-05-08 14:57 ` Richard Mittendorfer
2006-05-08 14:53 ` Arjan van de Ven
2006-05-08 15:04 ` Madhukar Mythri
2006-05-08 15:07 ` Avi Kivity
2006-05-08 15:15 ` Arjan van de Ven
2006-05-08 15:28 ` Madhukar Mythri
2006-05-08 15:27 ` Erik Mouw
2006-05-09 5:23 ` Madhukar Mythri
2006-05-09 5:37 ` Jan-Benedict Glaw
2006-05-09 9:57 ` Erik Mouw
2006-05-09 11:03 ` Alan Cox
2006-05-09 12:29 ` Stefan Smietanowski
2006-05-09 12:51 ` Richard Mittendorfer
2006-05-09 13:18 ` Madhukar Mythri
2006-05-09 14:44 ` Roger Heflin
2006-05-08 15:15 ` Michal Piotrowski
2006-05-08 15:43 ` linux-os (Dick Johnson)
2006-05-10 8:32 ` Dan Carpenter
2006-05-12 20:02 ` Arjan van de Ven [this message]
2006-05-08 15:16 ` linux-os (Dick Johnson)
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=1147464139.3173.58.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=error27.lkml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®