Hi Folks,
I just wanted to point out to people that I posted changes to make the
boot flow more flexible:
http://review.coreboot.org/3131
http://review.coreboot.org/3132
http://review.coreboot.org/3133
http://review.coreboot.org/3134
http://review.coreboot.org/3135
we really need the timer scheduler on newer platforms.
Some of the platforms are so old they may not be testable.
My plan is to provide timer_us for all platforms I can test, and then
have only the new platforms use timer queue interface. I think we can
manage this with proper configuration of
On Thu, Apr 25, 2013 at 12:52 PM, ron minnich rminn...@gmail.com wrote:
we really need the timer scheduler on newer platforms.
Some of the platforms are so old they may not be testable.
My plan is to provide timer_us for all platforms I can test, and then
have only the new platforms use
On Mon, 22 Apr 2013 17:04:29 +0200
Paul Menzel paulepan...@users.sourceforge.net wrote:
Dear coreboot folks,
could you please test building coreboot for your hardware with GCC
4.7.3 and report back your results [1]?
It also works on the Lenovo x60, I only did basic testing:
it booted
The timer scheduler for hardware init scares me a bit... but I'd like
to see an implementation.
On Thu, Apr 25, 2013 at 11:59 AM, Aaron Durbin adur...@chromium.org wrote:
On Thu, Apr 25, 2013 at 12:52 PM, ron minnich rminn...@gmail.com wrote:
we really need the timer scheduler on newer
In my view, udelay becomes a src/lib/ function, i.e. generic, and it
calls timer_us to know when it's done.
u32 udelay(int us){
now = timer_us();
end = now + us;
while (timer_us() end)
;
return timer_us(); // might as well, we know the time.
}
--
coreboot mailing list:
On Thu, Apr 25, 2013 at 3:45 PM, Marc Jones marcj...@gmail.com wrote:
The timer scheduler for hardware init scares me a bit... but I'd like
to see an implementation.
It's similar to the boot state callbacks. There is a free running
timer. One can say run this in 10milliseconds. In 10
Dear Li¹,
welcome to coreboot. If I am not mistaken you are already active in the
SeaBIOS project.
Am Donnerstag, den 25.04.2013, 11:59 +0800 schrieb li guang:
do we have plan to add loongson CPU or MIPS ARCH support?
There is no plan that I know of.
It seems no person from loongson
Am I doing the math right ...
a 32-bit microsecond timer is about 20 minutes. If we ever take more
than 20 seconds we need a new job.
That was my logic.
ron
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
On Thu, Apr 25, 2013 at 4:00 PM, ron minnich rminn...@gmail.com wrote:
Am I doing the math right ...
a 32-bit microsecond timer is about 20 minutes. If we ever take more
than 20 seconds we need a new job.
That was my logic.
Who says the timer has to start at zero? What about the reboot
在 2013-04-26五的 00:26 +0200，Paul Menzel写道：
Dear Li¹,
welcome to coreboot. If I am not mistaken you are already active in the
SeaBIOS project.
Yes :-)
Am Donnerstag, den 25.04.2013, 11:59 +0800 schrieb li guang:
do we have plan to add loongson CPU or MIPS ARCH support?
There is
On Thu, Apr 25, 2013 at 6:00 PM, ron minnich rminn...@gmail.com wrote:
Am I doing the math right ...
a 32-bit microsecond timer is about 20 minutes. If we ever take more
than 20 seconds we need a new job.
That was my logic.
You are doing your math correctly. However, not all platforms may
On Thu, Apr 25, 2013 at 6:00 PM, ron minnich rminn...@gmail.com wrote:
Am I doing the math right ...
a 32-bit microsecond timer is about 20 minutes. If we ever take more
than 20 seconds we need a new job.
That was my logic.
You are doing your math correctly. However, not all platforms may
On Thu, Apr 25, 2013 at 6:42 PM, David Hendricks dhend...@google.com wrote:
On Thu, Apr 25, 2013 at 4:00 PM, ron minnich rminn...@gmail.com wrote:
Am I doing the math right ...
a 32-bit microsecond timer is about 20 minutes. If we ever take more
than 20 seconds we need a new job.
That was
we have this notion of timer_init() or whatever we called it on arm.
On all platforms, timer_init could record the clock value when it's
called, and then timer_us could report the time relative to the
starting value of timer_init.
And then our time would be a 'microseconds since coreboot started'
That sounds exactly the way my thoughts were proceeding. Please
confirm you and I are both great minds. :) I hope so because my
experience dictates otherwise.
On Thu, Apr 25, 2013 at 11:28 PM, ron minnich rminn...@gmail.com wrote:
we have this notion of timer_init() or whatever we called it on
16 matches
Mail list logo
