public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Flash infrastructure rework
Date: Wed, 04 Aug 2004 19:13:00 -0000	[thread overview]
Message-ID: <20040804191334.GH9839@lunn.ch> (raw)
In-Reply-To: <20040716120045.GE6045@lunn.ch>

> However in the background i took a step back and overhauled the whole
> flash infrastructure in what i hope is a clean and consistent API with
> all the features required:
> 
>         Multiple device drivers at the same time
>         Multiple instantiations of the same driver
>         Probing to detect what is actually on the board
>         Support for boot block devices which have different size blocks
>         Thread safe when used with the kernel
>         Does not pollute the name space
>         Optional backward compatible with old drivers
>         Optional backward compatible with old API
>         Able to support multiple JFFS2 filesystems
>         Redboot to be able to access multiple devices
>         Documentation!

This is about ready to go live. The question is how do we do
this. There is a danger there are bugs left which could brick
boards. ie destroy the bootloader and if you don't have jtag there is
no way to recover the hardware.

There are a few options:

I commit it and let people test it. If there are major problems we
undo the change while we debug the problem.

I put the code on a branch so that a few people can test it and so we
get a better idea how stable the code is with hardware i don't have
access to.

I can send patches to people who would like to test.

Suggestions welcome.

        Andrew

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

  parent reply	other threads:[~2004-08-04 19:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 13:39 Andrew Lunn
2004-07-19 14:18 ` Ian Campbell
2004-07-30 10:43   ` Andrew Lunn
2004-08-04 12:54 ` Jani Monoses
2004-08-04 19:06   ` Andrew Lunn
2004-08-04 19:13 ` Andrew Lunn [this message]
2004-08-06 13:22   ` Andrew Lunn
2004-08-19 15:21 ` Bart Veer
2004-08-19 16:38   ` Andrew Lunn
2004-08-20 14:44     ` Bart Veer
2004-08-20 16:37       ` Andrew Lunn
2004-08-22 13:02         ` Gary Thomas
2004-08-04 19:49 Doyle, Patrick
2004-08-04 19:55 ` Andrew Lunn
2004-08-04 20:06 Doyle, Patrick
2004-08-04 20:12 ` Andrew Lunn
2004-08-04 20:17 Doyle, Patrick
2004-08-04 20:23 Doyle, Patrick
2004-08-06 13:43 David Marqvar (DAM)
2004-08-06 14:08 ` Andrew Lunn
     [not found] <0175EEA85416D811893E009027D0F5D79389D3@MAILHOST>
2004-08-06 16:40 ` Vivek Kumar
2004-08-06 18:06   ` Gary Thomas
     [not found] <0175EEA85416D811893E009027D0F5D79389D4@MAILHOST>
2004-08-06 17:19 ` Vivek Kumar
2004-08-09  8:47 David Marqvar (DAM)
2004-08-10  2:33 ` Vivek Kumar
2004-08-09 12:58 Doyle, Patrick
2004-09-08 12:25 Savin Zlobec

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=20040804191334.GH9839@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).