From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] MAKEALL: fix boards_by_field function
Date: Thu, 17 Oct 2013 11:41:39 +0200 [thread overview]
Message-ID: <20131017114139.375e9a9c@lilith> (raw)
In-Reply-To: <1381995462-32556-4-git-send-email-yamada.m@jp.panasonic.com>
Hi Masahiro,
On Thu, 17 Oct 2013 16:37:42 +0900, Masahiro Yamada
<yamada.m@jp.panasonic.com> wrote:
> Commit 27af930e changed the boards.cfg format
> and it changed boards_by_field() function incorrectly.
> For tegra cpus it returned Board Name field,
> not Target field.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
> ---
>
> Commit 27af930e adjusted this part like follows:
>
>
> -v field="$1" \
> -v select="$2" \
> -F "$FS" \
> - '($1 !~ /^#/ && $field == select) { print $1 }' \
> + '($1 !~ /^#/ && $field == select) { print $7 }' \
> boards.cfg
> }
> boards_by_arch() { boards_by_field 2 "$@" ; }
> boards_by_cpu() { boards_by_field 3 "$@" "[: \t]+" ; }
> -boards_by_soc() { boards_by_field 6 "$@" ; }
> +boards_by_soc() { boards_by_field 4 "$@" ; }
>
>
> TAB is also treated as a field speparator, so
> we should have taken the 8th field for Tegra
> whereas the 7th field for the other cpus.
(As per our discussion, 'tab' here should be 'colon')
Not sure I am getting the logic here. Colon is *not* a field separator,
precisely because it is not present on all lines; it is a sub-field
separator. At this low level, the only field separator should be spaces.
Therefore, I would prefer boards_by_field() and board_by_cpu() to *not*
handle colons and thus consider the CPU field as a whole even when it
consists in a cpu:splcpu pair.
Splitting that pair and using either cpu or splcpu depending on
whether building SPL or not should only happen when the CPU field is
actually used, not fetched.
Can you try and provide a v2 patch (set) along these lines?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-10-17 9:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 7:37 [U-Boot] [PATCH 0/3] Fix bugs of MAKEALL Masahiro Yamada
2013-10-17 7:37 ` [U-Boot] [PATCH 1/3] MAKEALL: fix awk warning message Masahiro Yamada
2013-10-17 7:37 ` [U-Boot] [PATCH 2/3] MAKEALL: fix a bug to use CROSS_COMPILE_<ARCH> Masahiro Yamada
2013-10-17 8:33 ` Albert ARIBAUD
2013-10-17 8:48 ` Masahiro Yamada
2013-10-17 9:27 ` Albert ARIBAUD
2013-10-17 10:09 ` Masahiro Yamada
2013-10-17 7:37 ` [U-Boot] [PATCH 3/3] MAKEALL: fix boards_by_field function Masahiro Yamada
2013-10-17 8:52 ` Albert ARIBAUD
2013-10-17 8:58 ` Masahiro Yamada
2013-10-17 9:41 ` Albert ARIBAUD [this message]
2013-10-17 10:32 ` Masahiro Yamada
2013-10-17 11:41 ` Albert ARIBAUD
2013-10-18 6:37 ` Masahiro Yamada
2013-10-21 10:09 ` Masahiro Yamada
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=20131017114139.375e9a9c@lilith \
--to=albert.u.boot@aribaud.net \
--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