From owner-freebsd-questions Mon Mar 22 15:26:57 1999 Delivered-To: freebsd-questions@freebsd.org Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by hub.freebsd.org (Postfix) with ESMTP id 0288014BD2 for ; Mon, 22 Mar 1999 15:26:54 -0800 (PST) (envelope-from raj@cisco.com) Received: from raj.cisco.com (dhcp-f-55-250.cisco.com [171.69.55.250]) by hubbub.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) with ESMTP id PAA04486 for ; Mon, 22 Mar 1999 15:26:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by raj.cisco.com (8.9.2/8.9.2) with ESMTP id PAA01583 for ; Mon, 22 Mar 1999 15:26:30 -0800 (PST) (envelope-from raj@cisco.com) Message-Id: <199903222326.PAA01583@raj.cisco.com> To: questions@freebsd.org Subject: Re: PCMCIA modem card problems In-reply-to: Your message of "Sun, 21 Mar 1999 11:01:43 PST." X-Quote: If you consult enough experts, you can confirm any opinion. Date: Mon, 22 Mar 1999 15:26:30 -0800 From: Richard Johnson Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Following up on my question about PCMCIA modem cards (which hasn't gotten an answer yet): I found that if I removed the configuration for "sio0" (which was finding the built in serial port), then the kernel doesn't hang when I open /dev/cuaa2 and I can talk to the modem (and get responses) just fine. The only remaining problem is that the driver doesn't recognize that the modem has output ready unless it has just finished delivering a character to it. When I type "at" followed by a return, I don't see any output (the "OK" response) until I send the modem another character. If I do the command to have the modem print all of its registers (forgotten what it is currently), I see a few lines of output and it stops in the middle of one of the lines. I then hit return and I get a little bit more output, etc. It appears as though the sio driver isn't getting interrupts when the card has output ready but is instead polling for output right after having delivered characters to the card. I don't know if this is a bug in the driver or if it's simply not recognizing the card correctly. According to "pccardc dumpcis" output the card has a 16550 chip and the driver says it's a 16550A. Maybe there's a small amount of difference here? Has anyone seen this type of problem with the i386/isa/sio.c driver code? /raj To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message