From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP3: Pending patches
Date: Tue, 28 Apr 2009 16:52:30 +0200 [thread overview]
Message-ID: <49F7182E.5040106@googlemail.com> (raw)
In-Reply-To: <20090427220254.B410883420E8@gemini.denx.de>
Dear Wolfgang,
Wolfgang Denk wrote:
> Dear Dirk,
>
> In message <49F5C746.6040204@googlemail.com> you wrote:
>> Short status update after recent merges and patch updates. As usual,
>> please correct if anything is wrong or missing.
>
> Thanks for the summary.
>
>> Dirk Behme wrote:
>>> To avoid loosing the overview, here my list of pending OMAP3 patches
>>> ready to be applied. From my point of view there are no open comments on
>>> these which will prevent to apply them. But please correct if I
>>> overlooked anything or add what (patches? comments?) I missed.
>>>
>>> 1. OMAP3: Beagle: Set pinmux conditionally for Rev C boards
>>> http://lists.denx.de/pipermail/u-boot/2009-April/051013.html
>> Mail
>>
>> http://lists.denx.de/pipermail/u-boot/2009-April/051459.html
>>
>> tells us that this should be applied to u-boot-arm next. But I can't
>> find it in gitweb
>>
>> http://git.denx.de/?p=u-boot/u-boot-arm.git;a=shortlog;h=refs/heads/next
>>
>> Did I miss something?
>
> I cannot find it either.
:(
>> Btw.: As initial patch and first update was sent ~1 day after merge
>> window close (Apr 4?) I hoped to have a chance to still get it into
>> master ;(
>
> We don't have to bend much to consider this even a bug fix (it fixes a
> specific board configuration, doesn't it?).
Yes. We got a new board HW revision ('revision C', with some
re-wiring) which needs some minor changes in PinMux to support this
changed wiring. Thanks to a HW identification (resistors on GPIOs) we
are able to auto detect HW revision and configure correct pin mux
automagically. This is done by this patch.
>>> 2. OMAP3: Remove legacy NAND defines
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050882.html
>> Applied to u-boot-arm next. Request to move to master by Wolfgang.
>>
>>> 3. OMAP3: Fix timer handling to 1ms and CONFIG_SYS_HZ to 1000
>>> http://lists.denx.de/pipermail/u-boot/2009-April/051178.html
>>>
>>> 4. OMAP3: Fix changed mmc init command
>>> http://lists.denx.de/pipermail/u-boot/2009-April/051179.html
>> Applied to u-boot-arm master.
>>
>>> 5. OMAP3: Remove unused board-types
>>> http://lists.denx.de/pipermail/u-boot/2009-April/051338.html
>>>
>>> 6. OMAP3: Print correct silicon revision
>>> http://lists.denx.de/pipermail/u-boot/2009-April/051339.html
>> Patches 5 & 6 replaced by update which includes switch to checkboard
>> and print_cpuinfo:
>>
>> OMAP3: Board specific updates (3 patches)
>> http://lists.denx.de/pipermail/u-boot/2009-April/051505.html
>> http://lists.denx.de/pipermail/u-boot/2009-April/051506.html
>> http://lists.denx.de/pipermail/u-boot/2009-April/051507.html
>>
>>> 7. Zoom2 respin II (10 patches)
>> Note: Initial patch series for this was sent 'Wed Apr 1 18:08:38 CEST
>> 2009'
>>
>> http://lists.denx.de/pipermail/u-boot/2009-April/050094.html
>>
>> IMHO this was while open merge window.
>>
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050863.html
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050864.html
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050865.html
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050866.html
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050868.html
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050867.html
>> Applied to u-boot-arm next (see comment about merge window above).
>>
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050869.html
>> Applied to u-boot-arm next (see comment about merge window above).
>>
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050870.html
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050871.html
>> Applied to u-boot-arm next. Request to move to master by Wolfgang.
>
>
> I think all the patches listed above could and should go into master
> now.
>
> Jean-Cristophe, what do you think? Do you have any specific reasons
> for not pulling these into master now?
>
>>> http://lists.denx.de/pipermail/u-boot/2009-April/050872.html
>> For the rest of the Zoom2 patches (#1, #2, #3, #4, #5, #8 & #10)
>>
>> http://lists.denx.de/pipermail/u-boot/2009-April/051383.html
>> http://lists.denx.de/pipermail/u-boot/2009-April/051384.html
>> http://lists.denx.de/pipermail/u-boot/2009-April/051385.html
>> http://lists.denx.de/pipermail/u-boot/2009-April/051386.html
>> http://lists.denx.de/pipermail/u-boot/2009-April/051455.html
>>
>> seem to apply.
>
> I'm not sure what you mean here, Dirk.
I tried to say that for patches #1, #2, #3, #4, #5, #8 & #10 there are
comments in the 5 mails linked above (i.e. the comments in the 5 mails
above apply to the patches #1, #2, #3, #4, #5, #8 & #10).
> I understand that
> Jean-Cristophe requested changes,
Yes.
> and we're waiting for a resubmit,
> right?
Well, before waiting for a resubmit, I would wait for a comment
(discussion?) from the patch author (Tom).
Anyhow, seems we got a comment from Tom
http://lists.denx.de/pipermail/u-boot/2009-April/051605.html
and _now_ we are waiting for a resubmit ;)
> Jean-Cristophe, I really would like to see some progress in this
> area, so I'd appreciate if you could apply the patches listed above
> to master and send me a pull request. Thanks.
Many thanks for helping and best regards
Dirk
next prev parent reply other threads:[~2009-04-28 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 20:32 [U-Boot] OMAP3: Pending patches Dirk Behme
2009-04-25 5:35 ` Dirk Behme
2009-04-25 22:11 ` Premi, Sanjeev
2009-04-27 14:55 ` Dirk Behme
2009-04-27 22:02 ` Wolfgang Denk
2009-04-28 14:52 ` Dirk Behme [this message]
2009-04-30 18:37 ` Dirk Behme
2009-04-30 22:02 ` Wolfgang Denk
2009-05-01 6:27 ` Dirk Behme
-- strict thread matches above, loose matches on Subject: below --
2009-06-18 16:43 [U-Boot] OMAP3 pending patches Dirk Behme
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=49F7182E.5040106@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