From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] socfpga cyclone5 dts
Date: Thu, 18 Oct 2018 21:54:22 +0200 [thread overview]
Message-ID: <02ac1e8c-4d0b-d013-1641-50d01a43e8fb@gmail.com> (raw)
In-Reply-To: <54b752ca-bcb9-46f7-82cc-d5b1101eea63@gmail.com>
On 10/18/2018 09:28 PM, Simon Goldschmidt wrote:
> Hi Marek,
Hi,
> I was playing with updating the dts files for cyclone5 (and arria5) from
> current kernel sources, but I found that the kernel as 4 boards that
> U-Boot doesn't have and U-Boot has 6 boards that the kernel doesn't have.
Thanks for doing this, really appreciated (even though it probably
doesn't look that way most of the time).
And yikes, which boards are where , can you list the problematic ones?
> How should I proceed here? Should I copy new boards from the kernel?
> Should I keep U-Boot-only boards and try to adjust them to changes (if
> any)?
I'd say sync as much as possible with kernel and the rest, update. I
don't think there are any real board specific things which would prevent
the update in those DTs missing in the kernel.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-10-18 19:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 19:28 [U-Boot] socfpga cyclone5 dts Simon Goldschmidt
2018-10-18 19:54 ` Marek Vasut [this message]
2018-10-18 20:20 ` Simon Goldschmidt
2018-10-18 21:04 ` Marek Vasut
2018-10-22 19:55 ` Simon Goldschmidt
2018-10-23 8:39 ` Marek Vasut
2018-10-22 20:48 ` Simon Goldschmidt
2018-10-22 22:32 ` Dalon L Westergreen
2018-10-23 8:41 ` Marek Vasut
2018-10-23 8:52 ` Simon Goldschmidt
2018-10-23 8:54 ` Marek Vasut
2018-10-24 19:44 ` Simon Goldschmidt
2018-10-25 7:26 ` Marek Vasut
2018-10-23 9:28 ` Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2018-10-18 19:24 goldsimon at gmx.de
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=02ac1e8c-4d0b-d013-1641-50d01a43e8fb@gmail.com \
--to=marek.vasut@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox