From: "machael" <dony.he@huawei.com.cn>
To: "Quinn Jensen" <jensenq@Lineo.COM>, <linux-mips@oss.sgi.com>
Subject: Re: Does Linux support RC32332 CPU now?
Date: Mon, 9 Apr 2001 09:09:34 +0800 [thread overview]
Message-ID: <001101c0c091$bdb1a220$8021690a@huawei.com> (raw)
In-Reply-To: 3ACDF3A1.4020109@Lineo.COM
Thank you, Quinn. I have downloaded your patch.
I find that you use linux-sgi-20010307 in your patch file. Is this an
offcial release which I can find in ftp.kernel.org ?
Where can I download it?
Thank you very much.
machael
----- Original Message -----
From: "Quinn Jensen" <jensenq@Lineo.COM>
To: <linux-mips@oss.sgi.com>
Sent: Saturday, April 07, 2001 12:49 AM
Subject: Re: Does Linux support RC32332 CPU now?
> The IDT RC32332 is a subset of the RC32334, which
> a working port exists for. I have submitted a
> patch to Ralf, but haven't seen it go into his tree
> yet. The patch is available at
> http://www.zdomain.com/patch.sgi.idt
>
> Quinn
>
> owner-linux-mips@oss.sgi.com wrote:
>
> > Hi, folks:
> >
> > I am a newbie in linux-mips. I have questions to ask:
> >
> > 1 Does Linux support RC32332 CPU now?
> > 2 I want to build my cross-compile environment for MIPS target
on my
> > X86 host. Are there any documents about how to implement it?
> >
> > Thank you very much.
>
>
WARNING: multiple messages have this Message-ID (diff)
From: "machael" <dony.he@huawei.com.cn>
To: Quinn Jensen <jensenq@Lineo.COM>, linux-mips@oss.sgi.com
Subject: Re: Does Linux support RC32332 CPU now?
Date: Mon, 9 Apr 2001 09:09:34 +0800 [thread overview]
Message-ID: <001101c0c091$bdb1a220$8021690a@huawei.com> (raw)
Message-ID: <20010409010934.551LqVyvQ7yXrUJ8hre5v6gEGXptQQ84BWMqJjkoPWY@z> (raw)
In-Reply-To: 3ACDF3A1.4020109@Lineo.COM
Thank you, Quinn. I have downloaded your patch.
I find that you use linux-sgi-20010307 in your patch file. Is this an
offcial release which I can find in ftp.kernel.org ?
Where can I download it?
Thank you very much.
machael
----- Original Message -----
From: "Quinn Jensen" <jensenq@Lineo.COM>
To: <linux-mips@oss.sgi.com>
Sent: Saturday, April 07, 2001 12:49 AM
Subject: Re: Does Linux support RC32332 CPU now?
> The IDT RC32332 is a subset of the RC32334, which
> a working port exists for. I have submitted a
> patch to Ralf, but haven't seen it go into his tree
> yet. The patch is available at
> http://www.zdomain.com/patch.sgi.idt
>
> Quinn
>
> owner-linux-mips@oss.sgi.com wrote:
>
> > Hi, folks:
> >
> > I am a newbie in linux-mips. I have questions to ask:
> >
> > 1 Does Linux support RC32332 CPU now?
> > 2 I want to build my cross-compile environment for MIPS target
on my
> > X86 host. Are there any documents about how to implement it?
> >
> > Thank you very much.
>
>
next prev parent reply other threads:[~2001-04-09 1:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 1:34 Does Linux support RC32332 CPU now? machael
2001-04-05 1:34 ` machael
2001-04-05 16:48 ` Keith M Wesolowski
2001-04-06 16:49 ` Quinn Jensen
2001-04-09 1:09 ` machael [this message]
2001-04-09 1:09 ` machael
-- strict thread matches above, loose matches on Subject: below --
2001-05-29 1:41 machael thailer
2001-05-29 1:41 ` machael thailer
2001-04-04 0:23 CVS Down? Andrew Linfoot
2001-04-04 12:18 ` Ralf Baechle
2001-04-04 13:00 ` Does Linux support RC32332 CPU now? machael
2001-04-04 13:00 ` machael
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='001101c0c091$bdb1a220$8021690a@huawei.com' \
--to=dony.he@huawei.com.cn \
--cc=jensenq@Lineo.COM \
--cc=linux-mips@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.