From: Stephan von Krawczynski <skraw@ithnet.com>
To: Didier Moens <moensd@xs4all.be>
Cc: rml@tech9.net, Nicolas.Aspert@epfl.ch, linux-kernel@vger.kernel.org
Subject: Re: [Fwd: Re: OOPS in agpgart (2.4.13, 2.4.15pre7)]
Date: Tue, 27 Nov 2001 11:51:03 +0100 [thread overview]
Message-ID: <20011127115103.2928bd15.skraw@ithnet.com> (raw)
In-Reply-To: <3C02BF41.1010303@xs4all.be>
In-Reply-To: <linux.kernel.3C021570.4000603@dmb.rug.ac.be> <3C022BB4.7080707@epfl.ch> <1006808870.817.0.camel@phantasy> <3C02BF41.1010303@xs4all.be>
On Mon, 26 Nov 2001 23:16:33 +0100
Didier Moens <moensd@xs4all.be> wrote:
> Dear Robert, Nicolas, Stephan, :)
>
> I got two patches :
>
>
> 1. From Stephan, to test whether my assumption about the secondary
> device was right :
>
> Stephan wrote :
>
> But if you want you can check that out pretty simple: just add a "break"
> right
> after the case :
>
> case PCI_DEVICE_ID_INTEL_830_M_0:
> ---> break;
>
> i810_dev = pci_find_device(PCI_VENDOR_ID_INTEL,
>
>
> This patch left me with a loaded agpgart, and accelerated X (DRM/DRI).
> The acceleration is still not up to par with an ATI Mobility-128 (30%
> lower, while it should be at least 200% faster), but I suspect an X
> CVS-problem here.
>
> Quitting and restarting X leaves me with a locked black screen.
Can you provide the output provided by the agp module at load time, please?
This mini-patch of mine should indeed be technically sufficient. Of course I
will provide a "real-world" patch working for all i830 agp-chipsets (M or MG)
as soon as it is clear, that the detection still works.
I am a bit bothered by your X setup. Can you stabilize this somehow? Maybe
using some known-to-work (older) X version for your graphics card.
It looks solvable.
Regards,
Stephan
next prev parent reply other threads:[~2001-11-27 10:51 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 ` [Fwd: Re: OOPS in agpgart (2.4.13, 2.4.15pre7)] 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 11:12 ` Stephan von Krawczynski
2001-11-27 11:43 ` Nicolas Aspert
2001-11-27 12:10 ` Stephan von Krawczynski
2001-11-27 12:49 ` Didier Moens
2001-11-27 10:51 ` Stephan von Krawczynski [this message]
2001-11-26 12:43 ` [PATCH]Re: " Nicolas Aspert
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=20011127115103.2928bd15.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=Nicolas.Aspert@epfl.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=moensd@xs4all.be \
--cc=rml@tech9.net \
/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