linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-actions@lists.infradead.org, linux-kernel@vger.kernel.org,
	Russell King <linux@armlinux.org.uk>,
	Manivannan Sadhasivam <mani@kernel.org>
Subject: Re: [PATCH 1/1] ARM: owl: Add Actions Semi Owl S500 SoC machine
Date: Fri, 12 Mar 2021 11:28:53 +0200	[thread overview]
Message-ID: <20210312092853.GA931435@BV030612LT> (raw)
In-Reply-To: <47295735-2792-a517-b96a-a00a68496846@suse.de>

Hi Andreas,

On Fri, Mar 12, 2021 at 09:39:31AM +0100, Andreas Färber wrote:
> Hi Cristian,
> 
> On 11.03.21 20:19, Cristian Ciocaltea wrote:
> > Add machine entry for the S500 variant of the Actions Semi Owl SoCs
> > family.
> > 
> > For the moment the only purpose is to provide the system serial
> > information which will be used by the Owl Ethernet MAC driver to
> > generate a stable MAC address.
> 
> Can't that be done in either a sys_soc driver or U-Boot?

I will look first at the sys_soc driver approach.

I haven't started working on the U-Boot side yet, but I'm planning to do
so as soon as possible. Last time when I checked, there was some initial
support only for the S700 and S900 SoCs, but I will do my best to add
also the S500 to the list.

Thanks,
Cristi

> Regards,
> Andreas
> 
> -- 
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer
> HRB 36809 (AG Nürnberg)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-03-12  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 19:19 [PATCH 1/1] ARM: owl: Add Actions Semi Owl S500 SoC machine Cristian Ciocaltea
2021-03-12  8:39 ` Andreas Färber
2021-03-12  9:28   ` Cristian Ciocaltea [this message]
2021-03-19 18:33     ` Cristian Ciocaltea

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=20210312092853.GA931435@BV030612LT \
    --to=cristian.ciocaltea@gmail.com \
    --cc=afaerber@suse.de \
    --cc=linux-actions@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mani@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).