linux-kernel - [0/5] PCI MMConfig per-chipset support

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

Date:	Thu, 7 Dec 2006 15:36:03 +0100
From:	Olivier Galibert <galibert@...ox.com>
To:	Andi Kleen <ak@...e.de>, linux-pci@...ey.karlin.mff.cuni.cz,
	"Hack inc." <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>
Subject: [0/5] PCI MMConfig per-chipset support

Done in 5 steps, at Andi's very reasonable request:

1/5: PCI MMConfig: Share what's shareable.
  Share code between i386 and x86-64

2/5: PCI MMConfig: Only call unreachable_devices() when type 1 is available.
  Trivial fix.

3/5: PCI MMConfig: Only map what's necessary.
  Trivial fix too.

4/5: PCI MMConfig: Detect and support the E7520 and the 945G/GZ/P/PL
  The actual per-chipset support.

5/5: PCI MMConfig: Reserve resources but only when we're sure about them.
  Add the resources in /proc/iomem when the chipset in known.

  OG.

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