search for: 3f8h

...lisima at gmail.com> wrote: > "A real serial port that can reliably operate at 115200 8n1 may be > necessary." > > Gene, is there something special in "A real serial port" usage, compared to emulated? I should restate: A serial port that responds on BIOS IO port 3F8h that can reliably operate at 115200 8n1 may be necessary. A USB serial port that the BIOS doesn't bother setting up for IO port 3F8h is just random hardware. In order to utilize it, the serial port should not be utilized for normal use (mixing gets ugly) and a special build must be made by ch...

On Tue, Jun 30, 2015 at 5:39 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 06/30/2015 01:52 PM, Gene Cumm via Syslinux wrote: >> >> I should restate: A serial port that responds on BIOS IO port 3F8h >> that can reliably operate at 115200 8n1 may be necessary. A USB >> serial port that the BIOS doesn't bother setting up for IO port 3F8h >> is just random hardware. >> > > A USB serial port looks completely different from a UART serial port, so > that is not...

...> >> "A real serial port that can reliably operate at 115200 8n1 may be >> necessary." >> >> Gene, is there something special in "A real serial port" usage, compared to emulated? > > I should restate: A serial port that responds on BIOS IO port 3F8h > that can reliably operate at 115200 8n1 may be necessary. A USB > serial port that the BIOS doesn't bother setting up for IO port 3F8h > is just random hardware. > > In order to utilize it, the serial port should not be utilized for > normal use (mixing gets ugly) and a sp...

On 06/30/2015 01:52 PM, Gene Cumm via Syslinux wrote: > > I should restate: A serial port that responds on BIOS IO port 3F8h > that can reliably operate at 115200 8n1 may be necessary. A USB > serial port that the BIOS doesn't bother setting up for IO port 3F8h > is just random hardware. > A USB serial port looks completely different from a UART serial port, so that is not really an option. -hpa

With this config: $ head -n2 isolinux/isolinux.cfg serial 0 9600 default vesamenu.c32 via the "Raw File Port Mode - VirtualBox" I got this: $ file /tmp/serial0.txt /tmp/serial0.txt: empty For the kernel log this in turn works OK: console=ttyS0 console=tty0 ignore_loglevel Is it really needed, exclusively a physical serial connection for the isolinux debug?

...code which can help solve this > mystery? There's not any mechanism that I know of aside from using cptime.c32 to time how long it takes for the files to be loaded or enabling some of the debug functionality (with debug.c32 to the screen or a recompile to output to a serial port at IO port 3F8h at 115200 8n1). There are some obvious questions that are yet unanswered: 1) What version? Where did it come from? 2) Where is it installed? SYSLINUX on a hard drive or perhaps installed to a USB drive of some sort? Some USB BIOSs are horribly slow. Perhaps ISOLINUX on a CD or hybridized to...

Hi Gene Thanks for your reply.I'm trying to breakdown overall system boot time and to understand each component duration. My linux image is a ~10 MB bzImage file with the rootfs cpio'ed inside. I also have 2 BIOS images:- some general purpose BIOS - a custom BIOS which loads real quick I'm using TSC to measure time. I'm not sure it's the best way (I've read about CPU's

I have configured it in the wine's config file as documented but the applications can't access any serial or parallel port what can be wrong? My config file is attached to this message. -- -- Jaime Alberto Silva Colorado Administrador servidores Linux grupo DESOFMAT Universidad Tecnol?gica de Pereira Pereira - Colombia ICQ# 75722794 AOL Messenger screen name: el mono jaime MSN/hotmail

...code which can help solve this > mystery? There's not any mechanism that I know of aside from using cptime.c32 to time how long it takes for the files to be loaded or enabling some of the debug functionality (with debug.c32 to the screen or a recompile to output to a serial port at IO port 3F8h at 115200 8n1). There are some obvious questions that are yet unanswered: 1) What version? Where did it come from? 2) Where is it installed? SYSLINUX on a hard drive or perhaps installed to a USB drive of some sort? Some USB BIOSs are horribly slow. Perhaps ISOLINUX on a CD or hybridized to...

...his >> mystery? > > There's not any mechanism that I know of aside from using cptime.c32 > to time how long it takes for the files to be loaded or enabling some > of the debug functionality (with debug.c32 to the screen or a > recompile to output to a serial port at IO port 3F8h at 115200 8n1). > > There are some obvious questions that are yet unanswered: > > 1) What version? Where did it come from? > > 2) Where is it installed? SYSLINUX on a hard drive or perhaps > installed to a USB drive of some sort? Some USB BIOSs are horribly > slow. Perha...

...his >> mystery? > > There's not any mechanism that I know of aside from using cptime.c32 > to time how long it takes for the files to be loaded or enabling some > of the debug functionality (with debug.c32 to the screen or a > recompile to output to a serial port at IO port 3F8h at 115200 8n1). > > There are some obvious questions that are yet unanswered: > > 1) What version? Where did it come from? > > 2) Where is it installed? SYSLINUX on a hard drive or perhaps > installed to a USB drive of some sort? Some USB BIOSs are horribly > slow. Perha...

...? >> >> There's not any mechanism that I know of aside from using cptime.c32 >> to time how long it takes for the files to be loaded or enabling some >> of the debug functionality (with debug.c32 to the screen or a >> recompile to output to a serial port at IO port 3F8h at 115200 8n1). >> >> There are some obvious questions that are yet unanswered: >> >> 1) What version? Where did it come from? >> >> 2) Where is it installed? SYSLINUX on a hard drive or perhaps >> installed to a USB drive of some sort? Some USB BIOSs ar...

On 09.10.2016 14:49, Gene Cumm wrote: > Excellent job digging up the differences. Looks like the code comes > from commit ID c4fa331 but is much older. The code comes from 7916325 > which is derived from the ASM in beaaa4f. It appears to me that it > was used to check the presence of a serial port and it was assumed the > order at that memory address would be consistent and

...? >> >> There's not any mechanism that I know of aside from using cptime.c32 >> to time how long it takes for the files to be loaded or enabling some >> of the debug functionality (with debug.c32 to the screen or a >> recompile to output to a serial port at IO port 3F8h at 115200 8n1). >> >> There are some obvious questions that are yet unanswered: >> >> 1) What version?? Where did it come from? >> >> 2) Where is it installed?? SYSLINUX on a hard drive or perhaps >> installed to a USB drive of some sort?? Some USB BIOSs ar...