From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Question about CFG_ENV_ADDR during RAMBOOT
Date: Wed, 30 May 2007 01:15:43 +0200 [thread overview]
Message-ID: <465CB41F.3050002@atmel.com> (raw)
In-Reply-To: <20070529224611.F3A2A353B27@atlas.denx.de>
>
> If you want to do something like this (opinions about usefulnes will
> probably differ - I'm not going to discuss this here), you don't need
> to add special commands. You should be able to use the existing
> commands, eventually packed into a macro definition.
>
* It is not a special command, it is a configurable side effect of
reading/writing to dataflash.
* running mkimage on the host will of course generate the crc check
but U-boot does not know that they thing you are copying to
storage is an image so it will not check crc automatically.
For your recommendation to work, people have to suspect that
the things stored in flash is bad.
In my experience, people do not realize that the image is bad, and
think they have made a mistake when generating the kernel or the root fs
and spend significant time trying to figure out what the problem
is and then call me.
If I generate/check the crc on all writes/reads, then this support
problem will more or less go away.
With your proposal, the support problem will remain.
I can of course generate macros, but again, people will want to do
their own macros, and they will run into the problem.
Reducing support, is very important, and is worth the extra code space needed.
>> By doing the crc check when copying from the dataflash to SDRAM
>> you immediately pinpoint the problem.
>
> I don't understand why your appended CRC word is in any way better
> than our embedded / prepended one, the result of the check will be
> the same in each case. If you need check the CRC independetly from
> the boot command, you can always use the "imi" command, or "crc"
> itself.
>
>> If U-Boot contained a command to write the kernel to dataflash,
>> then this command could check that the image fits into the partition
>> allocated for the kernel, and would report a "kernel too large"
>> warning message.
>
> This is not an issue of a special write command, but of such a
> concept of partitions in flash memory which, at the moment, does not
> exist.
>
The current dataflash drivers divides the flash into partitions.
In my private version, the partitions can have a name, and the address
of the partition is automatically stored in an environment variable
with this name,
It would be fairly easy to implement a command which flashes the kernel/rootfs,
to check that they fit into the named partition.
>
> Best regards,
>
> Wolfgang Denk
>
--
Best Regards,
Ulf Samuelsson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ulf.vcf
Type: text/x-vcard
Size: 301 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070530/f593bffc/attachment.vcf
next prev parent reply other threads:[~2007-05-29 23:15 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 10:53 [U-Boot-Users] Question about CFG_ENV_ADDR during RAMBOOT Ulf Samuelsson
2007-05-26 13:15 ` Wolfgang Denk
2007-05-28 11:37 ` Ladislav Michl
2007-05-28 14:08 ` Ulf Samuelsson
2007-05-28 15:39 ` Ladislav Michl
2007-05-28 16:16 ` Håvard Skinnemoen
2007-05-28 16:56 ` Ulf Samuelsson
2007-05-28 19:39 ` Ladislav Michl
2007-05-29 0:10 ` Wolfgang Denk
2007-05-29 22:13 ` Ulf Samuelsson
2007-05-29 22:46 ` Wolfgang Denk
2007-05-29 23:15 ` Ulf Samuelsson [this message]
2007-05-29 23:39 ` Wolfgang Denk
2007-05-30 0:46 ` Ulf Samuelsson
2007-05-30 6:57 ` Wolfgang Denk
2007-05-30 10:52 ` Ladislav Michl
2007-05-30 13:43 ` Wolfgang Denk
2007-05-30 18:11 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2007-05-30 11:34 Ulf Samuelsson
2007-05-30 12:16 ` Ladislav Michl
2007-05-30 13:47 ` Wolfgang Denk
2007-05-30 18:23 ` Ulf Samuelsson
2007-05-30 23:19 ` Wolfgang Denk
2007-05-16 19:58 Timur Tabi
2007-05-22 20:36 ` Timur Tabi
2007-05-22 20:53 ` Jerry Van Baren
2007-05-22 21:04 ` Wolfgang Denk
2007-05-22 21:07 ` Timur Tabi
2007-05-23 0:15 ` Wolfgang Denk
2007-05-23 15:58 ` Timur Tabi
2007-05-22 21:26 ` Jerry Van Baren
2007-05-22 21:20 ` Andy Fleming
2007-05-22 21:22 ` Timur Tabi
2007-05-23 0:17 ` Wolfgang Denk
2007-05-23 14:56 ` Timur Tabi
2007-05-22 21:00 ` Wolfgang Denk
2007-05-22 21:30 ` Andy Fleming
2007-05-23 10:04 ` Ladislav Michl
2007-05-23 10:48 ` Ulf Samuelsson
2007-05-23 11:39 ` Ladislav Michl
2007-05-23 12:52 ` Ulf Samuelsson
2007-05-23 13:57 ` Wolfgang Denk
2007-05-23 16:19 ` Ulf Samuelsson
2007-05-24 12:10 ` Ladislav Michl
2007-05-24 13:03 ` Wolfgang Denk
2007-05-24 13:34 ` Ladislav Michl
2007-05-24 19:08 ` Ulf Samuelsson
2007-05-24 21:11 ` Wolfgang Denk
2007-05-24 21:43 ` Ulf Samuelsson
2007-05-24 23:46 ` Wolfgang Denk
2007-05-25 5:37 ` Stefan Roese
2007-05-25 8:50 ` Ladislav Michl
2007-05-23 12:59 ` Ulf Samuelsson
2007-05-23 13:25 ` Ladislav Michl
2007-05-23 16:05 ` Ulf Samuelsson
2007-05-24 12:29 ` Ladislav Michl
2007-05-24 18:34 ` Ulf Samuelsson
2007-05-24 18:35 ` Ulf Samuelsson
2007-05-23 12:59 ` Wolfgang Denk
2007-05-23 15:44 ` Ulf Samuelsson
2007-05-23 18:08 ` Wolfgang Denk
2007-05-24 9:14 ` Ladislav Michl
2007-05-25 9:06 ` Ladislav Michl
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=465CB41F.3050002@atmel.com \
--to=ulf@atmel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox