From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] board/p2020rdb: fix the FDT_ERR_NOTFOUND issue
Date: Fri, 17 Apr 2015 10:45:11 -0700 [thread overview]
Message-ID: <553146A7.50307@freescale.com> (raw)
In-Reply-To: <1427183322-25911-1-git-send-email-ying.zhang@freescale.com>
On 03/24/2015 12:48 AM, ying.zhang at freescale.com wrote:
> From: Ying Zhang <b40530@freescale.com>
>
> Because the function ft_board_setup() delete the USB2 device node, it
> leads to can't find the device node and hung up.
>
> In fact only P1020RDB needs to delete the USB2 node, this patch fixes
> this issue.
>
> Signed-off-by: Ying Zhang <b40530@freescale.com>
> ---
> board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c b/board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c
> index 3f47cfb..0c60fc3 100644
> --- a/board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c
> +++ b/board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c
> @@ -428,8 +428,10 @@ int ft_board_setup(void *blob, bd_t *bd)
> {
> phys_addr_t base;
> phys_size_t size;
> +#if defined(CONFIG_P1020RDB_PD) || defined(CONFIG_P1020RDB_PC)
> const char *soc_usb_compat = "fsl-usb2-dr";
> int err, usb1_off, usb2_off;
> +#endif
"err" is used elsewhere. Your change causes compiling error on these boards
P1025RDB_SDCARD P2020RDB-PC_36BIT_SPIFLASH P1021RDB-PC_36BIT_SPIFLASH
P2020RDB-PC_SPIFLASH P1020MBG-PC_36BIT_SDCARD P1024RDB_SPIFLASH
P1021RDB-PC_SPIFLASH P1020MBG-PC_SDCARD P2020RDB-PC_36BIT_SDCARD
P1021RDB-PC_SDCARD P2020RDB-PC_SDCARD P1024RDB_SDCARD P1025RDB_SPIFLASH
P1020UTM-PC_36BIT_SDCARD P1021RDB-PC_36BIT_SDCARD P1020UTM-PC_SDCARD
York
prev parent reply other threads:[~2015-04-17 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 7:48 [U-Boot] [PATCH] board/p2020rdb: fix the FDT_ERR_NOTFOUND issue ying.zhang at freescale.com
2015-04-17 17:45 ` York Sun [this message]
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=553146A7.50307@freescale.com \
--to=yorksun@freescale.com \
--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 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.