All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/2] Add SIMATIC IOT2050 board support
Date: Wed, 23 Dec 2020 13:48:51 +0530	[thread overview]
Message-ID: <9c1a2e23-9641-8bbd-4983-ab7fbc18c4b1@ti.com> (raw)
In-Reply-To: <21894fc3-a6c2-f65e-a115-7baa79f99627@siemens.com>



On 18/12/20 11:43 am, Jan Kiszka wrote:
> On 18.12.20 07:04, Jan Kiszka wrote:
>> On 18.12.20 05:46, Lokesh Vutla wrote:
>>> Hi Jan,
>>> 	Sorry for the delayed response.
>>>
>>> On 04/12/20 1:29 pm, Jan Kiszka wrote:
>>>> This is the baseline support for the SIMATIC IOT2050 devices.
>>>>
>>>> Allows to boot mainline 5.10 kernels, but not the original BSP-derived
>>>> kernel we currently ship as reference. This is due to the TI sysfw ABI
>>>> breakages between 2.x and 3.x. We will soon provide a transitional
>>>> kernel that allows booting both firmware ABIs - as long as full upstream
>>>> kernel support is work in progress.
>>>>
>>>> Note that this baseline support lacks Ethernet drivers. We are working
>>>> closely with TI to ensure that the to-be-upstreamed icssg-prueth driver
>>>> will work both with new SR2.0 AM65x silicon as well as with SR1.0 which
>>>> is used in the currently shipped IOT2050 devices.
>>>>
>>>> Related but not strictly needed for baseline support is [1], i.e.
>>>> embedding of the watchdog firmware that is required on the AM65x. I will
>>>> soon pick up that discussion again.
>>>
>>> yeah, long pending one.
>>>
>>>>
>>>> A staging tree for complete IOT2050 support can be found at [2]. Full
>>>> image integration is available via [3].
>>>
>>> patches look good to me. Any chance these dts changes are reviewed in upstream
>>> Linux?
>>
>> I didn't want to push them there first before publishing a firmware that
>> allows to boot them - chicken-egg situation. I thought this way would be
>> better and would also be no issue as we we are only using existing
>> bindings. Obviously, any future changes to the kernel version would also
>> be sync'ed back to U-Boot by us.
> 
> But good that you mentioned it: I just realized that the path we are
> using ("siemens/iot2050-{basic,advanced}.dtb") is probably not
> upstreamable. This may have to become
> "ti/k3-am65-iot2050-{basic,advanced}.dtb", and that is also an interface
> between kernel and U-Boot...
> 

Planning to repost the series?

Thanks and regards,
Lokesh

> Jan
> 

  reply	other threads:[~2020-12-23  8:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  7:59 [PATCH 0/2] Add SIMATIC IOT2050 board support Jan Kiszka
2020-12-04  7:59 ` [PATCH 1/2] arm: dts: Add IOT2050 device tree files Jan Kiszka
2020-12-04  7:59 ` [PATCH 2/2] board: siemens: Add support for SIMATIC IOT2050 devices Jan Kiszka
2020-12-18  4:46 ` [PATCH 0/2] Add SIMATIC IOT2050 board support Lokesh Vutla
2020-12-18  6:04   ` Jan Kiszka
2020-12-18  6:13     ` Jan Kiszka
2020-12-23  8:18       ` Lokesh Vutla [this message]
2020-12-23  9:43         ` Jan Kiszka

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=9c1a2e23-9641-8bbd-4983-ab7fbc18c4b1@ti.com \
    --to=lokeshvutla@ti.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.