From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 8 May 2002 16:38:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 8 May 2002 16:38:30 -0400 Received: from astound-64-85-224-253.ca.astound.net ([64.85.224.253]:29198 "EHLO master.linux-ide.org") by vger.kernel.org with ESMTP id ; Wed, 8 May 2002 16:38:28 -0400 Date: Wed, 8 May 2002 13:36:14 -0700 (PDT) From: Andre Hedrick To: Alan Cox cc: Benjamin Herrenschmidt , Linus Torvalds , Martin Dalecki , Bjorn Wesen , Paul Mackerras , Kernel Mailing List Subject: Re: [PATCH] IDE 58 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 8 May 2002, Alan Cox wrote: > > I though about that, but what about corner cases where only a single > > register can be accessed ? (typically alt status). Provide specific > > routines ? Also, how does the extended addressing works ? by writing > > several times to the cyl registers ? That would have to be dealt with > > as well in each host driver then. > > There are lots of cases we don't care about speed - things like setup of > the controller, changing UDMA mode etc. Erm, think about the state diagram for testing the acceptance and command migration if TAG is going to be standard. > Begin a disk write > Begin a disk read test command accept/reject repeat 'til done: check_status > PIO transfer in > PIO transfer out io hardware atomic segment or burst (for linus, "atomic" is what is needed to complete, not just linusism") goto repeat if !done with entire request The above is where data integrity is lost if error happens. > End a disk I/O fastpaths (no error case) > > Maybe ATAPI command writes ? > > beyond that I doubt the rest are critical There are several other cases, but 95% is the command block execution. The rest is sense data. Cheers, Andre Hedrick LAD Storage Consulting Group