__put_page change in 2.6.17-rc1

2006-04-22 Thread Jesse Allen
Hi,

There has been a patch to 2.6.17-rc1
[PATCH] mm: make __put_page internal
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0f8053a509ceba4a077a50ea7b77039b5559b428

I believe this is causing drm cvs compiling to fail for the radeon module. I 
guess it is because __put_page's definition is hidden, and the drm cvs falls
back to an old definition in linux-core/drm_compat.h line 173. count vs 
_count. I made this patch to make it compile. Some please look at what
should be really done.

Jesse


--- drm-current/linux-core/drm_compat.h 2005-10-14 15:56:14.0 -0700
+++ drm/linux-core/drm_compat.h 2006-04-22 17:20:35.0 -0700
@@ -170,7 +170,10 @@ static inline void radeon_delete_i2c_bus
 #endif
 
 #ifndef __put_page
-#define __put_page(p)   atomic_dec((p)-count)
+static inline void __put_page(struct page *page)
+{
+   atomic_dec(page-_count);
+}
 #endif
 
 #ifndef REMAP_PAGE_RANGE_5_ARGS


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: ATI Mobility Radeon XPRESS 200

2006-03-23 Thread Jesse Allen
On 3/23/06, Scot Hetzel [EMAIL PROTECTED] wrote:
 I recently purchased a HP Pavilion dv81325nr.  This system uses a ATI
 Mobility Radeon Xpress 200 graphics card.

 When I booted FreeBSD 6.1-Beta 4, the radeon kernel module didn't
 detect this card.  I used pciconf -l -v, and it shows the following
 for this graphics card:

 [EMAIL PROTECTED]:5:0: class=0x03 card=0x309b103c chip=0x59551002 
 rev=0x00 hdr=0x00
 vendor   = 'ATI Technologies Inc'
 device   = 'Mobility Radeon XPRESS 200'
 class= display
 subclass = VGA

 I then added this cards chip id to sys/dev/drm/drm_pciids.h (see
 attached patch), recompiled the drm, and radeon kernel modules.  This
 allowed the radeon kernel module to detect the card.

 How do i test if this change is correct?

 Is this card in the current drm_pciid.txt file, if not could some on
 please added it?

 Scot
 --
 DISCLAIMER:
 No electrons were mamed while sending this message. Only slightly bruised.






The correct patch is found here:

https://bugs.freedesktop.org/attachment.cgi?id=4971

Beware it will lock up your machine when starting X.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: x700 and DRI

2006-03-23 Thread Jesse Allen
On 3/23/06, Roland Scheidegger [EMAIL PROTECTED] wrote:

 As Alex said, your drm is probably too old. Lots of pci ids (including
 those from X700) were just added a week ago and your drm looks way
 older. And, judging by the xorg log, the ddx is a bit oldish too, the
 memory detection output looks quite a bit different nowadays. If you're
 on x86_64, you may need to compile from cvs head.

 Roland


Do you think that the memory detection on the RS480 is correct now
with the recent changes?  I have not compiled xorg cvs since the
release of 6.9.  I have to switch to the modular build so I haven't
done it yet.

Jesse


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: Radeon Xpress 200 chipset

2006-03-08 Thread Jesse Allen
On 3/7/06, Dave Airlie [EMAIL PROTECTED] wrote:
 
  Based on X300 but isn't... it doesn't work yet due to having a
  different memory controller.. I've no idea how long it will take for
  someone to fix that or for me to get one long enough to play with it..
 
  Any possibility someone could enlighten me with ways to play around
  with my 200M?  I'd love to contribute some useful data that'll help us
  get the memory controller finally working.

 To be honest, it's not something for the feint of heart, you could get
 fglrx working on it, and start dumping the registers, but I'm not even
 sure where they are

 Dave.



One thing I just noticed with the video ram calculation on the 200M is
that when the BIOS setting is at 32 MB, DRI says it sees 8 MB.  I just
increased it to 128 MB, and now it says 32 MB. (Slightly less because
I guess DRI reserves some)  So the calculation is off by a factor of
four consistantly.  I wonder if we can find out why.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: 2.6.16-rc3: more regressions

