Archives
- November 2025
- October 2025
- September 2025
- August 2025
- July 2025
- June 2025
- May 2025
- April 2025
- March 2025
- February 2025
- January 2025
- December 2024
- November 2024
- October 2024
- September 2024
- August 2024
- July 2024
- June 2024
- May 2024
- April 2024
- March 2024
- February 2024
- January 2024
- October 2023
- September 2023
- August 2023
- July 2023
- June 2023
- May 2023
- April 2023
- March 2023
- January 2023
- December 2022
- November 2022
- October 2022
- September 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- January 2011
- November 2010
- October 2010
- August 2010
- July 2010
S3 Graphics Accelerators and the 8514/A
The previous article about the IBM 8514/A graphics accelerator and clones did not mention S3’s chips because S3-based graphics cards were never 8514/A compatible, unlike the ATI Mach 8 and Mach 32 chips and others. However, the relationship between S3 chips and 8514/A is a bit more complex.
S3 Inc. (later known as S3 Graphics) was founded in 1989 and in mid-1991 it released the S3 911, the first single-chip SuperVGA GUI accelerator (the 911 designation was a reference to the Porsche 911). This was soon followed by S3 924, 928, the S3 Vision family (864/964/868/968), and finally by the extremely successful S3 Trio integrated GUI accelerators (Trio32, Trio64, Trio64V+). The 3D-capable S3 ViRGE and Savage chips never reached the popularity of their 2D-only predecessors.
Reviewing a data sheet for the "S3 Trio64V+ Integrated Graphics/Video Accelerator", it is obvious that there was a very close relationship between S3 accelerators and the 8514/A. The same relationship is also apparent in the OS/2 DDK for example, where the sample Presentation Manager accelerated driver shares a significant portion of code between 8514/A and S3 drivers.
The S3 draw engine was obviously designed to be compatible with the 8514/A. This includes register naming (VESA-approved 8514/A register names), I/O addresses used for the registers (at least in later chips only optionally), and register layout. This similarity made it easy to port existing 8514/A drivers to support S3 hardware. At the same time, the S3 chips were never 100% 8514/A compatible and running unmodified 8514/A code on S3-based cards was out of the question.
The S3 graphics chips combined a VGA core with SuperVGA capabilities with an accelerated draw engine. The Trio series also added a DAC and a PLL synthesizer on the same chip (hence a "trio" of integrated chips). The display engine (often called CRTC, or CRT Controller) was a VGA/SuperVGA design and didn’t resemble the 8514/A at all. No less important was the fact that as integrated VGA/GUI accelerator designs, the S3 chips never had separate VGA and accelerator framebuffers, and the framebuffer was directly accessible from the host (whether in a banked fashion or mapped linearly).
The draw engine itself was also not identical to the 8514/A, despite the very high degree of similarity. S3 extended it to support higher color depths (16, 24, and 32 bits per pixel) and larger memory sizes, but even the in 8-bpp modes there were differences.
Where the 8514/A supported 32 mixes, S3 only supported 16 (the basic logical operations were retained while the additions/subtractions were dropped). There was no provision for the host to read the data which the draw engine would write—since the host could access the framebuffer directly, this functionality was unnecessary. Color comparisons were simplified to only support equality or inequality, no ranges.
The draw engine commands were also slightly different. S3 dropped the vertical rectangle fills (which achieved the same effect as the standard horizontal fill) as well as area fills, but added pattern blits (PatBLTs) which replicated an 8×8 pattern to a destination rectangle, a common GUI operation.
It is apparent that if an existing 8514/A driver were used as a starting point, the mode setting code would have to be very significantly modified if not entirely replaced to support S3 chips. On the other hand, the drawing code could most likely be kept with minor modifications (perhaps changing the register access mode from I/O to MMIO and slightly changing certain operations) and certainly retaining the overall structure.
Overall, S3 was clearly very much inspired by the 8514/A draw engine and its register interface, but felt free to both extend the functionality and drop existing 8514/A features that were not considered important, presumably to simplify the design and reduce cost. Being compatible with existing 8514/A software was not S3’s objective, and not a requirement in the age of Windows.
This site uses Akismet to reduce spam. Learn how your comment data is processed.