public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Tom Deconinck" <t.deconinck@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Questions about dual flash
Date: Mon, 03 Dec 2007 12:31:00 -0000	[thread overview]
Message-ID: <e37cb5250712030431p1af15b22v30c4fab822542af3@mail.gmail.com> (raw)
In-Reply-To: <e37cb5250712030430v4e71799ase1c40bc57889a1fc@mail.gmail.com>

On Dec 3, 2007 9:03 AM, Per-Erik Johansson <perka@dtek.chalmers.se> wrote:
> Hello again
>
> Found some posts from 2004 about merging flash_v2 and trunk..
> http://sources.redhat.com/ml/ecos-discuss/2004-10/msg00119.html
> will this still work?
> Also I have a home-cooked driver for the internal flash, do I have to
> change this driver or will it work with v2 as it is?
>
> Cheers
>  Per-Erik
>
>
>
> >> Hello
> >>
> >> I'm working on a redboot port for a PhyCore MPC5554 board.
> >> Our eval board has flash on it and the MPC5554 also has flash, but on
> >> startup the redboot prompt only displays one flash segment. Could it be
> >> made to show both?
> >> We added so redboot displays both our ram segments but cant understand
> >> how
> >> we could do it for flash since _flash_info() doesn't use a list.
> >> Also, just by using both flash drivers, with corresponding cdl and
> >> c-files, will redboot initiate both our flashes?
> >
> > The trunk of anoncvs has no support for discontinuous flash. Look at
> > the flash_v2 branch, which can have multiple flash devices.
> >
> >     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
>
>

Hi,

Yes, the merging will work.
I've done it a couple of weeks ago in light of porting eCos on the
AT91SAM7SE family.

Just start from the trunk tree and then replace the following
directories with their flash_v2 branch counter parts:
io/flash
dev/flash
redboot
fs/jffs2

You will probably have to make some small changes to your ecos.db too,
but those are pretty straight-forward.

If you enable the flash legacy api (CYGHWR_IO_FLASH_DEVICE_LEGACY cdl
option), I guess your home-cooked driver should still work.

Tom

-- 
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:[~2007-12-03 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03  8:04 Per-Erik Johansson
     [not found] ` <e37cb5250712030430v4e71799ase1c40bc57889a1fc@mail.gmail.com>
2007-12-03 12:31   ` Tom Deconinck [this message]
2007-12-13 14:48     ` Per-Erik Johansson
2007-12-14 10:46       ` Andrew Lunn
  -- strict thread matches above, loose matches on Subject: below --
2007-11-30 12:52 Per-Erik Johansson
2007-11-30 14:01 ` Andrew Lunn

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=e37cb5250712030431p1af15b22v30c4fab822542af3@mail.gmail.com \
    --to=t.deconinck@gmail.com \
    --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).