From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 23:41:54 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70C5016A420 for ; Mon, 6 Mar 2006 23:41:54 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-4.paradise.net.nz (bm-4a.paradise.net.nz [203.96.152.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id E413243D6E for ; Mon, 6 Mar 2006 23:41:47 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-3.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-4.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IVQ0087TCHLSF@linda-4.paradise.net.nz> for freebsd-hardware@freebsd.org; Tue, 07 Mar 2006 12:41:45 +1300 (NZDT) Received: from [192.168.1.11] (218-101-29-158.dsl.clear.net.nz [218.101.29.158]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 6EB521AF49C for ; Tue, 07 Mar 2006 12:41:45 +1300 (NZDT) Date: Tue, 07 Mar 2006 12:41:43 +1300 From: Mark Kirkwood To: freebsd-hardware@freebsd.org Message-id: <440CC8B7.4090708@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) Subject: Add warning notes for known quirkly ata chipsets X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Mar 2006 23:41:54 -0000 Do folks think that amending the ata(4) man page, and adding warnings beside known quirky or broken chipsets is a good idea? I'm thinking of Si 3112 here in particular(!) - the aim being to discourage folks from buying 'em based on the fact they appear in ata(4). I'm happy to draft up something - altho I'd be pretty basic like: Silicon Image: SiI0680, SiI3112 (see NOTES), SiI3114, SiI3512. Notes: .... There have been reports of data corruption and erratic behavior with some chipsets. This seems to be related to deficiencies with the chipset design rather than the driver code. It is recommended to avoid these. A list of known problematic chipsets is: SiI3112,... I don't know any others offhand - but if a) the basic idea seems sensible and b) people mail me with well documented cases, I'd be happy to add 'em! Finally, I'm bringing this up now, as 6.1 is out soon, and it seemed a good time :-) regards Mark