From: "Grant Mills" <gmills@ucsd.edu>
To: "Alex Schuilenburg" <alexs@ecoscentric.com>
Cc: yh@bizmail.com.au, ecos-discuss@ecos.sourceware.org,
"Andrew Lunn" <andrew@lunn.ch>
Subject: Re: [ECOS] Modifying RedBoot to support multiple flash devices
Date: Fri, 10 Mar 2006 17:25:00 -0000 [thread overview]
Message-ID: <6f506bf60603100925u2f8abadas9e483125fc096c65@mail.gmail.com> (raw)
In-Reply-To: <44116022.7080103@ecoscentric.com>
On 3/10/06, Alex Schuilenburg <alexs@ecoscentric.com> wrote:
> yh@bizmail.com.au wrote:
> > Hello Alex,
> >
> > I am looking for redboot to support Intel P3 and I took the snapshot, but
> > seems that the intel/stratav2 is empty. Where can I find the source code
> > for supporting P3?
>
> As Andrew said, the intel/stratav2 directory is the flash_v2 branch. My
> bad as I did not realise we were not generating snapshots of the
> flash_v2 branch (now added to the cron to generate future snapshots for
> flash_v2 until the merge).
>
> To kickstart, I have also just generated a flash_v2 snapshot but it
> looks like you may have lucked out with P3 support.
>
> -- Alex
>
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>
There is not a lot to supporting the P30 Flash Family from Intel.
From my perspective there are three main hurdles:
1. The entire chip is locked at reset. This means that the
implementation will need to check for lock before any write/erase
operation. This may already be in place.
2. When supporting 512Mb and greater, the flash chip itself contains
multiple dies. Each die is a 256Mb P30. Therefore, you'll need to
track them as independent devices (at least I would.)
3. Lastly, the 1Gb version has two chip selects. This is more of a
hardware issue than a firmware but worth mentioning.
As I will be looking at the flash_v2 branch here soon, I'll see if I
can get some P30 support in before my own deadlines. If not, I'll
table it til afterwards.
--
Grant Mills
gmills@ucsd.edu
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-03-10 17:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 4:44 yh
2006-03-10 7:22 ` Andrew Lunn
2006-03-10 11:19 ` Alex Schuilenburg
2006-03-10 17:25 ` Grant Mills [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 3:17 yh
2006-03-08 19:21 Grant Mills
2006-03-08 19:59 ` Andrew Lunn
2006-03-08 20:21 ` Grant Mills
2006-03-08 22:04 ` Alex Schuilenburg
2006-03-08 22:12 ` Andrew Lunn
2006-03-09 18:23 ` Chuck McManis
2006-03-10 11:11 ` Alex Schuilenburg
[not found] ` <20060308220250.GE19406@lunn.ch>
[not found] ` <6f506bf60603081426j4ec71e7dg1f068b4f42ad4b17@mail.gmail.com>
[not found] ` <20060308223947.GH19406@lunn.ch>
2006-03-09 6:09 ` Grant Mills
2006-03-09 20:58 ` Andrew Lunn
2006-03-09 21:09 ` Grant Mills
2006-03-09 21:18 ` Andrew Lunn
2006-03-09 21:40 ` Bart Veer
2006-03-08 22:07 ` Bart Veer
2006-03-08 22:14 ` Andrew Lunn
2006-03-08 22:31 ` Grant Mills
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=6f506bf60603100925u2f8abadas9e483125fc096c65@mail.gmail.com \
--to=gmills@ucsd.edu \
--cc=alexs@ecoscentric.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=yh@bizmail.com.au \
/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).