Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news-peer.gsl.net!news.gsl.net!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: internal modem sio question Date: 25 Oct 1996 21:20:11 GMT Organization: Private BSD site, Dresden Lines: 49 Message-ID: <54raub$9ta@uriah.heep.sax.de> References: <3266E9E8.5D0A@sprynet.com> <549ief$o6m@library.airnews.net> <dblizzar-2410962311150001@dd20-112.compuserve.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E dblizzar@sprynet.com (Dave Blizzard) wrote: > The problem is that FreeBSD doesn't even see the modem's serial > interface sio2. This seems to be a modem hardware problem as Jordan > says " some modems just emulate the 16550 uart" Almost all internal modems just emulate the 16550. They probably emulate it with an ASIC that has no real `registers' like a genuine UART, but instead runs some sort of microprogram to respond to the ISA bus commands. This often takes a microsecond or two, much more than a real UART needs. You can cause the sio driver to be more verbose about its doing (in particular at the device probe time) by specifying the flag 0x80 for your sio2 (boot with -c, and modify the `flags' field). This way, you'll see which probes fail. Use this info to walk into the file /sys/i386/isa/sio.c, look for the function sioprobe() there, and see whether it's possible to modify the timing for the probe that fails for you -- the failed probes are being registered in the array failures[] there. Btw: ``Jordan says''... (The following is not meant personally against you, Dave, but rather a general note, also based on own experience.) It's really not the most desirable behaviour to approach the developers directly for this kind of `generic' questions where quite a few more people will be able to answer it. Unless you know the special fields of each of the various developers, you often won't even reach the most knowledgable person for just your problem. So, better stick with the mailinglist freebsd-questions@freebsd.org, or this newsgroup here. There are more people around anyway, so it's not unlikely that the response time is shorter at all, and you help taking the load off the most busiest people. To make it clear, nobody of us minds people talking to any developer directly, after all, that's one of the advantages of an open and transparent software development organization. However, noone of us has an infinite amount of time available, and you certainly also expect us doing further development... :) So, use the direct approach only if you are convinced that this is a problem nobody else than your intended addressee could solve. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)