From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: mdhill@genxl.com, linux@cthulhu.engr.sgi.com
Subject: Re: 2.2.1 MIPS kernel sources plus Indy kernel binaries uploaded
Date: Tue, 2 Mar 1999 00:16:14 +0100 [thread overview]
Message-ID: <19990302001614.B2811@alpha.franken.de> (raw)
In-Reply-To: <9902281716.ZM1239@mdhill.genxl.com>; from Michael Hill on Sun, Feb 28, 1999 at 05:16:59PM -0500
On Sun, Feb 28, 1999 at 05:16:59PM -0500, Michael Hill wrote:
> Still have the aforementioned video quirks. Any further developments
> regarding Newport revisions?
so far nobody could tell me, how I can read the newport revision. Without
this information it's impossible to implement a runtime workaround for
the cursor problem (and mabye others).
So once again:
Is there anybody on this list, who knows and is willing to tell me, how I
get the newport revision ?
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
next prev parent reply other threads:[~1999-03-01 23:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-26 23:16 2.2.1 MIPS kernel sources plus Indy kernel binaries uploaded Thomas Bogendoerfer
1999-02-27 4:30 ` gkm
1999-02-27 11:01 ` Thomas Bogendoerfer
[not found] ` <tsbogend@alpha.franken.de>
1999-02-28 22:16 ` Michael Hill
1999-03-01 23:16 ` Thomas Bogendoerfer [this message]
1999-03-13 3:23 ` Ulf Carlsson
1999-03-06 0:35 ` Chad Carlin
1999-03-06 23:06 ` ralf
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 8:01 [parisc-linux] FB on c3k Grant Grundler
2002-03-06 23:22 ` Thomas Bogendoerfer
2002-03-07 7:31 ` Grant Grundler
2002-03-07 10:03 ` Thomas Bogendoerfer
2002-03-10 6:56 ` Grant Grundler
2002-03-07 14:00 ` Carlos O'Donell Jr.
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=19990302001614.B2811@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux@cthulhu.engr.sgi.com \
--cc=mdhill@genxl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.