All of lore.kernel.org
 help / color / mirror / Atom feed
From: sseeger@stellartec.com (Steven Seeger)
To: "'Jun Sun'" <jsun@mvista.com>
Cc: <linux-mips@linux-mips.org>
Subject: RE: NEC VR4181A
Date: Thu, 13 Feb 2003 05:22:36 -0800	[thread overview]
Message-ID: <02c101c2d362$f9e2eed0$3501a8c0@wssseeger> (raw)
In-Reply-To: <20030212224837.D16015@mvista.com>

>Osprey uses Vr4181, which is a different chip from vr4181a.

Yeah I didn't notice the A on there. We are looking into the possibility of
using the A in our board. Part of the problem is that the A only comes in
BGA and we don't like dealing with that.

>Interesting.  I was trying to get RT-Linux working at one time
>but aborted that effort in the middle.

Getting RTAI working wasn't easy. Took over a week and it was supposedly
already "ported." One of these days I really must find the time to check in
my changes to that project. It works very well and is quite stable. I think
46 us worst-case interrupt response off one of the VR4181's interrupts from
an external source is very good.

Steve

WARNING: multiple messages have this Message-ID (diff)
From: sseeger@stellartec.com (Steven Seeger)
To: 'Jun Sun' <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: RE: NEC VR4181A
Date: Thu, 13 Feb 2003 05:22:36 -0800	[thread overview]
Message-ID: <02c101c2d362$f9e2eed0$3501a8c0@wssseeger> (raw)
Message-ID: <20030213132236.522Oy0-8oUdvHMwkTbCk7QB6tPE7vIC5zD7qb_RbCdc@z> (raw)
In-Reply-To: <20030212224837.D16015@mvista.com>

>Osprey uses Vr4181, which is a different chip from vr4181a.

Yeah I didn't notice the A on there. We are looking into the possibility of
using the A in our board. Part of the problem is that the A only comes in
BGA and we don't like dealing with that.

>Interesting.  I was trying to get RT-Linux working at one time
>but aborted that effort in the middle.

Getting RTAI working wasn't easy. Took over a week and it was supposedly
already "ported." One of these days I really must find the time to check in
my changes to that project. It works very well and is quite stable. I think
46 us worst-case interrupt response off one of the VR4181's interrupts from
an external source is very good.

Steve

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 17:23 NEC VR4181A Julian Scheel
2003-02-12 17:30 ` Steven Seeger
2003-02-12 17:30   ` Steven Seeger
2003-02-13  6:48   ` Jun Sun
2003-02-13 13:22     ` Steven Seeger [this message]
2003-02-13 13:22       ` Steven Seeger
2003-02-13 17:46       ` Jun Sun
2003-02-14  8:41       ` Stuart Hughes
2003-02-14 12:56       ` 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='02c101c2d362$f9e2eed0$3501a8c0@wssseeger' \
    --to=sseeger@stellartec.com \
    --cc=jsun@mvista.com \
    --cc=linux-mips@linux-mips.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 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.