Skip to contentSkip to conversation

SATA status reports update

DISCUSSION Robert Hancock 2 participants 3 messages Sep 30, 2006 6 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): fa.qX++qRit8w9OM0g1pdrG/[email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): fa.qyxVQ/280iu/[email protected]

A message that is not in the archive (sent off-list or not yet received): fa.BuZY3hsao85GkcEIgE6/[email protected]

#5 lore raw
Quoted 8 lines · Jeff Garzik
Quoted 1 line · Prakash Punnoor

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"..

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
#6 lore raw
Quoted 11 lines · Robert Hancock
Quoted 8 lines · Jeff Garzik
Quoted 1 line · Prakash Punnoor

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"..

I just know it was a working driver at one time.

Jeff

A message that is not in the archive (sent off-list or not yet received): [email protected]

#8 lore raw
Quoted 10 lines · Prakash Punnoor

Am Freitag 29 September 2006 12:03 schrieb Jeff Garzik:

Quoted 7 lines
Quoted 2 lines · Prakash Punnoor

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.

Well, I tried to hack the patch into 2.6.18 driver, but wasn't very successful. It migt be also due to the case that I have a MCP51 chipset and if I read the patch correctly it isn't designed to activate ADMA on MCP51. Do you know whether MCP51 knows ADMA? If not, how is NCQ to be activated on MCP51? According to nvidia.com and windows user reports MCP51 does know NCQ.

The same Windows driver supports all of:

CK804SSS="NVIDIA nForce4 Serial ATA Controller" MCP51S="NVIDIA nForce 430/410 Serial ATA Controller" MCP55S="NVIDIA nForce 590/570/550 Serial ATA Controller"

From looking at the patch it seems to only use the ADMA code for CK804 only. Probably the others use the same programming interface (though who knows if they implemented a totally different one in the same Windows driver). I guess you could try hacking it to use ADMA on that controller and see what happens..

I have an nForce4 board and it would be nice if we could have working NCQ, though I haven't really played with libata before. I may experiment with it a bit, though - Jeff, what kernel was this patch against? It obviously won't apply to current -mm, that nv_host_desc structure it is patching is gone for one thing..

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/