All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Mark Zhang <nvmarkzhang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: ANNOUNCE: Tegra application notes, (and tegrarcm & cbootimage)
Date: Mon, 10 Dec 2012 10:37:41 -0700	[thread overview]
Message-ID: <50C61DE5.4060509@wwwdotorg.org> (raw)
In-Reply-To: <50C597CD.6060302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 12/10/2012 01:05 AM, Mark Zhang wrote:
> On 12/08/2012 09:08 AM, Stephen Warren wrote:
>> I'd like to announce or remind people of some documentation and tools we
>> have for Tegra development.
...
>> Finally, we hope to publish cbootimage configuration files for NVIDIA's
>> Tegra reference boards in the very near future. That will complete the
>> picture above.
>>
> 
> Yep. It's better to provide an example of "text representation BCT" as
> well so that we can use "bct_dump" to generate a binary BCT file.

If you already have a binary BCT, bct_dump (also in the cbootimage git)
can generate the text representation for you. If you don't already have
a binary BCT, we'll be publishing the real text-based configuration
files hopefully soon. So I don't think there's a need for a separate
example is there?

  parent reply	other threads:[~2012-12-10 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-08  1:08 ANNOUNCE: Tegra application notes, (and tegrarcm & cbootimage) Stephen Warren
     [not found] ` <50C2932A.7040501-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-10  8:05   ` Mark Zhang
     [not found]     ` <50C597CD.6060302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-10 17:37       ` Stephen Warren [this message]
2012-12-10 21:43   ` Stephen Warren

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=50C61DE5.4060509@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nvmarkzhang-Re5JQEeQqe8AvxtiuMwx3w@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.