Hi Jeff,
a quick question about libata + sata_via V1.10 as included in the most
recent kernel 2.6.11.2:
I have a MSI KT6V (MS-7021) mainboard with VIA VT-8237 Southbridge and want
to connect two S-ATA hard disk drives. Both drives should run in a RAID 0
array, which is to be configured through
good catch, I overlooked lba48 flag when introducing no_lba48_dma
I slightly modified your patch:
diff -Nru a/drivers/ide/ide-disk.c b/drivers/ide/ide-disk.c
--- a/drivers/ide/ide-disk.c2005-03-10 16:07:50 +01:00
+++ b/drivers/ide/ide-disk.c2005-03-10 16:07:50 +01:00
@@ -168,6 +168,8 @@
On Thu, Mar 10, 2005 at 05:30:12PM +0100, Bartlomiej Zolnierkiewicz wrote:
On Tue, 8 Mar 2005 14:33:58 +0100, Tobias Klauser [EMAIL PROTECTED] wrote:
Description: Use the DMA_{64,32}BIT_MASK constants from dma-mapping.h
when calling pci_set_dma_mask() or pci_set_consistent_dma_mask()
See
Hi,
On Thu, 3 Mar 2005 11:16:38 +0900, Tejun Heo [EMAIL PROTECTED] wrote:
+ [2] Both the input and output buffers are copied from the
+ user and written back to the user, even when not used. The
+ out_flags and in_flags are written back to the user after
+
As you might remember, the 3112 was giving us grief by sending a flood
of interrupts when doing the IDENTIFY ATAPI DEVICE (0xA1) command.
This was on a rev 1,1 chip.
When we tried a rev 1.21 chip, the problem was corrected.
Now it appears that even the rev 1.21 chip will flood us with
Brett Russ wrote:
Jeff Garzik wrote:
I checked the attached patch into a local repository, but haven't yet
merged it into libata-dev-2.6, or tested it.
Jeff,
The below works for me in testing. Can you push into libata-2.6?
pulled
-
To unsubscribe from this list: send the line unsubscribe
Updated libata 2.4.x branch to 2.4.30-pre3.
Patch URL, BK URL, and list of changes attached.
Jeff
BK users:
bk pull bk://gkernel.bkbits.net/libata-2.4
Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.4.30-pre3-libata1.patch.bz2
This will update the
Hi, I've just installed a Plextor PX-716SA in my server, and I'm having
trouble with it. I can do eject/load with the eject utility, and I can
mount DVDs and list the contents, but burning doesn't work at all.
Instead of burning start, the drive locks, and I get:
Mar 10 17:15:37 [kernel] SCSI
