From: Martin Costabel <costabel@wanadoo.fr>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Paul Mackerras <paulus@samba.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
Debian GNU/Linux PPC <debian-powerpc@lists.debian.org>
Subject: Re: [PATCH] Minor changes to control/imstt/platinum/valkyrie/atyfb
Date: Wed, 05 Dec 2001 12:22:58 +0100 [thread overview]
Message-ID: <3C0E0390.95CA5B75@wanadoo.fr> (raw)
In-Reply-To: 20011203080956.R7819@cpe-24-221-152-185.az.sprintbbd.net
Tom Rini wrote:
>
> On Mon, Dec 03, 2001 at 02:16:04PM +0100, Geert Uytterhoeven wrote:
> > On Sun, 2 Dec 2001, Martin Costabel wrote:
> > > Paul Mackerras wrote:
> > > > Martin Costabel writes:
[]
> > So please try `cmode 1' instead of `cmode 16'.
>
> These bits of code are always different still I think. Valkyriefb for
> example parses 'cmode:{8,15,16}' and does CMODE_8 or CMODE_16. I
> _think_ the userland tools did both 0/1/2 and 8/15/16/32 (24?).
I'll be happy to let my 6400 play the guinea pig, but I have to excuse
him until next week; I'm not at home right now.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-05 11:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 21:30 [PATCH] Minor changes to control/imstt/platinum/valkyrie/atyfb Tom Rini
2001-11-28 9:14 ` Geert Uytterhoeven
2001-12-28 11:28 ` Benjamin Herrenschmidt
2001-12-02 16:35 ` Tom Rini
2001-12-01 12:41 ` Martin Costabel
2001-12-02 10:14 ` Paul Mackerras
2001-12-02 21:11 ` Martin Costabel
2001-12-02 22:47 ` Paul Mackerras
2001-12-03 13:16 ` Geert Uytterhoeven
2001-12-03 15:09 ` Tom Rini
2001-12-05 11:22 ` Martin Costabel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-03 8:10 Bill Fink
2001-12-02 23:59 ` Benjamin Herrenschmidt
2001-12-03 15:29 ` Tom Rini
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=3C0E0390.95CA5B75@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=debian-powerpc@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.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).