From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org,
Chase Maupin <Chase.Maupin@ti.com>
Subject: Re: [PATCH] linux-dtb: Add simple DTB symlinks for devicetree
Date: Tue, 2 Apr 2013 17:35:54 -0400 [thread overview]
Message-ID: <515B4F3A.3070001@windriver.com> (raw)
In-Reply-To: <515B455E.4030504@linux.intel.com>
On 13-04-02 04:53 PM, Darren Hart wrote:
>
>
> On 03/29/2013 09:48 AM, Chase Maupin wrote:
>> * This is similar to the symlinks provided for the kernel image
>> in the /boot directory of a file system. The goal is to have
>> simply named symlinks in /boot that mirror the device tree
>> name in the kernel sources. This is so that programs like
>> U-Boot can easily find the default device tree binary in the
>> /boot directory and use that when booting the kernel.
>> * Use update-alternatives to handle proper creation and removal
>> of the symlinks.
>
> Hi Chase,
>
> So I have no experience myself with Device Tree. Adding Bruce A. for some
> additional review.
Let me dig up the entire thread and have a look later. gmail
helped me out and tagged this entire series as spam .. so I
didn't see any of it.
Cheers,
Bruce
>
> I am going to assume this is the right thing to do for u-boot systems.
> Which devices have you verified this as working with?
>
>>
>> Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
>> ---
>> meta/recipes-kernel/linux/linux-dtb.inc | 20 ++++++++++++++++++++
>> 1 files changed, 20 insertions(+), 0 deletions(-)
>>
>> diff --git a/meta/recipes-kernel/linux/linux-dtb.inc b/meta/recipes-kernel/linux/linux-dtb.inc
>> index ec6c375..66cf255 100644
>> --- a/meta/recipes-kernel/linux/linux-dtb.inc
>> +++ b/meta/recipes-kernel/linux/linux-dtb.inc
>> @@ -45,3 +45,23 @@ do_deploy_append() {
>> done
>> fi
>> }
>> +
>> +pkg_postinst_kernel-devicetree () {
>
> Please use tabs for bash functions. Oddly, I see the only tabs in this
> file are in the anonymous python blocks. Doh.
>
>> + cd /${KERNEL_IMAGEDEST}
>> + for DTS_FILE in ${KERNEL_DEVICETREE}
>> + do
>> + DTS_BASE_NAME=`basename ${DTS_FILE} | awk -F "." '{print $1}'`
>> + DTB_NAME="devicetree-uImage-${DTS_BASE_NAME}.dtb"
>
>
> Is "uImage" always correct here? Or should we be using
> ${KERNEL_IMAGETYPE} here?
>
>
>> + update-alternatives --install /${KERNEL_IMAGEDEST}/${DTS_BASE_NAME}.dtb ${DTS_BASE_NAME}.dtb ${DTB_NAME} ${KERNEL_PRIORITY} || true
>> + done
>> +}
>> +
>> +pkg_postrm_kernel-devicetree () {
>> + cd /${KERNEL_IMAGEDEST}
>> + for DTS_FILE in ${KERNEL_DEVICETREE}
>> + do
>> + DTS_BASE_NAME=`basename ${DTS_FILE} | awk -F "." '{print $1}'`
>> + DTB_NAME="devicetree-uImage-${DTS_BASE_NAME}.dtb"
>> + update-alternatives --remove ${DTS_BASE_NAME}.dtb ${DTB_NAME} ${KERNEL_PRIORITY} || true
>> + done
>> +}
>>
>
> Thanks,
>
next prev parent reply other threads:[~2013-04-02 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 16:48 [PATCH] linux-dtb: Add simple DTB symlinks for devicetree Chase Maupin
2013-04-02 20:53 ` Darren Hart
2013-04-02 21:35 ` Bruce Ashfield [this message]
2013-04-03 14:20 ` Maupin, Chase
2013-04-03 15:57 ` Darren Hart
2013-04-03 16:09 ` Bruce Ashfield
2013-04-03 17:26 ` Maupin, Chase
2013-04-03 17:01 ` Maupin, Chase
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=515B4F3A.3070001@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=Chase.Maupin@ti.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 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.