mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] uimage: add define for RISC-V architecture
Date: Tue, 14 Apr 2020 11:22:49 +0200	[thread overview]
Message-ID: <20200414092249.GD27288@pengutronix.de> (raw)
In-Reply-To: <20200406153845.0aa8ff006f40897eecd1c9ed@gmail.com>

On Mon, Apr 06, 2020 at 03:38:45PM +0300, Antony Pavlov wrote:
> On Mon,  6 Apr 2020 15:23:13 +0300
> Antony Pavlov <antonynpavlov@gmail.com> wrote:
> 
> Hi Sascha,
> 
> It looks like barebox IN_ARCH_* constants in image.h and the same constants from U-Boot's image.h
> are differ.
> 
> > --- a/include/image.h
> > +++ b/include/image.h
> > @@ -75,6 +75,7 @@
> >  #define IH_ARCH_NDS32		20	/* ANDES Technology - NDS32  */
> >  #define IH_ARCH_OPENRISC	21	/* OpenRISC 1000  */
> >  #define IH_ARCH_ARM64		22	/* ARM64	*/
> > +#define IH_ARCH_RISCV		23	/* RISC-V	*/
> >  
> >  #if defined(__PPC__)
> >  #define IH_ARCH IH_ARCH_PPC
> 
> Does it matters?

Yes, it does. The numbers should be the same.

Sascha

-- 
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 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2020-04-14  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 12:23 Antony Pavlov
2020-04-06 12:38 ` Antony Pavlov
2020-04-14  9:22   ` Sascha Hauer [this message]

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=20200414092249.GD27288@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=antonynpavlov@gmail.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