Messages in this thread | | | From | "mirabilos" <> | Subject | Re: Patch to make ymfpci legacy address 16 bits | Date | Thu, 10 May 2001 11:54:48 -0000 |
| |
> When you write "the kernel", do you mean the driver or generic > code? I hope you mean the driver, because I have this: > > 1. the device looks normal at power on > 2. the driver pokes a device-specific config register > 3. the config space header changes from type 0 to type 1 > > (The class code does NOT indicate PCI-to-PCI bridge. > You could say this is like CardBus but much weirder) > > If the kernel saves type 1 header data, cuts power using > motherboard features, restores power, and then tries to > restore type 1 header data into a type 0 header... the > system will be well and truly screwed IMHO.
This reminds me of being unable to use my sound card under Windoze after stand-by, suspend etc. (NB Win2k hibernate worked, suspend I had disabled then). Seems as not only linux has this kind of problems... I don't remember _which_ card it was but I am quite sure it was an old OPTi MAD16 Pro.
-mirabilos -- EA F0 FF 00 F0 #$@%CARRIER LOST
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |