From: anthony tong <atong@uiuc.edu>
To: Kevin Hendricks <khendricks@ivey.uwo.ca>
Cc: Kostas Gewrgiou <gewrgiou@imbc.gr>,
Benjamin Herrenschmidt <bh40@calva.net>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Patches to fix aty128fb and xf400 r128 to work with both Rage128 and Rage128Pros
Date: Mon, 20 Mar 2000 23:04:49 -0600 [thread overview]
Message-ID: <20000320230448.A30849@rogue.genunix.net> (raw)
In-Reply-To: <00032021464800.00801@localhost.localdomain>; from khendricks@ivey.uwo.ca on Mon, Mar 20, 2000 at 09:48:30PM -0500
Kevin Hendricks (Mon, Mar 20, 2000 at 09:48:30PM -0500):
> Assuming they test out fine, Kostas would you see about getting the r128 patch
> integrated into the next xf40X release while I see about getting Paul and/or
> Anthony to integrate the aty128fb.c patch into both the stable and development
> kernels.
>
> Hopefully with these in place, new G4s will work as well as older G4s
> and G3s.
Looks good and works fine here..
Thanks for the hard work, Kevin!
-at
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-21 5:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 9:44 patch to get latest XFree 4.0 snapshot (xf3918) to workonppcwithr128 Michel Danzer
2000-03-15 11:13 ` Michael Schmitz
2000-03-15 14:09 ` Kostas Gewrgiou
2000-03-21 2:33 ` Patches to fix aty128fb and xf400 r128 to work with both Rage128 and Rage128Pros Kevin Hendricks
2000-03-21 5:04 ` anthony tong [this message]
2000-03-21 11:11 ` Benjamin Herrenschmidt
2000-03-21 16:56 ` Kostas Gewrgiou
2000-03-21 17:23 ` anthony tong
2000-03-21 17:52 ` Geert Uytterhoeven
2000-03-21 19:08 ` Kostas Gewrgiou
2000-03-21 19:39 ` Kevin B. Hendricks
2000-03-21 20:06 ` Kevin B. Hendricks
2000-03-21 17:26 ` Kevin B. Hendricks
2000-03-21 19:00 ` Kostas Gewrgiou
2000-03-22 16:49 ` Gabriel Paubert
2000-03-23 4:46 ` Some issues to resolve with XFree 4.0 yet Kevin 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=20000320230448.A30849@rogue.genunix.net \
--to=atong@uiuc.edu \
--cc=bh40@calva.net \
--cc=gewrgiou@imbc.gr \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).