From: Robert Hancock <hancockr@shaw.ca>
To: Jeff Garzik <jeff@garzik.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Prakash Punnoor <prakash@punnoor.de>
Subject: Re: SATA status reports update
Date: Fri, 29 Sep 2006 21:30:07 -0600 [thread overview]
Message-ID: <451DE4BF.70906@shaw.ca> (raw)
In-Reply-To: <fa.BuZY3hsao85GkcEIgE6/7ZlG40A@ifi.uio.no>
Jeff Garzik wrote:
> Prakash Punnoor wrote:
>> Well, how would one debug it w/o hw docs? Or is it possible to compare
>> the patch with a working driver for another chipset?
>
> Well, it is based off of the standard ADMA[1] specification, albeit with
> modifications. There is pdc_adma.c, which is also based off ADMA. And
> the author (from NVIDIA) claims that the driver worked at one time, so
> maybe it is simply bit rot that broke the driver.
>
> If I knew the answer, it would be fixed, so the best answer
> unfortunately is "who knows".
>
> I wish I had the time. But I also wish I had a team of programmers
> working on libata, too ;-)
Do you know exactly what is allegedly broken in that version? I see that
there are some functions which are just "TODO"..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-09-30 3:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.qX++qRit8w9OM0g1pdrG/oO2vt0@ifi.uio.no>
[not found] ` <fa.Rp+FWnZ2aDKMZggJQPBaMZJIiTk@ifi.uio.no>
[not found] ` <fa.mf96kUVw9JlcVmzGTV5ysiCiT3E@ifi.uio.no>
[not found] ` <fa.qyxVQ/280iu/YZsbUzTDjAygfL4@ifi.uio.no>
[not found] ` <fa.BuZY3hsao85GkcEIgE6/7ZlG40A@ifi.uio.no>
2006-09-30 3:30 ` Robert Hancock [this message]
2006-09-30 3:41 ` SATA status reports update Jeff Garzik
[not found] ` <fa.l8JQ0qnQYteeWfINfpS73yv1OKw@ifi.uio.no>
2006-09-30 16:30 ` Robert Hancock
[not found] <fa.YaF1lJH12hP9W/r7m3pt7oXOeL4@ifi.uio.no>
[not found] ` <fa.g2Kx9MbD4ZVWpxAjjpedYrf09zM@ifi.uio.no>
[not found] ` <fa.b1vkqJfue4GOQ6qZfdh86ct/nDk@ifi.uio.no>
[not found] ` <fa.YmprXb8sC090DghGSt7gnlhfo2c@ifi.uio.no>
[not found] ` <fa.IewnjLanGhRn8aKEjkVZcxkolss@ifi.uio.no>
[not found] ` <fa.mQXoq13o43zcI4XRFyX1EjaYxI4@ifi.uio.no>
2006-09-30 22:09 ` Robert Hancock
2006-10-01 0:16 ` Tejun Heo
2006-09-29 9:35 Jeff Garzik
2006-09-29 9:49 ` Prakash Punnoor
2006-09-29 9:53 ` Jeff Garzik
2006-09-29 10:00 ` Prakash Punnoor
2006-09-29 10:03 ` Jeff Garzik
2006-09-30 7:26 ` Prakash Punnoor
2006-09-29 17:51 ` John Stoffel
2006-09-29 18:24 ` Alan Cox
2006-09-29 18:20 ` John Stoffel
2006-10-03 3:02 ` Shem Multinymous
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=451DE4BF.70906@shaw.ca \
--to=hancockr@shaw.ca \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prakash@punnoor.de \
/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