SCC driver: interrupt bug in Kernel 2.4?

From: ihz@ussonet.net
Date: Mon Jun 11 2001 - 11:01:47 EEST

  • Next message: Bent Bagger: "Re: Expect Scripting"

    1) The intro
    After finding that the pre-compiled z8530 utils wouldn't work
    I went to re-compile them. Unfortunateley they were a bit
    unhappy about my glibc2 headers. I've now updated them so
    the recompile OK and they seem to work OK. I'll mail the
    patch out tonight/tomorrow.

    2) The real problem
    Unfortunately, the kernel driver doesn't seem so happy. I've just
    upgraded from a 2.2.17 kernel to 2.4.4 (without making any
    changes to my hardware). I'm using a Baycom USCC4.
     Initialisation and configuration using sccinit, sccparam and
    ifconfig is fine. The problems come when TX interrupts occur on
    two SCC channels at the same time; it locks the whole box hard.
    When my machine boots, an rc script configures the devices and
    then runs beacon on all ports, which was hanging the box. When
    I changed this to beacon on one port only then there were no
    problems.
     Haven't checked anything to do with RX interrupts yet, so I
    can't say whether simultaneous RX ints have the same effect.

              Thoughts?

              73
                Jason G7OCD
    -
    To unsubscribe from this list: send the line "unsubscribe linux-hams" in
    the body of a message to awvatqg@kd7ry.com



    This archive was generated by hypermail 2b30 : Mon Jun 11 2001 - 11:01:52 EEST