RE: [ECOS] Different flash

["Laurie Gellatly" <laurie.gellatly@netic.com>]

Hi Andew,
Sorry if this came across as being lazy, that was not the intent.
I was trying to go with the spirit of this group which I thought included
not
re-inventing the wheel for a driver that already existed and simple sharing
of knowledge.
'2)' was missing - yeah, that what I get for writing email late at night.

CDL is not my strong suit so thanks for the advise. I'll give it a go.

I'm actually considering moving the flash routines onto the processor
and away from external flash. That way the processor flash could
have the specifics of the flash stored in it and the flash structure would
still be static.

Anyway, thanks again.			...Laurie:{)

> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@lunn.ch]
> Sent: Thursday, 3 July 2008 11:11 PM
> To: Laurie Gellatly
> Cc: ecos discuss
> Subject: Re: [ECOS] Different flash
>
>
> > 1) Are there specific drivers for the AT49 or will the AM29
> driver be OK.
>
> Im too lazy to go look at the data sheet, so i will skip 1)
>
> My mind reading capabilities is also off line,  so i will skip 2) as well.
>
> > 3) If there are specific drivers (or I have to modify/write my
> own)  then do
> > I populate the cyg_dev_flash_funs with the appropriate function set at
> > startup or do I have two of these structures?
> > If 2 structures where/how do I tie them into eCos?
>
> Flash v2 makes this easy. Just register both drivers. The flash
> infrastructure will run the probe function to see if the flash
> actually exist. So you would expect one to fail to probe and one to
> work. The flash infrastructure will then direct all operations through
> the working driver.
>
>     Andrew
>
> Internal Virus Database is out of date.
> Checked by AVG.
> Version: 8.0.100 / Virus Database: 270.3.0/1503 - Release Date:
> 6/14/2008 6:02 PM
>


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