From owner-freebsd-hardware Mon Nov 10 11:34:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA22680 for hardware-outgoing; Mon, 10 Nov 1997 11:34:22 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from grayling.erg.sri.com (grayling.erg.sri.com [128.18.4.194]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA22667 for ; Mon, 10 Nov 1997 11:34:19 -0800 (PST) (envelope-from templin@erg.sri.com) Received: by grayling.erg.sri.com (8.6.12/2.7davy) id LAA23754; Mon, 10 Nov 1997 11:34:26 -0800 Message-Id: <199711101934.LAA23754@grayling.erg.sri.com> Date: Mon, 10 Nov 1997 11:34:26 -0800 From: "Fred L. Templin" To: nate@mt.sri.com Cc: hardware@freebsd.org, kelvin@uni.net.hk Subject: Re: PCMCIA card support list Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate, > Actually, no. Xircom won't give out programming information on their > network cards, hence there is no driver for them. The 'modem' cards are > the same as everyone else's, but we don't recommend anyone buying them > due to the programming problems on everything else they make. That's right - I now remember seeing the comment about FreeBSD not supporting Xircom because of their closed architecture. This brings to mind an interesting question, however: when I finish the NetWave radio driver, will the FreeBSD community even want a copy for integration into the source tree? If not, I suppose I'll have to handle release engineering on my own. I understand (and support) where the FreeBSD community is coming from on this issue, and am somewhat chagrined at being stuck with developing a public-domain driver to a proprietary interface... Fred templin@erg.sri.com