From: "david bulkow" <dbulkow@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] ACPI
Date: Wed, 12 Jul 2006 21:26:05 -0400 [thread overview]
Message-ID: <2d5a784f0607121826k293267abq63b24333a4f01fa1@mail.gmail.com> (raw)
In-Reply-To: <44B46AF0.9070901@lanl.gov>
On 7/11/06, Ronald G Minnich <rminnich@lanl.gov> wrote:
> it would be great if you would (hint).
>
> And not do it the way linux did it (hint, hint).
>
I guess I walked into both of these :-)
Using the mptable code for clues, I have located and decoded the first
couple ACPI tables. Before digging in I was hoping to find someone
with which to discuss potential directions.
I see this project expanding into three areas:
- decode the tables of interest
- process AML so I can find most of the tables and eventually handle
more than interrupt setup and processor identification
- tie all this into the kernel boot sequence
As to the first item I seek clarification. Should I follow the
example in mp.[ch] and map C structures over each ACPI table or should
I decode them in a fashion similar to 9P message conversion?
Since this is a rather large project, should I submit code as I
complete sections of it, not breaking the kernel of course, or should
I package the whole thing up at the end?
prev parent reply other threads:[~2006-07-13 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 2:57 david bulkow
2006-07-12 3:22 ` Ronald G Minnich
2006-07-13 1:26 ` david bulkow [this message]
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=2d5a784f0607121826k293267abq63b24333a4f01fa1@mail.gmail.com \
--to=dbulkow@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).