From: Michael Walle <michael@walle.cc>
To: buildroot@busybox.net
Subject: [Buildroot] [External] Re: [PATCH 1/9] package/rcw: upgrade the rcw version to LSDK-19.09
Date: Wed, 20 Nov 2019 11:00:23 +0100 [thread overview]
Message-ID: <d4ad37bc14e611dc3ef2f4ff1ec8543b@walle.cc> (raw)
In-Reply-To: <CANQCQpYBjDv8-=hDyOGeCHMQymFqsu3St+9fCvhcgunVQs9UKw@mail.gmail.com>
Hi,
Am 2019-11-20 10:51, schrieb Matthew Weber:
> Changming,
>
> On Wed, Nov 20, 2019 at 3:45 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
>>
>> On Wed, 20 Nov 2019 03:38:40 -0600
>> Matthew Weber <matthew.weber@collins.com> wrote:
>>
>> > > True, rcw is very short and quite generic. Matt, what do you think?
>> >
>> > Michael, good points, maybe we could append a prefix to make it
>> > freescale-qoriq-rcw?
>>
>> Yes, freescale-qorqiq-rcw is good.
sounds good. but also see below.
>>
>
> I can send a patch, however do you want to add this rename as a patch
> in your current layerscape devkit series as you touch lots of RCW
> variables? Let me know your plan, I can send it but I don't want to
> do it in the middle of your work :).
The RCW is really board dependent. I can imagine some OEMs are using the
ones from freescale, but most likely they won't fit their boards. For
example, we have our own RCW repository (although only binary for now)
for our board. Therefore, wouldn't it be better to have different rcw
config(s) in the board directories?
TBH I just had a quick look at the package makefile and saw that it
copies the RCWs to /usr/share. Most likely, you (also?) need them in a
flash/sdcard image, though.
-michael
next prev parent reply other threads:[~2019-11-20 10:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 4:07 [Buildroot] [PATCH 0/9] new board ls1028ardb introduced Changming Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 1/9] package/rcw: upgrade the rcw version to LSDK-19.09 Changming Huang
2019-11-20 7:59 ` Thomas Petazzoni
2019-11-20 8:04 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 9:21 ` [Buildroot] " Michael Walle
2019-11-20 9:32 ` Thomas Petazzoni
2019-11-20 9:38 ` Matthew Weber
2019-11-20 9:45 ` Thomas Petazzoni
2019-11-20 9:51 ` [Buildroot] [External] " Matthew Weber
2019-11-20 9:57 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 10:00 ` Michael Walle [this message]
2019-11-20 10:23 ` [Buildroot] " Matthew Weber
2019-11-20 9:54 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 2/9] package/rcw: add target rcw binary support Changming Huang
2019-11-20 9:30 ` Matthew Weber
2019-11-20 4:07 ` [Buildroot] [PATCH 3/9] boot/arm-trusted-firmware: Add u-boot-dtb.bin support Changming Huang
2019-11-20 7:37 ` Sergey Matyukevich
2019-11-20 8:13 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 9:07 ` [Buildroot] " Thomas Petazzoni
2019-11-20 4:07 ` [Buildroot] [PATCH 4/9] boot/arm-trusted-firmware: Add RCW support Changming Huang
2019-11-20 7:50 ` Sergey Matyukevich
2019-11-20 8:45 ` [Buildroot] [EXT] " Jerry Huang
2019-11-21 8:02 ` Sergey Matyukevich
2019-11-21 8:37 ` Jerry Huang
2019-11-21 8:39 ` Jerry Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 5/9] package/freescale-qoriq: new package directory Changming Huang
2019-11-20 8:57 ` Thomas Petazzoni
2019-11-20 4:07 ` [Buildroot] [PATCH 6/9] package/freescale-qoriq/cadence: new package Changming Huang
2019-11-20 9:13 ` Thomas Petazzoni
2019-11-20 9:30 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 9:36 ` Thomas Petazzoni
2019-11-20 9:47 ` Jerry Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 7/9] package/rcw: Enable IIC5_PMUX and CLK_OUT_PMUX for GPIO Changming Huang
2019-11-20 9:14 ` Thomas Petazzoni
2019-11-20 9:34 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 9:38 ` Thomas Petazzoni
2019-11-20 10:22 ` Jerry Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 8/9] board/freescale/common/ls: Add standard post image script for Layerscape processors Changming Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 9/9] configs/freescale_ls1028ardb*: new board Changming Huang
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=d4ad37bc14e611dc3ef2f4ff1ec8543b@walle.cc \
--to=michael@walle.cc \
--cc=buildroot@busybox.net \
/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