mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Didier Moens <Didier.Moens@dmb001.rug.ac.be>
To: Nicolas Aspert <Nicolas.Aspert@epfl.ch>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
	abraham@2d3d.co.za, linux-kernel@vger.kernel.org,
	Robert Love <rml@tech9.net>
Subject: Re: [Fwd: Re: OOPS in agpgart (2.4.13, 2.4.15pre7)]
Date: Tue, 27 Nov 2001 13:49:42 +0100	[thread overview]
Message-ID: <3C038BE6.3060605@dmb.rug.ac.be> (raw)
In-Reply-To: <linux.kernel.3C021570.4000603@dmb.rug.ac.be> <3C022BB4.7080707@epfl.ch> <1006808870.817.0.camel@phantasy> <3C02BF41.1010303@xs4all.be> <20011127101148.C5778@crystal.2d3d.co.za> <3C034CAE.2090103@dmb.rug.ac.be> <3C036F83.2000903@dmb.rug.ac.be> <20011127121228.0df6db46.skraw@ithnet.com> <3C037C73.3090003@epfl.ch>

Nicolas Aspert wrote:

> 
>>
>> Ok, since performance and detection seems just ok, I would suggest the 
>> attached
>> patch as a fix. Unlike Nicolas I don't see a need for an additional 
>> i830MP
>> patch, its only the correct detection of the different i830 setups 
>> that needs
>> to be done IMHO.
>> If there are no further complaints we should submit the patch. What do 
>> you
>> think Nicolas?
>>
> 
> Well, I prefer my version on the patch (of course :-), and I find it 
> cleaner. Let me explain why : by just adding the 'break', you will fall 
> back to the generic initialization routines, which work in most of the 
> cases. However, if you look deeper the code & the specs, they are not 
> really that good. Esp., you will see that the APSIZE register is 
> accessed through 16bit reads/writes, whereas the spec says this is a 8 
> bit register. I have been taught not to write where it is not 
> explicitely allowed to. Moreover, the 'tlbflush' mechanism also writes 
> over reserved bits when using the generic routine. My patch is just a 
> adaptation of what had been done for the Intel 8xx routines (to which I 
> have contributed), so my way is more consistent with what was previously 
> done.
> However, before submitting the patch, I would like to hear from Didier 
> about the X server stuff.
> Does it still hard-locks when you start it ? If testgart works (which 
> seems to be the case... btw, yes the 8MB alloced by the program are 
> normal) and X locks, this would look more like a DRI/X problem (I saw 
> some problems w. Radeon cards on the dri-devel list, which do not seem 
> to be fully solved yet)


No more X hard locks.

Compiled & installed latest CVS X (20011127), which includes a Radeon 
DGA 2.0 patch : everything fine and dandy (except for my 3D performance 
problem).

Kudos to the developer community.


Kind regards,
Didier


Didier Moens
-----
RUG/VIB - Dept. Molecular Biology - Core IT
tel ++32(9)2645309 fax ++32(9)2645348
http://www.dmb.rug.ac.be


  reply	other threads:[~2001-11-27 12:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <linux.kernel.3C021570.4000603@dmb.rug.ac.be>
2001-11-26 11:47 ` Nicolas Aspert
2001-11-26 12:43 ` [PATCH]Re: " Nicolas Aspert
2001-11-26 21:07 ` Robert Love
2001-11-26 22:16   ` Didier Moens
2001-11-27  7:57     ` Nicolas Aspert
     [not found]     ` <20011127101148.C5778@crystal.2d3d.co.za>
     [not found]       ` <3C034CAE.2090103@dmb.rug.ac.be>
2001-11-27  9:10         ` Abraham vd Merwe
2001-11-27  9:52           ` Didier Moens
2001-11-27 10:05             ` Nicolas Aspert
2001-11-27 10:48               ` Didier Moens
2001-11-27 12:10                 ` Stephan von Krawczynski
2001-11-27 11:12         ` Stephan von Krawczynski
2001-11-27 11:43           ` Nicolas Aspert
2001-11-27 12:49             ` Didier Moens [this message]
2001-11-27 10:51   ` Stephan von Krawczynski
2001-11-26 10:12 Didier Moens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C038BE6.3060605@dmb.rug.ac.be \
    --to=didier.moens@dmb001.rug.ac.be \
    --cc=Nicolas.Aspert@epfl.ch \
    --cc=abraham@2d3d.co.za \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    --cc=skraw@ithnet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®