From owner-freebsd-mobile@FreeBSD.ORG Thu Jan 22 09:33:46 2004 Return-Path: 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 6A9EA16A4CE for ; Thu, 22 Jan 2004 09:33:46 -0800 (PST) Received: from ns1.san.rr.com (66-27-66-186.san.rr.com [66.27.66.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3793643D2D for ; Thu, 22 Jan 2004 09:33:45 -0800 (PST) (envelope-from amrx@ns1.san.rr.com) Received: from ns1.san.rr.com (localhost [127.0.0.1]) by ns1.san.rr.com (8.12.10/8.12.10) with ESMTP id i0MHZwii058762; Thu, 22 Jan 2004 09:35:58 -0800 (PST) (envelope-from amrx@ns1.san.rr.com) Received: (from amrx@localhost) by ns1.san.rr.com (8.12.10/8.12.10/Submit) id i0MHZwOQ058761; Thu, 22 Jan 2004 09:35:58 -0800 (PST) (envelope-from amrx) Date: Thu, 22 Jan 2004 09:35:58 -0800 From: Andrew Marks To: Anish Mistry Message-ID: <20040122173558.GA58737@mail.san.rr.com> References: <200401220305.i0M35k70055296@ns1.san.rr.com> <20040122170950.GA58577@mail.san.rr.com> <200401221216.21506.mistry.7@osu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200401221216.21506.mistry.7@osu.edu> User-Agent: Mutt/1.4.1i X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on mail.san.rr.com cc: freebsd-mobile@freebsd.org Subject: Re: Forgotten Subject, non-working devices on my Fujitsu P2120 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 17:33:46 -0000 > I don't believe this an issue, I also see this on my 2110, but can't figure > out what feature this matches up to, so it should be fine. Yes, I don't think these really matter too much > I invesitgated this serveral months ago on my 2110, and figured out there > is no FreeBSD driver for this chipset, and was unable to find the > datasheet that used to be available on acerlabs.com (they would return any > of my contact attempts), but which now is not :(. If some does have this > datasheet I'd be willing to put the time to get this driver working. I'll try my hand at getting the data sheet, it can't hurt. > I wish I had a 2120 to diagnose this problem since it is 2120 specific. I tried stepping through the boot process in ddb, but without much experience with ddb, and apparently no symbols (all I got was addresses) I didn't get very far. I would be happy to be your hands on the keyboard for this one, if you would be willing to instruct me. > > -- > Anish Mistry