Izumi Tsutsui | 9 Nov 2010 17:16
Picon
Gravatar

Re: Providing port specific sample xorg.conf file

macallan <at>  wrote:

> > To use Xorg server properly, several ports require some machine
> > specific but common settings (wskbd protocol for keyboard,
> > CCW settings for PDA screen etc.) in xorg.org.
> 
> Some ports ( IIRC macppc, sparc(64) and I think sgimips ) add these  
> lines automatically when generating a config file using Xorg -configure.

It looks these are for xf86-video-foo drivers.

Most ports that use wsfb driver don't require probing video to setup
xorg.conf, but users still have to modify lines for screen size
and keyboard layout etc. so I think it's still worth to provide
sample xorg.conf files in the default (/etc/X11) dir.

I'm planning to handle such xorg.conf examples in
src/external/mit/xorg/etc with CONFIGFILES as
src/etc does for misc config files, and I'll add
such xorg.conf files into xserver.tgz set (rather than xetc.tgz).

Comments?

Index: src/external/mit/xorg/Makefile
===================================================================
RCS file: /cvsroot/src/external/mit/xorg/Makefile,v
retrieving revision 1.7
diff -u -p -r1.7 Makefile
--- src/external/mit/xorg/Makefile	7 Sep 2009 21:07:03 -0000	1.7
+++ src/external/mit/xorg/Makefile	9 Nov 2010 16:08:31 -0000
(Continue reading)

Izumi Tsutsui | 13 Nov 2010 00:43
Picon
Gravatar

Re: Providing port specific sample xorg.conf file

> I'm planning to handle such xorg.conf examples in
> src/external/mit/xorg/etc with CONFIGFILES as
> src/etc does for misc config files, and I'll add
> such xorg.conf files into xserver.tgz set (rather than xetc.tgz).

Committed.

I'll also add xorg.conf examples for hpcarm, hpcmips, and hpcsh ports
which use a dumb wsfb driver.

---
Izumi Tsutsui

matthew green | 13 Nov 2010 00:48
Picon
Favicon

re: Providing port specific sample xorg.conf file


> > I'm planning to handle such xorg.conf examples in
> > src/external/mit/xorg/etc with CONFIGFILES as
> > src/etc does for misc config files, and I'll add
> > such xorg.conf files into xserver.tgz set (rather than xetc.tgz).
> 
> Committed.
> 
> I'll also add xorg.conf examples for hpcarm, hpcmips, and hpcsh ports
> which use a dumb wsfb driver.

thanks so much for porting more xfree to xorg!

it would be really great if someone (you? :-) could teach the
drivers how to autoconfigure themselves so that an xorg.conf is
not needed at all.

.mrg.

Izumi Tsutsui | 13 Nov 2010 00:59
Picon
Gravatar

Re: Providing port specific sample xorg.conf file

> it would be really great if someone (you? :-) could teach the
> drivers how to autoconfigure themselves so that an xorg.conf is
> not needed at all.

For keymaps, it could be done by overriding the default XKB settings
per WSKBDIO_GETENCODING ioctl, but current xf86-input-keyboard driver
is not abstracted well :-(

---
Izumi Tsutsui

Matthias Scheler | 17 Nov 2010 23:45
Picon
Favicon

Importing "xorg-docs" into "xsrc/external"


	Hello,

is there a reason why we wouldn't want to import "xorg-docs" into
"xsrc/external/mit"? A user has noticed that e.g. the X(7) manual page
is missing on ports using X.org (see PR xsrc/44034).

	Kind regards

--

-- 
Matthias Scheler                                  http://zhadum.org.uk/

matthew green | 18 Nov 2010 07:46
Picon
Favicon

re: Importing "xorg-docs" into "xsrc/external"


> is there a reason why we wouldn't want to import "xorg-docs" into
> "xsrc/external/mit"? A user has noticed that e.g. the X(7) manual page
> is missing on ports using X.org (see PR xsrc/44034).

no reason at all.

please feel free to do it before i may or may not get around to it.. :)

.mrg.

Michael | 18 Nov 2010 08:38
Picon

Accessing ROMs from libpciaccess


Hello,

