From owner-cvs-src@FreeBSD.ORG Thu Jul 29 23:52:22 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A27C916A4CE; Thu, 29 Jul 2004 23:52:22 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E1F543D45; Thu, 29 Jul 2004 23:52:22 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-94.dsl.snfc21.pacbell.net [64.171.186.94]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i6TNqHra020587; Thu, 29 Jul 2004 16:52:17 -0700 Message-ID: <41098DB1.8070500@root.org> Date: Thu, 29 Jul 2004 16:52:17 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7 (X11/20040702) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Oppermann References: <200407282235.i6SMZfdU014440@repoman.freebsd.org> <4108C179.D4FF44B1@freebsd.org> <41094638.3020807@root.org> <41097F65.E12A75E1@freebsd.org> In-Reply-To: <41097F65.E12A75E1@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/fdc fdc_acpi.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 23:52:22 -0000 Andre Oppermann wrote: > Nate Lawson wrote: > >>Andre Oppermann wrote: >>>Is there any kind of feedback chain towards the BIOS authors so they might >>>fix it in the next release? >> >>A few people had success getting problems with a ServerWorks board fixed >>in the next BIOS revision. But most of the time, the chance is 0. All >>we can do is work around the issue (like here) or disable it for the >>given board (Windows often does this also). > > And feeding it back to Phoenix etc.? Or don't they provide these parts of > the BIOS? I have no idea who does which parts of the BIOS. The OEM (i.e. VIA, ASUS, IBM, COMPAL, etc.) is responsible for the BIOS for a specific board. But they usually subcontract out a lot of this work and a lot of it is cut/pasted from reference BIOS implementations. It's difficult to identify who did which parts of the actual work behind a given board. Assuming you are a large enough customer (say, Yahoo), you find the problem and complain to your rep, who sometimes can get a fix rolled in. For one laptop I have, IBM fixed some major embedded controller problems in later BIOS revisions (not my doing.) However, another laptop I have (Sony) has never had a single BIOS revision issued. So in general, there is little chance of us doing anything. -Nate