This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
Re: NAND technical review
- From: Rutger Hofman <rutger at cs dot vu dot nl>
- To: Simon Kallweit <simon dot kallweit at intefo dot ch>
- Cc: Jonathan Larmour <jifl at jifvik dot org>, Ross Younger <wry at eCosCentric dot com>, eCos developers <ecos-devel at ecos dot sourceware dot org>
- Date: Mon, 19 Oct 2009 17:09:08 +0200
- Subject: Re: NAND technical review
- References: <4AC6218C.20407@jifvik.org> <4AD820DE.7030002@intefo.ch>
Simon Kallweit wrote:
... What
I dislike is how the synthetic chips have to be configured. R's
implementation needs the user to assign a valid NAND chip device id,
which will then be used through chip interrogation to determine the
chips geometry. I find it much more useful if you can directly define
the chips geometry in CDL, as it's more explicit.
This emulates the read_id command in the same way as the other commands.
I saw no way around this because the generic code calls read_id and
expects an answer in the prescribed way.
Well, this all (again) does mean that R's (my) common controller stuff
is really tied to the raw NAND chips. See my other responses for what to
do if anything else is needed.
Rutger