From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3) Date: Fri, 23 Nov 2007 19:20:01 -0500 Message-ID: <47476E31.2070801@garzik.org> References: <47463534.9010100@shaw.ca> <4746F02D.2060204@rtr.ca> <474711FE.8040805@rtr.ca> <47476CB9.2040409@shaw.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]:44105 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751755AbXKXAUK (ORCPT ); Fri, 23 Nov 2007 19:20:10 -0500 In-Reply-To: <47476CB9.2040409@shaw.ca> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Robert Hancock Cc: Mark Lord , "Morrison, Tom" , linux-kernel , ide , Tejun Heo Robert Hancock wrote: > Based on a quick look at sata_mv it appears it sets a 64-bit DMA mask > unconditionally, but for non-ATA_PROT_DMA commands (which includes all > ATAPI), it just falls back to ata_qc_issue_prot which issues via the > legacy SFF interface and can only handle 32-bit addressing. So yes, it > appears to have a similar bug as sata_nv had. sata_mv doesn't do ATAPI at all... Jeff