Talk:Serial Ports
Detection
This section needs details on exactly how to detect serial ports using legacy device techniques. It also doesn't mention IRG 3/4, if im not mistaken... do these not report incoming data or is that a BIOS thing? --Tyler 06:51, 9 January 2007 (CST)
Baud rate
I'm not SerialPorts guru, but bauds is usually symbols per second on the wire, and afaik, each symbol on a RS-232 line will only carry 1 bit, so the baud rate (here) is more likely to be the bitrate than the byte-per-second speed ... note however than modems typically send many bits per baud (because you may have more than 2 waveforms used), but not necessarily 8 of them ... Someone should check the specs and confirm/correct. - PypeClicker (copy from osfaq - Combuster 04:05, 20 January 2007 (CST))
Pages to convert
PLEASE mark the page as converted next time, you had me do almost everything a second time. - Combuster 04:40, 20 January 2007 (CST)
Category
This page current only has one category - network hardware... The page doesn't just cover networking with serial ports though. Suggest adding another relevant category? --pcmattman 03:36, 4 April 2009 (UTC)
- I added it to Common Devices. --Troy Martin 16:35, 4 April 2009 (UTC)
Sending Data Example
Under the "Example Code" section, under "Sending Data," it has return inb(PORT + 5) & 0x20; as the body for is_transmit_empty - is that meant to be return inb(PORT + 5) & 0x2;? --Retrocat 21:29, 26 May 2018 (CDT)
Should the article be updated to be a little more generalised?
Should this article be updated to provide a more general view of serial/uart communication hardware? It seems to be very x86-centric and doesn't provide a very generalised view of the topic. For my personal perspective, I've put in a little more time working with UART communication in embedded systems than with serial ports in X86 systems, but I've created simple 8250 compatible drivers before. 'uart' redirects to this article, should it not be the other way around? It doesn't tell the reader much about what specific kind of controller hardware that x86 uses or where to find datasheets for it. My suggestions specifically is just that the wording be changed slightly to reflect that the article deals specifically with the 8250/16550 UART on x86 systems. I think this would be helpful not only because it is more technically correct, but because it will encourage the reader to think in the correct terms: That what they are doing is writing a driver for a specific piece of hardware. I'm happy to make the changes myself if anyone agrees.