From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2 v2] cramfs: make cramfs usable on non NOR flash
Date: Thu, 28 Jan 2010 08:30:44 +0100 [thread overview]
Message-ID: <4B613D24.7060604@denx.de> (raw)
In-Reply-To: <20100127192831.32327D334C9@gemini.denx.de>
Hello Wolfgang,
Wolfgang Denk wrote:
> In message <4B5FEB9E.3040908@denx.de> you wrote:
>> [PATCH 1/2] cramfs: make cramfs usable without a NOR flash
>
> I'm afraid I still don't understand how this is supposed to work.
>
> Where would you store the cramfs on a system "without a NOR flash"?
> Are we talking about - say - a NAND storage device then?
The cramfs image is located in RAM (where it first was copied from
whenever), and then files are read from it with the "cramfsload"
command ...
>> @@ -119,7 +121,11 @@ int do_cramfs_load(cmd_tbl_t *cmdtp, int flag, int argc, char *argv[])
>> dev.id = &id;
>> part.dev = &dev;
>> /* fake the address offset */
>> +#if !defined(CONFIG_SYS_NO_FLASH)
>> part.offset = addr - flash_info[id.num].start[0];
>> +#else
>> + part.offset = addr;
>> +#endif
>
> I understand that we now can have the cramfs image either in NOR flash
> _or_ in NAND.
No, we can have it in ROM or in RAM.
> What about systems that have both NOR _and_ NAND?
Are there such systems, with cramfs support? Actual cramfs support
in mainline is only for NOR devices ...
But, I think, it should work to extract a file from a cramfs stored
on a NAND on such systems with the "cramfsload" command ... if not,
the cramfs image could be copied from NAND to RAM, and then it
works ...
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2010-01-28 7:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 7:56 [U-Boot] arm: suen3, suen3_v1, mgcoge2_arm_p1a support Heiko Schocher
2010-01-17 23:51 ` Wolfgang Denk
2010-01-18 8:34 ` Heiko Schocher
2010-01-18 9:31 ` Stefan Roese
2010-01-27 7:23 ` Heiko Schocher
2010-01-27 7:30 ` [U-Boot] [PATCH 1/2 v2] cramfs: make cramfs usable on non NOR flash Heiko Schocher
2010-01-27 19:28 ` Wolfgang Denk
2010-01-28 7:30 ` Heiko Schocher [this message]
2010-01-28 10:15 ` Wolfgang Denk
2010-01-28 11:02 ` Heiko Schocher
2010-01-27 7:31 ` [U-Boot] [PATCH 2/2 v2] arm: suen3, suen3_v1, mgcoge2_arm_p1a support Heiko Schocher
2010-01-27 13:50 ` Tom
2010-01-27 14:43 ` Heiko Schocher
2010-01-28 13:54 ` Tom
2010-01-27 19:49 ` Wolfgang Denk
2010-02-01 7:37 ` [U-Boot] [PATCH 2/2 v3] " Heiko Schocher
2010-02-02 18:07 ` Prafulla Wadaskar
2010-02-03 6:42 ` Wolfgang Denk
2010-02-03 15:52 ` Heiko Schocher
2010-02-03 16:53 ` Stefan Roese
2010-02-03 22:32 ` Scott Wood
2010-02-04 7:24 ` Heiko Schocher
2010-02-08 19:23 ` Scott Wood
2010-02-10 7:09 ` Heiko Schocher
2010-02-10 7:41 ` Prafulla Wadaskar
2010-02-10 9:27 ` Heiko Schocher
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=4B613D24.7060604@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.