From: Troy Kisky <troy.kisky@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] imx-common: cpu: add fdt_file environment variable
Date: Mon, 31 Mar 2014 11:29:01 -0700 [thread overview]
Message-ID: <5339B3ED.20405@boundarydevices.com> (raw)
In-Reply-To: <53384695.6000901@denx.de>
On 3/30/2014 9:30 AM, Stefano Babic wrote:
> Hi Troy,
>
> On 29/03/2014 23:34, Troy Kisky wrote:
>> This removes one block in the move toward 1 u-boot
>> for both a mx6q (quad) and mx6dl (duallite) processor.
>>
>> Now fdt_file hardcoded value can be removed.
>>
>> Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com>
>> ---
>
> I have a general problem with this implementation. I am ok if, as you
> proposed some times ago, there is a general rule for the "default" dtb
> file in the CONFIG_EXTRA_ENV.
>
> However, you are binding in code naming conventions. In U-boot, it must
> be allowed to set the environment as the user wants, and this must be
> not overwritten by such an internal code.
In the patch, the code returns without any changes if fdt_file is
already defined. So, I don't know what you are referring to here.
>
> I mean: a board user, if he wants, should be allowed to do something as
>
> setenv fdt_file my_preferred_dtb_name.dtb
>
> and this must work when the file is loaded from storage - this is not
> possible if the rule chosen from user is overwritten by code.
I agree, but it does work.
>
> This makes the environment useless and generates headaches for a lot of
> users. They will ask themselves why the wrong file is taken when they
> tried in any way to set it differently...
Still no disagreement.
prev parent reply other threads:[~2014-03-31 18:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 22:34 [U-Boot] [PATCH 1/1] imx-common: cpu: add fdt_file environment variable Troy Kisky
2014-03-29 23:04 ` Otavio Salvador
2014-03-30 14:52 ` Marek Vasut
2014-03-31 18:30 ` Troy Kisky
2014-03-29 23:11 ` Eric Nelson
2014-03-31 18:36 ` Troy Kisky
2014-03-31 19:22 ` Marek Vasut
2014-03-31 19:38 ` Otavio Salvador
2014-03-31 19:47 ` Marek Vasut
2014-03-31 21:09 ` Troy Kisky
2014-04-01 7:45 ` Marek Vasut
2014-03-30 16:30 ` Stefano Babic
2014-03-31 18:29 ` Troy Kisky [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=5339B3ED.20405@boundarydevices.com \
--to=troy.kisky@boundarydevices.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