From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Query: No IDE DMA for IBM 365X with PIIX chipset?
Date: Thu, 01 Jun 2006 14:50:12 +0100 [thread overview]
Message-ID: <1149169812.12932.20.camel@localhost> (raw)
In-Reply-To: <j9bi729h2u4dcn9da7na3t1d8ckk477d9b@4ax.com>
On Sul, 2006-05-28 at 15:29 +1000, Grant Coady wrote:
> PIIXa: chipset revision 2
> PIIXa: not 100% native mode: will probe irqs later
> PIIXa: neither IDE port enabled (BIOS)
It thinks the chip has not been activated, and then falls back to the
legacy driver. Could be incorrect enable checks or other problems.
> 00:01.0 ISA bridge: Intel Corporation 82371FB PIIX ISA [Triton I] (rev 02)
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
> 00: 86 80 2e 12 07 00 80 02 02 00 01 06 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
82371FB, whee thats prehistoric 8)
I don't actually have any support for the 371FB PIIX in either driver as
I've not been able to find a source for the data sheet to the chip. It
may work if added to the drivers/scsi/pata_oldpiix identifiers in the
2.6.17rc5-mm kernel. Would be useful to know as I don't know anyone else
with that chip any more 8)
Alan
next prev parent reply other threads:[~2006-06-01 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 5:29 Query: No IDE DMA for IBM 365X with PIIX chipset? Grant Coady
2006-05-28 12:06 ` Mark Lord
2006-05-28 22:57 ` Grant Coady
2006-06-01 13:50 ` Alan Cox [this message]
2006-06-01 15:55 ` Ondrej Zary
2006-06-02 7:17 ` Grant Coady
2006-06-01 17:22 ` Mark Lord
2006-06-01 18:52 ` Alan Cox
2006-06-02 14:57 ` Ondrej Zary
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=1149169812.12932.20.camel@localhost \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gcoady.lk@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.