This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: adding user defined flash variables as cdl_option to inl file problems

From: Nick Garnett <nickg at ecoscentric dot com>
To: Brian Austin <brian dot austin at cirrus dot com>
Cc: ecos-discuss <ecos-discuss at ecos dot sourceware dot org>
Date: 29 Nov 2006 11:29:07 +0000
Subject: Re: [ECOS] adding user defined flash variables as cdl_option to inl file problems
References: <1164589215.10044.49.camel@localhost.localdomain> <1164599489.10044.114.camel@localhost.localdomain>

Brian Austin <brian.austin@cirrus.com> writes:

> With ecos being so configurable, I do not see why flash variables have
> hard coded values.  Is there an example of a configurable flash
> implementation  for a certain chip flavor, or am I gonna have to come up
> with a solution myself?

An alternative approach is to switch to the V2 flash drivers and use
CFI to detect the flash device characteristics at runtime. This is
pretty much the default approach that we (eCosCentric) now take for
all flash support.

-- 
Nick Garnett                                     eCos Kernel Architect
http://www.ecoscentric.com                The eCos and RedBoot experts

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

Follow-Ups:
- Re: adding user defined flash variables as cdl_option to inl file problems
  - From: Brian Austin

References:
- adding user defined flash variables as cdl_option to inl file problems
  - From: Brian Austin
- Re: adding user defined flash variables as cdl_option to inl file problems
  - From: Brian Austin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]