From owner-freebsd-current Wed Dec 20 17:26:27 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 20 17:26:25 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id D552237B402 for ; Wed, 20 Dec 2000 17:26:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.1+3.4W/8.11.1) with ESMTP/inet id eBL1QH849050; Thu, 21 Dec 2000 10:26:18 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: current@FreeBSD.ORG In-Reply-To: <200012201942.MAA10802@harmony.village.org> References: <20001221021801G.matusita@jp.FreeBSD.org> <200012201805.eBKI5is41536@billy-club.village.org> <200012201942.MAA10802@harmony.village.org> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Peisino,Ak(B) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 20 From: Makoto MATSUSHITA To: imp@village.org Subject: Re: Why 'lnc.ko' instead of 'if_lnc.ko' ? Date: Thu, 21 Dec 2000 10:26:12 +0900 Message-Id: <20001221102612F.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG imp> This is a good start at a fix. However, all the attachments for the imp> lnc device also need to be called if_lnc. And they need to share the imp> same devclass_t so that unit numbers don't go wonky on you (eg, if you imp> have a isa and a pci lnc card in the same system, you might get two imp> lnc0's). Hmm, fixing these are beyond my skill... *** BTW, are there anybody working on 'pcn' (yet another lance driver) to work with VMware ? Current 5-current installation floppy makes VMware panic (caution: FreeBSD doesn't panic), and it is maybe caused by pcn driver when it knocks VMware pseudo ethernet device in 32bit mode. Note that FreeBSD 4-stable works well with VMware, so maybe there are hints in the differences between 4-stable and 5-current. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message