From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/7 v2] OMAP3: Add OMAP3 core changes for MUSB
Date: Wed, 11 Mar 2009 19:25:32 +0100 [thread overview]
Message-ID: <49B8021C.8080402@googlemail.com> (raw)
In-Reply-To: <20090311144615.GE12700@game.jcrosoft.org>
Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 19:55 Thu 12 Feb , Dirk Behme wrote:
>> OMAP3 core changes necessary for MUSB
>>
>> Signed-off-by: Dirk Behme <dirk.behme@googlemail.com>
>>
>> ---
> will you send a new version soon or this will wait the next release?
The developers which did the initial MUSB support for OMAP3/Beagle on
the Beagle specific "omap3-dev-usb" git branch [1] are busy at the
moment. I had a short discussion with them. I'd like to have the clock
changes discussed here to be tested first at Beagle specific U-Boot
branch/tree [1] before we extract them to send them to this list. In
short, this will be waiting for next release. Hopefully we have a
tested version then.
For the die ID (former serial number) patch [2] I will send an update
with better commit message as requested by Wolfgang, soon (weekend?).
Hopefully this will still be merged then in this release (?).
Do you agree to this way to go?
Dirk
[1]
http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=shortlog;h=refs/heads/omap3-dev-usb
[2] http://lists.denx.de/pipermail/u-boot/2009-March/048847.html
next prev parent reply other threads:[~2009-03-11 18:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 18:55 [U-Boot] [PATCH 0/7 v2] OMAP3: Add some additional improvements and fixes Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 1/7 v2] OMAP3: Overo: Clean up pin mux and GPIO configuration Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 2/7 v2] OMAP3: Beagle: Add board revision detection Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 3/7 v2] OMAP3: Add OMAP3 auto detection Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 4/7 v2] OMAP3: Pandora: Update pin mux Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 5/7 v2] OMAP3: Add serial number based on die ID Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 6/7 v2] OMAP3: Add OMAP3 core changes for MUSB Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 7/7 v2] OMAP3: Clean up MMC code Dirk Behme
2009-02-22 15:59 ` [U-Boot] [PATCH 6/7 v2] OMAP3: Add OMAP3 core changes for MUSB Jean-Christophe PLAGNIOL-VILLARD
2009-02-22 16:22 ` Dirk Behme
2009-02-23 12:13 ` Grazvydas Ignotas
2009-02-23 12:30 ` Nishanth Menon
2009-02-23 19:31 ` Dirk Behme
2009-02-23 21:36 ` Wolfgang Denk
2009-02-23 23:03 ` [U-Boot] Clock handling (wasRe: [PATCH 6/7 v2] OMAP3: Add OMAP3 core changes for MUSB) Nishanth Menon
2009-02-24 17:01 ` Dirk Behme
2009-02-24 17:01 ` [U-Boot] [PATCH 6/7 v2] OMAP3: Add OMAP3 core changes for MUSB Dirk Behme
2009-02-24 21:22 ` Wolfgang Denk
2009-02-25 17:39 ` Dirk Behme
2009-03-01 14:26 ` Dirk Behme
2009-03-01 19:18 ` Wolfgang Denk
2009-03-11 14:46 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-11 18:25 ` Dirk Behme [this message]
2009-03-11 18:44 ` Wolfgang Denk
2009-02-22 16:01 ` [U-Boot] [PATCH 5/7 v2] OMAP3: Add serial number based on die ID Jean-Christophe PLAGNIOL-VILLARD
2009-02-22 16:40 ` Dirk Behme
2009-02-22 21:44 ` Wolfgang Denk
2009-03-01 14:20 ` Dirk Behme
2009-03-01 18:57 ` Wolfgang Denk
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=49B8021C.8080402@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=u-boot@lists.denx.de \
/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