From: danc@iobjects.com (Dan Conti)
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Is an EP7312 port in the works?
Date: Mon, 05 Feb 2001 11:40:00 -0000 [thread overview]
Message-ID: <CAEMICOOKMKAGHPNGNFNIEBBCDAA.danc@iobjects.com> (raw)
In-Reply-To: <4.3.2.7.2.20010205123011.00b2a870@larwe.com>
It's a straightforward port, you can do it in the existing hal subtype. The
7312 doesn't have any faster clock speeds, but it does have more on chip
SRAM i believe. The changes between the 7212 and the 7312 are minor, the
biggest part is probably configuring the SDRAM controller, which might take
a total of 10 lines.
I have no idea about an "official" port. Last time i looked at the CVS stuff
there was no support for it.
-Dan
-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[ mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Lewin A.R.W.
Edwards
Sent: Monday, February 05, 2001 9:33 AM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Is an EP7312 port in the works?
I've been speaking to Cirrus Logic about the EP7312 (which will replace the
EP7212), and it seems fairly certain that it will be designed into our new
products. Can someone at RH please confirm/deny that an "official" port is
being worked on? If there is no current official plan to port the EDB7xxx
code to the 7312, I will work on it myself via the horror of CVS (wish me
luck :/)
I'm not sure what the eval board for the 7312 will offer, but I think it
will be very similar to the 7212's (SDRAM instead of DRAM, and possibly
faster clock speeds). Assuming I work on my own port, should I create a new
HAL or subtype the existing EDB7xxx HAL?
-- Lewin A.R.W. Edwards
Embedded Engineer, Digi-Frame Inc.
http://www.digi-frame.com/
Tel (914) 937-4090 9am-6:30pm M-F ET
prev parent reply other threads:[~2001-02-05 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 9:34 Lewin A.R.W. Edwards
2001-02-05 11:40 ` Dan Conti [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=CAEMICOOKMKAGHPNGNFNIEBBCDAA.danc@iobjects.com \
--to=danc@iobjects.com \
--cc=ecos-discuss@sources.redhat.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).