From: "Kevin D. Kissell" <kevink@mips.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Chris Boot <bootc@bootc.net>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: [Slightly-OT] VR4110 core
Date: Sat, 22 Oct 2005 19:23:43 +0200 [thread overview]
Message-ID: <435A759F.5010601@mips.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0510221857510.16077@numbat.sonytel.be>
Geert Uytterhoeven wrote:
> On Sat, 22 Oct 2005, Chris Boot wrote:
>
>>Geert Uytterhoeven wrote:
>>
>>>On Fri, 21 Oct 2005, Chris Boot wrote:
>>>
>>>>Geert Uytterhoeven wrote:
>>>>
>>>>>On Fri, 21 Oct 2005, Chris Boot wrote:
>>>>>
>>>>>>Hmm, glancing at the "Product Letter" I have, it does mention
>>>>>>"Enhanced
>>>>>>Multi-Media Architecture" so I'm guessing its an EMMA SoC indeed.
>>>>>
>>>>>Do you have to part number?
>>>>
>>>>Did I not send one?! It must have been late...
>>>>
>>>>It's a uPD61032, marked D61032GL on the chip. The exact markings are:
>>>>NEC JAPAN
>>>>D61032GL
>>>>9949EK019
>>>
>>>That's indeed the EMMA.
>>
>>Now we know what it is...where do I find the docs?
>
>
> I'm afraid it's available under NDA from NEC only :-(
Note, however, that the group that develops EMMA chips is based
in the UK. If you contact them and ask nicely, there's at least
a chance that they could provide some documentation for student
work.
Regards,
Kevin K.
prev parent reply other threads:[~2005-10-22 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 22:23 [Slightly-OT] VR4110 core Chris Boot
2005-10-21 7:59 ` Geert Uytterhoeven
2005-10-21 13:16 ` Chris Boot
2005-10-21 13:36 ` Geert Uytterhoeven
2005-10-21 14:20 ` Chris Boot
2005-10-21 18:42 ` Geert Uytterhoeven
2005-10-22 14:50 ` Chris Boot
2005-10-22 16:58 ` Geert Uytterhoeven
2005-10-22 17:23 ` Kevin D. Kissell [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=435A759F.5010601@mips.com \
--to=kevink@mips.com \
--cc=bootc@bootc.net \
--cc=geert@linux-m68k.org \
--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.