From: Daniel Stodden <daniel.stodden@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] kwboot: Boot Marvell Kirkwood SoCs over a serial link.
Date: Mon, 12 Nov 2012 23:01:54 -0800 [thread overview]
Message-ID: <1352790114.12535.209.camel@ramone> (raw)
In-Reply-To: <CANzncG+O6coXoVC0vJfj5FJJTWTtkER5e_d7L_Ux40a2GPSZyw@mail.gmail.com>
On Sat, 2012-11-10 at 09:04 -0500, Sam Bulka wrote:
> I understand the advantage of the tool when installed on a PC. But not
> the advantage of adding it to Uboot, since the tool is needed when
> Uboot is broken and doesn't work anymore. How would you use this tool
> from within Uboot, if you can't access Uboot prompt? :) And if you can
> access the prompt, then you can reflash Uboot or change its
> environment without this tool.
Sam,
in case this didn't become clear: the receiving end to which this tool
talks resides in firmware deeply embedded within the SoC. It's a
function specific to Marvell processors, not u-boot, and activated by
talking to the chip before any other software environment is loaded.
These chips support booting from a whole variety of peripheral sources
to load system images from, both SPI flash and UART are just
alternatives. So it's in u-boot as part of the toolchain, not boot
firmware.
Daniel
next prev parent reply other threads:[~2012-11-13 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 6:26 [U-Boot] kwboot: Boot Marvell Kirkwood SoCs over a serial link Daniel Stodden
2012-04-22 18:46 ` Prafulla Wadaskar
2012-04-22 21:28 ` Daniel Stodden
2012-04-23 20:56 ` Wolfgang Denk
2012-11-04 12:58 ` Sambul
2012-11-10 7:13 ` Prafulla Wadaskar
2012-11-10 14:04 ` Sam Bulka
2012-11-11 8:29 ` Luka Perkov
2012-11-13 7:01 ` Daniel Stodden [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-22 18:00 Daniel Stodden
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=1352790114.12535.209.camel@ramone \
--to=daniel.stodden@googlemail.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