public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Lord <lkml@rtr.ca>, Grant Coady <gcoady.lk@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Query: No IDE DMA for IBM 365X with PIIX chipset?
Date: Fri, 02 Jun 2006 16:57:26 +0200	[thread overview]
Message-ID: <448051D6.808@rainbow-software.org> (raw)
In-Reply-To: <1149187933.12932.70.camel@localhost>

Alan Cox wrote:
> On Iau, 2006-06-01 at 13:22 -0400, Mark Lord wrote:
>> That's the original Intel "triton" chipset.
>> I have a spare printed Intel document for the chipset (Intel #290519-001)
>> which I can mail you (Alan).  Email me privately with a postal address.
> 
>>From the other docs it appears 0x122E is the ISA bridge and this laptop
> has 0x122E (PIIX bridge) and an 82437MX system controller, but no PIIX
> IDE. That actually suggests its more like the "MPIIX" which has a PIO
> only IDE controller existing (logically anyway) on the ISA side of the
> system.
> 
> That would explain the observed behaviour and fit with the pattern of
> PCI identifiers. Now to hunt 82437 docs.
> 
> (In the mean time try adding the 0x1235 id to the 2.6.17-mm kernel in
> drivers/scsi/pata_mpiix and see if that works with the new libata layer
> not drivers/ide).

Maybe http://stuff.mit.edu/afs/sipb/contrib/doc/specs/unfiled/i82437MX.pdf

-- 
Ondrej Zary

      reply	other threads:[~2006-06-02 14:57 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
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 [this message]

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=448051D6.808@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gcoady.lk@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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