From owner-freebsd-mobile Sat Aug 26 8: 5:23 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from omega.ie.pitt.edu (omega.ie.pitt.edu [136.142.89.83]) by hub.freebsd.org (Postfix) with ESMTP id AF33937B423 for ; Sat, 26 Aug 2000 08:05:16 -0700 (PDT) Received: from ger_sun.wabash.edu (ger_sun.wabash.edu [161.32.151.172]) by omega.ie.pitt.edu (8.10.0/8.10.0) with ESMTP id e7QF4gg17241; Sat, 26 Aug 2000 11:04:42 -0400 (EDT) Date: Sat, 26 Aug 2000 10:04:38 -0500 (EST) From: "Gary E. Rafe" X-Sender: grafe@ger_sun.wabash.edu To: Hiroo ONO Cc: freebsd-mobile@FreeBSD.org Subject: Re: PAO support in 4.1? In-Reply-To: <20000826134131M.hiroo@oikumene.gcd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 26 Aug 2000, Hiroo ONO wrote: !I hear that it is being done by some committers. !Which PAO feature do you need? We have an ActionTec Datalink v.90 PCCARD modem that has been working well in a Toshiba 220CDS for almost a year now under 3.x-RELEASE with the PAO3 patches. Yesterday, I tried to upgrade the notebook to 4.1-RELEASE, and found the sio(4) driver is broken for this pc-card. When pccardd detects it, it is reported as a 16450? device with a "bogus IIR_TXRDY register". Then, when we try to talk to the card with cu(1), the system hangs hard, requiring a hard reset to recover. We've since restored 3.3-RELEASE with the PAO3 patches, and we can talk with the card again. We'll probably upgrade the OS on this notebook to 3.5.1-RELEASE with the appropriate PAO3 patches soon (we want linux_base-6.1), unless sio(4) is broken there, too. -- Gary gerst4+@pitt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message