mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Renaud Barbier <Renaud.Barbier@ametek.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 0/2] Initial LS1021-IOT board support
Date: Fri, 10 Feb 2023 13:25:40 +0100	[thread overview]
Message-ID: <20230210122540.GY10447@pengutronix.de> (raw)
In-Reply-To: <BL0PR07MB56659860B1E024CA7DA2AF55ECDE9@BL0PR07MB5665.namprd07.prod.outlook.com>

On Fri, Feb 10, 2023 at 11:54:31AM +0000, Renaud Barbier wrote:
> I have not tried yet. I was not sure if you like to have separate machine support as there are some differences in the SOC .
> 
> I will merge it and send you a new patch.

I like it better when it's merged, eventhough it's never compiled
together as they are different compiler architectures.

Sascha

> 
> > -----Original Message-----
> > From: Sascha Hauer <sha@pengutronix.de>
> > Sent: 10 February 2023 11:26
> > To: Renaud Barbier <Renaud.Barbier@ametek.com>
> > Cc: Barebox List <barebox@lists.infradead.org>
> > Subject: Re: [PATCH 0/2] Initial LS1021-IOT board support
> > 
> > ***NOTICE*** This came from an external source. Use caution when
> > replying, clicking links, or opening attachments.
> > 
> > On Wed, Feb 08, 2023 at 01:26:21PM +0000, Renaud Barbier wrote:
> > > The LS1021A-IOT is NXP ARMv7 Layerscape evaluation board.
> > >
> > > These patches provide a basic board support with:
> > >       - UART
> > >       - boot from SPI
> > >       - One Ethernet port - eth1*
> > >
> > > The content of the EEPROM having been lost so the MAC should be set in
> > > the config file
> > >
> > > The code is ported from NXP U-boot 2021-04. Like U-boot, the machine
> > > support i.e mac-lxxx lives in its own directory. However, it is very
> > > similar to the ls1046a machine support. This migth be merged. Please
> > advise.
> > 
> > It would be nice to have this merged to arch/arm/mach-layerscape. For
> > example arch/arm/mach-layerscape/pblimage.c looks identical to your
> > version.
> > 
> > Have you tried merging it? If yes, which problems did you encounter?
> > 
> > Sascha
> > 
> > --
> > Pengutronix e.K.                           |                             |
> > Steuerwalder Str. 21                       |
> > https://urldefense.com/v3/__http://www.pengutronix.de/__;!!HKOSU0g!C
> > ZdG8RU9gQpSVfJzH_T4b8q5lFRdLrpGiJsD5H-
> > H351N8ycvCriKuoi6quenVmESFrbU0Iw9qhIlb5z4ifTE$   |
> > 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
> > Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2023-02-10 12:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 13:26 Renaud Barbier
2023-02-10 11:25 ` Sascha Hauer
2023-02-10 11:54   ` Renaud Barbier
2023-02-10 12:25     ` Sascha Hauer [this message]
2023-02-10 15:57       ` Renaud Barbier
2023-02-10 16:59         ` Ahmad Fatoum

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=20230210122540.GY10447@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=Renaud.Barbier@ametek.com \
    --cc=barebox@lists.infradead.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