Talk:Detecting Colour and Monochrome Monitors

From OSDev Wiki
Jump to: navigation, search

How can this be improved? (Why is it in PFR?) Or can it just be removed from PFR? --Alboin

I think the 'only roughly converted' was enough :) - Combuster 11:35, 10 July 2007 (CDT)


could this short article be integrated into a larger article on VGA or Text mode, or both? JackScott 17:39, 18 February 2009 (UTC)

Well, we can rule out the VGA article - the VGA and friends cannot detect what kind of monitor is connected. Since this comes straight from the BDA, I assume it's a bios option if not defaulted to a colour monitor. The text mode article isn't good either since the monitor properties apply to both text and graphics mode. If it should be merged, it should be done with some article on EDID or similar. Right now, it IMO fits best here, alone. - Combuster 18:36, 18 February 2009 (UTC)

Video mode setup on linux

Here's a page on how linux implements this detection, maybe someone with time can integrate and find more source material to strengthen? Chazzeromus 19:20, 7 May 2012 (CDT)

I feel this to be an artifact from long, *loooong* ago. BIOS is on its way to the "legacy" booth, and I haven't seen a (working) monochrome monitor in decades. I don't think this article needs "strengthening". Let it sit here gathering dust, and maybe some time someone takes a heart and relieves it of its digital existence... ;-) -- Solar 09:38, 8 May 2012 (CDT)

ISO C doubts

I tried to compile this along with my OS. Apparently there was a complain that USHORT is not a variable type. A little research tells me to use unsigned int as USHORT can be a typedef of USHORT, but apparently doing so seems to break the program. Can someone do a check and reprogram the function to use ISO C types? Or is something wrong with my OS? --hometue

Uh, USHORT is really just a bad coding practice that expands to unsigned short. Note however that this code likely meant an unsigned 16-bit value, so uint16_t is probably a better choice. Then comes endian trouble and such, but since this is x86-specific anyway, I think it'll do. I'll just fix the code, seems trivial. --Sortie 18:34, 19 December 2013 (CST)
Personal tools