From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 4/5] gnu: kernel-config: Add armhf kernel config.
Date: Mon, 5 Sep 2016 16:25:43 +0200 [thread overview]
Message-ID: <20160905162543.126bd93e@scratchpost.org> (raw)
In-Reply-To: <87mvjmpx52.fsf@gnu.org>
> I wonder if it makes sense to have a single “armhf” configuration. My
> understanding is that the config is often tweaked for the specific ARM
> board that is targeted.
Even worse, it used to be the case that ARM kernels only worked on one specific ARM board.
However, the multi configuration is an effort to make it work on any ARM board that uses the given architecture. I didn't try these, however.
The multi defconfigs are: multi_v4t_defconfig multi_v5_defconfig multi_v7_defconfig
next prev parent reply other threads:[~2016-09-05 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 16:09 [PATCH] gnu: linux-libre-headers: Use modify-phases David Craven
2016-09-02 16:09 ` [PATCH 1/5] gnu: module-init-tools: Prevent line wrapping David Craven
2016-09-05 8:22 ` Ludovic Courtès
2016-09-02 16:09 ` [PATCH 2/5] gnu: linux-libre: Use modify-phases David Craven
2016-09-05 8:23 ` Ludovic Courtès
2016-09-02 16:09 ` [PATCH 3/5] gnu: linux-libre: Use system->architecture David Craven
2016-09-05 8:27 ` Ludovic Courtès
2016-09-02 16:09 ` [PATCH 4/5] gnu: kernel-config: Add armhf kernel config David Craven
2016-09-05 8:29 ` Ludovic Courtès
2016-09-05 14:25 ` Danny Milosavljevic [this message]
2016-09-05 14:29 ` David Craven
2016-09-05 20:44 ` Leo Famulari
2016-09-02 16:09 ` [PATCH 5/5] gnu: linux-libre: Add support for cross-compilation David Craven
2016-09-02 16:24 ` David Craven
2016-09-05 8:33 ` Ludovic Courtès
2016-09-05 8:23 ` [PATCH] gnu: linux-libre-headers: Use modify-phases Ludovic Courtès
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=20160905162543.126bd93e@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.