Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] board: Add PowerPC mac99
Date: Fri, 02 Aug 2019 11:30:07 +0200	[thread overview]
Message-ID: <87r263syn4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CACPK8XfC=f5t+=KwmzTHDR-KedP0nLkgf8YHcRv+NpVVZ5ikDw@mail.gmail.com> (Joel Stanley's message of "Fri, 2 Aug 2019 06:42:52 +0000")

>>>>> "Joel" == Joel Stanley <joel@jms.id.au> writes:

Hi,

 >> You forgot to specify the version of the Linux kernel /
 >> kernel-headers. Committed with those set to 5.2.4, thanks.

 > I didn't forget, I omitted them so the config would use the latest default.

 > Is there a reason we specify a fixed version?

Yes, reproducibility. If the defconfig is tested and working today, then
it should preferably still work in (say) 6 months from now.


 >> With that said, we now have 4 32bit ppc qemu defconfigs which sounds
 >> like a lot to me. Are they all still interesting / useful?

 > I am not familiar with them. Michael?

 > They all target different CPUs which means there is no overlap at least:

 > $ grep -r BR2_powerpc_ configs/qemu_ppc_*
 > configs/qemu_ppc_g3beige_defconfig:BR2_powerpc_750=y
 > configs/qemu_ppc_mac99_defconfig:BR2_powerpc_7400=y
 > configs/qemu_ppc_mpc8544ds_defconfig:BR2_powerpc_8548=y
 > configs/qemu_ppc_virtex_ml507_defconfig:BR2_powerpc_440=y

Correct. Ok, lets leave them for now then.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2019-08-02  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25  1:26 [Buildroot] [PATCH v3] board: Add PowerPC mac99 Joel Stanley
2019-07-18  6:41 ` Joel Stanley
2019-08-01 15:54 ` Peter Korsgaard
2019-08-02  6:42   ` Joel Stanley
2019-08-02  9:30     ` Peter Korsgaard [this message]
     [not found]     ` <87d0hlw4tk.fsf@concordia.ellerman.id.au>
2019-08-04 12:24       ` 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=87r263syn4.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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