From: Mike Frampton <mikeframpo@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/3] add support for Dragonboard410c
Date: Thu, 19 Nov 2020 22:08:51 +1300 [thread overview]
Message-ID: <20201119090854.48955-1-mikeframpo@gmail.com> (raw)
Hi Buildroot devs,
This is my second attempt at submitting a config for the Qualcomm
Dragonboard 410c. Thomas Petazzoni gave me some feedback on the last
series which I have tried to address in this patch.
I have built an image using the defconfig below and tested that it boots
on the DB410c. I also tested that the Wifi works.
Thomas suggested that I change the post-image.sh script so that it
doesn't reference the kernel build path. I was not able to achieve this
because my dtb and Image.gz were not copied to output/images. I
found that only the uncompressed kernel image was copied by the kernel
package, and I think my dts wasn't copied because I had
BR2_LINUX_KERNEL_DTB_IS_SELF_BUILT=y. Is this expected behaviour?
Mike Frampton (3):
package/qcom-db410c-firmware: new package
package/abootimg: add host build
configs/qcom_db410c: new defconfig
DEVELOPERS | 5 +
board/qcom/db410c/post-image.sh | 20 ++++
board/qcom/db410c/readme.txt | 93 +++++++++++++++++++
configs/qcom_db410c_defconfig | 28 ++++++
package/Config.in | 1 +
package/Config.in.host | 1 +
package/abootimg/Config.in.host | 8 ++
package/abootimg/abootimg.mk | 10 ++
package/qcom-db410c-firmware/Config.in | 6 ++
.../qcom-db410c-firmware.hash | 3 +
.../qcom-db410c-firmware.mk | 41 ++++++++
11 files changed, 216 insertions(+)
create mode 100755 board/qcom/db410c/post-image.sh
create mode 100644 board/qcom/db410c/readme.txt
create mode 100644 configs/qcom_db410c_defconfig
create mode 100644 package/abootimg/Config.in.host
create mode 100644 package/qcom-db410c-firmware/Config.in
create mode 100644 package/qcom-db410c-firmware/qcom-db410c-firmware.hash
create mode 100644 package/qcom-db410c-firmware/qcom-db410c-firmware.mk
--
2.25.1
next reply other threads:[~2020-11-19 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 9:08 Mike Frampton [this message]
2020-11-19 9:08 ` [Buildroot] [PATCH v2 1/3] package/qcom-db410c-firmware: new package Mike Frampton
2020-11-19 13:27 ` Thomas Petazzoni
2020-11-19 22:11 ` Thomas Petazzoni
2020-11-19 9:08 ` [Buildroot] [PATCH v2 2/3] package/abootimg: add host build Mike Frampton
2020-11-19 22:12 ` Thomas Petazzoni
2020-11-19 9:08 ` [Buildroot] [PATCH v2 3/3] configs/qcom_db410c: new defconfig Mike Frampton
2020-11-19 13:30 ` Thomas Petazzoni
2020-11-20 8:03 ` Mike Frampton
2020-11-21 8:16 ` Mike Frampton
2021-01-22 9:51 ` Peter Korsgaard
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=20201119090854.48955-1-mikeframpo@gmail.com \
--to=mikeframpo@gmail.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