Native xorg on macppc and sparc64

[Michael Lorenz]

Hello,

things seem to work so far - there are a few things in MesaLib's DRI  
code that need to be patched but otherwise it looks ok. I can't really  
try it on this G4 though since the r128 driver isn't built yet ( I'll  
give it a shot on my other boxes later on ). Anyway, Xorg -configure  
produced a mostly sane xorg.conf.
Some issues though:
- the way we create driver modules looks weird - we produce an so.x  
file and a .so symlink to it. Xorg finds both. No real problem, just  
annoying because it makes the module list in Xorg.0.log look weird and  
way too long.
- why do we build the vesa driver on macppc? It makes no sense on non-
x86.

On sparc64 we run into pointer size vs. integer size problems in  
MesaLib's R200 module. I need to look at the pkgsrc patches to fix  
that ( macro hell... ).
Let's hope out netbsdSbus.c still works with Xorg.

have fun
Michael

[Tyler Retzlaff]

Hi Michael,

On Sat, Oct 11, 2008 at 01:28:25PM -0400, Michael wrote:
> Hello,
>
> things seem to work so far - there are a few things in MesaLib's DRI  
> code that need to be patched but otherwise it looks ok. I can't really  
> try it on this G4 though since the r128 driver isn't built yet ( I'll  
> give it a shot on my other boxes later on ). Anyway, Xorg -configure  
> produced a mostly sane xorg.conf.

i'l check out r128.

> Some issues though:
> - the way we create driver modules looks weird - we produce an so.x file
> and a .so symlink to it. Xorg finds both. No real problem, just annoying
> because it makes the module list in Xorg.0.log look weird and way too
> long.

interesting didn't know it was finding the so.<major> it's more work to
get rid of it being installed.

> - why do we build the vesa driver on macppc? It makes no sense on non-
> x86.

no sense at all. if you find any that don't make sense for a platform
you're working on nobody will complain if you .if ${MACHINE} them out
of the build.

>
> On sparc64 we run into pointer size vs. integer size problems in  
> MesaLib's R200 module. I need to look at the pkgsrc patches to fix that (
> macro hell... ).

yeah that stuff is dirty and is obviously a problem on all 64-bit platforms.

Tyler

[Michael Lorenz]

Hello,

On Oct 11, 2008, at 10:03 PM, Tyler Retzlaff wrote:

> On Sat, Oct 11, 2008 at 01:28:25PM -0400, Michael wrote:
>> Hello,
>>
>> things seem to work so far - there are a few things in MesaLib's DRI
>> code that need to be patched but otherwise it looks ok. I can't  
>> really
>> try it on this G4 though since the r128 driver isn't built yet ( I'll
>> give it a shot on my other boxes later on ). Anyway, Xorg -configure
>> produced a mostly sane xorg.conf.
>
> i'l check out r128.

Thanks!

>> - why do we build the vesa driver on macppc? It makes no sense on  
>> non-
>> x86.
>
> no sense at all. if you find any that don't make sense for a platform
> you're working on nobody will complain if you .if ${MACHINE} them out
> of the build.

Ok, I'll shrink that list. There are a few others that have  
practically no chance to show up in a mac ( or non-PC for that  
matter ). What we really need is just all ati, nvidia, matrox, chips &  
technologies, tdfx on macppc and ati, all the sun stuff and permedia2  
on sparc64. Plus wsfb on both. Although, maybe we should build the  
matrox driver on sparc64 as well - xfree86's mga driver was able to  
use a cold Millennium II on sparc64 with some hacking ( mainly PCI  
access stuff, no x86 emulation involved here )

have fun
Michael

[Michael Lorenz]

Hello,

On Oct 11, 2008, at 10:03 PM, Tyler Retzlaff wrote:

> On Sat, Oct 11, 2008 at 01:28:25PM -0400, Michael wrote:
>> Hello,
>>
>> things seem to work so far - there are a few things in MesaLib's DRI
>> code that need to be patched but otherwise it looks ok. I can't  
>> really
>> try it on this G4 though since the r128 driver isn't built yet ( I'll
>> give it a shot on my other boxes later on ). Anyway, Xorg -configure
>> produced a mostly sane xorg.conf.
>
> i'l check out r128.

I saw you imported it. Now I get this:
dependall ===> external/mit/xorg/server/drivers/xf86-video-r128
awk: can't open file /configure
  source line number 1
nbmake: "/dump/src/external/mit/xorg/server/drivers/Makefile.xf86-
driver" line 18: warning: "awk '/^PACKAGE_VERSION=/  
{                  match($1, "[0-9]+\\.[0-9]+\\.[0-9]+");  version =  
substr($1, RSTART, RLENGTH);  } END { print  
version }'                        /configure" returned non-zero status
nbmake: nbmake: don't know how to make r128_accel.c. Stop
*** [dependall-xf86-video-r128] Error code 2
1 error

So, looks like for some reason the reachover Makefile can't find the  
source because ${X11SRCDIR}.${DRIVER} is empty. What am I missing?

have fun
Michael

[Tyler Retzlaff-2]

hi Michael,

On Tue, Oct 14, 2008 at 12:39:01AM -0400, Michael wrote:

> Hello,
>
> I saw you imported it. Now I get this:
> dependall ===> external/mit/xorg/server/drivers/xf86-video-r128
> awk: can't open file /configure
>  source line number 1
> nbmake: "/dump/src/external/mit/xorg/server/drivers/Makefile.xf86-
> driver" line 18: warning: "awk '/^PACKAGE_VERSION=/ {                  
> match($1, "[0-9]+\\.[0-9]+\\.[0-9]+");  version = substr($1, RSTART,
> RLENGTH);  } END { print version }'                        /configure"
> returned non-zero status
> nbmake: nbmake: don't know how to make r128_accel.c. Stop
> *** [dependall-xf86-video-r128] Error code 2
> 1 error

i did test this and it should operate the same as the rest. just a few
standard questions.

- you updated your xsrc?
- what is the output of tmake -V for:
  .PATH
  X11SRCDIR
  DRIVER
  '${X11SRCDIR}.${DRIVER}'

tyler

[Pierre Pronchery]

On 2008-10-11, Michael <macallan@...> wrote:
>
> Let's hope out netbsdSbus.c still works with Xorg.

I have been saying so (and using it) for ten months already :)

http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=37741
http://mail-index.netbsd.org/port-sparc64/2008/01/06/msg000009.html
http://mail-index.netbsd.org/port-sparc64/2008/04/08/msg000309.html

HTH,
--
khorben