public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: "Kathy Frazier" <kfrazier@mdc-dayton.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: DMA not supported with Intel ICH4 I/O controller?
Date: 28 Jul 2003 13:52:20 -0700	[thread overview]
Message-ID: <52brvegyrf.fsf@topspin.com> (raw)
In-Reply-To: <PMEMILJKPKGMMELCJCIGIEIMCDAA.kfrazier@mdc-dayton.com>

    Kathy> It's a proprietary board that we use to allow the PC to
    Kathy> send blocks of data to some industrial equipment.  We
    Kathy> developed the hardware and Linux driver in-house.  This
    Kathy> same board works (under Linux) on a MoBo using the Intel
    Kathy> 815E chipset (Pentium III) with an IHC2 I/O Controller Hub.
    Kathy> This is the system I did _all_ my stress testing in.  The
    Kathy> plan was to ship our product with these ASUS P4PE MoBos
    Kathy> (using Intel 845PE and ICH4 controller) and were
    Kathy> un-pleasantly surprise when it didn't work.

It sounds like your board is acting as a PCI bus master.  This is
completely different from DMA for the IDE controller.  External PCI
bus masters should be supported by any version of Linux that works on
the motherboard at all.

However there are of course many differences between an 815E and an
845PE motherboard, and between the ICH2 and ICH4.  You may have
borderline PCI compliance or signal integrity issues that only cause
problems on the P4PE motherboard.  The BIOS on the P4PE may be setting
your device up differently from the 815E motherboard.  Your device
might be confusing the BIOS on the P4PE so that the IRQ routing
information (eg in ACPI tables) is screwed up.  And so on.

However, I have not heard of any generic problems with external PCI
bus masters and the ICH4.

Best,
  Roland

  parent reply	other threads:[~2003-07-28 20:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 19:44 DMA not supported with Intel ICH4 I/O controller? Kathy Frazier
2003-07-28 18:45 ` Mike Dresser
2003-07-28 20:40   ` Kathy Frazier
2003-07-28 19:32     ` Mike Dresser
2003-07-28 21:02       ` Kathy Frazier
2003-07-28 20:03         ` Mike Dresser
2003-07-28 20:19         ` Alan Cox
2003-07-28 22:02           ` Kathy Frazier
2003-07-28 21:21             ` Terje Kvernes
2003-07-29 14:45               ` Kathy Frazier
2003-07-29 11:01             ` Alan Cox
2003-07-29 14:07               ` Mike Dresser
2003-07-28 20:52         ` Roland Dreier [this message]
2003-07-29 13:01           ` Kathy Frazier
     [not found] <1059443191.3861.48.camel@cube>
2003-07-29 13:14 ` Kathy Frazier

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=52brvegyrf.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=kfrazier@mdc-dayton.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox