public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ls1:config: Add USB support for ls1021atwr
Date: Wed, 14 Jan 2015 10:46:23 -0800	[thread overview]
Message-ID: <54B6B97F.3000808@freescale.com> (raw)
In-Reply-To: <54920CD0.3020708@freescale.com>



On 12/17/2014 03:08 PM, York Sun wrote:
> On 10/21/2014 04:36 AM, Ramneek Mehresh wrote:
>> Add USB EHCI/XHCI support for ls1021atwr platform and
>> making xHCI as default mode
>>
>> Signed-off-by: Ramneek Mehresh <ramneek.mehresh@freescale.com>
>> ---
>>  include/configs/ls1021atwr.h | 28 ++++++++++++++++++++++++++++
>>  1 file changed, 28 insertions(+)
>>
> 
> Please verify this patch on the latest u-boot. I saw compiling errors.
> 

Please fix. This patch cause compiling errors on all ls1021atwr boards. If this
patch depends on other patches, please put into comment so I can apply them in
order.


+drivers/usb/host/built-in.o: In function `usb_lowlevel_init':
+drivers/usb/host/xhci.c:948: undefined reference to `xhci_hcd_init'
+drivers/usb/host/built-in.o: In function `usb_lowlevel_stop':
+drivers/usb/host/xhci.c:1025: undefined reference to `xhci_hcd_stop'
+arm-linux-gnueabi-ld.bfd: BFD (GNU Binutils for Ubuntu) 2.22 assertion fail
../../bfd/elf32-arm.c:7498
+arm-linux-gnueabi-ld.bfd: BFD (GNU Binutils for Ubuntu) 2.22 assertion fail
../../bfd/elf32-arm.c:13830
+make[1]: *** [u-boot] Error 139
+make: *** [sub-make] Error 2

York

  reply	other threads:[~2015-01-14 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 11:36 [U-Boot] [PATCH] ls1:config: Add USB support for ls1021atwr Ramneek Mehresh
2014-10-21 11:36 ` [U-Boot] [PATCH] ls1:config: Add XHCI support for ls1021aqds Ramneek Mehresh
2014-12-17 23:07   ` York Sun
2014-12-17 23:08 ` [U-Boot] [PATCH] ls1:config: Add USB support for ls1021atwr York Sun
2015-01-14 18:46   ` York Sun [this message]
2015-01-15  4:47     ` Ramneek Mehresh

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=54B6B97F.3000808@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox