Re: [Dri-devel] HEADSUP: freedesktop vs sourceforge CVS status
On Sat, 2003-09-13 at 05:45, Alan Hourihane wrote: > On Sat, Sep 13, 2003 at 12:19:44PM +0100, Alan Hourihane wrote: > > On Fri, Sep 12, 2003 at 12:35:30PM -0700, Eric Anholt wrote: > > > On Fri, 2003-09-12 at 07:22, Ian Romanick wrote: > > > > Alan Hourihane wrote: > > > > > > > > > CVSROOT: /cvsroot/dri > > > > > Module name: xc > > > > > Repository: xc/xc/ > > > > > Changes by: [EMAIL PROTECTED] 03/09/12 04:23:10 > > > > > > > > On which server are you doing these commits? From the looks of it, > > > > you're doing them on the SourceForge server. I thought we weren't going > > > > to do that anymore. Is the freedesktop server ready for prime-time > > > > (i.e., does it have the "latest" CVS ,v files)? > > > > > > sourceforge.net has remained the place to be working until we get the > > > final move done, which I'll announce when it's completed. It's been > > > stalled on getting a new repo tarball from sourceforge.net. Today I got > > > a reponse (again) saying it was fixed, and this time it is. > > > > > > So: > > > Tomorrow, at around 3:00pm pacific I expect, I'll grab the tarball and > > > update dri.freedesktop.org. If you do commits between now and then, it > > > may not be reflected in that tarball, so I guess you'll just have to do > > > any commits again on dri.freedesktop.org. You may want to just save > > > them for tomorrow. (I'm saying tomorrow instead of right this minute > > > because of the 4.3.99.12 merge, which looks like it isn't in the current > > > tarball) > > > > O.k. I'm still finishing off the merge, but I'll tag it with > > XFree86-4_3_99_12-merge when I'm done. So as long as that tag exists > > in the tarball we'll be o.k. > > O.k. I've tagged the trunk. I've also generated a 5MB patch file against > XFree86, but most of that is Mesa 5.0.2. There are a few loose ends, but > nothing major that I'll fix up once we're on dri.freedesktop.org. Sigh. The nightly CVS tarball wasn't updated last night. I've submitted another support request asking if they can either produce another tarball or give us an idea of when the next one can be produced. Until I get a response, if folks can hang on, that would be great. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: [Dri-devel] ATI Radeon 9200 SE
Maybe the printed strings in your patch should mention the "SE" so that no one gets confused. Anything else looks smooth to me right now. -Alex. > -Original Message- > From: Michel Dänzer [mailto:[EMAIL PROTECTED] > Sent: Saturday, September 13, 2003 22:08 > To: #NGUYEN THANH NAM# > Cc: [EMAIL PROTECTED] > Subject: Re: [Dri-devel] ATI Radeon 9200 SE > > > On Sat, 2003-09-13 at 17:13, #NGUYEN THANH NAM# wrote: > > > > I bought a Creative 3D Blaster 5 RX9200 SE (uses ATI Radeon > 9200 SE chip). When I did a lspci the revision shown was > 0x5964 (and there was another one too, I guess it is for > secondary display). However, the radeon driver only supports > 0x5960 to 0x5963 (I checked against the latest radeon-pci.h) > > > > #define PCI_CHIP_RV280_5960 0x5960 > > #define PCI_CHIP_RV280_5961 0x5961 > > #define PCI_CHIP_RV280_5962 0x5962 > > #define PCI_CHIP_RV280_5963 0x5963 > > > > So I was just wondering whether another line like this > > > > #define PCI_CHIP_RV280_5964 0x5964 > > > > would make it work for me. > > You also need to add it some other places, try this patch. > > > -- > Earthling Michel Dänzer \ Debian (powerpc), XFree86 and > DRI developer > Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] ATI Radeon 9200 SE
On Sat, 2003-09-13 at 17:38, Adam K Kirchhoff wrote: > In the "Device" section of your XF86Config-4 file, you should add the > following line: > > ChipID 0x4242 One of the other 9200 IDs he mentioned would probably be better for him. > My Device section looks like: > > Section "Device" > Identifier "Radeon" > Driver "radeon" > BusID "PCI:1:0:0" > Option "AGPMode" "4" > Option "AGPSize" "128" BTW, I renamed this to "GARTSize" in current DRI CVS. > Option "EnablePageflip" "1" > ChipID 0x4242 > Screen 0 > EndSection -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] ATI Radeon 9200 SE
On Sat, 2003-09-13 at 17:13, #NGUYEN THANH NAM# wrote:
>
> I bought a Creative 3D Blaster 5 RX9200 SE (uses ATI Radeon 9200 SE chip). When I
> did a lspci the revision shown was 0x5964 (and there was another one too, I guess it
> is for secondary display). However, the radeon driver only supports 0x5960 to 0x5963
> (I checked against the latest radeon-pci.h)
>
> #define PCI_CHIP_RV280_5960 0x5960
> #define PCI_CHIP_RV280_5961 0x5961
> #define PCI_CHIP_RV280_5962 0x5962
> #define PCI_CHIP_RV280_5963 0x5963
>
> So I was just wondering whether another line like this
>
> #define PCI_CHIP_RV280_5964 0x5964
>
> would make it work for me.
You also need to add it some other places, try this patch.
--
Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer
Index: programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c
===
RCS file: /cvsroot/dri/xc/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c,v
retrieving revision 1.62
diff -p -u -r1.62 radeon_driver.c
--- programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 12 Sep 2003 20:33:25 - 1.62
+++ programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 13 Sep 2003 20:03:58 -
@@ -1921,6 +1927,7 @@ static Bool RADEONPreInitConfig(ScrnInfo
case PCI_CHIP_RV280_5961:
case PCI_CHIP_RV280_5962:
case PCI_CHIP_RV280_5963:
+case PCI_CHIP_RV280_5964:
info->ChipFamily = CHIP_FAMILY_RV280;
break;
Index: programs/Xserver/hw/xfree86/drivers/ati/radeon_pci.h
===
RCS file: /cvsroot/dri/xc/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_pci.h,v
retrieving revision 1.1
diff -p -u -r1.1 radeon_pci.h
--- programs/Xserver/hw/xfree86/drivers/ati/radeon_pci.h 18 Aug 2003 16:49:59 - 1.1
+++ programs/Xserver/hw/xfree86/drivers/ati/radeon_pci.h 13 Sep 2003 20:03:58 -
@@ -95,6 +95,7 @@
#define PCI_CHIP_RV280_5961 0x5961
#define PCI_CHIP_RV280_5962 0x5962
#define PCI_CHIP_RV280_5963 0x5963
+#define PCI_CHIP_RV280_5964 0x5964
#define PCI_CHIP_RV280_5968 0x5968
#define PCI_CHIP_RV280_5969 0x5969
#define PCI_CHIP_RV280_596A 0x596A
Index: programs/Xserver/hw/xfree86/drivers/ati/radeon_probe.c
===
RCS file: /cvsroot/dri/xc/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_probe.c,v
retrieving revision 1.16
diff -p -u -r1.16 radeon_probe.c
--- programs/Xserver/hw/xfree86/drivers/ati/radeon_probe.c 12 Sep 2003 20:33:25 - 1.16
+++ programs/Xserver/hw/xfree86/drivers/ati/radeon_probe.c 13 Sep 2003 20:03:59 -
@@ -130,6 +130,7 @@ SymTabRec RADEONChipsets[] = {
{ PCI_CHIP_RV280_5961, "ATI Radeon 9200 5961 (AGP)" },
{ PCI_CHIP_RV280_5962, "ATI Radeon 9200 5962 (AGP)" },
{ PCI_CHIP_RV280_5963, "ATI Radeon 9200 5963 (AGP)" },
+{ PCI_CHIP_RV280_5964, "ATI Radeon 9200 5964 (AGP)" },
{ PCI_CHIP_RV280_5968, "ATI Radeon M9+ 5968 (AGP)" },
{ PCI_CHIP_RV280_5969, "ATI Radeon M9+ 5969 (AGP)" },
{ PCI_CHIP_RV280_596A, "ATI Radeon M9+ 596A (AGP)" },
@@ -198,6 +199,7 @@ PciChipsets RADEONPciChipsets[] = {
{ PCI_CHIP_RV280_5961, PCI_CHIP_RV280_5961, RES_SHARED_VGA },
{ PCI_CHIP_RV280_5962, PCI_CHIP_RV280_5962, RES_SHARED_VGA },
{ PCI_CHIP_RV280_5963, PCI_CHIP_RV280_5963, RES_SHARED_VGA },
+{ PCI_CHIP_RV280_5964, PCI_CHIP_RV280_5964, RES_SHARED_VGA },
{ PCI_CHIP_RV280_5968, PCI_CHIP_RV280_5968, RES_SHARED_VGA },
{ PCI_CHIP_RV280_5969, PCI_CHIP_RV280_5969, RES_SHARED_VGA },
{ PCI_CHIP_RV280_596A, PCI_CHIP_RV280_596A, RES_SHARED_VGA },
Re: [Dri-devel] G550 dodgey lighting
On Fri, 2003-09-12 at 23:12, Ville Syrjälä wrote: > On Fri, Sep 12, 2003 at 03:58:35PM +0100, Bob Ham wrote: > > On Thu, 2003-09-11 at 17:08, Ville Syrjälä > > > > > > http://rose.clear.bash.sh/~rah/planeshift-dodgey-lighting.jpeg > > > > > > This is mentioned in the planeshift buglist so I'm not sure it's mga > > > specific. Updating to DRI's cvs has gotten rid of it in everything, including planeshift. Unfortuately, it seems to be at the expense of objects' polygons sometimes disappearing for an instant and then reappearing. This is nowhere hear as offputting tho, so I'll stick with CVS I reckon :) Cheers, Bob -- Bob Ham <[EMAIL PROTECTED]> Can you say "death chambers at Guantanamo with no real trial"? signature.asc Description: This is a digitally signed message part
Re: [Dri-devel] ATI Radeon 9200 SE
In the "Device" section of your XF86Config-4 file, you should add the following line: ChipID 0x4242 My Device section looks like: Section "Device" Identifier "Radeon" Driver "radeon" BusID "PCI:1:0:0" Option "AGPMode" "4" Option "AGPSize" "128" Option "EnablePageflip" "1" ChipID 0x4242 Screen 0 EndSection Adam --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] ATI Radeon 9200 SE
Hi, I bought a Creative 3D Blaster 5 RX9200 SE (uses ATI Radeon 9200 SE chip). When I did a lspci the revision shown was 0x5964 (and there was another one too, I guess it is for secondary display). However, the radeon driver only supports 0x5960 to 0x5963 (I checked against the latest radeon-pci.h) #define PCI_CHIP_RV280_5960 0x5960 #define PCI_CHIP_RV280_5961 0x5961 #define PCI_CHIP_RV280_5962 0x5962 #define PCI_CHIP_RV280_5963 0x5963 So I was just wondering whether another line like this #define PCI_CHIP_RV280_5964 0x5964 would make it work for me. Can any one give me some advices as to what files to edit? Thanks. Nam --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] HEADSUP: freedesktop vs sourceforge CVS status
On Sat, Sep 13, 2003 at 12:19:44PM +0100, Alan Hourihane wrote: > On Fri, Sep 12, 2003 at 12:35:30PM -0700, Eric Anholt wrote: > > On Fri, 2003-09-12 at 07:22, Ian Romanick wrote: > > > Alan Hourihane wrote: > > > > > > > CVSROOT:/cvsroot/dri > > > > Module name:xc > > > > Repository: xc/xc/ > > > > Changes by: [EMAIL PROTECTED] 03/09/12 04:23:10 > > > > > > On which server are you doing these commits? From the looks of it, > > > you're doing them on the SourceForge server. I thought we weren't going > > > to do that anymore. Is the freedesktop server ready for prime-time > > > (i.e., does it have the "latest" CVS ,v files)? > > > > sourceforge.net has remained the place to be working until we get the > > final move done, which I'll announce when it's completed. It's been > > stalled on getting a new repo tarball from sourceforge.net. Today I got > > a reponse (again) saying it was fixed, and this time it is. > > > > So: > > Tomorrow, at around 3:00pm pacific I expect, I'll grab the tarball and > > update dri.freedesktop.org. If you do commits between now and then, it > > may not be reflected in that tarball, so I guess you'll just have to do > > any commits again on dri.freedesktop.org. You may want to just save > > them for tomorrow. (I'm saying tomorrow instead of right this minute > > because of the 4.3.99.12 merge, which looks like it isn't in the current > > tarball) > > O.k. I'm still finishing off the merge, but I'll tag it with > XFree86-4_3_99_12-merge when I'm done. So as long as that tag exists > in the tarball we'll be o.k. O.k. I've tagged the trunk. I've also generated a 5MB patch file against XFree86, but most of that is Mesa 5.0.2. There are a few loose ends, but nothing major that I'll fix up once we're on dri.freedesktop.org. Thanks for your patience. Alan. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] HEADSUP: freedesktop vs sourceforge CVS status
On Fri, 2003-09-12 at 07:22, Ian Romanick wrote: > Alan Hourihane wrote: > > > CVSROOT:/cvsroot/dri > > Module name:xc > > Repository: xc/xc/ > > Changes by: [EMAIL PROTECTED] 03/09/12 04:23:10 > > On which server are you doing these commits? From the looks of it, > you're doing them on the SourceForge server. I thought we weren't going > to do that anymore. Is the freedesktop server ready for prime-time > (i.e., does it have the "latest" CVS ,v files)? sourceforge.net has remained the place to be working until we get the final move done, which I'll announce when it's completed. It's been stalled on getting a new repo tarball from sourceforge.net. Today I got a reponse (again) saying it was fixed, and this time it is. So: Tomorrow, at around 3:00pm pacific I expect, I'll grab the tarball and update dri.freedesktop.org. If you do commits between now and then, it may not be reflected in that tarball, so I guess you'll just have to do any commits again on dri.freedesktop.org. You may want to just save them for tomorrow. (I'm saying tomorrow instead of right this minute because of the 4.3.99.12 merge, which looks like it isn't in the current tarball) P.S. Sorry for the screwups on people not being able to make cvs locks on dri.freedesktop.org. I had created users in a different manner than the standard for freedesktop.org, and when I was fixing things up I hadn't readded people to the "dri" group. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] HEADSUP: freedesktop vs sourceforge CVS status
On Fri, Sep 12, 2003 at 12:35:30PM -0700, Eric Anholt wrote: > On Fri, 2003-09-12 at 07:22, Ian Romanick wrote: > > Alan Hourihane wrote: > > > > > CVSROOT: /cvsroot/dri > > > Module name: xc > > > Repository: xc/xc/ > > > Changes by: [EMAIL PROTECTED] 03/09/12 04:23:10 > > > > On which server are you doing these commits? From the looks of it, > > you're doing them on the SourceForge server. I thought we weren't going > > to do that anymore. Is the freedesktop server ready for prime-time > > (i.e., does it have the "latest" CVS ,v files)? > > sourceforge.net has remained the place to be working until we get the > final move done, which I'll announce when it's completed. It's been > stalled on getting a new repo tarball from sourceforge.net. Today I got > a reponse (again) saying it was fixed, and this time it is. > > So: > Tomorrow, at around 3:00pm pacific I expect, I'll grab the tarball and > update dri.freedesktop.org. If you do commits between now and then, it > may not be reflected in that tarball, so I guess you'll just have to do > any commits again on dri.freedesktop.org. You may want to just save > them for tomorrow. (I'm saying tomorrow instead of right this minute > because of the 4.3.99.12 merge, which looks like it isn't in the current > tarball) O.k. I'm still finishing off the merge, but I'll tag it with XFree86-4_3_99_12-merge when I'm done. So as long as that tag exists in the tarball we'll be o.k. Alan. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] cvs tarball from sf.net..
Okay there is one in my a/c on freedesktop.org with Sep 12 00:20 on it, but I'm sure it is from the backup server not the primary.. so it is probably missing 24 hrs of commits.. the history file in CVSROOT is probably the best place to start... god knows how long it will be until sf update the tarrball again.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Your Bugzilla buglist needs attention.
[This e-mail has been automatically generated.Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.] You have one or more bugs assigned to you in the Bugzilla bugsystem (http://bugs.xfree86.org/) that require attention. All of these bugs are in the NEW state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reassign bug to owner of selected component" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Just use the "Accept bug" command. To get a list of all NEW bugs, you can use this URL (bookmark it if you like!): http://bugs.xfree86.org/buglist.cgi?bug_status=NEW&[EMAIL PROTECTED] Or, you can use the general query page, at http://bugs.xfree86.org/query.cgi. Appended below are the individual URLs to get to all of your NEW bugs that haven't been touched for a week or more. You will get this message once a day until you've dealt with these bugs! radeon_vtxfmt.c:1057: radeonVtxfmtUnbindContext: Assertion `vb.context == ctx' failed. -> http://bugs.xfree86.org/show_bug.cgi?id=25 RFE: Add support for DRI with Xinerama configurations -> http://bugs.xfree86.org/show_bug.cgi?id=62 3D object surfaces 'randomly' render red -> http://bugs.xfree86.org/show_bug.cgi?id=98 Metabug - Mach64 DRI is not merged into the [DRI] trunk. -> http://bugs.xfree86.org/show_bug.cgi?id=131 Random triangle rendering dropout in Radeon DRI -> http://bugs.xfree86.org/show_bug.cgi?id=185 "euphoria" (really-slick screensavers) repeatably locks up system -> http://bugs.xfree86.org/show_bug.cgi?id=271 Two-sided lighting not working properly -> http://bugs.xfree86.org/show_bug.cgi?id=566 Screen remains blank when starting X w/ radeon 3D enabled -> http://bugs.xfree86.org/show_bug.cgi?id=609 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: XFree86 merge
On Fri, 12 Sep 2003, Alan Hourihane wrote: >> > Do DRI developers need to worry about that ? >> >> It's no problem for me personally, no idea about other developers, but >> what about users? > >They didn't have IPv6 before, so if it doesn't work now, there's still >no problem for users. The problem with the IPv6 support commited to XFree86 CVS, was that it requires the system to have IPv6 support wether you actually use IPv6 at all or not. In other words, if your kernel does not support IPv6, then you can not use XFree86 CVS as it requires IPv6 unconditionally to be available on the system wether or not the X server will actually be used with IPv6. That was the original problem, however I do not know if that is still the case or wether it's been fixed now or not. It's possible that someone fixed the IPv6 to not be unconditional, but if it did get fixed, I must have missed seeing the checkin. If the issue is still present however, then anyone compiling XFree86 CVS and using it must have IPv6 on their system, even if they don't use it. Hope this helps. TTYL -- Mike A. Harris --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] New gatos API.
On Fri, 2003-09-12 at 00:01, Mike Mestnik wrote: > > The main goal is to get a working DRI that has the new API, and maby some gatos > bells and > whistles. I'm assuming you read my post that recent DRI is to different from gatos. > My plan was > to diff gatos and DRI and weed ought all the changes that where depreciated. With > that patch one > could create the new DRI. I'm afraid it's not that simple, some new code needs to be written to be able to merge the two. > It seams as thought some of the developers are interested in making the > new DRI backwards compatible. More than that, backwards compatibility is a requirement, otherwise the DRM gets kicked out of the kernel by Linus. > -- Laurent Pinchart <[EMAIL PROTECTED]> wrote: > > > > I was also wondering if the move to the Gatos memory layout should not take > > into account the possible separation between X and the DRI (there have been > > several mails on this mailing list about splitting X and the DRI, and having > > X use OpenGL as its low-level API). Just my 2 cents... > > > There plan was to have a portable common driver, I don't see why this driver can't > use the new API > :). In fact, in the proposed solution (have you gotten any feedback on it by the GATOS people yet?), the DRM can fix up the difference between what the 3D driver thinks the memory layout is and what it actually is. -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
