Hi LaMont, thanks for your reply.
LaMont Jones wrote:
On Mon, Oct 13, 2008 at 06:18:56PM +0100, Phil Endecott wrote:
I'm also curious to know why reading the clock takes a second anyway.
Note that we have to use --directisa on this hardware to avoid a random
lock-up. It looks as if the CPU is busy for the second that it's
running - in a busy-loop maybe? Is there anything that can be done to
accelerate this?
With directisa, it waits for the realtime clock to transition. That is
going to take up to 1 second.
OK. We should really try to get the normal access fixed, if that
doesn't need to spin in that way.
As for why two copies, it's at least partially a result of rtc being a
module instead of a built-in. See also bug #443487.
Hmm. Well, since I'm not using adjtime and since I have no modules, it
would be good to avoid the second invocation somehow. Is there a tidy
way to do this?
Phil.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
