Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9166] Missing overlays directory in VFAT image for raspberry pi 3
Date: Thu, 18 Aug 2016 20:09:27 +0000	[thread overview]
Message-ID: <bug-9166-163-xlu6tZvhAC@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9166-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9166

--- Comment #4 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Diez,

> I checked, and matter of factly the patch would break buildroot if
> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS was not selected. So
> it's moot anyway.

I was not suggesting that you submit a patch to Buildroot, but that you
handle the customisation on your side. Use your own genimage.cfg file
that suits your need.

The manual has a section on how to handle local customisations:
    https://buildroot.org/downloads/manual/manual.html#customize

One would argue that overlays are very often used so they should be
installed by our defconfigs.

However, there are so many overlays, for so different things, that
usually only one or a few would be needed in a specific case. Or even
that overlays from anotehr place are used.

So I am still not sure we want to have our defconfigs install the
overlays.

Regards,
Yann E. MORIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2016-08-18 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 14:03 [Buildroot] [Bug 9166] New: Missing overlays directory in VFAT image for raspberry pi 3 bugzilla at busybox.net
2016-08-16 17:14 ` [Buildroot] [Bug 9166] " bugzilla at busybox.net
2016-08-16 17:41 ` bugzilla at busybox.net
2016-08-18 15:44 ` bugzilla at busybox.net
2016-08-18 17:31 ` bugzilla at busybox.net
2016-08-18 20:09 ` bugzilla at busybox.net [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=bug-9166-163-xlu6tZvhAC@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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