linux-kernel - Re: [PATCH 3/3] x86: ce4100: fixup PCI configuration register access for devices without interrupts

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] [day] [month] [year] [list]

Message-ID: <20121026154919.GA8459@linutronix.de>
Date:	Fri, 26 Oct 2012 17:49:19 +0200
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Florian Fainelli <ffainelli@...ebox.fr>
Cc:	linux-kernel@...r.kernel.org, x86@...r.kernel.org,
	mbizon@...ebox.fr, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org
Subject: Re: [PATCH 3/3] x86: ce4100: fixup PCI configuration register
 access for devices without interrupts

* Florian Fainelli | 2012-10-19 13:51:56 [+0200]:

>From: Maxime Bizon <mbizon@...ebox.fr>
>
>Some CE4100 devices such as the:
>- DFX module (01:0b.7)
>- entertainment encryption device (01:10.0)
>- multimedia controller (01:12.0)
>
>do not have a device interrupt at all. This patch fixes the PCI controller
>code to declare the missing PCI configuration register space, as well as a
>fixup method for forcing the interrupt pin to be 0 for these devices. This is
>required to ensure that pci drivers matching on these devices will be able to
>call honor the various PCI subsystem calls touching the configuration space.

So they realy don't have an Interrupt. I assumed that I was not good
enough reading the table and matching the entries to the HW.

>Signed-off-by: Florian Fainelli <ffainelli@...ebox.fr>
Acked-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>

for patches 1-3

Sebastian
--
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/