From: Aaron Lehmann <aaronl@vitelus.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Transmeta and Linux-2.4.0-test12-pre3
Date: Sat, 2 Dec 2000 12:08:46 -0800 [thread overview]
Message-ID: <20001202120846.C16734@vitelus.com> (raw)
In-Reply-To: <200012020409.UAA04058@adam.yggdrasil.com> <90a065$5ai$1@penguin.transmeta.com>
In-Reply-To: <90a065$5ai$1@penguin.transmeta.com>; from torvalds@transmeta.com on Fri, Dec 01, 2000 at 09:09:25PM -0800
On Fri, Dec 01, 2000 at 09:09:25PM -0800, Linus Torvalds wrote:
> NOTE! Getting the 2.4.x kernel up and running is the easy part. The
> machine also has a very recent ATI Rage Mobility chip in it, and you
> need the newest XFree86 CVS snapshot to make it work (along with a
> one-liner patch from me, unless that has already made it into the CVS
> tree by now).
It seems to just have:
1067. Fix ATI clock generator recognition when an adapter BIOS
cannot be retrieved (Linus Torvals).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-02 20:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-02 4:09 Transmeta and Linux-2.4.0-test12-pre3 Adam J. Richter
2000-12-02 4:55 ` H. Peter Anvin
2000-12-02 5:45 ` Can CMS be upgraded? -- " Miles Lane
2000-12-02 5:09 ` Linus Torvalds
2000-12-02 7:27 ` Linus Torvalds
2000-12-02 9:55 ` Transmeta and Linux-2.4.0-test12-pre3 [slightly off-topic] Ion Badulescu
2000-12-03 3:01 ` Linus Torvalds
2000-12-03 3:00 ` how to compile redhat6.0 kernel Mourad Lakhdar
2000-12-03 3:25 ` Paul Schulz
2000-12-03 14:40 ` Pete Keller
2000-12-02 13:04 ` Transmeta and Linux-2.4.0-test12-pre3 Alan Cox
2000-12-03 8:23 ` Linus Torvalds
2000-12-02 20:08 ` Aaron Lehmann [this message]
2000-12-02 22:35 ` Pavel Machek
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=20001202120846.C16734@vitelus.com \
--to=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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