| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | 16 bit ?? |
Francois Thunus wrote in a message to Thomas Seeling: FT> [device driver writing] TS> No, compiler/assembler/linker need to be 16 bit. FT> Call me dumb, but why ??? I thought warp was a full 32 bit FT> operating system ?? Some device drivers in OS/2 are 32-bit, but others are 16-bit. In general, the lowest level device drivers are 16-bit, which works out reasonably well because they tend to be small and I/O-bound. You can use 32-bit instructions in a 16-bit driver, however; it is only the 16-bit memory model to which the driver must conform. Most 16-bit device drivers are small enough so that they are written in small model (except for installation code which is discarded), which is as fast as 32-bit flat model. Where 16-bit code is slow is when segment register reloads must be done, as in large model. -- Mike ---* Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) SEEN-BY: 50/99 270/101 620/243 711/401 409 410 413 430 808 809 934 955 SEEN-BY: 712/407 515 517 628 713/888 800/1 @PATH: 323/107 396/1 270/101 712/515 711/808 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™.