public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] socfpga cyclone5 dts
Date: Mon, 22 Oct 2018 22:48:56 +0200	[thread overview]
Message-ID: <065bebef-3398-e7c2-eb4f-65dbf67c37ef@gmail.com> (raw)
In-Reply-To: <a438c356-da92-9f35-c418-55a48c4ab85b@gmail.com>

On 18.10.2018 23:04, Marek Vasut wrote:
> On 10/18/2018 10:20 PM, Simon Goldschmidt wrote:
>>
>> Marek Vasut <marek.vasut at gmail.com <mailto:marek.vasut@gmail.com>>
>> schrieb am Do., 18. Okt. 2018, 22:15:
>>
>>      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.
>>
>>
>> Ok, I'll just try and prepare a patch that ports the existing boards and
>> mentions the boards not ported from current kernel sources. I don't want
>> to remove boards from U-Boot, so we'll just have to test those not in Linux.
> Sounds good!

After a short test run, I decided to first ask for the boards before 
preparing a patch:

Boards in U-Boot but not in Linux (not updated):
- socfpga_cyclone5_dbm_soc1.dts
- socfpga_cyclone5_de0_nano_soc.dts (is this 
'socfpga_cyclone5_de0_sockit.dts'?)
- socfpga_cyclone5_de1_soc.dts
- socfpga_cyclone5_de10_nano.dts
- socfpga_cyclone5_is1.dts
- socfpga_cyclone5_sr1500.dts

Boards in Linux but not in U-Boot:
- socfpga_cyclone5_de0_sockit.dts (is this 
'socfpga_cyclone5_de0_nano_soc.dts'?)
- socfpga_cyclone5_sodia.dts

Also, Dinh has enabled the watchdog nearly 4 years ago in 
socfpga_cyclone5.dtsi but U-Boot doesn't. Should we keep it enabled or 
disable it in the U-Boot specific dts files?

Thanks,
Simon

  parent reply	other threads:[~2018-10-22 20:48 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
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 [this message]
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=065bebef-3398-e7c2-eb4f-65dbf67c37ef@gmail.com \
    --to=simon.k.r.goldschmidt@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