Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata atapi work #5
Date: 14 May 2004 13:27:25 -0600	[thread overview]
Message-ID: <1084562845.8752.37.camel@patibmrh9> (raw)
In-Reply-To: <40A5195C.2000402@pobox.com>

> Read up in the SATA docs ...

Will do at t13.org ...

> Reading your emails, you sound like a "hardware guy" to me :)

Yes.

Kind of you to celebrate my sanity. :-)

Specifically, I was salaried in 1994..1999 mostly to write device
firmware: SCSI/ PPT/ ATAPI/ USB/ FireWire/ etc.  But often for test &
once to ship I wrote the host-side of the cable too, most recently x86
PATA UDMA.

Also I helped write the usb.org USB/ATAPI bridge spec, so I find serial/
parallel conversion familiar.  And always my employer mass-produced one
basic drive and then added bridges to support other kinds of cabling, so
bridging to PATA ATAPI was my whole world in 1997..1999.

Pat LaVarre
http://sourceforge.net/projects/iomrrdtools/
http://members.aol.com/plscsi/tools/pldd/
http://members.aol.com/plscsi/



  reply	other threads:[~2004-05-14 19:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14 18:42 [PATCH] libata atapi work #5 Pat LaVarre
2004-05-14 19:09 ` Jeff Garzik
2004-05-14 19:27   ` Pat LaVarre [this message]
2004-05-14 19:47     ` Jeff Garzik
2004-05-14 20:00       ` Pat LaVarre
2004-05-14 20:14         ` Leon Woestenberg
2004-05-14 20:15         ` Jeff Garzik
2004-05-14 20:23           ` Leon Woestenberg
2004-05-14 20:29             ` Jeff Garzik
2004-05-14 23:09           ` Pat LaVarre
2004-05-15  0:01           ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2004-05-14 18:26 Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1084562845.8752.37.camel@patibmrh9 \
    --to=p.lavarre@ieee.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox