public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V7 4/4] rockchip: rk3288: enable rockusb support on rk3288 based device
Date: Fri, 30 Jun 2017 10:15:30 +0200	[thread overview]
Message-ID: <20170630101530.78ab1406@jawa> (raw)
In-Reply-To: <CAJrj+DP16YbG1mQ3EWgG=RB4XHv=Ci0dHt+wx+9DMB_9ZOzhAg@mail.gmail.com>

Hi Eddie,

> 2017-06-29 18:49 GMT+08:00 Lukasz Majewski <lukma@denx.de>:
> > On Thu, 29 Jun 2017 08:44:47 +0800
> > Eddie Cai <eddie.cai.linux@gmail.com> wrote:
> >
> >> >
> >> > The issue is not with this one particular board.
> >> >
> >> > I'm concerned, since your patch set causes build errors for other
> >> > boards.
> >> >
> >> > Can you build test (with travis-CI) your patches and check if you
> >> > can reproduce those errors?
> >> I can reproduce this error with travis-CI. but i can't not
> >> reproduce this rk3036 board error on my desktop.
> >> can you try to local build rk3036 board and see if can reproduce
> >> this error?
> >> >
> >  The rk3036 (evb-rk3036_defconfig) builds fine (with my old 4.8
> > gcc).
> >
> > However, your patches cause other issues [1]:
> > https://travis-ci.org/lmajewski/u-boot-dfu/jobs/248264628
> >
> > And for example I can reproduce the issue on
> > rock2_defconfig at my local PC.
> >
> > Can you build rock2 on your PC with your patches applied without any
> > issues?
> I reproduced and fixed this issue long time ago. I didn't send my
> next version because i don't know how to reproduce 3036 issue. It
> looks like 3036 work fine on your side now. Can i ignore this 3036
> issue?

Please before posting next version make sure that no build breaks
shows up in TravisCI.

Please as a reference use mainline .travis.yml. (especially build for
rockchip)

Please let me know if you need any assistance at fixing problems.

> >
> >
> >
> >
> >
> > [1] The "testing" tree can be found at:
> > https://github.com/lmajewski/u-boot-dfu/tree/testing
> >
> > Best regards,
> >
> > Lukasz Majewski
> >
> > --
> >
> > DENX Software Engineering GmbH,      Managing Director: Wolfgang
> > Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell,
> > Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email:
> > wd at denx.de




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de

      reply	other threads:[~2017-06-30  8:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25  8:50 [U-Boot] [PATCH V7 0/4] introduce Rockchip rockusb Eddie Cai
2017-05-25  8:50 ` [U-Boot] [PATCH V7 1/4] usb: rockchip: add the rockusb gadget Eddie Cai
2017-05-25  8:50 ` [U-Boot] [PATCH V7 2/4] usb: rockchip: add rockusb command Eddie Cai
2017-05-25  8:50 ` [U-Boot] [PATCH V7 3/4] rockchip:usb: add a simple readme for rockusb Eddie Cai
2017-05-25  8:50 ` [U-Boot] [PATCH V7 4/4] rockchip: rk3288: enable rockusb support on rk3288 based device Eddie Cai
2017-05-29  7:51   ` Lukasz Majewski
2017-05-31  2:27     ` Eddie Cai
2017-05-31  2:30       ` Tom Rini
2017-05-31  7:12       ` Lukasz Majewski
2017-05-31  8:02         ` Eddie Cai
2017-05-31  8:18           ` Lukasz Majewski
2017-05-31  8:22             ` Lukasz Majewski
2017-05-31  8:41               ` Eddie Cai
2017-05-31  8:43                 ` Eddie Cai
2017-06-03 14:23           ` Lukasz Majewski
2017-06-21  7:44             ` Lukasz Majewski
2017-06-28  7:33               ` Eddie Cai
2017-06-28  7:55                 ` Lukasz Majewski
2017-06-29  0:44                   ` Eddie Cai
2017-06-29 10:49                     ` Lukasz Majewski
2017-06-30  3:38                       ` Eddie Cai
2017-06-30  8:15                         ` Lukasz Majewski [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=20170630101530.78ab1406@jawa \
    --to=lukma@denx.de \
    --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