From owner-freebsd-current Sat Aug 18 16:21:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 79C4E37B403 for ; Sat, 18 Aug 2001 16:21:50 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f7INQ3S02916; Sat, 18 Aug 2001 16:26:08 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108182326.f7INQ3S02916@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ilmar S. Habibulin" Cc: current@freebsd.org Subject: Re: where can i find info on supported MB chipsets In-reply-to: Your message of "Fri, 17 Aug 2001 04:54:30 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Aug 2001 16:26:03 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Subj. I can browse through code (and i do so), looking for chip IDs and > comparing them with chipset ones, but it's sometimes difficult, because > not all chip IDs in chipsets are know to me. So maybe driver developers > know more than i do? > I want to buy VIA Apollo KT266 based MD for Athlon, but as i understand > it is unsupported right now. So i think that supported chipsets info will > be usefull. Chipsets are supported by default, unless they are so stupid and broken that they actually require software support. Note that it's been a very, very long time since we met a chipset that actually required driver support. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message