Re: Exposing ROM's though sysfs
From: Alan Cox (alan_at_lxorguk.ukuu.org.uk)
Date: 07/31/04
- Previous message: Alan Cox: "Re: Exposing ROM's though sysfs"
- In reply to: Matthew Wilcox: "Re: Exposing ROM's though sysfs"
- Next in thread: Jesse Barnes: "Re: Exposing ROM's though sysfs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Matthew Wilcox <willy@debian.org> Date: Fri, 30 Jul 2004 23:39:14 +0100
On Gwe, 2004-07-30 at 19:12, Matthew Wilcox wrote:
> I don't see a good way of doing this, unfortunately. It'd probably be
> enough to call ->suspend on the driver while you read the contents of
> the ROM, but that's pretty ugly.
Is the BIOS guaranteed readable in D3 if we call suspend ?
Since we only need the BIOS in some special cases we could just reject
the request if the device is in use. If it has a driver - ask the
driver, if it doesn't then ask sysfs.
-
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/
- Previous message: Alan Cox: "Re: Exposing ROM's though sysfs"
- In reply to: Matthew Wilcox: "Re: Exposing ROM's though sysfs"
- Next in thread: Jesse Barnes: "Re: Exposing ROM's though sysfs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|