public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: dri-devel@lists.sourceforge.net
Subject: [PATCH] Split up agpgart into per implementation files.
Date: Wed, 19 Jun 2002 17:19:19 +0100	[thread overview]
Message-ID: <20020619161919.GA14826@suse.de> (raw)

Something I've been meaning to do for a long time, and no-one has
beaten me to it, is to do something about agpgart_be.c, which seems
to grow and grow and..

I've just put up a patch at..
 ftp.kernel.org/pub/linux/kernel/people/davej/patches/agp/
which splits up the huge monolithic file into implementation
specific files.

This is a first cut, so I'll not be surprised if you manage to break
the compile, but please do try.. I've tried several combinations,
and it all seems to work out ok, but I can only test on VIA boards
here. You should see absolutely no change in behaviour if all goes
to plan.

I'm particularly interested in hearing if I got the CONFIG_AGP_I180
changes right.  The patch is against 2.5.23, but may apply with
trivial rejects to 2.4-current if you're feeling lucky.

There's lots more that can be done to cut down some of the duplication
that this patch introduces, but it's a good start at making the
backend code a little easier to navigate.

Comments?

		Dave.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

             reply	other threads:[~2002-06-19 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 16:19 Dave Jones [this message]
     [not found] <fa.ep8m4pv.1gkki2v@ifi.uio.no>
2002-06-20 12:49 ` [PATCH] Split up agpgart into per implementation files Nicolas Aspert
2002-06-20 14:06   ` Dave Jones
2002-06-20 14:32     ` Nicolas Aspert

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=20020619161919.GA14826@suse.de \
    --to=davej@suse.de \
    --cc=dri-devel@lists.sourceforge.net \
    --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