Date: Thu, 21 Dec 2000 10:26:12 +0900 From: Makoto MATSUSHITA <matusita@jp.FreeBSD.org> To: imp@village.org Cc: current@FreeBSD.ORG Subject: Re: Why 'lnc.ko' instead of 'if_lnc.ko' ? Message-ID: <20001221102612F.matusita@jp.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001221102612F.matusita>