From: Len Brown <lenb@kernel.org>
To: Mohan Kumar Jami <mohan124885@gmail.com>
Cc: Bruno Ducrot <ducrot@poupinou.org>, linux-acpi@vger.kernel.org
Subject: Re: ACPI _SUN
Date: Mon, 22 Jan 2007 02:00:32 -0500 [thread overview]
Message-ID: <200701220200.32798.lenb@kernel.org> (raw)
In-Reply-To: <80b0b9460701212125h263a625cr1a8b43853a444591@mail.gmail.com>
On Monday 22 January 2007 00:25, Mohan Kumar Jami wrote:
> Hi
>
>
> 1) I saw the _SUN object in DSDT table as "Name (_SUN, 0x01)", is this
> means that this slot number is fixed or is that going to change at
> run-time.
fixed.
> 2) Is there any other way to get the PCI slot number using ACPI tables?
PCI doesn't have slot numbers, it has device numbers.
you can get these from PCI (eg lspci),
SUN is supposed to be some sort of human-friendly number --
eg the number that is printed on the motherboard on the chassis.
> 3) How do I know that a perticular slot is populated, in user space.
> Is there any system call to know that?
no
> 4) Is it possible to override the AML, if yes can you please tell us
> how to do it?
yes.
you can replace your DSDT either by loading a new one in the initrd
or compiling a new one into the kernel.
Exactly what are you thing to do?
-Len
>
>
> On 1/19/07, Bruno Ducrot <ducrot@poupinou.org> wrote:
> > On Fri, Jan 19, 2007 at 03:26:26PM +0530, Mohan Kumar Jami wrote:
> > > Hi,
> > >
> > > I have couple of questions related to _SUN object.
> > >
> > > 1) Is _SUN object be present DSDT tables?
> >
> > They are defined under DSDT or RSDT tables as any other ACPI objects
> > populating the ACPI namespace.
> >
> > > 2) How this DSDT table get updated?
> >
> > They can't be updated.
> >
> > > 3) Is DSDT table is static binary file or it can be dynamically updated?
> >
> > A DSDT table is not a static binary file. On most i386 or amd64
> > architectures, DSDT and SSDT are part of the BIOS.
> > The BIOS uncompressed and copyied them into main memory at the
> > POST stage since the ROM is too limited in size.
> >
> > > 4) Who will update the DSDT tables?
> >
> > By the customer via BIOS updates obtained from the vendor.
> >
> > Cheers,
> >
> > --
> > Bruno Ducrot
> >
> > -- Which is worse: ignorance or apathy?
> > -- Don't know. Don't care.
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2007-01-22 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 9:56 ACPI _SUN Mohan Kumar Jami
2007-01-19 16:37 ` Bruno Ducrot
2007-01-19 19:51 ` Len Brown
2007-01-22 5:25 ` Mohan Kumar Jami
2007-01-22 7:00 ` Len Brown [this message]
2007-01-22 8:06 ` Mohan Kumar Jami
2007-01-23 0:16 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2007-01-19 10:07 Mohan Kumar Jami
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=200701220200.32798.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=ducrot@poupinou.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mohan124885@gmail.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;
as well as URLs for NNTP newsgroup(s).