From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 4/4] rockchip: enable rockusb for all rockchip SoCs
Date: Sun, 27 Aug 2017 13:02:59 -0400 [thread overview]
Message-ID: <20170827170259.GA17058@bill-the-cat> (raw)
In-Reply-To: <814bb51c-6f45-8b57-9cfd-6c882183f583@denx.de>
On Sat, Aug 26, 2017 at 07:28:05PM +0200, Łukasz Majewski wrote:
> On 08/26/2017 02:46 PM, Tom Rini wrote:
> >On Fri, Aug 25, 2017 at 01:06:55PM +0200, Łukasz Majewski wrote:
> >>Hi Philipp, Andy, Tom
> >>>
> >>>>On 25 Aug 2017, at 03:51, Andy Yan <andyshrk@gmail.com> wrote:
> >>>>
> >>>>Hi Lukasz:
> >>>>
> >>>>2017-08-22 18:05 GMT+08:00 Łukasz Majewski <lukma at denx.de <mailto:lukma@denx.de>>:
> >>>>Hi Kever,
> >>>>
> >>>>
> >>>>Philipp,
> >>>>
> >>>> I have no idea about the status of rockusb, it has been a long time
> >>>>on the list.
> >>>>
> >>>>Maybe Eddie or Lukasz have an answer?
> >>>>
> >>>>I've asked Eddie to fix issues with breaking other boards when enabling USB gadget infrastructure on RK.
> >>>>
> >>>>No reply since then.
> >>>>
> >>>>
> >>>>
> >>>>Eddie has fix all the issues he can reproduced on local。 The only problem now is that the rk3036 based boards(evb-rk3036/kylin-rk3036) show compile errors on CI[0],
> >>>
> >>>The Travis log shows linker errors for some of the other boards (i.e. not evb-rk3036/kylin-rk3036), due to unresolved symbols.
> >>
> >>Yes, Indeed.
> >>
> >>I've build those boards locally with gcc 6.3 and it was successful.
> >
> >The same one we use in travis-ci, from Linaro?
>
> I've been using some OE build from yocto 2.3 SDK.
>
> I will try to use the one from Linaro.
Thanks.
> >>Regarding travis CI:
> >>
> >>With Eddie's patches it shows error:
> >>https://travis-ci.org/lmajewski/u-boot-dfu/builds/268270904
> >>
> >>However, without Eddie's patches travis-CI doesn't show any errors:
> >>https://travis-ci.org/lmajewski/u-boot-dfu/builds/268303030
> >>
> >>
> >>Let's ask Tom (who has far more experience with travis-CI), if he
> >>saw something like that before.
> >
> >Well, travis talks about using docker to replicate their environment,
> >which means someone should be able to do that, get it to fail in a
> >debugable environment and then move forward.
>
> From the sentence it seems like travis-ci is going to use docker. Is
> it correct?
>
> Is it now possible to download the docker container for build testing?
I don't have the link off-hand, but in part of the "debugging travis
build failures" pages travis-ci has, it talks about how to re-create the
build environment using Docker.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170827/f654e69a/attachment.sig>
next prev parent reply other threads:[~2017-08-27 17:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 7:34 [U-Boot] [PATCH v2 1/4] rockchip: rk3229: move usb gadget into defconfig Kever Yang
2017-08-22 7:34 ` [U-Boot] [PATCH v2 2/4] rockchip: rk322x: update the sysreg number for boot mode Kever Yang
2017-09-12 19:55 ` [U-Boot] [U-Boot, v2, " Philipp Tomsich
2017-09-29 16:44 ` Philipp Tomsich
2017-08-22 7:34 ` [U-Boot] [PATCH v2 3/4] rockchip: add BOOT_LOADER support " Kever Yang
2017-09-12 16:17 ` [U-Boot] [U-Boot, v2, " Philipp Tomsich
2017-08-22 7:35 ` [U-Boot] [PATCH v2 4/4] rockchip: enable rockusb for all rockchip SoCs Kever Yang
2017-08-22 8:44 ` Dr. Philipp Tomsich
2017-08-22 9:36 ` Kever Yang
2017-08-22 10:05 ` Łukasz Majewski
2017-08-25 1:51 ` Andy Yan
2017-08-25 9:50 ` Dr. Philipp Tomsich
2017-08-25 11:06 ` Łukasz Majewski
2017-08-26 11:10 ` Łukasz Majewski
2017-08-26 12:46 ` Tom Rini
2017-08-26 17:28 ` Łukasz Majewski
2017-08-27 17:02 ` Tom Rini [this message]
2017-08-22 9:37 ` Kever Yang
2017-09-12 19:55 ` [U-Boot] [U-Boot, v2, " Philipp Tomsich
2017-09-12 19:55 ` [U-Boot] [U-Boot, v2, 1/4] rockchip: rk3229: move usb gadget into defconfig Philipp Tomsich
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=20170827170259.GA17058@bill-the-cat \
--to=trini@konsulko.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