| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Real-time Acquisition |
MB> and depends quite a lot on the exact behavior of the MB> peripheral. y'know, i've been puzzling on this now, since Luns Tee's comment. Why would a FIFO be memory-mapped?? i don't see that m-m buys you anything on the ISA bus over port i/o, and FIFOs don't have addresses. at least, not standard FIFOs. that's why it's so easy to plug a 4Kx9 into the same socket as a 2Kx9 when you get in trouble: same pinouts. i just talked with some folks who are running DAQ boards under Windows with DOS TSRs and were curious about using Win VxDs instead. i looked at some old literature i had lying about and hadn't read...Windows VIRTUALIZES all the PC IRQ and DMA stuff! Literally! Talk about a VDM! They got a virtual 8259 and virtual interrupt table and virtual DMA into virtual mem...oops! It's WHERE on the swapfile? Uh-oh. So you make this buffer in real memory...sheesh. I was wondering why all the DAQ boards were growing 7201 and 7202 FIFOs and dual DMA channels. Virt. IRQ response is sorta like DOS emulation on RISC: pathetically slow. That got me thinking about OS/2's drivers. Without getting a DDDK for OS/2 is there a good ref. on how IRQs and DMA are handled? I presume something more civilized is used to feed the VDMs. I guess "Writing OS/2 Device Drivers in C" would be one book. ___ X KWQ/2 1.2g X 3 deg. K: Not with a bang, but a whimper. --- Maximus/2 2.02* Origin: OS/2 Shareware BBS, Fairfax, VA: 703-385-4325 (1:109/347) SEEN-BY: 12/2442 620/243 624/50 632/348 640/820 690/660 711/409 410 413 430 SEEN-BY: 711/807 808 809 934 942 949 955 712/515 713/888 800/1 7877/2809 @PATH: 109/347 2 7 3615/50 105/103 42 724/13 600/500 2 82 229/2 12/2442 @PATH: 711/409 808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.