[U-Boot] [PATCH v2 4/4] rockchip: enable rockusb for all rockchip SoCs

[Tom Rini]

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 at gmail.com> wrote:
> >>>>
> >>>>Hi Lukasz:
> >>>>
> >>>>2017-08-22 18:05 GMT+08:00 Łukasz Majewski <lukma at denx.de <mailto:lukma at 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>