From: Jeroen Hofstee <dasuboot@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 02/14] ARM: zynq: Remove CONFIG_API
Date: Thu, 3 Dec 2015 18:57:33 +0100 [thread overview]
Message-ID: <5660828D.30903@myspectrum.nl> (raw)
In-Reply-To: <CAD6G_RTUZmMFteGFvuaqixtWCJFe_jYRgDhrBV73P08+8-c37w@mail.gmail.com>
Hi,
On 03-12-15 17:09, Jagan Teki wrote:
> On 3 December 2015 at 20:17, Michal Simek <michal.simek@xilinx.com> wrote:
>> CONFIG_API is causing compilation error when DM_ETH is enabled because
>> eth_get_dev() is not available.
> Then how come, freebsd elf generate w/o CONFIG_API?
>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>> ---
>>
>> Changes in v3: None
>> Changes in v2: None
>>
>> include/configs/zynq-common.h | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/include/configs/zynq-common.h b/include/configs/zynq-common.h
>> index a9e6bf046a97..5db501188b18 100644
>> --- a/include/configs/zynq-common.h
>> +++ b/include/configs/zynq-common.h
>> @@ -297,7 +297,6 @@
>>
>> /* Boot FreeBSD/vxWorks from an ELF image */
>> #if defined(CONFIG_ZYNQ_BOOT_FREEBSD)
>> -# define CONFIG_API
>> # define CONFIG_SYS_MMC_MAX_DEVICE 1
>> #endif
>>
>
FreeBSD boot relies on CONFIG_API. Removing it will brick FreeBSD boots....
Regards,
Jeroen
next prev parent reply other threads:[~2015-12-03 17:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 14:47 [U-Boot] [PATCH v3 01/14] ARM: zynq: Remove PHYLIB from config to defconfig Michal Simek
2015-12-03 14:47 ` [U-Boot] [PATCH v3 02/14] ARM: zynq: Remove CONFIG_API Michal Simek
2015-12-03 16:09 ` Jagan Teki
2015-12-03 17:57 ` Jeroen Hofstee [this message]
2015-12-04 8:20 ` Michal Simek
2015-12-04 8:33 ` Jagan Teki
2015-12-04 7:47 ` Michal Simek
2015-12-03 14:47 ` [U-Boot] [PATCH v3 03/14] net: gem: Do not continue if phy is not found Michal Simek
2015-12-03 16:23 ` Jagan Teki
2015-12-03 14:47 ` [U-Boot] [PATCH v3 04/14] net: gem: Change mdio_wait prototype to pass regs Michal Simek
2015-12-03 14:47 ` [U-Boot] [PATCH v3 05/14] net: gem: Change mii function not to use eth_device structure Michal Simek
2015-12-03 14:47 ` [U-Boot] [PATCH v3 06/14] net: gem: Remove phydev variable Michal Simek
2015-12-03 14:47 ` [U-Boot] [PATCH v3 07/14] net: gem: Extract phy init code Michal Simek
2015-12-03 14:47 ` [U-Boot] [PATCH v3 08/14] net: gem: Check if priv->phydev is valid Michal Simek
2015-12-03 16:24 ` Jagan Teki
2015-12-03 14:47 ` [U-Boot] [PATCH v3 09/14] net: gem: Enable MDIO bus earlier Michal Simek
2015-12-03 14:47 ` [U-Boot] [PATCH v3 10/14] net: gem: Remove zynq_gem_of_init() Michal Simek
2015-12-03 16:24 ` Jagan Teki
2015-12-03 14:47 ` [U-Boot] [PATCH v3 11/14] net: gem: Fix miiphy_read name Michal Simek
2015-12-03 16:25 ` Jagan Teki
2015-12-03 14:48 ` [U-Boot] [PATCH v3 12/14] net: gem: Move driver to DM Michal Simek
2015-12-03 16:16 ` Jagan Teki
2015-12-03 18:57 ` Simon Glass
2015-12-03 19:00 ` Joe Hershberger
2015-12-03 19:04 ` Simon Glass
2015-12-04 6:24 ` Bin Meng
2015-12-03 14:48 ` [U-Boot] [PATCH v3 13/14] net: gem: Read information about interface from DT Michal Simek
2015-12-03 16:21 ` Jagan Teki
2015-12-03 14:48 ` [U-Boot] [PATCH v3 14/14] net: gem: Move gem to Kconfig Michal Simek
2015-12-03 16:19 ` Jagan Teki
2015-12-03 16:11 ` [U-Boot] [PATCH v3 01/14] ARM: zynq: Remove PHYLIB from config to defconfig Jagan Teki
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=5660828D.30903@myspectrum.nl \
--to=dasuboot@myspectrum.nl \
--cc=u-boot@lists.denx.de \
/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