Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Basic rk3288 usb support
Date: Thu, 31 Jul 2014 07:14:08 +0200	[thread overview]
Message-ID: <3299271.Yo7kjNWRH9@diego> (raw)
In-Reply-To: <CAOesGMimqXVPMhM3-GPK4fTUuFfNUP09YHC+ORD98=115uyr3A@mail.gmail.com>

Am Mittwoch, 30. Juli 2014, 22:05:50 schrieb Olof Johansson:
> [adding LAKML which you seem to have missed in your pull request]

damn ... included maybe interested parties, but forgot the list, very bad 
trade ... sorry about that

> 
> On Wed, Jul 30, 2014 at 9:58 PM, Heiko St?bner <heiko@sntech.de> wrote:
> > Hi Arnd, Olof,
> > 
> > thanks to Doug and Kever, the rk3288 devboard can get basic ehci support
> > with just some minor dts modifications, so maybe you could pull on top of
> > the previous tag:
> > 
> > The following changes since commit 
b1db66b818a4cb1a654ae51a5ca32a09d1ccd825:
> >   ARM: dts: Build dtbs for Rockchip boards (2014-07-26 13:07:27 +0200)
> > 
> > are available in the git repository at:
> >   git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git
> >   tags/v3.17-rockchip-rk3288-2> 
> > for you to fetch changes up to 163cb917b836184c42f185b8fbd9185e20c5f499:
> >   ARM: dts: Enable USB host0 (EHCI) on rk3288-evb (2014-07-31 05:35:38
> >   +0200)
> 
> It's really late in the cycle, but this is a minor increment on top of
> an otherwise new platform, so that's OK with me.
> 
> Merged. With this I should be able to get my board up and going in the
> boot farm sometime next week.

I'm currently looking at what happens with multi_v7_defconfig ... something 
seems fishy there.


Heiko

      reply	other threads:[~2014-07-31  5:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3117047.MiGWvobrqb@diego>
2014-07-31  5:05 ` [GIT PULL] Basic rk3288 usb support Olof Johansson
2014-07-31  5:14   ` Heiko Stübner [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=3299271.Yo7kjNWRH9@diego \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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