2006-02-15 Thread Jesse Allen
On 2/13/06, Felix Kühling [EMAIL PROTECTED] wrote:
 Am Montag, den 13.02.2006, 16:27 -0700 schrieb Jesse Allen:
 
  Well a while back, I hacked in the pci id for my Xpress 200M (5955),
  which is basically an RV370 with no dedicated vram.  I did the same
  thing and claimed an RV350, which is the closest model.  This allowed
  the radeon module to load.  When I startx'ed and DRI was allowed to
  load on it, it locked up.  So I never sent in the patch.  I believe
  the person who sent this one in originally seemed to indicate that it
  worked, and I believed it if he had an X300 and my problem was having
  the IGP version.  But now having this reported, I'm pretty sure it is
  the same problem.  RV370 doesn't seem to work as an RV350.

 The Xpress200 chips have a completely different GART implementation.
 Thus the driver can't even send commands to the command processor and
 that's why X locked up on you when DRI was enabled. This has nothing to
 do with the Xpress200 being (almost) an RV370 or not.



Well, I did not know about the GART problem.  So this means that
RV370s and XPRESS will be listed both separately in the driver in the
future?  They certainly don't function as an RV350 and of course they
aren't quite compatable then.

Jesse


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: 2.6.16-rc3: more regressions

2006-02-13 Thread Jesse Allen
On 2/13/06, Linus Torvalds [EMAIL PROTECTED] wrote:


 On Mon, 13 Feb 2006, Adrian Bunk wrote:
 
  The one thing I have not yet been proven wrong for is that this PCI id
  is the only one we have in this driver for an RV370.

 It definitely is an RV370, you're right in that. I'm too lazy to actually
 see if the other entries that claim to be RV350's really are RV350's.


Well a while back, I hacked in the pci id for my Xpress 200M (5955),
which is basically an RV370 with no dedicated vram.  I did the same
thing and claimed an RV350, which is the closest model.  This allowed
the radeon module to load.  When I startx'ed and DRI was allowed to
load on it, it locked up.  So I never sent in the patch.  I believe
the person who sent this one in originally seemed to indicate that it
worked, and I believed it if he had an X300 and my problem was having
the IGP version.  But now having this reported, I'm pretty sure it is
the same problem.  RV370 doesn't seem to work as an RV350.

Jesse


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: Considering Radeon Xpress 200

2005-10-24 Thread Jesse Allen
I just bought a Compaq Presario V2405, which is similar to Daniel
Kasak's Turion.  It has the Xpress 200M as well but on a Sempron cpu. 
I got X.org cvs running with the 2d radeon driver just fine.  I had to
add its pci id for drm radeon module to load.  After starting X it
says there is not enough memory for dri, as it thinks it only has 7
mb.  I added the VideoRam option at 32768, but then X locks up at
black screen when starting, but can ssh in ok.

--- shared-core/drm_pciids.txt-orig 2005-10-24 18:23:53.0 -0700
+++ shared-core/drm_pciids.txt  2005-10-24 18:23:27.0 -0700
@@ -71,6 +71,7 @@
 0x1002 0x5835 CHIP_RS300|CHIP_IS_IGP|CHIP_IS_MOBILITY ATI Radeon
RS300 Mobility IGP
 0x1002 0x5836 CHIP_RS300|CHIP_IS_IGP ATI Radeon RS300 IGP
 0x1002 0x5837 CHIP_RS300|CHIP_IS_IGP ATI Radeon RS300 IGP
+0x1002 0x5955 CHIP_RV350|CHIP_IS_IGP ATI Radeon RV370 IGP XPRESS 200M
 0x1002 0x5960 CHIP_RV280 ATI Radeon RV280 9200
 0x1002 0x5961 CHIP_RV280 ATI Radeon RV280 9200 SE
 0x1002 0x5962 CHIP_RV280 ATI Radeon RV280 9200


---
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: Considering Radeon Xpress 200

2005-10-24 Thread Jesse Allen
On 10/24/05, Alex Deucher [EMAIL PROTECTED] wrote:
 On 10/24/05, Jesse Allen [EMAIL PROTECTED] wrote:
  mb.  I added the VideoRam option at 32768, but then X locks up at
  black screen when starting, but can ssh in ok.

 I'm not really sure how the newer IGPs deal with vram.  Hopefully you
 can adjust the amount in the bios, if not, someone needs to figure out
 how it needs to be done and implement it in the driver.  Unforunately,
 ati has not released any documentation on the XPRESS chips.

 Alex



Oh, the Bios has the setting at 32MB, and allows 64MB and 128MB.


---
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel