From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 4/4] A20-OLinuXino-Lime: new board (mali)
Date: Sat, 20 Jun 2015 09:29:49 +0200 [thread overview]
Message-ID: <20150620072949.GI11732@lukather> (raw)
In-Reply-To: <CAB0FRsvzKgP23+-fuwawaqyrJfzY39BLns+jkd1rBwgfdCoMsQ@mail.gmail.com>
On Sat, Jun 20, 2015 at 07:28:01AM +0200, Fran?ois Perrad wrote:
> >> +# Bootloaders
> >> +BR2_TARGET_UBOOT=y
> >> +BR2_TARGET_UBOOT_BOARDNAME="A20-OLinuXino-Lime"
> >> +BR2_TARGET_UBOOT_CUSTOM_GIT=y
> >> +BR2_TARGET_UBOOT_VERSION="sunxi"
> >> +BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/linux-sunxi/u-boot-sunxi.git"
> >> +# based on U-Boot 2014.04
> >> +BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="ea1ac32bf76eb60baef474c2516fc431b381d952"
> >> +BR2_TARGET_UBOOT_FORMAT_BIN=y
> >> +BR2_TARGET_UBOOT_SPL=y
> >> +BR2_TARGET_UBOOT_SPL_NAME="u-boot-sunxi-with-spl.bin"
> >
> > U-boot sunxi is unmaintained and deprecated, you probably don't wnat
> > to use that.
> >
>
> When I try to use the mainline U-Boot (which works well with a
> mainline kernel), I cannot start the linux-sunxi kernel.
> I think that it is problem with bootargs, but I haven't found the good
> 'magic' value.
> So, I stay with U-boot sunxi.
I'm not sure this is a valid argument for such a patch. Have you read
https://linux-sunxi.org/Mainline_U-boot#Boot ?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150620/39cab939/attachment.asc>
next prev parent reply other threads:[~2015-06-20 7:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 19:13 [Buildroot] [V2 0/4] A20-OLinuXino-Lime: new board Francois Perrad
2015-06-19 19:13 ` [Buildroot] [V2 1/4] sunxi-board: bump to version a6a4e94066f4ec6b26fc7060dc453a6bcf26a504 Francois Perrad
2015-06-21 4:42 ` Thomas Petazzoni
2015-06-19 19:13 ` [Buildroot] [V2 2/4] a10disp: bump to version v0.6.1 Francois Perrad
2015-06-21 4:43 ` Thomas Petazzoni
2015-06-19 19:13 ` [Buildroot] [V2 3/4] A20-OLinuXino-Lime: new board (mainline) Francois Perrad
2015-06-19 20:49 ` Arnout Vandecappelle
2015-06-22 12:23 ` Luca Ceresoli
2015-06-22 20:56 ` Yann E. MORIN
2015-06-22 21:22 ` Arnout Vandecappelle
2015-06-22 12:06 ` Luca Ceresoli
2015-06-19 19:13 ` [Buildroot] [V2 4/4] A20-OLinuXino-Lime: new board (mali) Francois Perrad
2015-06-19 20:08 ` Maxime Ripard
2015-06-20 5:28 ` François Perrad
2015-06-20 7:29 ` Maxime Ripard [this message]
2015-06-19 20:49 ` Arnout Vandecappelle
2015-06-20 5:39 ` François Perrad
2015-06-19 21:55 ` Arnout Vandecappelle
2015-06-20 5:33 ` François Perrad
2015-06-20 9:26 ` Arnout Vandecappelle
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=20150620072949.GI11732@lukather \
--to=maxime.ripard@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