Return to BSD News archive
Xref: sserve comp.os.linux.development:18385 comp.os.linux.misc:28401 comp.os.386bsd.questions:14119 comp.os.386bsd.misc:3879 sci.electronics:82904 Newsgroups: comp.os.linux.development,comp.os.linux.misc,comp.os.386bsd.questions,comp.os.386bsd.misc,sci.electronics Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!news.sprintlink.net!sunserver.insinc.net!cuugnet!pepersb From: pepersb@cuug.ab.ca (Brad Pepers) Subject: 16550 detection Sender: usenet@cuug.ab.ca Message-ID: <CyIzxz.97A@cuug.ab.ca> Date: Mon, 31 Oct 1994 07:10:46 GMT References: <CMETZ.94Oct30051603@itchy.inner.net> <SRA.94Oct30162124@rurha-pente.epilogue.com> <CMETZ.94Oct30192816@itchy.inner.net> Organization: Calgary UNIX User's Group Lines: 19 The current serial code checks for a 16550 by turning on the fifo's and then checking some bits that are supposed to tell you if the fifo's are on. This sounds great and should work all the time right? But it seems some 16550 compatible chips sets don't work this way. In the last couple of days I've loaded Linux on 2 systems that swear they use 16550's and seem to work fine when I use setserial to say the are 16550's but are only recognized as 16450's by Linux. Anyone know why? Anyone got a clue if there is another way to check for a 16550 chip? I know it isn't required since setserial can fix things up but it would be nice to have Linux figure it out by itself. I'm looking into finding our exactly what chips are being used. +----------------------------Ren & Stimpy--------------------------------+ | "Psst. Hey Guido. It's all so clear to me now. I'm the keeper of the | | cheese. And you're the lemon merchant. Get it? And he knows it. That's | | why he's gonna kill us. So we gotta beat it. Yeah. Before he lets | | loose the marmosets on us! Don't worry, little missy! I'll save you!" | +------------------ Brad Pepers -- pepersb@cuug.ab.ca -------------------+