mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Stefan Lengfeld <contact@stefanchrist.eu>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: imx: add support for Udoo Neo full
Date: Wed, 28 Jun 2017 10:16:07 +0200	[thread overview]
Message-ID: <20170628081607.oidrzpkvvfc5zj2a@pengutronix.de> (raw)
In-Reply-To: <20170627194002.GB675@sill.h.stcim.de>

Hello Stefan,

On Tue, Jun 27, 2017 at 09:40:02PM +0200, Stefan Lengfeld wrote:
> > new file mode 100644
> > index 000000000000..9bf480305d70
> > --- /dev/null
> > +++ b/arch/arm/boards/udoo-neo/board.c
> > @@ -0,0 +1,27 @@
> > +/*
> > + * Copyright (C) 2014 Pengutronix, Sascha Hauer
> 
> Maybe add or replace your copyright here. At least you have changed some
> strings and function names.

I wonder if a board.c like this is copyrightable at all and don't feel
an urge to eternalize my name there.
 
> > + * This program is free software; you can redistribute it and/or
> > + * modify it under the terms of the GNU General Public License
> > + * version 2, as published by the Free Software Foundation.
> > + *
> > + * This program is distributed in the hope that it will be useful,
> > + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> > + * GNU General Public License for more details.
> > + */
> > +
> > +#include <common.h>
> > +#include <init.h>
> > +#include <linux/clk.h>
> > +
> > +static int imx6sx_udoneo_coredevices_init(void)
> > +{
> > +	if (!of_machine_is_compatible("fsl,imx6sx-udoo-neo"))
> > +		return 0;
> > +
> > +	barebox_set_hostname("mx6sx-udooneo");
> > +
> > +	return 0;
> > +}
> > +coredevice_initcall(imx6sx_udoneo_coredevices_init);
> > diff --git a/arch/arm/boards/udoo-neo/flash-header-mx6sx-udoo-neo_full.imxcfg b/arch/arm/boards/udoo-neo/flash-header-mx6sx-udoo-neo_full.imxcfg
> > new file mode 100644
> > index 000000000000..176aff49b3ec
> > --- /dev/null
> > +++ b/arch/arm/boards/udoo-neo/flash-header-mx6sx-udoo-neo_full.imxcfg
> > @@ -0,0 +1,124 @@
> > +loadaddr 0x80000000
> > +soc imx6
> > +dcdofs 0x400
> 
> I'm always wondering where the magic values in the flash headers are
> coming from. Whether they are copied from u-boot or another
> variant/board or completely self-made or provided by a friendly hardware
> engineer in an Excel sheet ;-) Maybe you can add a comment here or in
> the commit message. But this would be a new convention, because I have
> not seen it in other flash headers yet.

I got it in a patch from Sascha, don't know where he got it from. I
guess it's a mixure of copy-and-paste from other imxcfgs and the RAMs
datasheet.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

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

  reply	other threads:[~2017-06-28  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27 19:03 Uwe Kleine-König
2017-06-27 19:40 ` Stefan Lengfeld
2017-06-28  8:16   ` Uwe Kleine-König [this message]
2017-06-30  6:35   ` Sascha Hauer
2017-06-30  9:06     ` Uwe Kleine-König
2017-06-30  9:28       ` Sascha Hauer
2017-06-30 19:46 ` Andrey Smirnov

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=20170628081607.oidrzpkvvfc5zj2a@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=contact@stefanchrist.eu \
    /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