From: Ross Younger <wry@ecoscentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Simon Kallweit <simon.kallweit@intefo.ch>,
"ecos-devel@ecos.sourceware.org"
<ecos-devel@ecos.sourceware.org>
Subject: Re: NAND review
Date: Wed, 20 May 2009 15:25:00 -0000 [thread overview]
Message-ID: <4A1420E3.20808@ecoscentric.com> (raw)
In-Reply-To: <4A1411F0.1070805@mlbassoc.com>
Gary Thomas wrote:
> I don't know what/where you were looking to come to these conclusions :-(
> Linux MTD has had the ability to use the RedBoot FIS directory for many (7+) years.
At the moment, as I understand things, FIS implies io/flash, which pretty
much implies NOR. I don't have any plans to implement FIS on top of NAND;
people who do use NAND will generally be using a filesystem, so "obviously"
the right place to put static config data is on that filesystem? (Chicken,
meet egg?)
Now, if we were to need to write a primary bootloader - say, if a
OneNAND-based SOC came into the frame and we wanted to run RedBoot on it -
then we might very well find ourselves needing something along these lines.
A very very simple filesystem, combined perhaps with the ability to store a
little config data and/or partition table layout, for which it might be
worth considering reusing some or all of the FIS code? With that in mind, I
suppose that defining a scheme for a partition table and very simple FS for
NAND would be a worthwhile exercise, which could then of course be
contribbed to Linux. Comments?
Ross
--
Embedded Software Engineer, eCosCentric Limited.
Barnwell House, Barnwell Drive, Cambridge CB5 8UU, UK.
Registered in England no. 4422071. www.ecoscentric.com
next prev parent reply other threads:[~2009-05-20 15:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 8:27 Simon Kallweit
2009-05-19 13:47 ` Ross Younger
2009-05-19 14:17 ` Andrew Lunn
2009-05-20 13:24 ` Bart Veer
2009-05-20 13:34 ` Rutger Hofman
2009-05-20 13:53 ` Andrew Lunn
2009-05-20 13:56 ` Gary Thomas
2009-05-20 14:22 ` Andrew Lunn
2009-05-20 15:22 ` Andrew Lunn
2009-05-20 15:34 ` Bart Veer
2009-05-20 13:58 ` Rutger Hofman
2009-05-20 14:16 ` Ross Younger
2009-05-20 14:21 ` Gary Thomas
2009-05-20 15:25 ` Ross Younger [this message]
2009-05-20 15:37 ` Gary Thomas
2009-05-19 16:29 ` Andrew Lunn
2009-06-03 8:51 ` Andrew Lunn
2009-06-03 10:21 ` Ross Younger
2009-06-03 10:48 ` Andrew Lunn
2009-06-03 11:52 ` Simon Kallweit
2009-06-03 12:26 ` Rutger Hofman
2009-06-03 13:33 ` Jürgen Lambrecht
2009-06-10 17:39 ` Nick Garnett
2009-06-11 11:25 ` Rutger Hofman
2009-06-13 16:31 ` Andrew Lunn
2009-06-18 14:10 ` Nick Garnett
2009-06-19 7:47 ` Andrew Lunn
2009-06-19 14:14 ` Ross Younger
2009-06-19 15:02 ` Andrew Lunn
2009-06-19 16:54 ` Jürgen Lambrecht
2009-06-29 11:09 ` Nick Garnett
2009-06-19 8:07 ` Andrew Lunn
2009-06-19 11:37 ` Daniel Morris
2009-06-19 12:06 ` Andrew Lunn
2009-05-20 1:02 ` Jonathan Larmour
2009-05-20 7:11 ` Simon Kallweit
2009-05-20 11:12 ` Rutger Hofman
2009-05-20 11:29 ` Simon Kallweit
2009-05-20 13:37 ` Rutger Hofman
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=4A1420E3.20808@ecoscentric.com \
--to=wry@ecoscentric.com \
--cc=andrew@lunn.ch \
--cc=ecos-devel@ecos.sourceware.org \
--cc=gary@mlbassoc.com \
--cc=simon.kallweit@intefo.ch \
/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).