From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jacek Anaszewski <j.anaszewski81@gmail.com>
Cc: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
stewart@linux.vnet.ibm.com, cooloney@gmail.com,
rpurdie@rpsys.net, linuxppc-dev@lists.ozlabs.org,
linux-leds@vger.kernel.org, khandual@linux.vnet.ibm.com
Subject: Re: [PATCH v2 2/2] leds/powernv: Add driver for PowerNV platform
Date: Mon, 27 Apr 2015 08:08:26 +1000 [thread overview]
Message-ID: <1430086106.16571.79.camel@kernel.crashing.org> (raw)
In-Reply-To: <20150424121549.27b74b25@ja.home>
On Fri, 2015-04-24 at 12:15 +0200, Jacek Anaszewski wrote:
> No matter what format of device tree OPAL produces, I assume that
> it must compile it from some sources.
Nope. Well... .C code maybe qualifies as "sources" :-)
> dtb file is a compiled form of human readable dts file containing
> Flattened Device Tree - a data structure for describing the hardware
> in the system.
>
> Please refer to: http://elinux.org/Device_Tree
We are quite familiar with this, guess what architecture created the
whole flat device-tree stuff in the first place ?
In any case, in our case, the fdt is procedurally generated by firmware.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jacek Anaszewski <j.anaszewski81@gmail.com>
Cc: stewart@linux.vnet.ibm.com, cooloney@gmail.com,
Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
rpurdie@rpsys.net, linuxppc-dev@lists.ozlabs.org,
linux-leds@vger.kernel.org, khandual@linux.vnet.ibm.com
Subject: Re: [PATCH v2 2/2] leds/powernv: Add driver for PowerNV platform
Date: Mon, 27 Apr 2015 08:08:26 +1000 [thread overview]
Message-ID: <1430086106.16571.79.camel@kernel.crashing.org> (raw)
In-Reply-To: <20150424121549.27b74b25@ja.home>
On Fri, 2015-04-24 at 12:15 +0200, Jacek Anaszewski wrote:
> No matter what format of device tree OPAL produces, I assume that
> it must compile it from some sources.
Nope. Well... .C code maybe qualifies as "sources" :-)
> dtb file is a compiled form of human readable dts file containing
> Flattened Device Tree - a data structure for describing the hardware
> in the system.
>
> Please refer to: http://elinux.org/Device_Tree
We are quite familiar with this, guess what architecture created the
whole flat device-tree stuff in the first place ?
In any case, in our case, the fdt is procedurally generated by firmware.
Cheers,
Ben.
next prev parent reply other threads:[~2015-04-26 22:13 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 21:45 [PATCH v2 2/2] leds/powernv: Add driver for PowerNV platform Jacek Anaszewski
2015-04-22 21:45 ` Jacek Anaszewski
2015-04-23 5:25 ` Vasant Hegde
2015-04-23 5:25 ` Vasant Hegde
2015-04-23 14:13 ` Jacek Anaszewski
2015-04-23 14:13 ` Jacek Anaszewski
2015-04-24 4:18 ` Stewart Smith
2015-04-24 4:18 ` Stewart Smith
2015-04-24 10:16 ` Jacek Anaszewski
2015-04-24 10:16 ` Jacek Anaszewski
2015-04-28 6:59 ` Stewart Smith
2015-04-28 6:59 ` Stewart Smith
2015-04-28 9:10 ` Jacek Anaszewski
2015-04-28 9:10 ` Jacek Anaszewski
2015-04-24 5:30 ` Vasant Hegde
2015-04-24 5:30 ` Vasant Hegde
2015-04-24 10:15 ` Jacek Anaszewski
2015-04-24 10:15 ` Jacek Anaszewski
2015-04-26 22:08 ` Benjamin Herrenschmidt [this message]
2015-04-26 22:08 ` Benjamin Herrenschmidt
2015-04-27 11:15 ` Jacek Anaszewski
2015-04-27 11:15 ` Jacek Anaszewski
2015-04-26 22:07 ` Benjamin Herrenschmidt
2015-04-26 22:07 ` Benjamin Herrenschmidt
2015-04-27 7:24 ` Jacek Anaszewski
2015-04-27 9:53 ` Benjamin Herrenschmidt
2015-04-27 11:15 ` Jacek Anaszewski
2015-04-27 13:47 ` Vasant Hegde
2015-04-28 11:06 ` Vasant Hegde
-- strict thread matches above, loose matches on Subject: below --
2015-03-20 11:02 [PATCH v2 0/2] LED interface " Vasant Hegde
2015-03-20 11:04 ` [PATCH v2 2/2] leds/powernv: Add driver " Vasant Hegde
2015-03-20 11:04 ` Vasant Hegde
2015-03-25 5:21 ` Benjamin Herrenschmidt
2015-03-25 5:21 ` Benjamin Herrenschmidt
2015-04-14 5:40 ` Vasant Hegde
2015-04-14 5:40 ` Vasant Hegde
2015-04-14 15:20 ` Jacek Anaszewski
2015-04-14 15:20 ` Jacek Anaszewski
2015-04-15 6:26 ` Vasant Hegde
2015-04-15 6:26 ` Vasant Hegde
2015-04-15 8:42 ` Jacek Anaszewski
2015-04-15 10:15 ` Vasant Hegde
2015-04-15 10:15 ` Vasant Hegde
2015-04-15 13:12 ` Jacek Anaszewski
2015-04-16 6:47 ` Jacek Anaszewski
2015-04-16 6:52 ` Vasant Hegde
2015-04-16 6:52 ` Vasant Hegde
2015-04-16 8:51 ` Jacek Anaszewski
2015-04-16 8:51 ` Jacek Anaszewski
2015-04-16 10:26 ` Vasant Hegde
2015-04-16 10:26 ` Vasant Hegde
2015-04-16 11:34 ` Jacek Anaszewski
2015-04-16 11:34 ` Jacek Anaszewski
2015-04-20 7:29 ` Jacek Anaszewski
2015-04-20 7:29 ` Jacek Anaszewski
2015-04-20 11:45 ` Jacek Anaszewski
2015-04-20 11:45 ` Jacek Anaszewski
2015-04-20 12:34 ` Vasant Hegde
2015-04-20 15:20 ` Jacek Anaszewski
2015-04-20 15:53 ` Vasant Hegde
2015-04-15 18:50 ` Stewart Smith
2015-04-15 18:50 ` Stewart Smith
2015-04-16 5:07 ` Vasant Hegde
2015-04-16 5:07 ` Vasant Hegde
2015-04-21 23:03 ` Stewart Smith
2015-04-21 23:03 ` Stewart Smith
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=1430086106.16571.79.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=cooloney@gmail.com \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=j.anaszewski81@gmail.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-leds@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rpurdie@rpsys.net \
--cc=stewart@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.