public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Ross Younger <wry@ecoscentric.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 14:21:00 -0000	[thread overview]
Message-ID: <4A1411F0.1070805@mlbassoc.com> (raw)
In-Reply-To: <4A1410BA.3040808@ecoscentric.com>

Ross Younger wrote:
> Andrew Lunn wrote:
>> Why cannot this partition information be configured by redboot? 
>> Why must it be platform specific?
> 
> When I was designing my NAND library, I was striving for compatibility with
> Linux - that is to say, the ability for an eCos app (RedBoot?) and a Linux
> kernel to share the same NAND array.
> 
> There has to be some sort of partition mechanism, but there is no really
> standard way of doing so. The Linux MTD layer doesn't define anything in
> this regard; typically, the partition info is passed to the kernel at boot
> time (having been hard-coded into the bootloader or read from EEPROM or
> somesuch) and it then appears in /dev as the relevant number of devices
> (mtdblock*). What this means is - if I understand the situation correctly -
> if whoever put the platform together wanted the chip to appear as multiple
> partitions for whatever reason, they had to invent their own mechanism to
> specify the dimensions.

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.

> If compatibility with Linux is not a selling point, then we can of course do
> what we like. For example, it would be relatively straightforward for me to
> carve off a block or two to robustly store a partition table - as Rutger
> hints, the MTD bad block table as mimicked by both of our NAND libraries
> already does this - and a little more work to add helper commands to RedBoot
> to allow it to be manipulated interactively. However, if we went down this
> route, it would be dangerous to maintain the pretence of compatibility with
> Linux; this could of course be trivially given up by changing the signature
> magic numbers on our BBT.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

  reply	other threads:[~2009-05-20 14:21 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 [this message]
2009-05-20 15:25         ` Ross Younger
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=4A1411F0.1070805@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=simon.kallweit@intefo.ch \
    --cc=wry@ecoscentric.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).