From: Yann Sionneau <ysionneau@kalray.eu>
To: gianluca <gianlucarenzi@eurek.it>, barebox@lists.infradead.org
Subject: Re: STM32MP1 SoC support in latest Barebox
Date: Fri, 22 Mar 2019 10:46:31 +0100 [thread overview]
Message-ID: <09d70666-fe6d-0bfb-bbcc-e232d52d3e6d@kalray.eu> (raw)
In-Reply-To: <73e974ac-11a7-6ee7-ee1a-d5fab51e3b2f@eurek.it>
Hello,
By searching in list archive you could have found:
http://lists.infradead.org/pipermail/barebox/2019-March/037572.html
So there is a bit of support, which has been commited in "next" branch.
See
https://git.pengutronix.de/cgit/barebox/tree/arch/arm/boards/stm32mp157c-dk2?h=next
No idea how far this boots.
On 3/22/19 9:07 AM, gianluca wrote:
> Hello list!
>
> I need a __very quick__ answer to this subject, because a customer
> wants to migrate from a iMX28 based board to a STM32MP1.
>
> Actually the iMX28 board was developed by me, 6 years ago and it has
> Barebox 2013.02, Linux Kernel 3.12.1 and a Debian Wheezy. It runs from
> eMMC, but it can boot from microSD for production line.
>
> I modified Barebox with custom made init scripts to enable some i2c
> hardware before running Linux kernel, and Barebox had access/drivers
> for ethernet, serial for debugging console, i2c (bit-banging) and some
> gpios.
>
> It had access to ext4 filesystem on eMMC partition and managed somehow
> the device tree to pass to Linux and it works like charms!
>
> Now I would like to know (without spending too much time to gitclone
> the repo and reading the configuration stuff) if Barebox is still able
> to boot off a microSD, and having the same drivers available as the
> iMX28 has, just to reduce the porting session at their minimum levels.
>
> P.S.: I know UBoot for the evaluation board has all stuff I need, but
> I hate the way it works: too messy, too #ifdef clauses, etc.,...
>
> Thank you in advance,
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-03-22 9:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 4:57 selected processor does not support `rev r7,r7' Lewis Zhou
2019-03-20 7:52 ` Sascha Hauer
2019-03-21 1:03 ` Lewis Zhou
2019-03-21 7:33 ` Sascha Hauer
2019-03-21 7:53 ` Lewis Zhou
2019-03-21 8:06 ` Sascha Hauer
[not found] ` <CAD_PvuY8oVy3Ny65bcF2a3LPC0R4+8uXCu6qda6CcbY+Ji+3JQ@mail.gmail.com>
[not found] ` <CAPWKHJSLmc1+-rV0rZeGn37uhkWwKsqmWXZSGJAs32zLE=Hxtg@mail.gmail.com>
2019-03-21 8:49 ` Lewis Zhou
2019-03-21 9:25 ` Juergen Borleis
2019-03-22 1:02 ` Lewis Zhou
2019-03-22 8:07 ` STM32MP1 SoC support in latest Barebox gianluca
2019-03-22 9:31 ` gianluca
2019-12-25 8:32 ` Ahmad Fatoum
2019-03-22 9:46 ` Yann Sionneau [this message]
2019-03-22 11:24 ` Robert Schwebel
2019-03-22 1:22 ` selected processor does not support `rev r7,r7' Lewis Zhou
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=09d70666-fe6d-0bfb-bbcc-e232d52d3e6d@kalray.eu \
--to=ysionneau@kalray.eu \
--cc=barebox@lists.infradead.org \
--cc=gianlucarenzi@eurek.it \
/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