From: Jonathan Larmour <jlarmour@redhat.com>
To: Ling Su <lingsu@palmmicro.com>
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: Anyway to access the 7 segment display on NEC vrc4373 board?
Date: Wed, 13 Sep 2000 11:58:00 -0000 [thread overview]
Message-ID: <39BFCE4F.1EA8AF46@redhat.com> (raw)
In-Reply-To: <001501c01d0c$8f661960$1201a8c0@crusoe>
Ling Su wrote:
>
> I can not find the 7 segment display on the schematic of NECvr4373 board I
> have, and actually I want to use it for some signaling purpose. I found it
> is enabled in plarform.S, but I don't know what is the address that it is
> mapped to. Could you please do me a favor to look it up in your document? I
> just want to write some bytes into it to show the progress of a program.
If you look at the vrc4372 data sheet at:
http://www.necel.com/home.nsf/Createpage?OpenAgent&Microprocessors&V ()R()+Series(TM)+64-Bit+MIPS(R)+RISC&Companion+Chips&&&&&&&
Then look at section 6.5, page 24. And as you can see in platform.S, the 7
segment display is IOPROF_06 and IOPROF_07.
For more than this, you're on your own, sorry :-/. Unless someone else out
there has done this.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-09-13 11:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-11 21:05 [ECOS] Fw: [ECOS] How to access PCI memory(HELP) Ling Su
2000-09-12 2:56 ` [ECOS] " Nick Garnett
2000-09-12 11:07 ` Ling Su
2000-09-13 3:09 ` Nick Garnett
2000-09-12 15:52 ` [ECOS] Anyway to access the 7 segment display on NEC vrc4373 board? Ling Su
2000-09-13 11:58 ` Jonathan Larmour [this message]
2000-09-12 18:31 ` [ECOS] Problem on allocate PCI memory space Ling Su
2000-09-13 3:19 ` [ECOS] " Nick Garnett
2000-09-13 12:40 ` Ling Su
2000-09-13 17:41 ` Ling Su
2000-09-14 3:32 ` Nick Garnett
2000-09-14 3:43 ` Andrew Lunn
2000-09-14 14:46 ` Ling Su
2000-09-14 14:51 ` Jonathan Larmour
2000-09-14 17:53 ` Ling Su
2000-09-14 3:08 ` Nick Garnett
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=39BFCE4F.1EA8AF46@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=lingsu@palmmicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).