From owner-freebsd-mobile@FreeBSD.ORG Mon Dec 13 15:27:15 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 DFAEF16A4CE for ; Mon, 13 Dec 2004 15:27:15 +0000 (GMT) Received: from smtp-sv.canvas.ne.jp (smtp-sv.canvas.ne.jp [210.172.56.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31CA943D2D for ; Mon, 13 Dec 2004 15:27:15 +0000 (GMT) (envelope-from colinp@mx3.canvas.ne.jp) Received: from canvas.ne.jp (unknown [192.168.100.61]) by smtp-2.canvas.ne.jp (Postfix) with SMTP id 9FF2015EA1E for ; Tue, 14 Dec 2004 00:27:13 +0900 (JST) Received: (qmail 19674 invoked from network); 14 Dec 2004 00:27:13 +0900 Received: from unknown (HELO mail.mx3v.canvas.ne.jp) (192.168.100.53) by vc1d with SMTP; 14 Dec 2004 00:27:13 +0900 Received: from [127.0.0.1] (unknown [202.71.91.13]) by mail.mx3v.canvas.ne.jp (Postfix) with ESMTP id 3A48D2C2B; Tue, 14 Dec 2004 00:27:13 +0900 (JST) Message-ID: <41BDB499.4050103@mx3.canvas.ne.jp> Date: Tue, 14 Dec 2004 00:26:17 +0900 From: Colin Peters User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: ja, en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20041209120101.DF76716A4E3@hub.freebsd.org> <41B9CFDC.3040305@mx3.canvas.ne.jp> <20041212.110236.12174219.imp@bsdimp.com> In-Reply-To: <20041212.110236.12174219.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: corega FEtherII PCC-TXD 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: Mon, 13 Dec 2004 15:27:16 -0000 Hi. Thanks for responding. M. Warner Losh wrote: >: Now I will try to figure out where these functions are called and why >: the flags are cleared between them. Perhaps it would be better to call >: match again at the beginning of probe (or use a similar approach to >: determine the device type at probe time)? > >You aren't allowed to set flags in the probe routine. Look things up >again in the attach routine... You'll be a lot happier. > >Warner > > > After a little more looking at the docs that's what I ended up thinking should be done. I'm not exactly sure I'll be able to do it (the ed probe routine seems to mix probing and initialization), but I'll give it a try in the near-ish future. I think I may have quite a few questions if I start trying to do this right instead of just doing whatever gets my card working. Colin.