From owner-freebsd-mobile  Mon Oct 14 14: 9:20 2002
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2320637B401
	for <freebsd-mobile@FreeBSD.ORG>; Mon, 14 Oct 2002 14:09:19 -0700 (PDT)
Received: from postal3.es.net (postal3.es.net [198.128.3.207])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 87E9A43EB7
	for <freebsd-mobile@FreeBSD.ORG>; Mon, 14 Oct 2002 14:09:18 -0700 (PDT)
	(envelope-from oberman@es.net)
Received: from ptavv.es.net ([198.128.4.29])
        by postal3.es.net (Postal Node 3) with ESMTP id MUA74016;
        Mon, 14 Oct 2002 14:09:17 -0700
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Postfix) with ESMTP
	id 806365D06; Mon, 14 Oct 2002 14:09:16 -0700 (PDT)
To: Kirill Bezzubets <kirill@solaris.ru>
Cc: Julian Chesterfield <Julian.Chesterfield@cl.cam.ac.uk>,
	freebsd-mobile@FreeBSD.ORG
Subject: Re: Sierra Wireless Aircard 750 GSM/GPRS 
In-reply-to: Your message of "Tue, 15 Oct 2002 00:20:29 +0400."
             <20021014202029.GA77467@solaris.ru> 
Date: Mon, 14 Oct 2002 14:09:16 -0700
From: "Kevin Oberman" <oberman@es.net>
Message-Id: <20021014210916.806365D06@ptavv.es.net>
Sender: owner-freebsd-mobile@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-mobile.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-mobile>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-mobile>
X-Loop: FreeBSD.org

> Date: Tue, 15 Oct 2002 00:20:29 +0400
> From: Kirill Bezzubets <kirill@solaris.ru>
> Sender: owner-freebsd-mobile@FreeBSD.ORG
> 
> On Mon, Oct 14, 2002 at 04:49:41PM +0100, Julian Chesterfield wrote:
> 
> > 
> > sio4 at port 0x240-0x27f irq 9 flags 0x40000 slot 0 on pccard0
> > sio4: type 8250
> 
> 8250?.. Hmm.. Even my old USR Megahertz shows up as 16550A sio..

As it turns out, the sio driver will report 8250 if the interface
fails to respond. The driver tries sending a couple of requests to the
serial port that the 16550 family will understand and use this to
determine just what chip the interface uses. If attempts to
communicate with the hardware fail, it assumes 8250, but it's probably
more likely that it is not talking to the interface at all.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message