-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2001-05-08 9:15, Michael Schmitz at [EMAIL PROTECTED] wrote:
>> i think the `nobody has bothered' is probably the explanation. > > Nope, it's actuakky pretty difficult to implement and probably > not worth the hassle (at least not for anyone who'll never use > that feature, sorry this is how free software works). No, I know. I'm half inclined to tackle this myself, but I'm currently too interested in spending time at my day job and with my family. :-) > Localtalk over > serial requires synchronous mode operation of the SCC and the > protocol timing constraints are pretty tight. You don't want to do > that sort of stuff in non-realtime context. In a multitasking OS > you don't want to do it busy-waiting in the interrupt handler > either. But you may see things different, please go ahead and prove > me wrong. I used to write device drivers for DOS and Windows (years ago!), so I understand what you're saying. Ugh. > PC localtalk cards have a coprocessor to offload the protocol > handling to IIRC. Ah. I had an inkling this might be the case. More and more, I'm thinking I just need to go ahead and buy that Postscript-capable laser printer I've had my eye on.... -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com> iQA/AwUBOvgMOhNvDO+i/75BEQJyVACgjhWLhl6yAxluXcmQqBuiTB8ETSkAnjEB YgheK4ObPu6G7yZL28fNZDWQ =+5YP -----END PGP SIGNATURE----- -- Craig S. Cottingham [EMAIL PROTECTED] PGP key available from: <http://pgp.ai.mit.edu:11371/pks/lookup?op=get&search=0xA2FFBE41> ID=0xA2FFBE41, fingerprint=6AA8 2E28 2404 8A95 B8FC 7EFC 136F 0CEF A2FF BE41
