From: Marek Vasut <marex@denx.de>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Tom Rini <trini@konsulko.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] u-boot: Upgrade to 2018.03 release
Date: Tue, 1 May 2018 01:30:32 +0200 [thread overview]
Message-ID: <91b044f5-b110-8a74-31cd-bbbd2176f57e@denx.de> (raw)
In-Reply-To: <CAP9ODKrSENfuyMmvuyFMaAXfsr-Dd8dzM1X1pRp5m_5ys_3x2Q@mail.gmail.com>
On 04/30/2018 10:29 PM, Otavio Salvador wrote:
> On Mon, Apr 30, 2018 at 5:25 PM Tom Rini <trini@konsulko.com> wrote:
>
>> On Mon, Apr 30, 2018 at 07:57:18PM +0000, Otavio Salvador wrote:
>>> On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin <
>>> alexander.kanavin@linux.intel.com> wrote:
>>>
>>>> On 04/30/2018 08:25 PM, Marek Vasut wrote:
>>>>>>>> Isn't it possible to solve your issue in the OE side?
>>>>>>>>
>>>>>>>
>>>>>>> Can we NOT compile DTC alongside U-Boot somehow ? :)
>>>>>>> That'd be the most desired solution IMO.
>>>>>>
>>>>>> Yes please. Can you adjust the recipes and classes in oe-core, and
>>>>>> remove the dtc recipe altogether?
>>>>>
>>>>> Remove dtc recipe ? Not sure I understand what you're implying.
>>>
>>>> If u-boot bundles dtc in its source tree, can we use that, and remove
>>>> the external dtc recipe?
>>>
>>> We shouldn't. The point in use the recipes inside OE-Core is because our
>>> bugfixes, patches and etc are used everywhere. If we use the bundled
> copy
>>> how we'd fix a host issue for example? Duplicate patches?
>
>> What do you do for the kernel here?
>
> We use our dtc-native. As we do for all other recipes (but few exceptions)
Yeah, we should use the DTC from OE , not the DTC from U-Boot.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-04-30 23:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 23:02 [PATCH] u-boot: Upgrade to 2018.03 release Marek Vasut
2018-04-09 0:54 ` Khem Raj
2018-04-09 7:12 ` Martin Jansa
2018-04-09 8:25 ` Marek Vasut
2018-04-09 13:48 ` Khem Raj
2018-04-09 15:24 ` Marek Vasut
2018-04-10 9:49 ` Martin Hundebøll
2018-04-10 9:55 ` Marek Vasut
[not found] ` <d89b39f665a14c63b0821c1ad600da72@SOC-EX01V.e01.socionext.com>
2018-04-11 8:42 ` Martin Hundebøll
[not found] ` <32a348ed6176434db8178d29d7e1f183@SOC-EX01V.e01.socionext.com>
2018-04-16 8:40 ` Marek Vasut
2018-04-30 12:17 ` Alexander Kanavin
2018-04-30 17:25 ` Marek Vasut
2018-04-30 18:05 ` Martin Hundebøll
2018-04-30 19:46 ` Alexander Kanavin
2018-04-30 19:57 ` Otavio Salvador
2018-04-30 20:25 ` Tom Rini
2018-04-30 20:29 ` Otavio Salvador
2018-04-30 23:30 ` Marek Vasut [this message]
2018-05-01 0:25 ` Tom Rini
2018-05-01 1:56 ` Otavio Salvador
2018-04-11 14:47 ` Burton, Ross
2018-04-11 14:51 ` Marek Vasut
2018-04-21 10:01 ` Robert Berger
2018-04-21 10:52 ` Robert Berger
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=91b044f5-b110-8a74-31cd-bbbd2176f57e@denx.de \
--to=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=otavio@ossystems.com.br \
--cc=trini@konsulko.com \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox