From: Sid Boyce <sboyce@blueyonder.co.uk>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Is the OMAP patch process badly flawed?
Date: Tue, 17 Nov 2009 21:44:34 +0000 [thread overview]
Message-ID: <4B031942.5020106@blueyonder.co.uk> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB030A8C916A@dbde02.ent.ti.com>
On 17/11/09 14:51, Gadiyar, Anand wrote:
> Sid Boyce wrote:
>
> <snip>
>
>>>>
>>>> I would expect patches sent upstream would result in all the basics for
>>>> long established platforms to be fully covered. Appreciating that
>>>> development is quite fast paced with mods and supporting new platforms.
>>>> Could someone please enlighten me?
>>>
>>> Sid,
>>>
>>> Speaking purely for EHCI, this is now queued up in Greg's USB queue
>>> for upstream and will get merged in the next cycle.
>>>
>>> Until then, the linux-omap code does have working EHCI support
>>> on beagle, evm and the other boards. If you're cloning from
>>> gitorious, you're probably picking the wrong tree.
>>>
>>> - Anand
>>>
>>>
>>
>> Thanks, that explains a lot as I can't remember seeing those patches on
>> the linux-usb list for submission upstream.
>> What tree is best to clone?
>
>
> Not sure which is best - I suppose that depends on what all you need.
> The canonical linux-omap tree maintained by Tony is at [1].
>
> For EHCI, Felipe sent the driver to Greg who queued it up for .33 [2].
> Tony lined up the board files and mach-omap2/usb-ehci.c in the for-next
> branch.
>
>
>
> [1] git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
> [2] http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-07-usb-2.6.32-rc6.patch
>
>
Thanks for the update and the patch. I downloaded the launchpad 2.6.31
kernel which I have currently running. Finally found one that outputs to
the LCD.
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-17 21:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 5:04 linux-next: manual merge of the omap_dss2 tree with the omap tree Stephen Rothwell
2009-11-16 5:04 ` Stephen Rothwell
2009-11-16 10:06 ` Tomi Valkeinen
2009-11-16 18:34 ` Tony Lindgren
2009-11-17 10:00 ` Tomi Valkeinen
2009-11-17 23:49 ` Stephen Rothwell
2009-11-17 3:08 ` Sid Boyce
2009-11-17 13:30 ` Is the OMAP patch process badly flawed? Sid Boyce
2009-11-17 13:34 ` Gadiyar, Anand
2009-11-17 14:00 ` Sid Boyce
2009-11-17 14:51 ` Gadiyar, Anand
2009-11-17 21:44 ` Sid Boyce [this message]
2009-11-17 22:07 ` Felipe Contreras
2009-11-18 3:20 ` 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=4B031942.5020106@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--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 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.