Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Julian Scheel <jscheel@activevb.de>
To: Yoichi Yuasa <yoichi_yuasa@montavista.co.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: [patch] VR4181A and SMVR4181A
Date: Fri, 14 Feb 2003 20:59:29 +0100	[thread overview]
Message-ID: <200302142059.29634.jscheel@activevb.de> (raw)
In-Reply-To: <20030213155833.56019323.yoichi_yuasa@montavista.co.jp>

Hi Yoichi,

I have a short question to your patch: What CPU do I have to select for the 
VR4181A?
MIPS32? or R41xx?

Am Donnerstag, 13. Februar 2003 07:58 schrieb Yoichi Yuasa:
> Hello Ralf,
>
> I added support of NEC VR4181A and NEC SMVR4181A board.
>
> As for VR4181A, The peripheral differs from VR4181 or VR4100 series
> greatly. If a VR4100 core is removed from VR4181, VR4181A and VR4100
> series, they are completely different chip.
>
> Therefore, the directory vr4181a was newly created below to arch/mips.
>
> This patch is based on linux_2_4 tag cvs tree on ftp.linux-mips.org
> Would you apply this patch to CVS on ftp.linux-mips.org?
>
> P.S.
> The patch for 2.5 is also created now. Please wait for a moment.
>
> Best Regards,
>
> Yoichi

-- 
Grüße,
Julian

  reply	other threads:[~2003-02-14 19:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13  6:58 [patch] VR4181A and SMVR4181A Yoichi Yuasa
2003-02-14 19:59 ` Julian Scheel [this message]
2003-02-15 10:17 ` Julian Scheel
2003-02-15 15:22   ` Kunihiko IMAI
2003-02-17  1:51   ` Yoichi Yuasa
2003-02-17  7:32     ` Yoichi Yuasa
2003-02-17  7:50       ` Julian Scheel
2003-02-17  8:34         ` Yoichi Yuasa
2003-02-17 14:10           ` Julian Scheel
2003-02-17 14:10             ` Julian Scheel
2003-02-17 14:33             ` Yoichi Yuasa
  -- strict thread matches above, loose matches on Subject: below --
2003-02-16 17:20 Julian Scheel
2003-02-16 20:00 ` Kunihiko IMAI

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=200302142059.29634.jscheel@activevb.de \
    --to=jscheel@activevb.de \
    --cc=linux-mips@linux-mips.org \
    --cc=yoichi_yuasa@montavista.co.jp \
    /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