Re: Update to the DRM

2002-07-14 Thread Stanislav Grozev

On Fri, Jul 12, 2002 at 05:29:01PM -0600, Eric Anholt wrote:
> > well if you give me details, i could try
> 
> cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login 
> cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri -z3 co -P xc 
> 


ok i'll try :-) I am not a kernel hacker, so MMMV (my mileage my vary:-)

-tacho

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-13 Thread Eric Anholt

On Sat, 2002-07-13 at 11:23, Michael Nottebrock wrote:
> Eric Anholt wrote:

> I have just compiled a world with the 20020711.diff. It sure runs fast, 
> but the quality isn't very good. I tested with glxgears and gltron and 
> in both there is a lot of flashing and lighting errors.
> 
> Do you have any recommendations what other tests I could run?
> 
> Hardware:
> 
> drm0@pci1:0:0:  class=0x03 card=0x008a1002 chip=0x51441002 rev=0x00 
> hdr=0x00
>  vendor   = 'ATI Technologies'
>  device   = 'Radeon 7200 / Radeon'
>  class= display
>  subclass = VGA

Okay, I'm seeing that with 4.2.0+Radeon on the new DRM.  I'll build a
4.2.0 for linux and see if that shows it too, to figure out if it's a
BSD-specific issue.

-- 
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-13 Thread Michael Nottebrock

Eric Anholt wrote:
> On Wed, 2002-07-10 at 17:17, Eric Anholt wrote:
> 
>>I've posted a diff to the DRM at
>>http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta 
> 
> 
> Evolution's "send" button is way too big.
> 
> http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.diff
> is the file.  The patch brings the current DRM from DRI CVS into the
> system.  It includes PCI Rage 128 support and support for "transform,
> clipping, & lighting" (TCL) hardware on Radeons.

I have just compiled a world with the 20020711.diff. It sure runs fast, 
but the quality isn't very good. I tested with glxgears and gltron and 
in both there is a lot of flashing and lighting errors.

Do you have any recommendations what other tests I could run?

Hardware:

drm0@pci1:0:0:  class=0x03 card=0x008a1002 chip=0x51441002 rev=0x00 
hdr=0x00
 vendor   = 'ATI Technologies'
 device   = 'Radeon 7200 / Radeon'
 class= display
 subclass = VGA


Regards,
-- 
Michael Nottebrock
"The circumstance ends uglily in the cruel result." - Babelfish



msg40985/pgp0.pgp
Description: PGP signature


Re: Update to the DRM

2002-07-12 Thread Eric Anholt

On Fri, 2002-07-12 at 13:49, Stanislav Grozev wrote: 
> On Fri, Jul 12, 2002 at 01:06:31PM -0600, Eric Anholt wrote:
> > Luckily for you, support for mach64s (Rage Pros specifically, which I
> > think your chip is) is being worked on in DRI CVS, so it should be
> > available soon.  What's needed at this point is for someone to port the
> > Mach64 DRM from Linux to the Linux/BSD framework we've got in DRI CVS
> > now.  It's a pretty straightforward process now for most chipsets, but
> > does take some time.
> 
> well if you give me details, i could try

cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login 
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri -z3 co -P xc 

That's trunk, which includes the Radeon TCL (transform+lighting) 3d
driver and the "os-independent" framework for the DRM.  The DRM is in
xc/programs/Xserver/hw/xfree86/os-support/${OS}/drm/kernel.  To get the
branch with mach64 work add -rmach64-0-0-5-branch to the checkout.

You would probably want to check out a trunk and a mach64-0-0-5-branch. 
Install World with the mach64 branch, then copy the mach64* files from
the mach64-branch drm into the trunk's drm and port the DRM from there.

