mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: davej@codemonkey.org.uk
To: linux-kernel@vger.kernel.org
Subject: [CFT][2.5] AGPGART reworking.
Date: Tue, 3 Dec 2002 18:37:57 GMT	[thread overview]
Message-ID: <200212031837.gB3IbvQT008482@noodles.internal> (raw)

As per private discussion with Linus over the last few days,
I've reworked the AGPGART driver considerably.  There's likely
some gotchas left here, so I'd appreciate testers/code-review
of this quite large change (>200KB worth of diff, but several
files get moved about a bit).

- Introduces a new 'agp_register_driver' function, which is used
  to seperate the chipset drivers completely from the backend.

- chipset drivers become modules in their own right.
  This seems to work when everything is compiled in. Built as modules
  is untested yet, but it means right now you have to insmod via-agp.o
  or whatever chipset vendor you need before starting X.
  agp_try_supported() is now a param to the chipset modules, not the
  agpgart.o module.

- i8x0.c & i810.c have become intel-agp.c
  CONFIG_AGP_I810 is currently broken, I'll fix this up soon.

- agp.c becomes backend.c

- split out generic routines into generic.c

- version number bump to 1.0
  This is a pretty major change IMO, and it's been stuck at 0.99 forever.

- Cast fixes (Alan)

- x86-64 fixes (Andi)

- Add recognition for several new devices.

- list myself as maintainer of 1.0+
  Jeff Hartmann hasn't done any considerable work on agpgart since `99
  to my knowledge. Attempts to contact him in the past have failed.

You can get this from bk://linux-dj.bkbits.net/agpgart or for the
bk-challenged, you can get the gnu diff at ..
 ftp.kernel.org/pub/linux/kernel/people/davej/patches/2.5/2.5.50/agpgart-recore-2.diff.gz

		Dave


             reply	other threads:[~2002-12-03 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 18:37 davej [this message]
2002-12-04  8:36 ` Rudmer van Dijk

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=200212031837.gB3IbvQT008482@noodles.internal \
    --to=davej@codemonkey.org.uk \
    --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

all inboxes | Powered by JetHome®