From: Manfred Gruber <gruber.m@utanet.at>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] redboot autodetect flash device ?
Date: Fri, 24 Jun 2005 14:40:00 -0000 [thread overview]
Message-ID: <200506241639.49900.gruber.m@utanet.at> (raw)
In-Reply-To: <20050624142654.D212865C06C@smtp.ecoscentric.com>
Am Freitag, 24. Juni 2005 16:26 schrieb Bart Veer:
> >>>>> "Manfred" == Manfred Gruber <gruber.m@utanet.at> writes:
>
> Manfred> I use redboot v2.0, is there any newer code for detecting
> Manfred> the flash device?
>
> Manfred> I want to detect several AMD flash chips. It is enough
> Manfred> for me if only the size will be detected, because i want
> Manfred> to use same types, with different size. The flash chips
> Manfred> will also be placed in the same way on my hardware.
>
> Manfred> Maybe there is some code or information for me in newer
> Manfred> cvs? versions ?
>
> Not in the trunk, but in the flash_v2 branch there is a new AMD driver
> which supports CFI. Hence it can adapt at run-time to any
> AMD-compatible flash device.
>
> Bart
hi !
ok thanks, i will try to switch to cvs version.
eric: thanks also for the point about u-boot.
i will look what is easer for me to switch :-)
what is then the best and correct way to give the start-addresse and size to
the linux kernel, to start up physmap_configure() ? a command line, ATAG? or
what, i don't know?
now i have enabled redboot partition parsing which works wonderfull... i have
6 partions on my flash which i don't want to do over commandline, so redboot
partition parsing would be fine :-)
thanks regards manfred
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-06-24 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 13:59 Manfred Gruber
2005-06-24 14:27 ` Bart Veer
2005-06-24 14:40 ` Manfred Gruber [this message]
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=200506241639.49900.gruber.m@utanet.at \
--to=gruber.m@utanet.at \
--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).