tech-x11 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: X11 per machine_arch not per port (Was: Moving ports across to X11R7)

On Sun, Feb 08, 2009 at 12:11:46PM -0500, Michael wrote:
> Hash: SHA1
> Hello,
> On Feb 8, 2009, at 9:09 AM, David Brownlee wrote:
>> On Sun, 8 Feb 2009, Quentin Garnier wrote:
>>> On Sun, Feb 08, 2009 at 12:51:10AM +0000, David Brownlee wrote:
>>>>    Is there anything stopping moving ports which do not currently
>>>>    build Xservers (apart from Xvfb) across to X11R7?
>>> I don't think so.  Please go ahead if you can.
>>      Is moving to X11R7 a good time to make X11 sharable per
>>      machine_arch rather than per port?
>>      At the moment only amd64, i386, macppc, shark, & sparc64 have
>>      moved across, so...
> Should work for the client stuff at least. The only incompatibility I  
> can think of right now is the way we mmap (PCI) IO space on powerpc and 
> shark - by picking a magic address range which isn't used by any PCI 
> device, on macppc it's 0xf2000000 ( traditionally the 1st PCI bridge's IO 
> range ), prep and ofppc use different values, they're currently #defined 
> in sys/params.h so there are no magic values or #ifdefs in the Xserver. 
> We could just add an ioctl so the Xserver can ask the kernel where it 
> would find IO space, that would take a few clock cycles more during setup 
> but the result would be the same and Xservers would be compatible across 

I think we can leave the xserver set per-port.  It's not just the way
it access the hardware, it's also the set of drivers.

Quentin Garnier - -
"See the look on my face from staying too long in one place
[...] every time the morning breaks I know I'm closer to falling"
KT Tunstall, Saving My Face, Drastic Fantastic, 2007.

Attachment: pgpt6PnrTwKzf.pgp
Description: PGP signature

Home | Main Index | Thread Index | Old Index