public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: EHCI on 2.6.32-rc5-git4 + patches
Date: Sat, 31 Oct 2009 23:41:40 +0000	[thread overview]
Message-ID: <4AECCB34.9010003@blueyonder.co.uk> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0309C86298@dbde02.ent.ti.com>

On 31/10/09 17:08, Gadiyar, Anand wrote:
> Sid Boyce wrote:
>> There is no way to configure EHCI on beagleboard, so my devices are
>> never seen. Only OHCI has ARCH_ARM as a config option.
>> I shall edit it into drivers/usb/Kconfig and see if it works.
> 
> drivers/usb/Kconfig looks okay to me.
> 
> <http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=blob;f=drivers/usb/Kconfig;h=5620e924a218da2bc5e03124934f339095dd18da;hb=HEAD>
> 
> See line 63 - it says USB_ARCH_HAS_EHCI is y if ARCH_OMAP34XX
> 
> - Anand
> 
> 
> 
> 

I am tried "beagleboard_defconfig" I downloaded, but when the .config
was written at the start of the kernel build ....
# CONFIG_USB_ARCH_HAS_EHCI is not set.
" make CROSS_COMPILE=/opt/arm-2009q1/bin/arm-none-linux-gnueabi-" on
Fedora 12.
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


  reply	other threads:[~2009-10-31 23:41 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 [this message]
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
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=4AECCB34.9010003@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.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