From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Use non-zero address for CRC calculations
Date: Wed, 3 Feb 2016 09:43:19 -0700 [thread overview]
Message-ID: <56B22E27.8050603@wwwdotorg.org> (raw)
In-Reply-To: <1454459458-7177-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On 02/02/2016 05:30 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> Currently, U-Boot's itest command cannot read from address 0. On Tegra20,
> soc['ram-base'] can be 0, and is the address passed to itest. Modify the
> code to use an offset from this address, so as not to use address 0.
>
> Note that in Tegra30 and later, the RAM base is non-zero, so this issue
> does not occur. This issue also only affects the "flash" command, and not
> the "exec" command.
>
> A patch is also in progress to fix the itest command in U-Boot. However,
> fixing tegra-uboot-flasher not to use address 0 seems reasonable too, and
> will immediately solve the issue irrespective of which U-Boot code-base is
> in use.
>
> Signed-off-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> ---
> Untested so far since I'm working from home today due to snowfall and can't
> remotely plug in my old Tegra20 HW. I'll test before I apply this tomorrow.
Tested on Seaboard/Springbank and Jetson TK1, and applied.
prev parent reply other threads:[~2016-02-03 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 0:30 [PATCH] Use non-zero address for CRC calculations Stephen Warren
[not found] ` <1454459458-7177-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2016-02-03 16:43 ` Stephen Warren [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=56B22E27.8050603@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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 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.