From: Tom Rini <trini@kernel•crashing.org>
To: Derrik Pates <dpates@dsdk12•net>
Cc: benh@kernel•crashing.org,
Christopher Murtagh <christopher.murtagh@mcgill•ca>,
yellowdog-devel@lists•yellowdoglinux.com,
Eric Leblond <eric@regit•org>,
linuxppc-dev@lists•linuxppc.org,
"Kevin B. Hendricks" <khendricks@ivey•uwo.ca>
Subject: Re: Support for new Dual G4 1 Gig machines?
Date: Tue, 29 Jan 2002 15:06:19 -0700 [thread overview]
Message-ID: <20020129220619.GH25973@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.43.0201291022250.27121-100000@andromeda.dsdk12.net>
On Tue, Jan 29, 2002 at 10:25:45AM -0700, Derrik Pates wrote:
>
> On Tue, 29 Jan 2002 benh@kernel•crashing.org wrote:
>
> > I recently spotted a problem with >512Mb (CONFIG_HIGHMEM or not) & SMP that
> > is fixed in the current bk _2_4 (2.4.18pre7). I also sent a fix to Marcelo
> > that should hopefully be in the next 2.4.18preX release.
> >
> > You should also use sungem preferably to the old gmac driver.
>
> Maybe you should officially deprecate the GMAC driver in favor of SunGEM,
> then? Put something on its line in the config scripts that says
> ***DEPRECATED***, and something in Configure.help for it that says
> something like "Please DO NOT use me, use the SunGEM driver instead!" so
> there's no question, so maybe someday it can be dropped?
Well, I think the plan is to simply rm the file in 2.5.x :) Dropping it
from 2.4.x is probably a bad idea, since it's not broken for old things.
The defconfigs should probably be updated tho. :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-29 22:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C55A9A8.9B3EB57E@wvi.com>
2002-01-28 20:34 ` Support for new Dual G4 1 Gig machines? Christopher Murtagh
2002-01-29 12:39 ` benh
2002-01-29 14:52 ` Christopher Murtagh
2002-01-29 15:01 ` Holger Bettag
2002-01-29 17:01 ` Edward Swarthout
2002-01-29 19:09 ` benh
2002-01-29 19:08 ` benh
2002-01-30 9:44 ` Alain RICHARD
2002-01-30 14:55 ` benh
2002-01-29 17:25 ` Derrik Pates
2002-01-29 22:06 ` Tom Rini [this message]
2002-01-30 7:00 ` Eric Leblond
2002-01-28 19:40 Kevin B. Hendricks
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=20020129220619.GH25973@opus.bloom.county \
--to=trini@kernel$(echo .)crashing.org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=christopher.murtagh@mcgill$(echo .)ca \
--cc=dpates@dsdk12$(echo .)net \
--cc=eric@regit$(echo .)org \
--cc=khendricks@ivey$(echo .)uwo.ca \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=yellowdog-devel@lists$(echo .)yellowdoglinux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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