From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, bzolnier@gmail.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.19-rc1] Toshiba TC86C001 IDE driver
Date: Wed, 13 Dec 2006 17:16:45 +0300 [thread overview]
Message-ID: <45800B4D.8000906@ru.mvista.com> (raw)
In-Reply-To: <20061212234145.557cb035@localhost.localdomain>
Hello.
Alan wrote:
>>+ * We work around this by initiating dummy, zero-length DMA transfer on
>>+ * a DMA timeout expiration. I found no better way to do this with the current
> Novel workaround and probably better than resetting the chip as the
> winbong does.
I didn't try resetting however the datasheet suggests it just won't do.
>>+static int tc86c001_busproc(ide_drive_t *drive, int state)
>>+{
> Waste of space having a busproc routine. The maintainer removed all the
> usable hotplug support from old IDE so this might as well be dropped.
Don't know what you mean, ioctl is still there...
>>@@ -1407,6 +1407,24 @@ DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_IN
>> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_INTEL, 0x260a, quirk_intel_pcie_pm);
>> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_INTEL, 0x260b, quirk_intel_pcie_pm);
>>+/*
>>+ * Toshiba TC86C001 IDE controller reports the standard 8-byte BAR0 size
>>+ * but PIO transfer won't work if BAR0 falls at the odd 8 bytes.
>>+ * Re-allocate the region if needed.
>>+ */
> NAK. I think this fixup should be testing if the device port 0 is in
> native mode before doing the fixup. In comaptibility mode bar 0 is
The chip is native mode only.
> "Close but no cookie": please fix the PCI quirk to match the current -mm
> behaviour with the ATA resource tree. Otherwise - nice driver.
Ugh, I should've expected some backstab from -mm tree...
> Alan
WBR, Sergei
next prev parent reply other threads:[~2006-12-13 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 22:48 [PATCH 2.6.19-rc1] Toshiba TC86C001 IDE driver Sergei Shtylyov
2006-12-12 22:57 ` Sergei Shtylyov
2006-12-12 23:00 ` Randy Dunlap
2006-12-12 23:07 ` Sergei Shtylyov
2006-12-12 23:12 ` Randy Dunlap
2006-12-12 23:41 ` Alan
2006-12-13 1:09 ` Bartlomiej Zolnierkiewicz
2006-12-13 11:32 ` Alan
2006-12-13 14:01 ` Bartlomiej Zolnierkiewicz
2006-12-13 14:16 ` Alan
2006-12-13 14:19 ` Bartlomiej Zolnierkiewicz
2006-12-13 14:16 ` Sergei Shtylyov [this message]
2006-12-13 14:53 ` Alan
2006-12-13 0:40 ` Alan
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=45800B4D.8000906@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--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