From: trini@ti•com (Tom Rini)
To: linux-arm-kernel@lists•infradead.org
Subject: Unifying cape overlays into boot .dtb for BeagleBoard.org boards
Date: Tue, 17 Jun 2014 10:58:24 -0400 [thread overview]
Message-ID: <53A05790.7090803@ti.com> (raw)
In-Reply-To: <20140617125640.GC3705@n2100.arm.linux.org.uk>
On 06/17/2014 08:56 AM, Russell King - ARM Linux wrote:
> On Tue, Jun 17, 2014 at 08:37:09AM -0400, Tom Rini wrote:
>> On 06/17/2014 05:09 AM, Russell King - ARM Linux wrote:
>>> A good way that this could have been done is to put an I2C EEPROM on
>>> each cape, and have that store the DT fragment. The boot loader could
>>> have then read that from each cape, and used that information to build
>>> up the final DT. Why this hasn't been thought of, considering that the
>>> kernel has been moving towards DT for years, is quite unbelievable.
>>
>> I had actually talked about this a long while back (face to face) with
>> people, but the problem was (and still kind of is) the bindings
>> changing, etc.
>
> And that's a strong argument for having stable bindings - or at the
> very least, ensuring that new bindings which are compatible with older
> versions.
Yes. This was a few years back (a bit before the first beaglebone was
public) so before we had really pushed up on some level of binding
stability.
--
Tom
next prev parent reply other threads:[~2014-06-17 14:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+T6QP==raXdWz9mezK3JxSvZjWhUZZ7aKv4CpCr0SbdaCMgDQ@mail.gmail.com>
2014-06-11 5:11 ` Unifying cape overlays into boot .dtb for BeagleBoard.org boards Jason Kridner
2014-06-17 7:11 ` Gupta, Pekon
2014-06-17 16:25 ` Jason Kridner
2014-06-18 8:51 ` Gupta, Pekon
2014-06-26 7:50 ` Tony Lindgren
2014-06-26 13:06 ` Tom Rini
2014-06-26 15:27 ` Jason Kridner
2014-06-16 13:22 ` Jason Kridner
2014-06-17 9:09 ` Russell King - ARM Linux
2014-06-17 12:37 ` Tom Rini
2014-06-17 12:56 ` Russell King - ARM Linux
2014-06-17 14:58 ` Tom Rini [this message]
2014-06-17 12:58 ` Matt Porter
2014-06-17 13:15 ` Russell King - ARM Linux
2014-06-17 13:30 ` Matt Porter
2014-06-17 13:32 ` Pantelis Antoniou
2014-06-17 16:01 ` Russell King - ARM Linux
2014-06-17 16:33 ` Jason Kridner
2014-06-17 16:59 ` Pantelis Antoniou
2014-06-17 17:05 ` Russell King - ARM Linux
2014-06-17 17:10 ` Pantelis Antoniou
2014-06-17 17:41 ` Russell King - ARM Linux
2014-06-17 19:24 ` Pantelis Antoniou
2014-06-17 13:45 ` Vladimir Pantelic
2014-06-17 13:50 ` Grant Likely
2014-06-17 14:08 ` Iain Paton
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=53A05790.7090803@ti.com \
--to=trini@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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