From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7] board: add support for Intel Galileo Gen 2
Date: Tue, 10 Nov 2015 20:59:55 +0100 [thread overview]
Message-ID: <56424CBB.2080306@mind.be> (raw)
In-Reply-To: <1447175442.3010.65.camel@intel.com>
On 10-11-15 18:10, Kinsella, Ray wrote:
[snip]
>> Why not just hard link all of these instead of loading them as modules? The
>> drivers that differ between the two modules are so small that it's not going to
>> make a significant difference in kernel size.
>
> Ok I will figure out which ones are not model specific and hard link
> them. I seem to have some memory the model specific ones are mutually
> exclusive, they shouldn't be loaded at the same time, will need to
> verify.
If that's the case, please mention it in the commit log.
Regards,
Arnout
>
>> Perhaps add a comment here that this version is needed for the -Wl,... option.
> Agreed,
>
>> Can we use ext4 instead?
> Agreed,
>
>>
>>> +BR2_TARGET_ROOTFS_EXT2_LABEL="rootfs.ext2"
>>
>> That's not needed.
> Ok.
>
> Ray K
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-11-10 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 16:48 [Buildroot] [PATCH v7] board: add support for Intel Galileo Gen 2 Kinsella, Ray
2015-10-28 22:28 ` Arnout Vandecappelle
2015-11-10 17:10 ` Kinsella, Ray
2015-11-10 19:59 ` Arnout Vandecappelle [this message]
2015-11-16 17:29 ` Kinsella, Ray
2015-11-16 18:17 ` Kinsella, Ray
2015-11-04 20:53 ` Thomas Petazzoni
2015-11-05 8:46 ` Kinsella, Ray
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=56424CBB.2080306@mind.be \
--to=arnout@mind.be \
--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