All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Sid Boyce <sboyce@blueyonder.co.uk>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: What's in omap git tree for 2.6.33
Date: Mon, 7 Dec 2009 09:58:55 -0800	[thread overview]
Message-ID: <20091207175855.GB24013@atomide.com> (raw)
In-Reply-To: <4B1CE04F.5000806@blueyonder.co.uk>

* Sid Boyce <sboyce@blueyonder.co.uk> [091207 02:59]:
> On 06/12/09 03:37, Gadiyar, Anand wrote:
> > Sid Boyce wrote:
> >> Still a few fragments missing on beagleboard - Very roughly:
> >> drivers/usb/Kconfig
> >> +       default y if ARCH_OMAP34X
> > 
> > 
> > This one's in Greg's queue for sure.
> > 
> > <http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/usb/usb-ehci-allow-ehci-to-be-built-on-omap3.patch>
> > 
> > And I did point out the other one. Olaf sent a patch too.
> > We can get that in during the merge window, or right after.
> > 
> > So, wait up for -rc1 to be tagged.
> > 
> > - Anand
> > 
> > 
> 
> That's one bit, but with EHCI an integral part of the beagleboard, there
> shouldn't be a need to hunt around for patches as without this support
> it limits what you can do. OTG with the solder bridge couldn't see any
> of my USB hubs, so I had to rely on the EHCI.

Right. Sounds like we should have omap EHCI working by -rc1 with
these fixes.

Regards,

Tony

      reply	other threads:[~2009-12-07 17:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 18:26 What's in omap git tree for 2.6.33 Tony Lindgren
2009-12-04 18:26 ` Tony Lindgren
2009-12-06  3:15 ` Sid Boyce
2009-12-06  3:37   ` Gadiyar, Anand
2009-12-07 11:00     ` Sid Boyce
2009-12-07 17:58       ` Tony Lindgren [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=20091207175855.GB24013@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=sboyce@blueyonder.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.