From: Juan Quintela <quintela@mandrakesoft.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Carsten Langgaard <carstenl@mips.com>,
Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: Yet another problem/bug on 20Kc Rev4.0 :-(
Date: 31 Jan 2002 20:27:19 +0100 [thread overview]
Message-ID: <m23d0mb9t4.fsf@localhost.mandrakesoft.com> (raw)
In-Reply-To: <20020131201010.C2309@dea.linux-mips.net>
>>>>> "ralf" == Ralf Baechle <ralf@oss.sgi.com> writes:
ralf> On Thu, Jan 31, 2002 at 04:35:28PM +0100, Carsten Langgaard wrote:
>> Please ignore my previous mail, it wasn't intended for this list, it was
>> intended for our internal linux list.
>> I'm just testing linux on one of our prototype chips, which probably has
>> no interest to you.
ralf> There burns the NDA ;-)
We now know that MIPS is developing a new MIPS chip :ppppp
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
prev parent reply other threads:[~2002-01-31 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 13:20 Yet another problem/bug on 20Kc Rev4.0 :-( Carsten Langgaard
2002-01-31 15:35 ` Carsten Langgaard
2002-01-31 19:10 ` Ralf Baechle
2002-01-31 19:27 ` Juan Quintela [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=m23d0mb9t4.fsf@localhost.mandrakesoft.com \
--to=quintela@mandrakesoft.com \
--cc=carstenl@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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.