public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: ?yvind Harboe <oyvind.harboe@zylin.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Are the HALs in the eCos repository meant for deployment?
Date: Mon, 14 Aug 2006 12:33:00 -0000	[thread overview]
Message-ID: <20060814123346.GX2053@lunn.ch> (raw)
In-Reply-To: <c09652430608140517m17f5146cg8ca5f628bad1c7ec@mail.gmail.com>

> - modifications to the EBI interface. There is no provision in the
> EB40a HAL for configuring the EBI.

This could be done in "application" space. If necassary, use a static
constructor with the appropriate priority. Otherwise do it from
cyg_user_start().

> - The reset on the EB40a HAL does not reset external circuits(or even the 
> flash)

Reseting flash has to be done by hardware, not software. If the CPU
does it via software, you are going to get into trouble, when you get
a reboot part way through a flash operation, leaving the flash in
write mode, resulting in yet another crash. 

Other bits of hardware should be reset by there respective device
drivers.

> - changes to memory layout

Making the RAM/ROM bigger can sometimes be a problem, granted.

       Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2006-08-14 12:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-13 19:37 Øyvind Harboe
2006-08-14 11:21 ` Gary Thomas
2006-08-14 11:54   ` Øyvind Harboe
2006-08-14 12:00     ` Gary Thomas
2006-08-14 12:08     ` Andrew Lunn
2006-08-14 12:17       ` Øyvind Harboe
2006-08-14 12:33         ` Andrew Lunn [this message]
2006-08-14 12:35         ` Gary Thomas
2006-08-14 12:52           ` Øyvind Harboe
2006-08-14 13:28 ` Bart Veer

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=20060814123346.GX2053@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=oyvind.harboe@zylin.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).