From: Michal Simek <michal.simek@xilinx.com>
To: Michael Walle <michael@walle.cc>, Michal Simek <michal.simek@xilinx.com>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
<soc@kernel.org>
Subject: Re: [PATCH 0/3] add Ebang EBAZ4205 support
Date: Thu, 21 Jan 2021 14:16:40 +0100 [thread overview]
Message-ID: <cbfc4899-eb92-938a-95f2-23ca9485beaf@xilinx.com> (raw)
In-Reply-To: <df072e37bb6f3500d713be565cfa1328@walle.cc>
On 1/21/21 11:41 AM, Michael Walle wrote:
> Hi,
>
> Am 2021-01-21 11:23, schrieb Michal Simek:
>>>> Back to your case. Board is cheap which is not all the time case for
>>>> any
>>>> xilinx board but you have only uart, sd and partially described
>>>> ethernet
>>>> which doesn't work without PL. Is it worth to have this described?
>>>
>>> I got your point. But it is at least a jump start for the users if that
>>> board boots out of the box. And yes, its unfortunate, that ethernet
>>> just works if the PL is configured. This is already done by the
>>> bootloader, because there I do have the same problem.
>>
>> Zynq/ZynqMP boards can use U-Boot SPL. "Advantage" of this solution
>> especially for Zynq is that in u-boot there is open a way for adding
>> ps7_init file which is determined by device tree name.
>> I think it would make sense to add these DTs and also ps7_init to U-Boot
>> project and wire it up with zynq_virt platform and then you can boot
>> Linux with using U-Boot's DT pointed by $fdtcontroladdr.
>> Then you will get support from scratch to be able to boot.
>
> I already have patches for u-boot (using SPL). But my impression was
> that linux is the master for the device trees. Esp. if there are some
> problems with the board its often useful to have an in-tree device
> tree.
>
> What is the difference between this board and the other zynq boards
> in the kernel?
>
> In any case, please make this decision now: will you accept this
> device tree or not?
If you promise to regularly test it I am fine with it.
Thanks,
Michal
next prev parent reply other threads:[~2021-01-21 13:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 19:40 [PATCH 0/3] add Ebang EBAZ4205 support Michael Walle
2021-01-20 19:40 ` [PATCH 1/3] dt-bindings: add ebang vendor prefix Michael Walle
2021-02-09 2:32 ` Rob Herring
2021-01-20 19:40 ` [PATCH 2/3] dt-bindings: arm: add Ebang EBAZ4205 board Michael Walle
2021-01-20 19:40 ` [PATCH 3/3] ARM: dts: add Ebang EBAZ4205 device tree Michael Walle
2021-01-21 9:25 ` [PATCH 0/3] add Ebang EBAZ4205 support Michal Simek
2021-01-21 9:35 ` Michael Walle
2021-01-21 9:57 ` Michal Simek
2021-01-21 10:13 ` Michael Walle
2021-01-21 10:23 ` Michal Simek
2021-01-21 10:41 ` Michael Walle
2021-01-21 13:16 ` Michal Simek [this message]
2021-01-21 15:14 ` Michael Walle
2021-01-26 13:31 ` Michal Simek
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=cbfc4899-eb92-938a-95f2-23ca9485beaf@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).