All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Linux 2.5.60-dj2
Date: Tue, 11 Feb 2003 18:22:56 +0000	[thread overview]
Message-ID: <20030211182256.GA28903@codemonkey.org.uk> (raw)

Been a while since I did a -dj, but I've accumulated a bunch
of driver stuff (which shouldn't crossover too much with what
Andrew is doing in -mm) that could use some extra testing,
so here's what I've been up to of late..

ftp://ftp.kernel.org/pub/linux/kernel/people/davej/patches/2.5/2.5.60/

(Thanks to Steven Cole for noticing the agp problems before I
 even got a chance to write the changelog 8-)

2.5.60-dj2
- Fix up modules versioning (Kai)
- Throw out some stale agpgart bits that broke the compile.


2.5.60-dj1
- cpufreq updates.
  - Athlon/Duron powernow cpufreq support.
    Handle with care. Only known bug is that the top speed
	isn't usable.
  - Updates various core parts, and other cpufreq drivers.
- AGPGART updates
  VIA KT400 support.
  Updated VIA AGP2.0 GART tables (PLE133 and others).
  Various cleanups.
- VIA C3 Nehemiah support.
  Compiles as i686/c3-2, works around L2 cache size errata.
- Watchdog fixes
  sc1200wdt PNP API conversion (Adam Belay)
- Lots of other leftovers from older -dj patches
  This stuff needs sorting, and some bits throwing out.
  There's lots of 2.4 forward port stuff here, and more
  pending.
- Latest from Linus' bk tree.
  (Just there to help me stay in sync)

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

             reply	other threads:[~2003-02-11 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-11 18:22 Dave Jones [this message]
2003-02-12 13:47 ` 2.5.60-dj2: lonkhaul.c doesn't compile Adrian Bunk
2003-02-12 13:49   ` 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=20030211182256.GA28903@codemonkey.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.