| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20070215002457.7b382d5f@localhost.localdomain> Date: Thu, 15 Feb 2007 00:24:57 +0000 From: Alan <alan@...rguk.ukuu.org.uk> To: akennedy@...hmoninc.com Cc: linux-kernel@...r.kernel.org Subject: Re: Serial console issues. On Wed, 14 Feb 2007 16:11:14 -0700 akennedy@...hmoninc.com wrote: > In a previous post I incorrectly stated that my serial port is a > TI16750, as this is what /proc/tty/... revealed to me. After > re-reading the product manual, I see that this is actually a 16550. > Since Linux is seeing this port as a 16750, could that explain why I'm > seeing missing characters in the transmission. After doing some > research, I found that the 16750 has a 64-byte buffer, whereas I know > this to only have a 16-byte buffer. The autodetect is pretty solid so you may well find the chip is 16750 compatible, 16550A is what is usually listed because it is what people look for. > If my assumptions are correct and Linux is detecting this serial port > incorrectly, how can I force the serial driver to see this a 16550? man setserial - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists