Re: [PATCH] Experimental IDE oops dumper v0.1

Alan Cox (alan@redhat.com)
Mon, 16 Sep 2002 08:18:07 -0400 (EDT)


> + /* Pause (at least 400ns) in case we just issued a command */
> + oopser_usec(1);
> + for (i = 0; i < 1000; i++) {
> + b = inb(HD_STATUS);
> + if (!(b & BUSY_STAT)) {
> + if (b & ERR_STAT) return 0;
> + if (b & flag) return 1;
> + }
> + oopser_usec(1000);

This will stop working on SATA when VDMA goes into newer controllers btw.

> + /* Bits 24-27, 0x40=LBA, 0x10=slave */
> + if (!wait_before_command()) return -EIO;
> + outb(0x40 | (master ? 0 : 0x10) | ((lba >> 24) & 0x0F), HD_CURRENT);

Doesn't work for LBA48

> + if (!wait_before_command()) return -EIO;
> + outb(0x40 | (master ? 0 : 0x10) | ((lba >> 24) & 0x0F), HD_CURRENT);

Ditto

> +/* Called with interrupts off */
> +int oopser_read_ide(char dump[512], unsigned int block)
> +{
> + /* Wait for non-busy: if not, reset anyway */
> + wait_before_command();
> + /* Soft reset of drive (set nIEN as well) */
> + outb(0x0e, HD_CMD);

Be careful here - one or two drives get nIEN backwards, you might just
want to turn off interrupts and be done with it

> + oopser_usec(1); /* 400ns according to spec */
> + outb(0x0a, HD_CMD);

You really need to reset and reprogram/retune the controller as well.

I like the infrastructure but the IDE dumper code is wishful thinking
in one or two spots. You don't know f the controller is in DMA modes,
tuned for different things to the drives or legacy free. Im not sure what
to do for legacy free cases but the other bits like LBA48 and retuning
probably can be handled with some small chipset specific hooks

Alan
-
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/