<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/arch/sandbox/Kconfig, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2018-02-18T22:53:48Z</updated>
<entry>
<title>sandbox: Add 64-bit sandbox</title>
<updated>2018-02-18T22:53:48Z</updated>
<author>
<name>Mario Six</name>
</author>
<published>2018-02-12T07:05:57Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=c6b89f31806df06a5d7b688a65f9d2e6e6119a55'/>
<id>urn:sha1:c6b89f31806df06a5d7b688a65f9d2e6e6119a55</id>
<content type='text'>
To debug device tree issues involving 32- and 64-bit platforms, it is useful to
have a generic 64-bit platform available.

Add a version of the sandbox that uses 64-bit integers for its physical
addresses as well as a modified device tree.

Signed-off-by: Mario Six &lt;mario.six@gdsys.cc&gt;
Added CONFIG_SYS_TEXT_BASE to configs/sandbox64_defconfig
Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Convert SANDBOX_BITS_PER_LONG to Kconfig</title>
<updated>2017-09-12T03:43:58Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2017-08-01T23:33:34Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=226b50bbd87b0c4ebf913066dfadbe04306ce402'/>
<id>urn:sha1:226b50bbd87b0c4ebf913066dfadbe04306ce402</id>
<content type='text'>
Convert SANDBOX_BITS_PER_LONG to Kconfig and assign it a correct
number depending on which host we are going to build and run.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Introduce Kconfig option for 32/64 bit host</title>
<updated>2017-09-12T03:43:58Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2017-08-01T23:33:33Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=98cff66027c44e6e15eb48dbb2300f388bcc172c'/>
<id>urn:sha1:98cff66027c44e6e15eb48dbb2300f388bcc172c</id>
<content type='text'>
It seems most of the time we are building and running sandbox on 64-bit host.
But we do support 32-bit host as well. Introduce Kconfig option for this.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>drivers/pci/Kconfig: Add PCI</title>
<updated>2016-10-28T00:33:56Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2016-10-26T21:15:37Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=af27382e2d6f7b4966e6932c9820939259498c1b'/>
<id>urn:sha1:af27382e2d6f7b4966e6932c9820939259498c1b</id>
<content type='text'>
Add 'PCI' as a menu option and migrate all existing users.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
Acked-by: Stephen Warren &lt;swarren@nvidia.com&gt;
</content>
</entry>
<entry>
<title>sandbox, x86: select DM_KEYBOARD instead of default y entry</title>
<updated>2016-10-02T00:04:33Z</updated>
<author>
<name>Masahiro Yamada</name>
</author>
<published>2016-09-08T09:47:35Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=558e12571e3cc949837ab0c232a1bb528a8f95da'/>
<id>urn:sha1:558e12571e3cc949837ab0c232a1bb528a8f95da</id>
<content type='text'>
Once we migrate to DM-based drivers, we cannot go back to legacy
ones, i.e. config options like DM_* are not user-configurable.

Make SANDBOX and X86 select DM_KEYBOARD like other platforms do.

Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Add a new sandbox_spl board</title>
<updated>2016-07-15T02:40:24Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2016-07-04T17:57:54Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=8797b2cae3ac5ddb005665e4b5cde4783a4f5555'/>
<id>urn:sha1:8797b2cae3ac5ddb005665e4b5cde4783a4f5555</id>
<content type='text'>
It is useful to be able to build SPL for sandbox. It provides additional
build coverage and allows SPL features to be tested in sandbox. However
it does not need worthwhile to always create an SPL build. It nearly
doubles the build time and the feature is (so far) seldom used.

So for now, create a separate build target for sandbox SPL. This allows
experimentation with this new feature without impacting existing workflows.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Set CONFIG_SYS_CPU</title>
<updated>2016-04-18T21:11:49Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2016-04-18T17:57:42Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=0c4b3880c1113276c6949effdd88d28578ab8ed5'/>
<id>urn:sha1:0c4b3880c1113276c6949effdd88d28578ab8ed5</id>
<content type='text'>
Give a valid value here as well to allow things which want
CONFIG_ENV_VARS_UBOOT_CONFIG to build

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>dm: cros_ec: Convert cros_ec keyboard driver to driver model</title>
<updated>2015-11-20T03:13:40Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2015-10-19T03:17:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=1fa4bfde181c020274b9689af9b001c31ae43f0f'/>
<id>urn:sha1:1fa4bfde181c020274b9689af9b001c31ae43f0f</id>
<content type='text'>
Adjust the cros_ec keyboard driver to support driver model. Make this the
default for all Exynos boards so that those that use a keyboard will build
correctly with this driver.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Use defconfig to enable features</title>
<updated>2015-05-21T13:13:18Z</updated>
<author>
<name>Joe Hershberger</name>
</author>
<published>2015-05-20T19:27:15Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=c0d57304eba166d133b84b36e38df2a27fc9e832'/>
<id>urn:sha1:c0d57304eba166d133b84b36e38df2a27fc9e832</id>
<content type='text'>
Stop using the sandbox arch Kconfig to override defaults for config
options. This is a bit of abuse and may be causing build problems.

Signed-off-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</content>
</entry>
<entry>
<title>dm: select CONFIG_DM* options</title>
<updated>2015-04-18T17:11:30Z</updated>
<author>
<name>Masahiro Yamada</name>
</author>
<published>2015-03-31T03:47:53Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=58d423b88e5bc1b6e43aa04a05feccd0e737c061'/>
<id>urn:sha1:58d423b88e5bc1b6e43aa04a05feccd0e737c061</id>
<content type='text'>
As mentioned in the previous commit, adding default values in each
Kconfig causes problems because it does not co-exist with the
"depends on" syntax.  (Please note this is not a bug of Kconfig.)
We should not do so unless we have a special reason.  Actually,
for CONFIG_DM*, we have no good reason to do so.

Generally, CONFIG_DM is not a user-configurable option.  Once we
convert a driver into Driver Model, the board only works with Driver
Model, i.e. CONFIG_DM must be always enabled for that board.
So, using "select DM" is more suitable rather than allowing users to
modify it.  Another good thing is, Kconfig warns unmet dependencies
for "select" syntax, so we easily notice bugs.

Actually, CONFIG_DM and other related options have been added
without consistency: some into arch/*/Kconfig, some into
board/*/Kconfig, and some into configs/*_defconfig.

This commit prefers "select" and cleans up the following issues.

[1] Never use "CONFIG_DM=n" in defconfig files

It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
It is more common to use "# CONFIG_FOO is not set".  But here, we
do not even have to do it.
Less than half of OMAP3 boards have been converted to Driver Model.
Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
weird.  Instead, add "select DM" only to appropriate boards, which
eventually eliminates "CONFIG_DM=n", etc.

[2] Delete redundant CONFIGs

Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
in configs/sandbox_defconfig.
Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
defines it also in omap3_beagle_defconfig and devkit8000_defconfig.

Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
</content>
</entry>
</feed>
