Re: [linux-pm] [RFC] userland swsusp
From: Jesse Barnes (jbarnes_at_virtuousgeek.org)
Date: 11/19/05
- Previous message: Greg KH: "Re: question about driver built-in kernel"
- In reply to: Alan Cox: "Re: [linux-pm] [RFC] userland swsusp"
- Next in thread: Arjan van de Ven: "Re: [linux-pm] [RFC] userland swsusp"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Alan Cox <alan@lxorguk.ukuu.org.uk> Date: Fri, 18 Nov 2005 20:18:21 -0800
On Friday, November 18, 2005 2:07 pm, Alan Cox wrote:
> On Gwe, 2005-11-18 at 22:23 +0100, Arjan van de Ven wrote:
> > 1) accessing non-ram memory (eg PCI mmio space) by X and the likes
> > (ideally should use sysfs but hey, changing X for this will take
> > forever)
>
> Once sysfs supports the relevant capabilities fixing X actually
> doesn't look too horrible, the PCI mapping routines are abstracted
> and done by PCITAG (ie PCI device). You would need the ISA hole too
> in some cases.
It's actually partly done already (at least for ia64, but the code I put
together works on x86 too, iirc, and should work elsewhere). The ISA
stuff is exported on a per-bus basis in legacy_io and legacy_mem files.
If vbetool and friends want to get at the ROM, they can use the sysfs
rom file like everyone else. There are problems with this however, on
systems where the ROM is unpacked at 0xc0000 or something, especially
if the unpacked version is modified by the BIOS at startup time, not
sure how to address that reliably.
Jesse
-
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: Greg KH: "Re: question about driver built-in kernel"
- In reply to: Alan Cox: "Re: [linux-pm] [RFC] userland swsusp"
- Next in thread: Arjan van de Ven: "Re: [linux-pm] [RFC] userland swsusp"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
