Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kinsella, Ray <ray.kinsella@intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7] board: add support for Intel Galileo Gen 2
Date: Tue, 10 Nov 2015 17:10:42 +0000	[thread overview]
Message-ID: <1447175442.3010.65.camel@intel.com> (raw)
In-Reply-To: <56314C13.5030302@mind.be>

Hi Arnout,

Humblest apologies for the delay in responding to your email.

>  There is now a v1.2 BSP at Intel that is based on 3.14. Unfortunately, it's in
> a 7z-packed tarball so not exactly easy to integrate...

There is - I am very familiar with it. There is more yocto specific
stuff to strip from this, so I will integrate after I get the base
enabling upstream based on 3.8.7. 

>  Doesn't genimage allow to specify this in a single file?
I tried putting them together - can't remember the issues I had, will
look at it again. 

>  ext2 is completely useless.
Agreed.

>  ext3 could be replaced by ext4.

Agreed.

> > +CONFIG_CRYPTO_CRC32C=y
> 
>  That's probably a leftover of some option you disabled.
Ok - will investigate. 

> > +# CONFIG_VIRTUALIZATION is not set
> > +CONFIG_CRC_T10DIF=y
>  This one too.

Ok - will investigate. 

>  No bashisms here, so /bin/sh

Agreed 

> 
>  Perhaps add a -e to exit on failure.

Agreed 

> > +RET=${?}
> > +exit ${RET}
> 
>  These two lines are redundant.

Agreed 

>  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. 

>  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

  reply	other threads:[~2015-11-10 17:10 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 [this message]
2015-11-10 19:59     ` Arnout Vandecappelle
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=1447175442.3010.65.camel@intel.com \
    --to=ray.kinsella@intel.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