From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] configs: new defconfig for TI am335x-evm
Date: Wed, 21 Sep 2016 10:53:03 +0200 [thread overview]
Message-ID: <20160921105303.1832ad5e@free-electrons.com> (raw)
In-Reply-To: <87fuotya3r.fsf@dell.be.48ers.dk>
Hello,
On Wed, 21 Sep 2016 09:40:08 +0200, Peter Korsgaard wrote:
> > +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="am335x_evm"
>
> > I.e, isn't U-Boot consequently only working on the arm335x_evm
> > platform? Or is the am335x_evm U-Boot configuration also usable for
> > BeagleBone/BeagleBoneBlack?
>
> I believe so, yes. It afaik detects the board variant based on the
> content of an i2c eeprom.
Hum, OK.
> > It seems that it's the case thanks to:
>
> > CONFIG_OF_LIST="am335x-evm am335x-bone am335x-boneblack am335x-evmsk am335x-bonegreen am335x-icev2"
>
> > in the U-Boot configuration. Can you confirm?
>
> > If that's the case, then is the name of the defconfig really properly
> > chosen? Should we remove beaglebone_defconfig in favor of a common
> > defconfig for all am335x configurations?
>
> > I'd say, either we name the defconfig am335x_evm_defconfig, and it
> > should support only this board, or we name it am335x_defconfig and it
> > supports multiple boards and replaces other AM335x defconfigs we
> > already have.
>
> Well, it is only for the ti/circuitco boards, not any other boards with
> a am335x.
>
> I still think naming the defconfig beaglebone_defconfig makes it easier
> to find for newcomers, even though it could also be used on the TI
> evm. People are also much more likely to have one of the beaglebone
> variants than the evm.
So maybe it's easier to have separate beaglebone_defconfig (for just
the beaglebone) and am335x_evm_defconfig (for just the EVM), without
trying to have a defconfig that handles multiple boards.
What do you think?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-21 8:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 11:51 [Buildroot] [PATCH 1/1] configs: new defconfig for TI am335x-evm Lothar Felten
2016-09-18 17:30 ` Thomas Petazzoni
2016-09-21 7:40 ` Peter Korsgaard
2016-09-21 8:53 ` Thomas Petazzoni [this message]
2016-09-21 9:01 ` Peter Korsgaard
2016-09-21 10:18 ` Thomas Petazzoni
2016-09-21 10:36 ` Peter Korsgaard
2016-09-21 10:55 ` Thomas Petazzoni
2016-09-21 11:23 ` Peter Korsgaard
2016-09-21 12:09 ` Thomas Petazzoni
2016-09-22 22:21 ` Lothar Felten
2016-09-23 5:47 ` Thomas Petazzoni
2016-09-23 6:50 ` 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=20160921105303.1832ad5e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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.