From: Ryan Du Bois <rdub@kamama.com>
To: Lucas Stach <dev@lynxeye.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: nvidia jetson tk1 help
Date: Thu, 25 Sep 2014 13:53:24 -0700 [thread overview]
Message-ID: <D69D1ADD-3E4C-41E0-8740-85F366D8CC0F@kamama.com> (raw)
In-Reply-To: <1411678267.2207.7.camel@tellur.intern.lynxeye.de>
[-- Attachment #1.1: Type: text/plain, Size: 1030 bytes --]
Oh, I see! I thought the image names were named after the default kernel source (e.g., where they'd read the kernel from), not where barebox itself was loaded from...
Makes sense now...
Thanks!
--
+Ryan Du Bois
rdub@kamama.com
On Sep 25, 2014, at 1:51 PM, Lucas Stach <dev@lynxeye.de> wrote:
> Am Donnerstag, den 25.09.2014, 10:55 -0700 schrieb Ryan Du Bois:
>> Okay, that worked, but I have to use the *-usbloader.img image. The emmc image doesn't output anything over UART.
>>
>> Is that expected?
>>
> That's expected. As said in the docs the images for Tegra are specific
> for the boot source. If you are starting with tegrarcm this would be the
> -usbloader boot source. If you want to persist barebox on the EMMC by
> copying the image to the boot0 partition you need to use the -emmc
> image, the -usbloader image won't come up there.
>
> If the doc isn't clear enough in that regard and you have suggestions on
> how to improve this: patches welcome. :)
>
> Regards,
> Lucas
>
>
[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-09-25 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 19:23 Ryan Du Bois
2014-09-25 8:14 ` Lucas Stach
2014-09-25 15:43 ` Ryan Du Bois
2014-09-25 17:55 ` Ryan Du Bois
2014-09-25 20:51 ` Lucas Stach
2014-09-25 20:53 ` Ryan Du Bois [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=D69D1ADD-3E4C-41E0-8740-85F366D8CC0F@kamama.com \
--to=rdub@kamama.com \
--cc=barebox@lists.infradead.org \
--cc=dev@lynxeye.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