* fadt.boot_flags.MSI_not_supported
@ 2006-09-28 0:14 Brown, Len
2006-09-28 4:23 ` fadt.boot_flags.MSI_not_supported Randy Dunlap
2006-09-28 22:45 ` fadt.boot_flags.MSI_not_supported Andi Kleen
0 siblings, 2 replies; 4+ messages in thread
From: Brown, Len @ 2006-09-28 0:14 UTC (permalink / raw)
To: linux-acpi
sifting through ACPI 3.0a I just noticed a bit (3)
in the FADT boot_flag to indicate the platform
does not support MSI.
Has anybody noticed fadt.boot_flags bit 3 set on their box?
thanks,
-Len
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: fadt.boot_flags.MSI_not_supported
2006-09-28 0:14 fadt.boot_flags.MSI_not_supported Brown, Len
@ 2006-09-28 4:23 ` Randy Dunlap
2006-09-28 4:43 ` fadt.boot_flags.MSI_not_supported Len Brown
2006-09-28 22:45 ` fadt.boot_flags.MSI_not_supported Andi Kleen
1 sibling, 1 reply; 4+ messages in thread
From: Randy Dunlap @ 2006-09-28 4:23 UTC (permalink / raw)
To: Brown, Len; +Cc: linux-acpi
On Wed, 27 Sep 2006 20:14:58 -0400 Brown, Len wrote:
> sifting through ACPI 3.0a I just noticed a bit (3)
> in the FADT boot_flag to indicate the platform
> does not support MSI.
>
> Has anybody noticed fadt.boot_flags bit 3 set on their box?
Would we observe that in kernel boot messages or by using
acpidump?
---
~Randy
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: fadt.boot_flags.MSI_not_supported
2006-09-28 4:23 ` fadt.boot_flags.MSI_not_supported Randy Dunlap
@ 2006-09-28 4:43 ` Len Brown
0 siblings, 0 replies; 4+ messages in thread
From: Len Brown @ 2006-09-28 4:43 UTC (permalink / raw)
To: Randy Dunlap; +Cc: linux-acpi
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
On Thursday 28 September 2006 00:23, Randy Dunlap wrote:
> On Wed, 27 Sep 2006 20:14:58 -0400 Brown, Len wrote:
>
> > sifting through ACPI 3.0a I just noticed a bit (3)
> > in the FADT boot_flag to indicate the platform
> > does not support MSI.
> >
> > Has anybody noticed fadt.boot_flags bit 3 set on their box?
>
> Would we observe that in kernel boot messages or by using
> acpidump?
Using the acpitbl script attached:
# cat /proc/acpi/fadt |acpitbl |grep IAPC_BOOT_FLAGS
IAPC_BOOT_FLAGS: 0x0003
(this example has bit 0 and 1 set, we are looking for bit 3).
If you have an acpidump output, you can do it this way
$ acpixtract FACP acpidump.out | acpitbl | grep IAPC_BOOT_FLAGS
IAPC_BOOT_FLAGS: 0x0003
[-- Attachment #2: acpitbl --]
[-- Type: application/x-perl, Size: 3749 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: fadt.boot_flags.MSI_not_supported
2006-09-28 0:14 fadt.boot_flags.MSI_not_supported Brown, Len
2006-09-28 4:23 ` fadt.boot_flags.MSI_not_supported Randy Dunlap
@ 2006-09-28 22:45 ` Andi Kleen
1 sibling, 0 replies; 4+ messages in thread
From: Andi Kleen @ 2006-09-28 22:45 UTC (permalink / raw)
To: Brown, Len; +Cc: linux-acpi
"Brown, Len" <len.brown@intel.com> writes:
> sifting through ACPI 3.0a I just noticed a bit (3)
> in the FADT boot_flag to indicate the platform
> does not support MSI.
Implementing that is on my todo list. We definitely should.
-Andi
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-09-28 22:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-28 0:14 fadt.boot_flags.MSI_not_supported Brown, Len
2006-09-28 4:23 ` fadt.boot_flags.MSI_not_supported Randy Dunlap
2006-09-28 4:43 ` fadt.boot_flags.MSI_not_supported Len Brown
2006-09-28 22:45 ` fadt.boot_flags.MSI_not_supported Andi Kleen
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).