From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Sun, 27 Aug 2017 13:02:59 -0400 Subject: [U-Boot] [PATCH v2 4/4] rockchip: enable rockusb for all rockchip SoCs In-Reply-To: <814bb51c-6f45-8b57-9cfd-6c882183f583@denx.de> References: <1503387300-1759-1-git-send-email-kever.yang@rock-chips.com> <1503387300-1759-4-git-send-email-kever.yang@rock-chips.com> <4D5E4692-551C-4DE8-95E1-D4597855FCF7@theobroma-systems.com> <23abf202-d4fa-1568-5911-f6522991d9ae@rock-chips.com> <4b6b4a84-b90f-ce78-999d-d93354fe8648@denx.de> <677B34F6-1941-4668-A280-1F6027441F77@theobroma-systems.com> <120a4a7d-9014-e386-2294-77a9b14e9cf1@denx.de> <20170826124659.GQ2827@bill-the-cat> <814bb51c-6f45-8b57-9cfd-6c882183f583@denx.de> Message-ID: <20170827170259.GA17058@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: u-boot@lists.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 wrote: > >>>> > >>>>Hi Lukasz: > >>>> > >>>>2017-08-22 18:05 GMT+08:00 Łukasz Majewski >: > >>>>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: