public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Porting a freescale sabrelite-like board to master ?
Date: Sat, 22 Feb 2014 14:16:28 -0700	[thread overview]
Message-ID: <530913AC.3000807@boundarydevices.com> (raw)
In-Reply-To: <53090207.5060003@free.fr>

Hi Thierry,

On 02/22/2014 01:01 PM, Thierry Bultel wrote:
> Le 22/02/2014 20:20, Wolfgang Denk a ?crit :
>> Dear Thierry,
>>
>> In message <5308E4D1.5000509@free.fr> you wrote:
>>> The board I am working on, is based on the Freescale sabrelite board,
>>> the manufacturer provides
>>> support for it , as an about 1000 lines patch that applies to
>>> rel_imx_3.0.35_4.1.0
>>> (3.0.35_4.1.0 is the kernel version I am using)
>> The kernel version is actually totally uninteresting here.  What
>> matters is what U-Boot version you have.  Let me guess - it is some
>> v2009.x - i. e. 5 year old stuff?
>
> Dear Wolfgang,
>
> Sorry for the confusion. I should have been more specific.
> What I meant is that my current u-boot version is
> tag "rel_imx_3.0.35_4.1.0" from
> http://git.freescale.com/git/cgit.cgi/imx/uboot-imx.git
>
> If I was mentioning the kernel version, it is just to say that switching
> to a more recent kernel
> version is not an option, because we do not have a device tree BSP for it.
>

Support for SABRE Lite is in the main-line kernel as well, but that's
a completely separate topic.

>>> So what would be the easiest and time less costing option to achieve
>>> what I want to do ?
>> It is best to take current code (top of tree in git repository) and
>> port it to your hardware from scratch.  You can use your old code as
>> reference, for example how to set up pin muxing and such.  Otherwise
>> it is pretty much worthless.
 >
> If the sabrelite board would still be supported in master, it would be
> straightforward.
> So I am thinking about re-bringing support for sabrelite my branch, first.
>

It **is** still in master. It just uses board/boundary/nitrogen6x.c
as the implementation.

It doesn't look anything like the 2009.08 code base, because, as
Wolfgang said, that's very old.

Regards,


Eric

  parent reply	other threads:[~2014-02-22 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-22 17:56 [U-Boot] Porting a freescale sabrelite-like board to master ? Thierry Bultel
2014-02-22 19:20 ` Wolfgang Denk
2014-02-22 20:01   ` Thierry Bultel
2014-02-22 20:05     ` Fabio Estevam
2014-02-22 21:16     ` Eric Nelson [this message]
2014-02-22 22:43     ` Wolfgang Denk
2014-02-22 21:12 ` Eric Nelson
2014-02-24  6:38   ` Yan, Miao

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=530913AC.3000807@boundarydevices.com \
    --to=eric.nelson@boundarydevices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox