Port-mvme68k archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: mvme68k timecounters.... untested
On Fri, Jan 04, 2008 at 10:54:13PM +0900, Izumi Tsutsui wrote:
> @@ -75,10 +77,12 @@
> static int clock_pcc_profintr __P((void *));
> static int clock_pcc_statintr __P((void *));
> static void clock_pcc_initclocks __P((void *, int, int));
> -static long clock_pcc_microtime __P((void *));
> static void clock_pcc_shutdown __P((void *));
> +static uint32_t clock_pcc_getcount(struct timecounter *);
static u_int clock_pcc_getcount(struct timecounter *);
to match the prototype.
>
> static struct clock_pcc_softc *clock_pcc_sc;
> +static uint32_t clock_pcc_count;
> +static uint16_t clock_pcc_reload;
>
> /* ARGSUSED */
> int
> @@ -75,10 +77,11 @@
> static int clock_pcctwo_profintr(void *);
> static int clock_pcctwo_statintr(void *);
> static void clock_pcctwo_initclocks(void *, int, int);
> -static long clock_pcctwo_microtime(void *);
> static void clock_pcctwo_shutdown(void *);
> +static uint32_t clock_pcctwo_getcount(struct timecounter *);
Same here.
>
> static struct clock_pcctwo_softc *clock_pcctwo_sc;
> +static uint32_t clock_pcctwo_count;
>
> /* ARGSUSED */
> int
If you can freely program the frequency and just have a free running
counter, use as high a frequency as possible. With the two glitches
above, it is otherwise fine.
Joerg
Home |
Main Index |
Thread Index |
Old Index