Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 05 May 2005 00:39:48 -0500
From:      Jonathan Noack <noackjr@alumni.rice.edu>
To:        Eric Anholt <eta@lclark.edu>
Cc:        freebsd-x11@freebsd.org
Subject:   Re: r350 drm
Message-ID:  <4279B1A4.7020003@alumni.rice.edu>
In-Reply-To: <1115270660.23405.21.camel@leguin>
References:  <4279A5A0.2060806@alumni.rice.edu> <1115269161.23405.19.camel@leguin>  <4279AC8A.7060208@alumni.rice.edu> <1115270660.23405.21.camel@leguin>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
On 05/05/05 00:24, Eric Anholt wrote:
> On Thu, 2005-05-05 at 00:18 -0500, Jonathan Noack wrote:
>>On 05/04/05 23:59, Eric Anholt wrote:
>>>On Wed, 2005-05-04 at 23:48 -0500, Jonathan Noack wrote:
>>>>I decided to play around with all the new DRM/DRI/XORG/ETC stuff.  I 
>>>>looked over at the r300.sourceforge.net site for some info, added my 
>>>>All-In-Wonder 9800 Pro to the PCI IDs (see attached drm.diff), and then 
>>>>kldloaded radeon.  Looks like it worked successfully:
>>>>
>>>>kernel: drm0: <ATI Radeon NH R350 9800 Pro> port 0x7800-0x78ff mem 
>>>>0xd0000000-0xd7ffffff,0xefcf0000-0xefcfffff irq 16 at device 0.0 on pci1
>>>>kernel: info: [drm] AGP at 0xe0000000 128MB
>>>>kernel: info: [drm] Initialized radeon 1.16.0 20050311 on minor 0
>>>>kernel: info: [drm] Loading R300 Microcode
>>>>
>>>>With the xorg-server-snapshot and dri-devel I seem to have even enabled 
>>>>direct rendering (see Xorg log output in attached drm.txt), although 
>>>>render acceleration is disabled.
>>>
>>>You did install both the DRM and DRI driver from r300.sf.net CVS, right?
>>>I was wrong about our kernel DRM really supporting r300 -- the
>>>development is now happening in their CVS, until they get things
>>>stabilized.
>>>
>>>This patch should be sent to r300.sf.net folks once you get it working,
>>>assuming they don't already have it in their CVS.
>>>
>>>http://dri.sourceforge.net/cgi-bin/moin.cgi/DriTroubleshooting  has
>>>instructions on troubleshooting DRI issues.
>>
>>No, that patch is the only change I made.  I pulled the PCI ID from the 
>>r300 CVS, so they already have it.  If the r300 support in our kernel 
>>DRM doesn't work then I have accomplished nothing because I was just 
>>making the r350 look like an r300.  So much for the easy way...
> 
> Hopefully soon they'll be ready to merge back to DRM and Mesa CVS.  I'll
> only be merging DRM CVS to FreeBSD-current, though.

Makes sense.  Until then I'll try to get it working from CVS.  You took 
care of Step 1 of the setup instructions with the xorg-server-snap port, 
so thanks!

-- 
Jonathan Noack | noackjr@alumni.rice.edu | OpenPGP: 0x991D8195

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFCebGpUFz01pkdgZURAr/GAKC6NC+1ah3MoQ3WTAGTyLydoKDOpQCgvTG6
YN8mZgn+yIdpBBDaEtTlhQQ=
=Tryc
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4279B1A4.7020003>