From owner-freebsd-questions@FreeBSD.ORG Wed Feb 11 11:37:19 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 468A716A4CE for ; Wed, 11 Feb 2004 11:37:19 -0800 (PST) Received: from mail.radicalv.com (secure.radicalv.com [216.118.91.10]) by mx1.FreeBSD.org (Postfix) with SMTP id DF77443D31 for ; Wed, 11 Feb 2004 11:37:18 -0800 (PST) (envelope-from ecrist@adtechintegrated.com) Received: (qmail 97978 invoked from network); 11 Feb 2004 19:37:01 -0000 Received: from unknown (HELO localhost.invalid) (66.188.176.110) by mail.radicalv.com with SMTP; 11 Feb 2004 19:37:01 -0000 From: Eric F Crist Organization: AdTech Integrated Systems, Inc To: freebsd-questions@freebsd.org, duanewinner@att.net Date: Wed, 11 Feb 2004 13:37:07 -0600 User-Agent: KMail/1.6 References: <1076527398.252.27.camel@localhost> In-Reply-To: <1076527398.252.27.camel@localhost> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_pRoKAXFkxUERIng"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402111337.14211.ecrist@adtechintegrated.com> Subject: Re: com ports in freebsd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ecrist@adtechintegrated.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2004 19:37:19 -0000 --Boundary-02=_pRoKAXFkxUERIng Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 11 February 2004 01:23 pm, Duane Winner wrote: > Hello, > > I have a question about how FreeBSD handles the serial ports. > > After messing around for 2 days, I finally got my PCMCIA modem working > on my laptop. All I really had to do was to > "cd /dev/ && ./MAKEDEV cuaa4" > > I did this because dmesg kept reporting the Megahertz modem at "sio4". > > What I don't understand is the why or how. My kernel config is still > using the default sio0 thru sio3 devices: > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > device sio1 at isa? port IO_COM2 irq 3 > device sio2 at isa? disable port IO_COM3 irq 5 > device sio3 at isa? disable port IO_COM4 irq 9 > > So if there is now sio4 in the kernel, how is this working? > > I'm not complaining, nor looking for a solution, since I have everything > working now. > > I'm just trying to understand how this working. > > Thanks, > DW If you look, sio2 and sio3 have been disabled in the kernel config. since= =20 sio0 and sio1 are assigned as hardware serial devices, the first available = is=20 sio4 that either hasn't been disabled or isn't in use. =20 HTH =2D-=20 Eric F Crist AdTech Integrated Systems, Inc (612) 998-3588 --Boundary-02=_pRoKAXFkxUERIng Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAKoRpzdyDbTMRQIYRAtFdAJ9YkjEAqB5jpiK2sZNY6wGiVW4Y5wCgvbUK miW+gR5VDd2bKM285dH/ib8= =9PNd -----END PGP SIGNATURE----- --Boundary-02=_pRoKAXFkxUERIng--