From: Dave Jones <davej@codemonkey.org.uk>
To: BoehmeSilvio <Boehme.Silvio@afb.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-ac1 KT400 AGP support
Date: Fri, 13 Dec 2002 16:36:01 +0000 [thread overview]
Message-ID: <20021213163601.GB1633@suse.de> (raw)
In-Reply-To: <2F4E8F809920D611B0B300508BDE95FE294452@AFB91>
On Fri, Dec 13, 2002 at 11:18:39AM +0100, BoehmeSilvio wrote:
> I don't need the AGP 8X mode, but is it possible,
> to get this setup running in whatever agp mode ?
You misunderstand. You have an AGP 3.0 bridge.
Various things are done differently to how they were in previous
revisions of the standard. For example, the aperture size is now
a 16 bit field (which is why people are getting that
"can't determine aperture size" error).
I'm working on merging the Intel patches posted here a while
ago, and bending the generic bits into something that *might*
work (I don't have a board to test -- I'll shout when I have
something I want people to test with), note that I'm doing this
for 2.5 however. 2.4 is going to have to wait.
> Currently it is only possible to start X with VESA support,
> because all other drivers need agpgart.
X should start, but you'll get no accelerated 3d.
None of the X drivers _need_ agpgart except for maybe the
i810 with shared memory.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-12-13 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 10:18 2.4.20-ac1 KT400 AGP support BoehmeSilvio
2002-12-13 16:36 ` Dave Jones [this message]
2002-12-14 1:57 ` Courtney Grimland
2002-12-14 10:13 ` Dave Jones
2002-12-14 19:15 ` Courtney Grimland
-- strict thread matches above, loose matches on Subject: below --
2002-12-14 22:55 Nicolas Mailhot
2002-12-12 18:04 BoehmeSilvio
2002-12-12 19:20 ` Dave Jones
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=20021213163601.GB1633@suse.de \
--to=davej@codemonkey.org.uk \
--cc=Boehme.Silvio@afb.de \
--cc=linux-kernel@vger.kernel.org \
/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