From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
tglx@linutronix.de, johnstul@us.ibm.com
Subject: Re: [PATCH] rest of works for migration to GENERIC_TIME
Date: Mon, 23 Oct 2006 22:57:11 +0400 [thread overview]
Message-ID: <453D1087.9020109@ru.mvista.com> (raw)
In-Reply-To: <453D0F85.3090207@ru.mvista.com>
Hello, I wrote:
> Atsushi Nemoto wrote:
>>> The whole idea of using such timer as TX39 has for both
>>> generating the interrupts and as a clocksource was wrong, I'm
>>> afraid. You only can use a something similar to the MIPS counter
>>> which doesn't ever get auto-reloaded for both purposes at once.
>> Sure, we can do this improvement and it would be a right direction.
>> But for now I just want to get previous facility back again. And
>> anyway I think someone who still have interest on this platform should
>> make it buildable and bootable before further improvement ;-)
> Frankly, I'm sowewhat doubtful about TX39 timer code being sane at
> all since it doesn't clear the timer interrupt -- it clearly should
> override mips_timer_ack() and it doesn't! OTOH, it was working in 2.4
> without this somehow... I'm puzzled since with the interrupt not being
> cleared anywhere jmr3927_do_gettimeoffset() should be returning complete
> crap once the frist interupt happens, i.e. only be jiffy-precise. Why it
> doesn't get the interrupt flood I don't know or contrarywise, no further
> interrupts after the first one, I don't know... :-/
Ah, they put it into jmp3927_irq_ack(). Crap! :-/
>> ---
>> Atsushi Nemoto
WBR, Sergei
next prev parent reply other threads:[~2006-10-23 18:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 18:34 [PATCH] rest of works for migration to GENERIC_TIME Atsushi Nemoto
2006-10-22 19:25 ` Sergei Shtylyov
2006-10-23 3:00 ` Atsushi Nemoto
2006-10-23 12:32 ` Sergei Shtylyov
2006-10-23 15:29 ` Atsushi Nemoto
2006-10-23 18:52 ` Sergei Shtylyov
2006-10-23 18:57 ` Sergei Shtylyov [this message]
2006-10-23 3:04 ` Atsushi Nemoto
2006-10-23 13:08 ` Ralf Baechle
2006-10-23 16:41 ` mlachwani
2006-10-22 19:39 ` Manish Lachwani
2006-10-23 2:09 ` Atsushi Nemoto
2006-10-23 1:45 ` Atsushi Nemoto
2006-10-23 14:38 ` Sergei Shtylyov
2006-10-23 15:38 ` Atsushi Nemoto
2006-10-23 15:39 ` Sergei Shtylyov
2006-10-23 15:51 ` Atsushi Nemoto
2006-11-11 15:13 ` Atsushi Nemoto
2006-10-23 17:02 ` Sergei Shtylyov
2006-10-23 15:21 ` Atsushi Nemoto
2006-10-24 13:39 ` Sergei Shtylyov
2006-10-24 15:14 ` Sergei Shtylyov
-- strict thread matches above, loose matches on Subject: below --
2006-10-22 18:30 Atsushi Nemoto
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=453D1087.9020109@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=johnstul@us.ibm.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.