Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 0/2] Add Freescale e5500 & e6500 support
Date: Mon, 8 Dec 2014 00:21:43 +0100	[thread overview]
Message-ID: <20141208002143.55b94d12@free-electrons.com> (raw)
In-Reply-To: <5484E01A.7080802@zacarias.com.ar>

Dear Gustavo Zacarias,

On Sun, 07 Dec 2014 20:17:46 -0300, Gustavo Zacarias wrote:

> > Patches applied. I must say I'm a bit confused by why we exclude PP64le
> > for those new platforms. Is there theoretically something that would
> > prevent those from being used in LE mode?
> 
> As far i was able to find out without hardware the fsl ppc64 SOCs aren't
> able to boot in LE mode.
> It's like ARM, if the peripherals aren't ready for it even though the
> CPU itself can do so it won't work right.

Hum, right. I worked on an ARM platform that does support both LE and
BE. For most things, there is no need for any sort of BE/LE handling at
the peripheral level, except maybe for DMA descriptors shared by the
CPU and device (even though the CPU could do the effort of doing things
LE even if the system is running BE).

> For example for pseries there's the pseries_le_defconfig, for the fsl 64
> bit chips there's corenet64_smp_defconfig but no LE counterpart.
> Even though CONFIG_CPU_LITTLE_ENDIAN can be toggled for said config i
> wasn't able to find anything related to actually booting that (and it's
> a pretty generic option).
> So i "erred" on the safe side.

Ok, works for me.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-12-07 23:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 23:14 [Buildroot] [RFC PATCH 0/2] Add Freescale e5500 & e6500 support Gustavo Zacarias
2014-11-17 23:14 ` [Buildroot] [PATCH 1/2] arch/powerpc: add fsl e5500 and " Gustavo Zacarias
2014-11-18 13:56   ` Matthew Weber
2014-11-18 14:28     ` Gustavo Zacarias
2014-11-18 15:20       ` Thomas Petazzoni
2014-11-18 16:28         ` Gustavo Zacarias
2014-11-18 16:56           ` Thomas Petazzoni
2014-11-18 17:00             ` Gustavo Zacarias
2014-11-18 17:04               ` Thomas Petazzoni
2014-11-18 18:31             ` Baruch Siach
2014-11-18 20:59               ` Thomas Petazzoni
2014-11-17 23:14 ` [Buildroot] [PATCH 2/2] package/gcc: set e5500 and e6500 version mask Gustavo Zacarias
2014-12-07 22:48 ` [Buildroot] [RFC PATCH 0/2] Add Freescale e5500 & e6500 support Thomas Petazzoni
2014-12-07 23:17   ` Gustavo Zacarias
2014-12-07 23:21     ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-20 16:41 Dwayne Fontenot

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=20141208002143.55b94d12@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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