I would sure enough be interested in that also, if you don't mind... One must remember that Bo is from the South - Texas, isn't it? Anyway, since no-one has dared to suggest a value for the serial bus timeout I asked for, I thought I'd run a value past you gyus that I have arrived at while hand-coding the network routines. If the 'detect' routine uses 256 iterations of a loop, it will take 3328 cycles to time out which is 3.25ms with an NTSC clock or 3.38ms with PAL. Now if the routine that actually produces the pulses uses 3 runs of a 256 iteration delay loop, it will take about 3840 cycles which is 3.76ms in NTSC or 3.90ms in PAL. Thus, no matter which type of machine is the master and which the slave, the timeout will occur before the pulse ends. The question remains - are CLK and DATA ever likely to be low for this long during normal serial bus routines? ... Incidentally, those worried about using NTSC and PAL machines together in a 'musical' setup can relax - the slave reply protocol for this very sequence specifies whether the slave is an NTSC or PAL machine, so the master can then tell it what scaling factors to use in the music with the command words. Richard On Thu, 3 Feb 2000, [ISO-8859-1] Marko Mäkelä wrote: > > > I'd sho nuff be interested in that also, if'n ya don't mind? > > > After a quick decoding process: should I understand, you complain > > because I sent this short note to the list? > > My decoder produced a different result: he would also like to have a copy > of the package you sent to Richard. > > Marko > > - > This message was sent through the cbm-hackers mailing list. > To unsubscribe: echo unsubscribe | mail email@example.com. > - This message was sent through the cbm-hackers mailing list. To unsubscribe: echo unsubscribe | mail firstname.lastname@example.org.
Archive generated by hypermail 2.1.1.