From: Alan Cox <alan@redhat.com>
To: Ian Hastie <ianh@iahastie.clara.net>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Alan Cox <alan@redhat.com>
Subject: Re: PATCH: Add support for IT8212 IDE controllers
Date: Sun, 1 Aug 2004 16:10:42 -0400 [thread overview]
Message-ID: <20040801201042.GC20007@devserv.devel.redhat.com> (raw)
In-Reply-To: <200408012022.42516.ianh@iahastie.local.net>
On Sun, Aug 01, 2004 at 08:22:28PM +0100, Ian Hastie wrote:
> ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio
> it8212: controller in RAID mode.
>
> That doesn't. I have no RAID sets defined in the IT8212 card BIOS. BTW, the
The controller runs in RAID mode on the "smart" cards even without raid
definitions being used - its still doing the hardware assist.
> ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:pio, hdh:pio
> hde: Maxtor 6Y120P0, ATA DISK drive
> it8212: selected 50MHz clock.
>
> Nor does this as it really should be using the 66MHz clock setting.
Currently it always picks 50MHz, thats a feature I'm still working on
adding intelligence to
> ide2 at 0xb000-0xb007,0xa802 on irq 17
> hde: max request size: 128KiB
> hde: recal_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: recal_intr: error=0x04 { DriveStatusError }
>
> Any idea what could be causing this? My hacked driver doesn't get this in
> 2.6.7, but then it could be a 2.6.8 problem.
It was sent a command it didnt know.
The UDMA33 speed behaviour looks to me like cable detect got the wrong
answer. The reference driver doesn't actually do host side cable detect
so it may be that its in the docs but doesn't actually work or isnt wired
on the boards. Can you see what the ata66 function is doing ?
next prev parent reply other threads:[~2004-08-01 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-31 23:22 PATCH: Add support for IT8212 IDE controllers Alan Cox
2004-08-01 19:22 ` Ian Hastie
2004-08-01 20:10 ` Alan Cox [this message]
2004-08-01 23:05 ` Alan Cox
2004-08-06 0:45 ` Ian Hastie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040801201042.GC20007@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=ianh@iahastie.clara.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).