Re: [PATCH 2.6.21-rc1] sata_vsc: refactor vsc_sata_interrupt and hook up error handling

On Fri, Feb 23, 2007 at 04:36:43PM -0700, Dan Williams wrote: Separate sata_vsc interrupt handling into a normal (per-port) path and an error path with the addition of vsc_port_intr and vsc_error_intr respectively. The error path handles interrupt based hotplug events which requires the

pata_pcmcia takes long time to detect certain cf cards

Hello, pata_pcmcia takes a very long time to recognize a 1.0GB SanDisk CF card (MIPS, Au1200, linux-2.6.21-rc1): pccard: PCMCIA card inserted into slot 0 pcmcia: registering new device pcmcia0.0 ata1: PATA max PIO0 cmd 0xC0054000 ctl 0xC005400E bmdma 0x0 irq 5 scsi0 : pata_pcmcia ata1.00: CFA,

Re: [PATCH] (pata-2.6 fix queue) cmd64x: fix primary channel address setup time

Hello, I wrote: The driver used to merge the address setup timing for the secondary channel but this must have been done for both channels actually despite the primary channel had separate registers for each drive (I'afraid that this is too common mistake in both hardware and software --

Re: Current PATA working tree

Alan wrote: While Andrew and -mm are taking a bit of a break... I've uploaded a patch file of the libata PATA working tree versus 2.6.20-mm2 to http://zeniv.linux.org.uk/~alan/IDE Generated without --show-c-function. Sigh. - To unsubscribe from this list: send the line unsubscribe

[PATCH]Support for Marvell 7042 Chip

Added Support for Marvell 7042 Chip - 7042 has same capabilities behavior as 6042. Patch based upon stable Linux 2.6.20.1 Kernel Tree... Signed-off-by: Thomas A. Morrison [EMAIL PROTECTED] --- drivers/ata/sata_mv.c.orig 2007-02-20 01:34:32.0 -0500 +++ drivers/ata/sata_mv.c

[PATCH] (pata-2.6 fix queue) cmd64x: add back MWDMA support

Add back the multiword DMA support (I think nobody will miss single-word DMA). In order to do it, a number of changes had to be done: - rename program_drive_counts() to program_cycle_times(), pass to it cycle's total/active times instead of the clock counts, and convert them into the

Re: [RFT] sata_promise: intermittent errors bug hunting

Mikael Pettersson wrote: There have been some reports of intermittent errors with sata_promise, especially with newer disks. My theory is that the driver isn't initialisating the controller properly for SATAII 3Gbps transfer speeds. Just to confirm a working set-up with a 3Gbps capable

[ignore] am I still subscribed?

test (our mail server has been dead for 5 days..) - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [ignore] am I still subscribed?

Okay, once more, with *feeling* this time. (resubscribed.. hopefully I'll see my own shadow this time). - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

[RFT] sata_promise: decode and report error reasons

This is a preliminary patch to add error reason decoding and reporting to sata_promise. It's fairly simplistic but should log all error info the controller is able to provide. Works for me, but my test rig hardly ever throws any errors. Testing by those that experience frequent errors would be

Marvell 6145 SATA via AHCI

I'm trying Jeff Garzik's preliminary Marvell 6145 SATA support patch and getting nowhere so I'm just checking to see if anyone has got it working or if there have been any further developments. Basically, I'll get failed to IDENTIFY messages for each of the drives when the module loads. If I

Adaptec 1220SA (Sil3132) sata_sil24 question

I have an Adaptec 1220SA which I originally thought was just a re-badged Sil3132 design. Externally it appears that way (the stamp on the chip reads 3132), however it identifies as a Silicon Image type 0x0242 according to lspci. sata_sil24 does not attach. I made the trivial addition to

Re: end to end error recovery musings

Martin K. Petersen wrote: Alan == Alan [EMAIL PROTECTED] writes: Not sure you're up-to-date on the T10 data integrity feature. Essentially it's an extension of the 520 byte sectors common in disk [...] Alan but here's a minor bit of passing bad news - quite a few older Alan ATA

RE: end to end error recovery musings

On Tuesday, February 27, 2007 12:07 PM, Martin K. Petersen wrote: Not sure you're up-to-date on the T10 data integrity feature. Essentially it's an extension of the 520 byte sectors common in disk arrays. For each 512 byte sector (or 4KB ditto) you get 8 bytes of protection data. There's

Re: end to end error recovery musings

Doug == Douglas Gilbert [EMAIL PROTECTED] writes: Doug Work on SAT-2 is now underway and one of the agenda items is Doug end to end data protection and is in the hands of the t13 Doug ATA8-ACS technical editor. So it looks like data integrity is on Doug the radar in the SATA world. It's cool