From owner-freebsd-mobile Sun Jan 9 17:43:23 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8419514E06 for ; Sun, 9 Jan 2000 17:43:16 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA28363; Sun, 9 Jan 2000 18:43:08 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA01312; Sun, 9 Jan 2000 18:43:08 -0700 (MST) Message-Id: <200001100143.SAA01312@harmony.village.org> To: Dominik Brettnacher Subject: Re: support for 3Com 3C563D Cc: mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 09 Jan 2000 13:23:32 +0100." References: Date: Sun, 09 Jan 2000 18:43:08 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Dominik Brettnacher writes: : Does FreeBSD support the 3Com 3C563D? FreeBSD-current appears to support it. I have one of these cards that I borrowed at FreeBSD CON'99. I didn't get a dongle with it and I damaged it on the way home, but when I insert mine into my laptop, it gets as far as getting its dhcp address, but won't pass traffic. Don't know if this is the cards fault or the driver's. This is with -current only, since -stable doesn't have support for it iirc. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message