> PCI bridges at zero is perfectly valid indeed and I'm sure we have thatOn a PC system 0x00-0xFF are motherboard resources (sometimes chipset, some even swallowed by the CPU in certain cases) so 0 as disabled is sort of safe but as shown by the pci_enable_device_bars replacement code - not a good idea neccessarily. A lot of driver code does assume 0 == unavailable/off/disabled including large chunks of serial, ata, ide and probably other subsystems. Alan --
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Andi Kleen | Re: [patch] Add basic sanity checks to the syscall execution patch |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Stoyan Gaydarov | From 2.4 to 2.6 to 2.7? |
git: | |
| Elijah Newren | Trying to use git-filter-branch to compress history by removing large, obsolete bi... |
| Matthieu Moy | git push to a non-bare repository |
| Johannes Schindelin | Re: Git as a filesystem |
| Jakub Narebski | Re: VCS comparison table |
| Richard Stallman | Real men don't attack straw men |
| Joachim Schipper | Re: OpenBSD/alpha Status |
| Theo de Raadt | Re: hardware needed for network stack performance work |
| Marcus Andree | Re: Cyrus IMAP performance problems [Long] |
| Andrew Morton | Re: [Bugme-new] [Bug 10473] New: Infinite loop "b44: eth0: powering down PHY" |
| John Rigby | [PATCH] [Rev2] MPC5121 FEC support |
| Pekka Enberg | Re: [rfc][patch 1/3] slub: fix small HWCACHE_ALIGN alignment |
| Ilpo Järvinen | [PATCH] [TCP]: Separate lost_retrans loop into own function |
