From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH] sata_mv: Fix broken Marvell 7042 support. Date: Wed, 05 Dec 2007 23:43:59 -0500 Message-ID: <47577E0F.1030709@pobox.com> References: <4751A2DA.6030403@rtr.ca> <20071203154749.6lah7pulw8ow0s84@email.syntomax.com> <47543C58.4040106@rtr.ca> <475447A0.2010101@rtr.ca> <47544B3C.2010901@rtr.ca> <1196712661.6362.5.camel@liza> <475465F7.7050705@rtr.ca> <1196714235.6362.9.camel@liza> <47546CF6.30301@rtr.ca> <1196722124.6362.17.camel@liza> <20071203231057.39ae9b71@the-village.bc.nu> <1196726490.6362.21.camel@liza> <47549A26.6080900@rtr.ca> <1196727475.6362.27.camel@liza> <47549E0B.9070509@rtr.ca> <1196812599.6909.10.camel@liza> <47572A18.2010904@rtr.ca> <475732C0.2090901@rtr.ca> <475735B4.7020401@rtr.ca> <47573A54.5000004@rtr.ca> <47573C16.7010704@pobox.com> <47577499.7000004@rtr.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:49764 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751004AbXLFEoS (ORCPT ); Wed, 5 Dec 2007 23:44:18 -0500 In-Reply-To: <47577499.7000004@rtr.ca> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Mark Lord Cc: Hein-Pieter van Braam , Alan Cox , "Morrison, Tom" , IDE/ATA development list , Tejun Heo , Alan Cox Mark Lord wrote: > Jeff Garzik wrote: >> Mark Lord wrote: >>> To do so, requires that we perhaps do a similar capacity truncation >>> in sata_mv, but only if we see a metadata block at the expected location >>> (because a "Legacy" mode drive will use the *real* capacity, >>> placing the metadata in the 9th sector instead. >> >> Definitely _not_. This is a core Linux maxim: export what the >> hardware exports, no more no less. We drive the "bare metal." > .. > > The hardware limitation here is the SATA controller card: > it corrupts data at the last GB boundary. The BIOS does that, not the controller card. If you pop the BIOS chip or plug the card into a non-x86 box (or any of several other alternatives), the problem is likely to go away. Jeff