All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Penny Chiu <pchiu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
	swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [cbootimage PATCH 1/1] Add Tegra124 support
Date: Mon, 26 Aug 2013 11:01:36 -0600	[thread overview]
Message-ID: <521B89F0.2000704@wwwdotorg.org> (raw)
In-Reply-To: <20130826074700.GA31726@ulmo>

On 08/26/2013 01:47 AM, Thierry Reding wrote:
> On Fri, Aug 23, 2013 at 01:05:11PM -0600, Stephen Warren wrote:
>> On 08/22/2013 09:46 PM, Penny Chiu wrote:
>>> Add the Tegra124 chip support to cbootimage. User can use "-t124" as
>>> option to parse .cfg and generate BCT/image for Tegra124.
>>
>> This looks fine to me at a quick glance. Just one small comment below:
>>
>>> diff --git a/src/cbootimage.c b/src/cbootimage.c
>>
>>>  	printf("Usage: cbootimage [options] configfile imagename\n");
>>>  	printf("    options:\n");
>>> -	printf("    -h, --help, -?        Display this message.\n");
>>> -	printf("    -d, --debug           Output debugging information.\n");
>>> -	printf("    -gbct                 Generate the new bct file.\n");
>>> -	printf("    -o<ODM_DATA>          Specify the odm_data(in hex).\n");
>>> -	printf("    [-t20|-t30|-t114]     Select one of the possible target devices,\n");
>>> -	printf("                          -t20 if unspecified.\n");
>>> -	printf("    configfile            File with configuration information\n");
>>> -	printf("    imagename             Output image name\n");
>>> +	printf("    -h, --help, -?              Display this message.\n");
>>> +	printf("    -d, --debug                 Output debugging information.\n");
>>> +	printf("    -gbct                       Generate the new bct file.\n");
>>> +	printf("    -o<ODM_DATA>                Specify the odm_data(in hex).\n");
>>> +	printf("    [-t20|-t30|-t114|-t124]     Select one of the possible target devices,\n");
>>> +	printf("                                -t20 if unspecified.\n");
>>> +	printf("    configfile                  File with configuration information\n");
>>> +	printf("    imagename                   Output image name\n");
>>>  }
>>
>> To avoid continually re-formatting that text when adding new SoCs, why
>> not start the description of the -tNN options on a separate line, and
>> leave the indentation as-is for all the unmodified lines. i.e.:
>>
>>>> +	printf("    [-t20|-t30|-t114|-t124]\n");
>>>> +	printf("                          Select one of the possible target devices,\n");
>>>> +	printf("                          -t20 if unspecified.\n");
> 
> Perhaps in the long run it would be better to turn this into something
> like:
> 
> 	printf("    -t, --target SOC      Select target device. Must be one of:\n");
> 	printf("                          20, 30, 114, 124 (default: 20)\n");

I don't like the idea of "--target 20", since "20" isn't an SoC name;
it's "tegra20" or just perhaps "t20".

I'd be fine with a patch that allowed "-SOC" or "--target SOC", with
SOC being "t20", "t30", ...

  reply	other threads:[~2013-08-26 17:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23  3:46 [cbootimage PATCH 1/1] Add Tegra124 support Penny Chiu
     [not found] ` <1377229591-21235-1-git-send-email-pchiu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-08-23 19:05   ` Stephen Warren
     [not found]     ` <5217B267.3030205-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-08-26  7:47       ` Thierry Reding
2013-08-26 17:01         ` Stephen Warren [this message]
     [not found]           ` <521B89F0.2000704-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-08-27  7:14             ` Thierry Reding
2013-08-27 16:03               ` Stephen Warren
2013-08-27 18:07       ` 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=521B89F0.2000704@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pchiu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=thierry.reding-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.