R500 initial driver release announcement

[Robert Y]

On 6/16/07, Jerome Glisse <j.glisse at gmail.com> wrote:
> On 6/15/07, Robert Y <rob2687.nix at gmail.com> wrote:
> > On 6/15/07, Nathanael D. Noblet <nathanael at gnat.ca> wrote:
> > > Robert Y wrote:
> > > > Hi,
> > > > I have tested this on my x1900xtx the device id is 7249. It seems to
> > > > work without any major graphical glitches or artifacts but only at 24
> > > > bit depth. If I set it to 16 bit it shows a green screen then the system
> > > > locks up. Also I have to unload the fglrx module otherwise the system
> > > > will lock up when X starts.
> > >
> > > I've been attempting to get it to work on my x1650 (pro). device id
> > > 71c6. I'm curious, I'm on F7, and so the fglrx driver won't get as far
> > > as starting X. However do you run X with fglrx as the driver normally,
> > > before using the avivo driver and unloading the kernel module? If I load
> > > the kernel module and unload it then use the avivo driver it starts to
> > > initialize X but then just 'hangs' in that I can't switch terminals,
> > > move the mouse etc. ssh is still fine and I can ctrl-alt-del to a clean
> > > reboot... Just wondering what situation you are using fglrx in.
> > >
> >
> > I use fglrx 8.37.6 on Ubuntu Gutsy with no problems. Avivo works as
> > long as the fglrx module isn't loaded. I don't need to use fglrx first
> > or anything.
>
>
> Strange last time we checked the driver on x1900 hw it wasn't working
> out of box. Maybe your bios is doing a lot more initialization than other
> bios. I might need you to spy this out, i will upload the tools somewhere
> and ping you.
>
> best,
> Jerome Glisse
>

I have been poking around with Valgrind, avivo tool and  radeondump.
Honestly I don't know what I'm doing here most of the time... I have
done a dcomp with the outputs from radeondump. For both drivers I did
a cold boot and got a few dumps after doing vt switching, glxgears,
etc.. WIth the avivo driver X restarts when I vt switch though.
Specifically when switching back to X. I have attached the dcomp
output.

I'm not sure if I've done it right. I'll be in #dri-devel once in a
while under the nick. Rob2687.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dcomp.out
Type: application/octet-stream
Size: 3881 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20070616/e2d8caf6/attachment.obj>