From: Bruce Harada <bruce@ask.ne.jp>
To: John R Lenton <john@grulic.org.ar>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IMS Twin Turbo 128 framebuffer
Date: Sun, 4 Mar 2001 01:01:45 +0900 [thread overview]
Message-ID: <20010304010145.1d6a1dfb.bruce@ask.ne.jp> (raw)
In-Reply-To: <20010302203231.E1640@grulic.org.ar>
In-Reply-To: <20010302203231.E1640@grulic.org.ar>
On Fri, 2 Mar 2001 20:32:31 -0300
John R Lenton <john@grulic.org.ar> wrote:
> Is there any particular reason why imsttfb isn't available in the
> i386 arch?
I believe it's because the Twin Turbo was introduced into the kernel via
the PPC kernel port - was there actually a TT board for PCs? I'm not
talking about bus (the TTs were all PCI, IIRC), but rather the firmware on
the board - does it work on x86? If not, can it be flashed? If it can't,
you're out of luck.
--
Bruce Harada
bruce@ask.ne.jp
prev parent reply other threads:[~2001-03-03 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 23:32 IMS Twin Turbo 128 framebuffer John R Lenton
2001-03-03 16:01 ` Bruce Harada [this message]
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=20010304010145.1d6a1dfb.bruce@ask.ne.jp \
--to=bruce@ask.ne.jp \
--cc=john@grulic.org.ar \
--cc=linux-kernel@vger.kernel.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).