Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!metro!metro!asstdc.scgt.oz.au!nsw.news.telstra.net!act.news.telstra.net!psgrain!usenet.eel.ufl.edu!arclight.uoregon.edu!feed1.news.erols.com!howland.erols.net!news.mathworks.com!fu-berlin.de!informatik.tu-muenchen.de!news.muc.de!news.space.net!news.camelot.de!news.hannibal.camelot.de!usenet
From: os@hannibal.camelot.de (Oliver Scheel)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Problems with uucico
Date: 31 Oct 1996 18:00:59 GMT
Organization: Hannibal Online
Lines: 27
Message-ID: <55apgr$ls@hannibal.camelot.de>
References: <Pine.LNX.3.91.961023224820.1769C-100000@speedy.ruhr.de>
<54pvdd$897@uriah.heep.sax.de> <54thaa$8ue@hannibal.camelot.de>
<555rgi$621@uriah.heep.sax.de>
NNTP-Posting-Host: hannibal.camelot.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.7
In article <555rgi$621@uriah.heep.sax.de>,
j@uriah.heep.sax.de (J Wunsch) writes:
> UMC8669F?
I own the Chaintech M586IFM which uses an UM(C?)8669F (c't says this). I
thought this only concerns older boards (I bought my Chaintech three or four
months ago).
> These chips are broken, period. You can find software workarounds
> (and there is one in the current driver), but the origin of the
> problems is a broken (by design) chip. They've botched the FDC, and
> they've botched the UARTs. (The FDC generates unexpected interrupts,
> the UARTs don't resynchronize when changing the divisor latch while
> data are flowing in -- even if you change it to the same value.)
Very nice :-(. And why does this happen only with UUCP?
I will try UUCP with my third sio (original 16550) next week.
Many thanks.
Oliver
--
*** Oliver Scheel, Zenettistr. 45a, D-80337 Muenchen, Germany ***
*** email: os@hannibal.camelot.de http://www.camelot.de/~os/ ***