On Mon, Dec 17, 2007 at 01:57:33PM -0800, Kok, Auke wrote:
> what kind of platform actually is doing this? It almost seems like something is
> wrong with that platform's BIOS and I wonder if this workaround should not be more
> general (IOW is it not just e100 that is affected but other components as well?)
It's alpha sx164. But I don't think the firmware does anything wrong here,
it just put e100 in "sleep" or "soft off" state.
I think a general rule is that you cannot access device MEM or IO registers
without pci_enable_device first (or making sure that the device is actually
enabled in other ways).
Ivan.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
