From: Carlo Caione <carlo@caione.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Dave Thompson <dthompson@nexusisp.com>, barebox@lists.infradead.org
Subject: Re: rpi 2 support ?
Date: Mon, 30 Nov 2015 09:14:12 +0100 [thread overview]
Message-ID: <CAOQ7t2aPeKjW5kdZJw8v4iFb_LZ+fDb9dp37G89S7=FzFHBosw@mail.gmail.com> (raw)
In-Reply-To: <20151130072810.GT11966@pengutronix.de>
On Mon, Nov 30, 2015 at 8:28 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Hi Dave,
>
> On Sun, Nov 29, 2015 at 10:15:37AM -0500, Dave Thompson wrote:
>> Good day
>> This seems to be an active list so my question is
>> Is there raspberry pi 2B support,, BCM2836?
>> from looking at the rpi config it seem to only mention 2835,
>> I am not sure that it would compile (native) on a 2836
>> since memory for example is different
>> Not wanting to insult,,
>> why I am interested is to make it a boot manager,
>> to load the start elf, then bareboot.bin and run a script
>> to choose what to boot.. Sort of like smart boot manager,
>> maybe not so smoothly,, that is what starts this computer
>> And how to add the kernel configs?
>
> Currently there is no rpi2 support for barebox. I don't know what's
> missing to add support since I'm not familiar with the rpi and don't
> know how much it differs from the rpi2. Added Carlo Caione to Cc who
> added the rpi support initially. Maybe he has a few words for us.
Hi Sasha,
no idea about the rpi2 support. The rpi support was very basic, just
UART and timers IIRC.
--
Carlo Caione
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-11-30 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 15:15 Dave Thompson
2015-11-30 7:28 ` Sascha Hauer
2015-11-30 8:14 ` Carlo Caione [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='CAOQ7t2aPeKjW5kdZJw8v4iFb_LZ+fDb9dp37G89S7=FzFHBosw@mail.gmail.com' \
--to=carlo@caione.org \
--cc=barebox@lists.infradead.org \
--cc=dthompson@nexusisp.com \
--cc=s.hauer@pengutronix.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