All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9166] New: Missing overlays directory in VFAT image for raspberry pi 3
Date: Thu, 11 Aug 2016 14:03:01 +0000	[thread overview]
Message-ID: <bug-9166-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 9166
           Summary: Missing overlays directory in VFAT image for raspberry
                    pi 3
           Product: buildroot
           Version: 2016.05
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: diez.roggisch at ableton.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

When running a raspberry pi 3 buildroot, dtoverlay-parameters (e.g. 
dtoverlay=pi3-disable-bt) don't work, because the VFAT image doesn't contain
the overlays-subdirectory.

The following patch fixes this.

diff --git a/board/raspberrypi/genimage-raspberrypi3.cfg
b/board/raspberrypi/genimage-raspberrypi3.cfg
index 7ba89c5..baab0c4 100644
--- a/board/raspberrypi/genimage-raspberrypi3.cfg
+++ b/board/raspberrypi/genimage-raspberrypi3.cfg
@@ -7,6 +7,7 @@ image boot.vfat {
       "rpi-firmware/config.txt",
       "rpi-firmware/fixup.dat",
       "rpi-firmware/start.elf",
+      "rpi-firmware/overlays",
       "kernel-marked/zImage"
     }
   }

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

             reply	other threads:[~2016-08-11 14:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 14:03 bugzilla at busybox.net [this message]
2016-08-16 17:14 ` [Buildroot] [Bug 9166] Missing overlays directory in VFAT image for raspberry pi 3 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

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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.