public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
* ECOS ARM7 Variant Porting
@ 2005-11-29 18:42 Fishell, Bryan J.
  2005-11-29 19:40 ` Andrew Lunn
  0 siblings, 1 reply; 2+ messages in thread
From: Fishell, Bryan J. @ 2005-11-29 18:42 UTC (permalink / raw)
  To: ecos-devel

Hi All, 

I am curious how involved porting a variant of ECOS to a specific ARM7
core would be? Where exactly to start?

TIA

B.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: ECOS ARM7 Variant Porting
  2005-11-29 18:42 ECOS ARM7 Variant Porting Fishell, Bryan J.
@ 2005-11-29 19:40 ` Andrew Lunn
  0 siblings, 0 replies; 2+ messages in thread
From: Andrew Lunn @ 2005-11-29 19:40 UTC (permalink / raw)
  To: Fishell, Bryan J.; +Cc: ecos-devel

On Tue, Nov 29, 2005 at 01:42:30PM -0500, Fishell, Bryan J. wrote:
> Hi All, 
> 
> I am curious how involved porting a variant of ECOS to a specific ARM7
> core would be? Where exactly to start?

You say here core. Is it just the core you have? By this, i mean have
you licenced the core and put it into your own silicon? Are are you
actually talking about a commercially available chipset, which is more
than just the code, eg memory controllers, serial ports, USB devices,
MMC drivers etc?

A lot depends on how similar the core is to any of the other ARM
systems which are already supported. So i would start by doing a
comparision of what you have against the device which are currently
supported. Which is the most similar. Do any have serial drivers,
flash drivers, ic2 drivers which you can reuse etc.

You will find the porting guide useful:

http://ecos.sourceware.org/docs-latest/ref/hal-porting-guide.html

        Andrew

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-11-29 19:40 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-11-29 18:42 ECOS ARM7 Variant Porting Fishell, Bryan J.
2005-11-29 19:40 ` Andrew Lunn

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).