From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Tomi Lapinlampi <lapinlam@vega.lnet.lut.fi>,
Adrian Bunk <bunk@stusta.de>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
rth@twiddle.net, adaplas@pol.net
Subject: Re: [Linux-fbdev-devel] Re: 2.6.12-rc3 compile failure in tgafb.c, tgafb not working anymore
Date: Fri, 22 Apr 2005 21:51:34 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.62.0504221954410.24170@numbat.sonytel.be> (raw)
In-Reply-To: <Pine.LNX.4.58.0504221051240.2344@ppc970.osdl.org>
On Fri, 22 Apr 2005, Linus Torvalds wrote:
> On Fri, 22 Apr 2005, Maciej W. Rozycki wrote:
> > JFTR, a few of the TURBOchannel variations of the TGA are supported for
> > MIPS, but regrettably the necessary code hasn't been ported from 2.4 to
> > 2.6 yet.
>
> Ok, so that would have increased the testing base by, what? One person or
> two? I think we're still in single digits ;)
All the DEC UDB (`Multia') machines have builtin TGA.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2005-04-22 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 18:50 2.6.12-rc3 compile failure in tgafb.c Tomi Lapinlampi
2005-04-21 20:43 ` Adrian Bunk
2005-04-22 7:28 ` Tomi Lapinlampi
2005-04-22 11:20 ` Tomi Lapinlampi
2005-04-22 14:40 ` 2.6.12-rc3 compile failure in tgafb.c, tgafb not working anymore Tomi Lapinlampi
2005-04-22 17:26 ` Linus Torvalds
2005-04-22 17:44 ` Maciej W. Rozycki
2005-04-22 17:51 ` Linus Torvalds
2005-04-22 18:07 ` Maciej W. Rozycki
2005-04-22 19:51 ` Geert Uytterhoeven [this message]
2005-04-25 3:21 ` Antonino A. Daplas
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=Pine.LNX.4.62.0504221954410.24170@numbat.sonytel.be \
--to=geert@linux-m68k.org \
--cc=adaplas@pol.net \
--cc=bunk@stusta.de \
--cc=lapinlam@vega.lnet.lut.fi \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=rth@twiddle.net \
/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).