From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCH] ARM: sun6i: dt: Add new Mele I7 device
Date: Wed, 11 Mar 2015 15:41:45 +0100 [thread overview]
Message-ID: <55005429.5060103@redhat.com> (raw)
In-Reply-To: <20150311134158.GM5085@lukather>
Hi,
On 11-03-15 14:41, Maxime Ripard wrote:
> On Tue, Mar 10, 2015 at 11:33:51PM +0100, Hans de Goede wrote:
>>>>> and we have no way to replace U-Boot in NAND
>>>>> so far (afaik). But replacing them by stdout-path is a very good
>>>>> solution too.
>>>>
>>>> You mean putting stdout-path in the dts, I'm not sure if I like that,
>>>> to me both bootargs and stdout-path are something which should be
>>>> left to the bootloader to set. But I understand that when not
>>>> using upstream u-boot that may be an issue.
>>>
>>> I know that some other platforms ask for stdout-path when they review
>>> it, because iirc, barebox uses it to know on which console to output
>>> its log and export its shell, which is also a valid interpretation of
>>> that property, and, contrary to bootargs, doesn't really imply that
>>> the bootloader should update it.
>>
>> Hmm, that is interesting we should probably start doing the same in
>> all the sunxi dts files, as eventually I would like to move all u-boot
>> board config to devicetree, so that we only need to maintain dts files
>> and not both dts files and u-boot board configs.
>
> I had the plan to remove all earlyprintk in the bootargs of the DTS, I
> can do it to convert all DTS to use stdout-path as well.
Sounds good, please do.
Regards,
Hans
prev parent reply other threads:[~2015-03-11 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 13:48 [PATCH] ARM: sun6i: dt: Add new Mele I7 device codekipper at gmail.com
2015-03-03 7:16 ` Maxime Ripard
2015-03-03 7:55 ` [linux-sunxi] " Hans de Goede
2015-03-03 8:22 ` Maxime Ripard
2015-03-03 13:20 ` Hans de Goede
2015-03-03 13:58 ` Maxime Ripard
2015-03-10 11:16 ` Hans de Goede
2015-03-10 11:40 ` Ian Campbell
2015-03-10 18:44 ` Maxime Ripard
2015-03-10 22:33 ` Hans de Goede
2015-03-11 13:41 ` Maxime Ripard
2015-03-11 14:41 ` Hans de Goede [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=55005429.5060103@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).