I just committed a fix for libpciaccess's ROM access method. It used  
to just open /dev/mem, mmap(ROM_BASE) and crossfingers hoping physical  
addresses are the same as bus addresses on the machine it's running.  
Obviously this assumption is false on many non-x86 machines ( sparc64  
for example ) but the fix is simple - use the same mechanism as  
pci_device_netbsd_map_range().
This should work as before on x86, additionally it should work on all  
other ports as well - here's an example from sparc64:
(II) RADEON(1): Attempting to read un-POSTed bios
(WW) RADEON(1): Not an x86 BIOS ROM image, BIOS data will not be used
no kidding, it's an xvr-100 with Sun firmware.
I have a mach64 card with PC firmware in the same box but the driver  
is unable to cold start it and int10 isn't built by default - I'll  
look at that next.
On macppc int10 crashed with a SIGBUS trying to muck with an R128's  
ROM, in LockVGA() - let's see how much work it takes to get the x86  
emulator running.
That said, please test it, on x86 nothing should change ( unless you  
have a machine with several independent PCI buses - these should work  
now )
On non-x86 you should see at least some acknowledgement that the ROM  
isn't what the driver expected, if it's not a PC BIOS.

have fun
Michael

(Continue reading)

Matthias Scheler | 18 Nov 2010 09:07
Picon
Favicon

Re: Importing "xorg-docs" into "xsrc/external"

On Thu, Nov 18, 2010 at 05:46:00PM +1100, matthew green wrote:
> 
> > is there a reason why we wouldn't want to import "xorg-docs" into
> > "xsrc/external/mit"? A user has noticed that e.g. the X(7) manual page
> > is missing on ports using X.org (see PR xsrc/44034).
> 
> no reason at all.
> 
> please feel free to do it before i may or may not get around to it.. :)

Is there anything specific I need to keep in mind when I do that?
Do I assume correctly that the vendortag should be "xorg" and the
releasetag "xorg-docs-1-5"?

	Kind regards

--

-- 
Matthias Scheler                                  http://zhadum.org.uk/

matthew green | 18 Nov 2010 09:12
Picon
Favicon

re: Importing "xorg-docs" into "xsrc/external"


> On Thu, Nov 18, 2010 at 05:46:00PM +1100, matthew green wrote:
> > 
> > > is there a reason why we wouldn't want to import "xorg-docs" into
> > > "xsrc/external/mit"? A user has noticed that e.g. the X(7) manual page
> > > is missing on ports using X.org (see PR xsrc/44034).
> > 
> > no reason at all.
> > 
> > please feel free to do it before i may or may not get around to it.. :)
> 
> Is there anything specific I need to keep in mind when I do that?
> Do I assume correctly that the vendortag should be "xorg" and the
> releasetag "xorg-docs-1-5"?

that looks right.  there's nothing particularly tricks.  thanks!

.mrg.

Nick Hudson | 18 Nov 2010 12:31
Picon
Favicon

Re: Accessing ROMs from libpciaccess

On Thursday 18 November 2010 07:38:36 Michael wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> 
> I just committed a fix for libpciaccess's ROM access method. It used
> to just open /dev/mem, mmap(ROM_BASE) and crossfingers hoping physical
> addresses are the same as bus addresses on the machine it's running.
> Obviously this assumption is false on many non-x86 machines ( sparc64
> for example ) but the fix is simple - use the same mechanism as
> pci_device_netbsd_map_range().
> This should work as before on x86, additionally it should work on all
> other ports as well - here's an example from sparc64:
> (II) RADEON(1): Attempting to read un-POSTed bios
> (WW) RADEON(1): Not an x86 BIOS ROM image, BIOS data will not be used
> no kidding, it's an xvr-100 with Sun firmware.
> I have a mach64 card with PC firmware in the same box but the driver
> is unable to cold start it and int10 isn't built by default - I'll
> look at that next.
> On macppc int10 crashed with a SIGBUS trying to muck with an R128's
> ROM, in LockVGA() - let's see how much work it takes to get the x86
> emulator running.

This definitely helps me on cats - I had a similar local changes to get cats 
working again.

int10 has problems on cats as follows. I'm still looking what this might be.

(II) S3VIRGE(0): initializing int10                                                                                                                                    
(Continue reading)


Gmane