cvs logs of os-support/shared/drm/kernel/* along with looking at 
os-support/linux/drm/kernel/drm_os_linux.h and
os-support/linux/drm/kernel/drm_os_freebsd.h should give an example of
most of the changes to be done in porting a driver. 

I've taken a quick look at the mach64 code, and I have the following
concerns on porting it:
- we don't have any os-independent macros for linked lists yet.
- needs allocation of 16kb, 16kb-aligned memory (do we have a clean
method of doing this?) which is "consistent for DMA".  For x86 it looks
like we can ignore the "consistent" stuff.

They still have interrupt code enabled, but it should probably be #if
MACH64_INTERRUPTS (currently 0).  We don't have any DRMs on FreeBSD
using interrupts, so I don't know how well it would work if that got
turned back on.

The goal for porting drivers to *BSD for the DRI project is to have no
os-specific #ifdefs in the driver code itself.  They might be a little
more flexible allowing that now, but if we can avoid ifdefs it'll help
get the code merged faster.

-- 
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-12 Thread Stanislav Grozev

On Fri, Jul 12, 2002 at 01:06:31PM -0600, Eric Anholt wrote:
> That's a Mach64-based chip, so the r128 driver won't work with it. 

i see...

> Luckily for you, support for mach64s (Rage Pros specifically, which I
> think your chip is) is being worked on in DRI CVS, so it should be
> available soon.  What's needed at this point is for someone to port the
> Mach64 DRM from Linux to the Linux/BSD framework we've got in DRI CVS
> now.  It's a pretty straightforward process now for most chipsets, but
> does take some time.

well if you give me details, i could try

-tacho

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-12 Thread Eric Anholt

On Fri, 2002-07-12 at 03:07, Stanislav Grozev wrote:
> ok, it compiles and runs fine...
> but my card isn't recognized. here's what pciconf -l -v shows:
> 
> none6@pci0:13:0:class=0x03 card=0x80af104d chip=0x4c521002 rev=0x64 
>hdr=0x00
> vendor   = 'ATI Technologies'
> device   = 'Rage P/M Mobility PCI'
> class= display
> subclass = VGA
> 
> so I just added the chipid to r128_drv.c (hoping that it will work;-):
> 
> {0x1002, 0x4c52, __REALLY_HAVE_SG, "ATI Rage 12m Mobility P/M (PCI)"},

That's a Mach64-based chip, so the r128 driver won't work with it. 
Luckily for you, support for mach64s (Rage Pros specifically, which I
think your chip is) is being worked on in DRI CVS, so it should be
available soon.  What's needed at this point is for someone to port the
Mach64 DRM from Linux to the Linux/BSD framework we've got in DRI CVS
now.  It's a pretty straightforward process now for most chipsets, but
does take some time.

-- 
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-12 Thread Michael Nottebrock


Stanislav Grozev wrote:
> On Fri, Jul 12, 2002 at 09:56:50AM +0200, Stanislav Grozev wrote:
> 
> 
>>>Missed the N on my cvs diff -uN.  New patch is uploaded, including not
>>>stripping FreeBSD ID tags. 
>>>http://people.freebsd.org/~anholt/dri/files/currentdrm-20020711.diff
>>
>>thanks, i'll try it now
> 
> 
> ok, it compiles and runs fine...
> but my card isn't recognized. here's what pciconf -l -v shows:
> 
> none6@pci0:13:0:class=0x03 card=0x80af104d chip=0x4c521002 rev=0x64 
>hdr=0x00
> vendor   = 'ATI Technologies'
> device   = 'Rage P/M Mobility PCI'
> class= display
> subclass = VGA
> 
> so I just added the chipid to r128_drv.c (hoping that it will work;-):
> 
> {0x1002, 0x4c52, __REALLY_HAVE_SG, "ATI Rage 12m Mobility P/M (PCI)"},
> 
> and the driver now detects it:
> 
> drm0:  port 0x1400-0x14ff mem 
>0xfc00c000-0xfc00cfff,0xfd00-0xfdff irq 9 at device 13.0 on pci0
> [drm:r128_init] 
> [drm:r128_agp_init] agp_available = 0
> [drm:r128_ctxbitmap_next] drm_ctxbitmap_next bit : 0
> [drm:r128_ctxbitmap_init] drm_ctxbitmap_init : 0
> info: [drm] Initialized r128 2.2.0 20010917 on minor 0
> 
> but, glxinfo still says 'Direct rendering: no' (i have load "dri" in my
> x config, do i need something else?).

Load "glx"

and something like

Section "DRI"
 Mode 0666
EndSection

See http://www.xfree86.org/current/DRI6.html#10 for details.


Regards,
-- 
Michael Nottebrock
"The circumstance ends uglily in the cruel result." - Babelfish



msg40941/pgp0.pgp
Description: PGP signature


Re: Update to the DRM

2002-07-12 Thread Stanislav Grozev

On Fri, Jul 12, 2002 at 09:56:50AM +0200, Stanislav Grozev wrote:

> > Missed the N on my cvs diff -uN.  New patch is uploaded, including not
> > stripping FreeBSD ID tags. 
> > http://people.freebsd.org/~anholt/dri/files/currentdrm-20020711.diff
> 
> thanks, i'll try it now

ok, it compiles and runs fine...
but my card isn't recognized. here's what pciconf -l -v shows:

none6@pci0:13:0:class=0x03 card=0x80af104d chip=0x4c521002 rev=0x64 
hdr=0x00
vendor   = 'ATI Technologies'
device   = 'Rage P/M Mobility PCI'
class= display
subclass = VGA

so I just added the chipid to r128_drv.c (hoping that it will work;-):

{0x1002, 0x4c52, __REALLY_HAVE_SG, "ATI Rage 12m Mobility P/M (PCI)"},

and the driver now detects it:

drm0:  port 0x1400-0x14ff mem 
0xfc00c000-0xfc00cfff,0xfd00-0xfdff irq 9 at device 13.0 on pci0
[drm:r128_init] 
[drm:r128_agp_init] agp_available = 0
[drm:r128_ctxbitmap_next] drm_ctxbitmap_next bit : 0
[drm:r128_ctxbitmap_init] drm_ctxbitmap_init : 0
info: [drm] Initialized r128 2.2.0 20010917 on minor 0

but, glxinfo still says 'Direct rendering: no' (i have load "dri" in my
x config, do i need something else?).

so any ideas would be appreciated.

-tacho

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-12 Thread Stanislav Grozev

On Thu, Jul 11, 2002 at 12:25:08PM -0600, Eric Anholt wrote:
> On Thu, 2002-07-11 at 03:19, Stanislav Grozev wrote: 
> > i wanted to try the pci rage 128, as i have a sony vaio with it (i think) :-)
> > so, the patch applied cleanly, but then, make buildkernel complains about
> > missing ati_pcigart.h. i did a find /usr/src/sys -follow -name ati_pcigart.h
> > and nothing showed up. any ideas?
> 
> Missed the N on my cvs diff -uN.  New patch is uploaded, including not
> stripping FreeBSD ID tags. 
> http://people.freebsd.org/~anholt/dri/files/currentdrm-20020711.diff

thanks, i'll try it now

-tacho
-- 
[i am the mask you wear] | [http://daemonz.org/ || [EMAIL PROTECTED]]
0x44fc3339 || [02b5 798b 4bd1 97fb f8db 72e4 dca4 be03 44fc 3339]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-11 Thread Dag-Erling Smorgrav

Eric Anholt <[EMAIL PROTECTED]> writes:
> Missed the N on my cvs diff -uN.  New patch is uploaded, including not
> stripping FreeBSD ID tags. 
> http://people.freebsd.org/~anholt/dri/files/currentdrm-20020711.diff

Looks good, I'll rebuild & reboot in a couple of minutes.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-11 Thread Eric Anholt

On Thu, 2002-07-11 at 03:19, Stanislav Grozev wrote: 
> i wanted to try the pci rage 128, as i have a sony vaio with it (i think) :-)
> so, the patch applied cleanly, but then, make buildkernel complains about
> missing ati_pcigart.h. i did a find /usr/src/sys -follow -name ati_pcigart.h
> and nothing showed up. any ideas?

Missed the N on my cvs diff -uN.  New patch is uploaded, including not
stripping FreeBSD ID tags. 
http://people.freebsd.org/~anholt/dri/files/currentdrm-20020711.diff

-- 
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-11 Thread Dag-Erling Smorgrav

Eric Anholt <[EMAIL PROTECTED]> writes:
> http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.diff

You should put back the $FreeBSD$ tags, or you won't be able to
commit.  http://people.freebsd.org/~des/software/drm-20020711.diff
should apply the same changes without touching the tags.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-11 Thread Stanislav Grozev

On Wed, Jul 10, 2002 at 05:23:25PM -0600, Eric Anholt wrote:
> On Wed, 2002-07-10 at 17:17, Eric Anholt wrote:
> > I've posted a diff to the DRM at
> > http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta 
> 
> Evolution's "send" button is way too big.
> 
> http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.diff
> is the file.  The patch brings the current DRM from DRI CVS into the
> system.  It includes PCI Rage 128 support and support for "transform,

i wanted to try the pci rage 128, as i have a sony vaio with it (i think) :-)
so, the patch applied cleanly, but then, make buildkernel complains about
missing ati_pcigart.h. i did a find /usr/src/sys -follow -name ati_pcigart.h
and nothing showed up. any ideas?

rm -f .newdep
make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | xargs  env MKDEP_CPP="cc -E" CC="cc" 
mkdep -a -f .newdep -O -pipe -march=pentium -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wno-format -ansi  -nostdinc -I-  -I. -I/usr/src/sys -I/usr/src/sys/dev 
-I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter 
-I/usr/src/sys/../include  -D_KERNEL -include opt_global.h -fno-common   
-mpreferred-stack-boundary=2 -ffreestanding
/usr/src/sys/dev/drm/r128_drv.c:41:33: dev/drm/ati_pcigart.h: No such file or directory
mkdep: compile failed
*** Error code 1

Stop in /home/scratch/obj/usr/src/sys/LOGRUS.


 
> I'm looking for testers of this code in -current.  Hopefully this will
> support 4.2.0 as well as the old code did, in which case I would like to
> commit this soon.

yeah i'll be happy to test. i'm with 4.2.0

-tacho
-- 
[i am the mask you wear] | [http://daemonz.org/ || [EMAIL PROTECTED]]
0x44fc3339 || [02b5 798b 4bd1 97fb f8db 72e4 dca4 be03 44fc 3339]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-10 Thread Terry Lambert

Eric Anholt wrote:
> I've posted a diff to the DRM at
> http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta

http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.diff

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Update to the DRM

2002-07-10 Thread Eric Anholt

On Wed, 2002-07-10 at 17:17, Eric Anholt wrote:
> I've posted a diff to the DRM at
> http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta 

Evolution's "send" button is way too big.

http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.diff
is the file.  The patch brings the current DRM from DRI CVS into the
system.  It includes PCI Rage 128 support and support for "transform,
clipping, & lighting" (TCL) hardware on Radeons.  Another user and I
have been banging on it with DRI CVS X Servers on Radeon, and I've
tested it with several other cards with DRI CVS.  What is probably least
tested is using 4.2.0 X Servers with the new DRM, I'll work on that
soon.

I'm looking for testers of this code in -current.  Hopefully this will
support 4.2.0 as well as the old code did, in which case I would like to
commit this soon.

-- 
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message