linux-kernel - Re: [PATCH 1/1] ACPI: pci_irq, add PRT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 19 Jul 2010 13:19:04 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Jiri Slaby <jslaby@...e.cz>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>, lenb@...nel.org,
	linux-pci@...r.kernel.org, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH 1/1] ACPI: pci_irq, add PRT_ quirk for IBM Bartolo

On Mon, Jul 19, 2010 at 10:29 AM, Jiri Slaby <jslaby@...e.cz> wrote:
>>> I still no point in comparing this to Windows' setup. We can't find out
>>> whether it is quirked or better (without some bug) handled there.
>>
>> Well, you can see if Windows shows IRQ 10 or 11 for that device..
>
> But how can I find out which link it is routed to in Windows? Without
> that information the number is meaningless, no?

If you look at the pattern of which IRQs are shared by what devices in
Linux and compare it to Windows you can get a good idea. Normally the
assignment of devices to interrupt lines is hard-wired on the
motherboard and doesn't change.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/