RE: 2.5.69, IDE TCQ can't be enabled

Andre Hedrick (andre@linux-ide.org)
Tue, 13 May 2003 13:34:44 -0700 (PDT)


Correct no drives shipped.

Maxtor failed to move forward in updating the device side TCQ.
I will have to look up my email record to give you who I was working with
and talking to about the issues. I do know it was in the Longmont
division.

The last discussion I had with Maxtor releated in forcing the state
machine to default to bus release on execution of the command block.
This would fix the the gaping hole in the protocol. The effects from this
single change were not fully white board material, and may have addressed
or covered the other two pitfalls.

Drop the ball, meaning it was started and then tabled.
Tabled because of SATA/SAS.

Comments?

Andre Hedrick
LAD Storage Consulting Group

On Tue, 13 May 2003, Mudama, Eric wrote:

>
>
> -----Original Message-----
> >From: Andre Hedrick [mailto:andre@linux-ide.org]
> >Sent: Tuesday, May 13, 2003 2:04 PM
> >To: Jens Axboe
> >Cc: Jeff Garzik; Dave Jones; Mudama, Eric; Oleg Drokin; Bartlomiej
> >Zolnierkiewicz; Alan Cox; Oliver Neukum; lkhelp@rekl.yi.org;
> >linux-kernel@vger.kernel.org
> >Subject: Re: 2.5.69, IDE TCQ can't be enabled
> >
> >Why are we still dorking around with device TCQ.
> >There are three holes in the state machine.
> >IBM's design (goat-screw) is lamer than a duck.
> >Maxtor thought about redoing TCQ, to not leave the host in a daze but
> >dropped the ball.
>
> What ball, exactly, did we drop? We have yet to ship a TCQ drive because we
> think we can get it "right" but it is taking us time, in our view, to do
> properly.
>
> --eric
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/