From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] post: fix compile issue for post tests on kirkwood
Date: Mon, 28 Nov 2011 09:51:56 +0100 [thread overview]
Message-ID: <4ED34BAC.5040307@keymile.com> (raw)
In-Reply-To: <201111270807.36629.marek.vasut@gmail.com>
Hi,
On 11/27/2011 08:07 AM, Marek Vasut wrote:
>>>>>>>
>>>>>>>> commit f31a911fe (arm, post: add missing post_time_ms for arm)
>>>>>>>> enables get_ticks and get_tbclk for all arm based boards,
>>>>>>>> but kirkwood has currently no implementation for this. So
>>>>>>>> undefine this for kirkwood boards.
>>>>>>>
>>>>>>> So this means the kirkwood timer doesn't conform to current timer
>>>>>>> api? Why work
>>>>>>> it around and not fix it then?
>>>>>>
>>>>>> I think this is better approach
>>>>>
>>>>> Right? :) So now the question is ... who's gonna do it ? ;-)
>>>>
>>>> Patch from any one is welcomed. :-D
>>>
>>> Anyone, eh? Anyone ... anyone like the maintainer maybe ? >:-D
>>
>> I would have loved to do it, but I am very busy with some other very
>> important assignment. May be I will post a patch in feb2012
>>
>
> I'll keep an eye on this ;-)
I do also agree that implementing the functions would be better then adding an
#ifdef as my patch does. But I currently got also no time to do this.
So could someone please pick this patch up that the keymile ARM boards are
compilable again?
Best regards
Holger
prev parent reply other threads:[~2011-11-28 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 13:09 [U-Boot] [PATCH] post: fix compile issue for post tests on kirkwood Holger Brunck
2011-11-25 8:52 ` Marek Vasut
2011-11-25 9:16 ` Prafulla Wadaskar
2011-11-25 9:22 ` Marek Vasut
2011-11-26 10:29 ` Prafulla Wadaskar
2011-11-26 11:45 ` Marek Vasut
2011-11-27 5:56 ` Prafulla Wadaskar
2011-11-27 7:07 ` Marek Vasut
2011-11-28 8:51 ` Holger Brunck [this message]
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=4ED34BAC.5040307@keymile.com \
--to=holger.brunck@keymile.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