[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Xorg, libpciaccess and /dev/mem
From: |
olafBuddenhagen |
Subject: |
Re: Xorg, libpciaccess and /dev/mem |
Date: |
Fri, 12 Mar 2010 00:32:44 +0100 |
User-agent: |
Mutt/1.5.19 (2009-01-05) |
Hi,
On Thu, Mar 11, 2010 at 05:35:13PM +0100, Samuel Thibault wrote:
> Using the iopl device is a bit of a hack, a more proper solution needs
> to be done.
I don't consider it a hack. What would be a more "proper" solution in
your opinion?...
Of course, one day hopefully we will have a lovely PCI bus server, which
allows clients to map individual regions according to the device
configuration... But that will still need a method for obtaining a
memory object for the physical address space from the kernel.
> Maybe in the meanwhile we should alias mem and iopl in the gnumach
> kernel, so already installed hurds can run Xorg (and the name "iopl"
> doesn't sound so good to me to replace mem :)).
Yeah, I actually mentioned on IRC that probably the best fix is renaming
the kernel device...
-antrik-
- Xorg, libpciaccess and /dev/mem, Jérémie Koenig, 2010/03/11
- Re: Xorg, libpciaccess and /dev/mem, olafBuddenhagen, 2010/03/11
- Re: Xorg, libpciaccess and /dev/mem, Samuel Thibault, 2010/03/11
- Re: Xorg, libpciaccess and /dev/mem,
olafBuddenhagen <=
- Re: Xorg, libpciaccess and /dev/mem, Samuel Thibault, 2010/03/11
- Re: Xorg, libpciaccess and /dev/mem, olafBuddenhagen, 2010/03/12
- Re: Xorg, libpciaccess and /dev/mem, Samuel Thibault, 2010/03/14
- Re: Xorg, libpciaccess and /dev/mem, olafBuddenhagen, 2010/03/18
- Re: Xorg, libpciaccess and /dev/mem, Samuel Thibault, 2010/03/18
- Re: Xorg, libpciaccess and /dev/mem, olafBuddenhagen, 2010/03/19
Re: Xorg, libpciaccess and /dev/mem, Samuel Thibault, 2010/03/19
Re: Xorg, libpciaccess and /dev/mem, Emilio Pozuelo Monfort, 2010/03/19