On 10/30/07, Michael Tokarev [EMAIL PROTECTED] wrote:
By the way, did you forget to remove a jumper on the drive
(the only jumper installed by default) that limits drive
usage to SATAI?
...
..etc. Try again without the jumper? Note that NCQ is NOT supported
in SATAI mode, or there were
On 2/23/07, Alan [EMAIL PROTECTED] wrote:
Code looks OK. Not applied due to for testing note.
General comment: it might be nice to do this in the core, just as a
sanity check for a variety of problems, past, present and future.
We tried that with old IDE and all hell broke loose. Lots of
On 2/15/07, Albert Lee [EMAIL PROTECTED] wrote:
Some Maxtor drives have Maxtor and others have MAXTOR in the identify
device data.
If the slave is a MAXTOR one, the following code segment doesn't work.
The 6L drive is a design brought over from Maxtor's purchase of
Quantum, the 6Y is a Maxtor
On 2/2/07, Mark Lord [EMAIL PROTECTED] wrote:
7 seconds is not enough for current drives to report back.
Adding another (8 seconds total) is enough, but I prefer to
see a little margin there, so call it 10 seconds.
If you're going to allow 30 seconds (or more) for a cache flush, you
probably
On 2/1/07, Steven Scholz [EMAIL PROTECTED] wrote:
Hi all,
I am seeing kernel messages like
[ 1284.48] hda: status timeout: status=0xd0 { Busy }
[ 1284.48] ide: failed opcode was: unknown
[ 1284.48] hda: no DRQ after issuing MULTWRITE_EXT
[ 1284.49] ide0: unexpected interrupt,
On 1/30/07, Steven Scholz [EMAIL PROTECTED] wrote:
I have connected HDD's A[2..0] to CPU's A[3..1] and do something like
for (i = IDE_DATA_OFFSET; i = IDE_STATUS_OFFSET; i++) {
hw.io_ports[i] = ide_virt_base + (i 1);
}
thus all HDD registers are accessed on a
On 1/30/07, Sergei Shtylyov [EMAIL PROTECTED] wrote:
Steven Scholz wrote:
How could one then explain
current capacity is 78140160 sectors would be 0x04A85300
native capacity is 185074430006016 sectors would be0xA852FFA85300
? First three bytes ok, then the other three
Maxtor 6V100E0 VA11 PQ: 0 ANSI: 5
Signed-off-by: Eric D. Mudama [EMAIL PROTECTED]
---
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index a388a8d..7dc4dad 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -1607,6 +1607,7 @@ int ata_dev_configure
SCSI only supports a 4-character firmware revision string, while ATA
uses 8 characters. Record this firmware revision string into dmesg.
Signed-off-by: Eric D. Mudama [EMAIL PROTECTED]
---
Patch is against 2.6.20-rc6 pull via GIT. Resubmitting to (hopefully)
fix linewrap and bad formatting
Per Jeff's suggestion, this patch rearranges the info printed for ATA
drives into dmesg to add the full ATA firmware revision and model
information, while keeping the output to 2 lines.
Signed-off-by: Eric D. Mudama [EMAIL PROTECTED]
---
This extra information is helpful for debugging drive
On 1/16/07, Jeff Garzik [EMAIL PROTECTED] wrote:
ISTR either Jens or Andrew ran some numbers, and found that there was
little utility beyond 4 or 8 tags or so.
Write cache is effectively queueing small writes already, so NCQ
simply brings random read performance closer to writes.
I know on
On 11/28/06, Sergei Shtylyov [EMAIL PROTECTED] wrote:
Hello.
Mark Lord wrote:
Bit #4, when actually implemented, is a rotational seek indicator,
which can be used for timing purposes.
Hm, I thought it was DSC (drive seek complete) set by the SEEK command
completion, and it's always
we'd need to see the dmesg output I am sure
On 8/16/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
My Maxtor Hard Disk supports UDMA = 6 (133)
How can I control BITS options in controller ? What's line command ?
How can I verify controller is properly configured in my kernel ?
--
13 matches
Mail list logo
