🚀 go-pugleaf

In <92309.234426BJT105@psuvm.psu.edu> BJT105@psuvm.psu.edu writes:
>Any member of the developer assistance program can get sample source code
>for video drivers .. currently what is available is the code to VSVGA, V8514
>VVGA BVHVGA, BVHSVGA, BVH8514, and, unfortunately, the only PM driver at
>this time is the code to 16-bit VGA.  "very soon now" the code to the 32-bit
>tseng drivers is planned to be released .. I have no idea when.

It also include the 8514 PM drivers. Quite useful to learn how
to make a 256c driver...

>Documenation is available in the forms of
>"OS/2 2.0 virtual device driver reference"
>"OS/2 2.0 physical device driver reference"
>and "OS/2 2.0 presentation driver reference"
>all three are part of the CSET/2 documentation set, and can be purchaced
>seperately.
>
>OK .. now WHY doesn't every board around have OS/2 device drivers,
>since so much is available?!:
>(1) IBM didn't release the code mentioned above until September

Yeah, we had to wait quite a long time...


>(2) The VV, BV, and PM source code is comprised on hundreds of thousands
>    of lines of mixed C and assembler, so it is very difficult to
>    pick up quickly!

Well, at least the PM drivers are ASM only... :-) (80000 lines)

>(3) Most video board companies are fly-by-night operations that feed on
>    consumers that don't realize that SVGA means NOTHING by itself ..
>    that each chipset requires custom software for Windows, OS/2, X
>    and whatever else.  And, basically, they don't want to have to deal
>    with writing drivers for more than one operating system (windows)
>    (BTW .. there are exceptions to this rule .. Orchid and Trident
>    come to mind ...)
>
>Bernie

   Since the 32bit PM drivers use a completely new (and undocumented)
architecture, I would not start writing a PM driver now... I would
just wait for the 32bit version of the above kit (hopefully about
to be released...).

-Joel Armengaud