From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8516] mkcubiecard.sh uses outdated sfdisk switch -D
Date: Sun, 06 Nov 2016 22:15:10 +0000 [thread overview]
Message-ID: <bug-8516-163-tvvtlugTVX@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8516-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8516
--- Comment #6 from Tudor <tudor@tudorholton.com> ---
I was just pointing out that the bug report and your previous comment are out
of sync. I reported this bug against the cubieboard2, not the original
cubieboard as you assumed from the cruft left behind.
I have only ever owned a cubieboard2. At the time I reported the bug, the
cubieboard2_defconfig also called mkcubieboard.sh. As you noted, it doesn't
any more as it was converted to genimage before I was able to get to it.
I was only ever reporting against the cubieboard2 build, anyway, so it doesn't
affect me. However, I believe the build between the two boards is identical
(since the only difference is the number of cores), so I believe that the
genimage script for the cubieboard2 could be easily used by
cubieboard_defconfig also. However, I don't own an original cubieboard to test
it.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-11-06 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 2:22 [Buildroot] [Bug 8516] New: mkcubiecard.sh uses outdated sfdisk switch -D bugzilla at busybox.net
2015-12-14 5:37 ` [Buildroot] [Bug 8516] " bugzilla at busybox.net
2016-02-14 21:10 ` bugzilla at busybox.net
2016-11-03 21:53 ` bugzilla at busybox.net
2016-11-04 1:20 ` bugzilla at busybox.net
2016-11-04 8:44 ` bugzilla at busybox.net
2016-11-06 22:15 ` 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-8516-163-tvvtlugTVX@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.