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] [PATCH 5/5 v2] configs: add a DT-enabled Raspberry Pi defconfig
Date: Sat, 10 Jan 2015 12:17:51 +0100	[thread overview]
Message-ID: <20150110121751.0bddd30b@free-electrons.com> (raw)
In-Reply-To: <b65d009bf4aeb83b97e02a9fd03c14888b5f1ce2.1420843412.git.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Fri,  9 Jan 2015 23:46:23 +0100, Yann E. MORIN wrote:

>   - we can not use the minimalist RPi defconfig bundled with the kernel,
>     namely bcmrpi_quick_defconfig, because it is not DT-enabled, and
>     sets CONFIG_ARM_PATCH_PHYS_VIRT to 'n', which prompts a value for
>     CONFIG_PHYS_OFFSET, as it as no default for the bcm familly;
> 
>   - we have to use the 'default' but bloated bcmrpi_defconfig, which
>     makes for a very fat kernel with lots of modules, and takes ages to
>     build;
> 
>   - most importantly, the rpi-3.18.y branch is constantly rebased, so
>     there is no guarantee that the sha1 I use today will still be usable
>     in the long term. Using the name of hte branch is not better either.

Well, you could alternatively decide to have a custom kernel defconfig
in board/raspberrypi/, which would be the same as bcmrpi_quick, with
just the modifications you need for DT. Sure it means it will have to
be updated from time to time, but hopefully at some point in the future
the official bcmrpi_quick defconfig will have DT support enabled.

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

  reply	other threads:[~2015-01-10 11:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 22:46 [Buildroot] [PATCH 0/5 v2] RPi: enable building a device-tree-enabled kernel (branch yem/rpi-dt) Yann E. MORIN
2015-01-09 22:46 ` [Buildroot] [PATCH 1/5 v2] package/rpi-firmware: add DT-aware marking script Yann E. MORIN
2015-01-09 22:46 ` [Buildroot] [PATCH 2/5 v2] package/rpi-firmware: install DTB blobs Yann E. MORIN
2015-01-09 22:46 ` [Buildroot] [PATCH 3/5 v2] boards/raspberrypi: don't document non-existent files Yann E. MORIN
2015-01-09 22:46 ` [Buildroot] [PATCH 4/5 v2] boards/raspberrypi: update readme with Device Tree instructions Yann E. MORIN
2015-01-09 22:46 ` [Buildroot] [PATCH 5/5 v2] configs: add a DT-enabled Raspberry Pi defconfig Yann E. MORIN
2015-01-10 11:17   ` Thomas Petazzoni [this message]
2015-01-10 11:28     ` Thomas Petazzoni
2015-01-10 11:23 ` [Buildroot] [PATCH 0/5 v2] RPi: enable building a device-tree-enabled kernel (branch yem/rpi-dt) Thomas Petazzoni
2015-01-10 11:27   ` Yann E. MORIN

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=20150110121751.0bddd30b@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