From: Sid Boyce <sboyce@blueyonder.co.uk>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: EHCI on 2.6.32-rc5-git4 + patches
Date: Tue, 03 Nov 2009 20:35:15 +0000 [thread overview]
Message-ID: <4AF09403.8080300@blueyonder.co.uk> (raw)
In-Reply-To: <4551feaf0911021728s6587dffchd716ff1241b0373b@mail.gmail.com>
On 03/11/09 01:28, Robert Nelson wrote:
>> I tried that and various others to get other than the hub enumerated, no
>> luck so far with kernels I have built - no lights on the hub. I am now
>> rebuilding after following the config for the working narcissus build,
>> EHCI looks much the same, so here's hoping.
>> I have another 16G MMC card I am trying on after cross compiling on a
>> Fedora 12 VirtualBox VM.
>> Regards
>> Sid.
>
> Hi Sid
>
> I eventually got ehci working today on my tree on launchpad. But it's
> not that small of a patch once i added all the mach to plat changes...
>
> However, this commit made all the difference for me, it's currently
> missing from tmlind's tree, the beagleboard needs it to enable power
> to the ehci..
>
> http://patchwork.kernel.org/patch/55703/
>
> Regards,
Thanks, I shall give it a try.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next prev parent reply other threads:[~2009-11-03 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 15:14 EHCI on 2.6.32-rc5-git4 + patches Sid Boyce
2009-10-31 17:08 ` Gadiyar, Anand
2009-10-31 23:41 ` Sid Boyce
2009-11-01 15:42 ` Robert Nelson
2009-11-01 23:29 ` Sid Boyce
2009-11-02 7:04 ` Felipe Balbi
2009-11-03 1:08 ` Sid Boyce
2009-11-03 1:28 ` Robert Nelson
2009-11-03 20:35 ` Sid Boyce [this message]
2009-11-04 0:36 ` Sid Boyce
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=4AF09403.8080300@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.com \
/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