From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [External] Re: [PATCH] arm64: zynqmp: Support converting pm_cfg_obj.c
Date: Wed, 24 Jun 2020 08:49:26 +0200 [thread overview]
Message-ID: <22e7c200-8d8e-37f2-abf2-22cfc047b176@xilinx.com> (raw)
In-Reply-To: <CA+fik50sKA4EdtwP_L2MSbeW6=xPwEs3PEKY6aJyzZWdmMevrQ@mail.gmail.com>
On 23. 06. 20 23:46, Brandon Maier wrote:
> On Tue, Jun 23, 2020 at 4:33 PM Luca Ceresoli <luca@lucaceresoli.net> wrote:
>>
>> Hi,
>>
>> On 23/06/20 23:23, Luca Ceresoli wrote:
>>> Hi Brandon,
>>>
>>> On 23/06/20 19:08, Brandon Maier wrote:
>>>> On Tue, Jun 23, 2020 at 10:18 AM Luca Ceresoli <luca@lucaceresoli.net> wrote:
>>>>>
>>>> I'm trying to get it to work with Buildroot. Buildroot does have a
>>>> package for uboot-tools, so I could use that to run it. I'd have to
>>>> move the config and build commands into Buildroot's uboot package.
>>>> Since the script belongs to U-Boot anyway, it seemed cleaner to
>>>> integrate it directly into U-Boot so it could be used by other build
>>>> systems too.
>>>
>>> I understand. But I also understand Michal's concern: the U-Boot
>>> makefiles are quite complex already, and this feature is a relatively
>>> minor improvement.
>>>
>>> Probably having the conversion in Buildroot could be even simpler as you
>>> can support _only_ the C format there and do the conversion
>>> unconditionally. Only one workflow, no ifs, simpler code. Don't forget
>>> to Cc: me if you send a patch for that, I'll be glad to review it.
>
> Either U-Boot or Buildroot is fine by me. If Yocto alreads does it in
> their U-Boot package then I can see that being a precedent for
> patching Buildroot. I'll drop this patch to U-Boot then.
I have never started to use Luca's python script because I use different
methods how to get this fragment.
The first one was taking fsbl and simply extract pmu cfg fragment from
it with using binutils. I have sent that script some time ago.
And the second method is simply take what Xilinx C file and link it with
embeddedSW repository (just for headers) and build it by gcc.
A month ago I was experiment with this fragment and was trying to find
out if we can have generic one which works on all platforms.
As is visible this is fine for boot but not so good for live system.
The fragment itself by spec has feature for exchanging it at run time.
I sent a patch to utilize it based on current code.
https://lists.denx.de/pipermail/u-boot/2020-June/416310.html
It means I would more prefer to go in a way that pmufw will be able to
accept board/platform/configuration specific fragments and have just one
in u-boot which in general enable everything by default.
But I don't have time to go to pmufw and fix it.
Thanks,
Michal
next prev parent reply other threads:[~2020-06-24 6:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 20:45 [PATCH] arm64: zynqmp: Support converting pm_cfg_obj.c Brandon Maier
2020-06-23 15:17 ` Luca Ceresoli
[not found] ` <CA+fik50_-6oRQTY0MdXacg=LHoKtjkBTQ+MYgK4VptDy5Njygg@mail.gmail.com>
2020-06-23 21:22 ` Fwd: " Brandon Maier
2020-06-23 21:23 ` Luca Ceresoli
2020-06-23 21:31 ` Luca Ceresoli
2020-06-23 21:46 ` [External] " Brandon Maier
2020-06-24 6:49 ` Michal Simek [this message]
2020-06-23 16:08 ` Michal Simek
[not found] ` <CA+fik51z3vVQDs23Yu7i164vzCQfJz_4jOa_k4nsY58edDHYYw@mail.gmail.com>
2020-06-23 21:23 ` Fwd: " Brandon Maier
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=22e7c200-8d8e-37f2-abf2-22cfc047b176@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=u-boot@lists.denx.de \
/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.