Re: Configuring speed for SCO OpenServer

brian_at_aljex.com
Date: 03/31/05

  • Next message: Ron Kirschner: "c8xx hba open unix 8"
    Date: 30 Mar 2005 16:31:29 -0800
    
    

    Actually, you can use 115,200 and I actually use that same article on
    Tony's site as my recipe for doing it, just adding another line "q" to
    gettydefs and using 115200 in place of 57600 everywhere.

    I set that up for dial-in or ppp (in/out) modems on the theory that I
    need the host-modem interface to be faster than 56k in order to get any
    value out of the modems on the fly compression.

    I avoid doing it on built-in com ports though as you'll be generating
    more interrupts. I usually do it on various digi and equinox smart
    serial cards and networked serial port server boxes.
    Even on built-in ports though, it's probably not noticeable on lightly
    loaded systems 5 years old or newer.

    My gettydefs ends with:

    qx # B115200 HUPCL # B115200 CS8 SANE HUPCL TAB3 RTSFLOW CTSFLOW
    -ORTSFL #\r\nlogin: # qx

    qz # B115200 HUPCL # B115200 CS8 SANE HUPCL TAB3 -IXON -IXOFF -IXANY
    RTSFLOW CTSFLOW -ORTSFL #\r\nlogin: # qz

    (I use qx, qz is just there for "might want xon/xoff some time")

    my Devices includes:
    ACU tty01E4 - 115200 /usr/lib/uucp/atdial115

    atdial115 is a symlink to atdialer and /usr/lib/uucp/default/atdial115
    contains just:
    MDM_SETUP=ATZ

    works great on at least 5.0.6 and 5.0.7.

    5.0.5 & lower?
    I don't remember if it works on 5.0.5 without a 3rd party dialer. I
    think the stock atdialer binary on 5.0.5 doesn't accept 115200 as a
    valid value, although the serial driver has no problem with it. I do
    know that it works with at last 2 3rd party dialer binaries if not the
    stock atdialer.
    I also know it works with the stock atdialer if you are using a smart
    serial card that provides false speeds just for this purpose. You use
    110 or one of the other extremely low but valid values, and atdialer
    accepts it, and the serial driver really does 115k when asked to do 110
    if the feature is enabled in the driver.

    Seems to me it should be possible to set it up so that the modem &
    serial driver do 115k but the modem simply doesn't report it's
    connection speed and atdialer doesn't look for it, but merely looks for
    "CONNECTED" and so the stock 5.0.5 & under atdialer could maybe work
    that way too. But I don't think I ever tried it.

    The other possible limiting factor is can the modem do 115k to the host
    and in this case it's known yes, and a strong probably yes for any
    other 56k modem too.


  • Next message: Ron Kirschner: "c8xx hba open unix 8"

    Relevant Pages

    • Re: Need break driver<-->pci-device automatic association
      ... There seems to be growing evidence that 8250_pci should not claim the ... modem class id match could leave a fair number of people in the lurch, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • cygwin serial driver code is echoing written characters.
      ... Hi.I have written a serial driver to communicate with a modem and ... executed on cygwin.My driver is reading what ever being written ... hyperterminal.What may be the cause?Can we execute a serial driver ...
      (microsoft.public.windowsxp.embedded)
    • Re: pppd and 2.6.25 serial driver
      ... as I can receive faxes with a fax modem using the ... I have checked with the serial driver in the latest 2.6.26 ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)

  • Quantcast