All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:16:48 -0500	[thread overview]
Message-ID: <200701221916.48740.lenb@kernel.org> (raw)
In-Reply-To: <80b0b9460701220006p4b8dc3a6i9bf274a63f679036@mail.gmail.com>

On Monday 22 January 2007 03:06, Mohan Kumar Jami wrote:
> Hi,
> 
> Actually we need to retrieve the slot number (Using _SUN object) for
> PCI where it is inserted.
> But when we have gone through the DSDT table (SMBIOS version 2.3) , is
> not having _SUN entry.
> Is presence of _SUN is related to BIOS issue?
> Is there any difference between SMBIOS and ACPI bios?
> Is _SUN is optional in SMBIOS version 2.5
> I didn't clear  about
>                            Name (_SUN, 0x01)
> Is that 0x01 is slot number or not?

_SUN is a number that the system vendors thinks will
mean something to a human.  Eg it may correspond
to a number painted on the outside of a machine.

It  doesn't necessarily have anything to do with electrical
or logical slot numbers on a PCI bus, or any other bus
for that matter.

SMBIOS and ACPI BIOS are independent features of a BIOS.
You can have one, the other, both, or neither.

cheers,
-Len

  reply	other threads:[~2007-01-23  0:18 UTC|newest]

Thread overview: 9+ 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
2007-01-22  8:06       ` Mohan Kumar Jami
2007-01-23  0:16         ` Len Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-19 10:07 Mohan Kumar Jami
2007-01-19  9:47 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=200701221916.48740.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.