Re: external master clock

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 04 October 2002 01:02 am, David Schleef wrote:
>
> This should be done with an extended trigger, since it requires
> several inputs, including input channel selection (assuming that
> you could use multiple inputs for the clock source), rising edge/
> falling edge, and the divisor.
>
> There isn't an extended trigger currently defined for this, but
> this seems appropriate:
>
> data 1 - INSN_CONFIG_TIMER_1
> data 1 - trigger configuration
> data 2 - primary input chanspec
> data 3 - primary combining machine configuration (should always be 0x04)
> data 4 - divisor
>
> I have a gut feeling that I'm missing ways this should be
> generalized, but it doesn't matter.
>

I think this needs to be split into two insn, one for setting up the master 
clock, and one for setting the divisor for a particular trigger?  I'm 
thinking of the case where both the scan_begin and convert triggers are 
running off the master clock with different divisors.

- -- 
Frank

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9n2k25vihyNWuA4URAoOvAKDi1wbHXo21aytojLR6u8y5NzddwQCg3H/s
c/7pCUAmMbJnYG6UHEkPaIU=
=WSzi
-----END PGP SIGNATURE-----

Received on 2002-10-05Z21:35:30