Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: Bjorn Andersson <bjorn@kryo.se>
Cc: Doug Anderson <dianders@chromium.org>,
	Tomasz Figa <tomasz.figa@gmail.com>,
	Arun Kumar K <arun.kk@samsung.com>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Olof Johansson <olofj@google.com>,
	Tomasz Figa <t.figa@samsung.com>,
	Sachin Kamat <sachin.kamat@linaro.org>,
	Tushar Behera <tushar.behera@linaro.org>,
	Arun Kumar <arunkk.samsung@gmail.com>
Subject: Re: [PATCH 3/3] ARM: dts: Add peach-pi board support
Date: Thu, 8 May 2014 18:16:52 -0400	[thread overview]
Message-ID: <536C0254.8050108@ti.com> (raw)
In-Reply-To: <CAJAp7Og6Bqnbq5b=Ki5vLaVkvSXxqsKaFaxCoqbX+fRkgouh=A@mail.gmail.com>

On 05/08/2014 05:55 PM, Bjorn Andersson wrote:
> On Mon, May 5, 2014 at 11:18 AM, Tom Rini <trini@ti.com> wrote:
> [...]
>> The problem I was raising at the ELC BoF is that today we can't just
>> stop overwriting values in the non-zero case as many boards lie about
>> their memory size, in non-zero ways, but no one noticed as they only
>> tested with U-Boot which was performing the fixup.
> 
> So, should we conclude are we stuck being bug-compatible forever?
> 
> I was hoping to add this logic to the kernel by [1], but of course
> this won't fly
> based on the argument you highlighted (as was pointed out by Uwe).
> 
> [1] https://lkml.org/lkml/2014/5/7/28

Well, device tree should always win and once passed to the kernel, be
correct.  If you have control of the kernel but not bootloader, like Uwe
says, drop the ATAG support.

-- 
Tom

  reply	other threads:[~2014-05-08 22:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 13:03 [PATCH 0/3] Add Exynos5800 support Arun Kumar K
2014-05-02 13:03 ` [PATCH 1/3] clk: exynos5420: Add 5800 specific clocks Arun Kumar K
2014-05-02 17:23   ` Tomasz Figa
2014-05-03 12:06     ` Arun Kumar K
2014-05-02 17:51   ` Andrew Bresticker
2014-05-03 12:12     ` Arun Kumar K
2014-05-02 18:52   ` Arnd Bergmann
2014-05-02 19:35     ` Doug Anderson
2014-05-03  2:12       ` Tomasz Figa
2014-05-02 13:03 ` [PATCH 2/3] ARM: dts: Add Exynos5800 dt file Arun Kumar K
2014-05-02 16:49   ` Olof Johansson
2014-05-02 17:03   ` Tomasz Figa
2014-05-02 13:03 ` [PATCH 3/3] ARM: dts: Add peach-pi board support Arun Kumar K
2014-05-02 17:10   ` Tomasz Figa
2014-05-02 18:31     ` Doug Anderson
2014-05-03  2:00       ` Tomasz Figa
     [not found]         ` <53644DDB.7050503-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-05 15:17           ` Doug Anderson
2014-05-05 18:18             ` Tom Rini
2014-05-08 21:55               ` Bjorn Andersson
2014-05-08 22:16                 ` Tom Rini [this message]
2014-05-08 22:22                   ` Bjorn Andersson
2014-05-02 13:14 ` [PATCH 0/3] Add Exynos5800 support Kukjin Kim

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=536C0254.8050108@ti.com \
    --to=trini@ti.com \
    --cc=arun.kk@samsung.com \
    --cc=arunkk.samsung@gmail.com \
    --cc=bjorn@kryo.se \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olofj@google.com \
    --cc=sachin.kamat@linaro.org \
    --cc=t.figa@samsung.com \
    --cc=tomasz.figa@gmail.com \
    --cc=tushar.behera@linaro.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