From: Jun Sun <jsun@mvista.com>
To: Pete Popov <ppopov@mvista.com>
Cc: Jeff Baitis <baitisj@evolution.com>,
Linux MIPS mailing list <linux-mips@linux-mips.org>,
jsun@mvista.com
Subject: Re: Improperly handled case in arch/mips/au1000/common/time.c
Date: Tue, 22 Apr 2003 16:07:19 -0700 [thread overview]
Message-ID: <20030422160719.G28544@mvista.com> (raw)
In-Reply-To: <1051052439.2552.352.camel@zeus.mvista.com>; from ppopov@mvista.com on Tue, Apr 22, 2003 at 04:00:39PM -0700
On Tue, Apr 22, 2003 at 04:00:39PM -0700, Pete Popov wrote:
> On Tue, 2003-04-22 at 15:56, Jun Sun wrote:
> > I think this is a good example to show benefit of code sharing.
> > There is no good reason for au1x00 boards of not using new time.c.
> > You get to write less board code, fewer bugs and future proof.
>
> The I didn't use the generic time.c back then is power management.
Oh, I see. My ignorance ... :)
> The
> CP0 counter sleeps when using the 'wait' instruction, so in that case
> you have to use a different counter with a rather poor resolution. The
> modifications I had to make were such that they couldn't go in the
> generic time.c. But that area definitely needs to be revisited and
> cleaned up.
>
Yeah, there might be something interesting to do here.
Jun
next prev parent reply other threads:[~2003-04-22 23:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 19:54 Improperly handled case in arch/mips/au1000/common/time.c Jeff Baitis
2003-04-22 20:20 ` Pete Popov
2003-04-22 20:49 ` Ralf Baechle
2003-04-22 22:56 ` Jun Sun
2003-04-22 23:00 ` Pete Popov
2003-04-22 23:07 ` Jun Sun [this message]
2003-04-23 15:35 ` Dan Malek
2003-04-22 23:07 ` Ralf Baechle
2003-04-22 23:13 ` Jun Sun
2003-04-22 23:18 ` Pete Popov
2003-04-22 23:30 ` Jun Sun
2003-04-23 0:29 ` Ralf Baechle
2003-04-23 13:24 ` Maciej W. Rozycki
2003-04-22 23:17 ` Matthew Dharm
2003-04-22 23:17 ` Matthew Dharm
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=20030422160719.G28544@mvista.com \
--to=jsun@mvista.com \
--cc=baitisj@evolution.com \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@mvista.com \
/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