archive mirror
 help / color / mirror / Atom feed
From: joe briggs <>
To: Alan Cox <>
Cc: David Brodbeck <>,
	"''" <>,,
	Linux Kernel Mailing List <>,
Subject: Re: [Motion] Re: IDE corruption during heavy bt878-induced interr upt load [LKM]
Date: Thu, 24 Apr 2003 06:31:49 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

That's what I thought, which is why I suspected that the underlying problem 
might be related to the scope and completeness of the hardware arbitration.  
Specifically, if a PCI board is DMA'ing a block of data to main memory, how 
is the operation of the direct-connect IDE device impacted?  When most PCI 
devices transfer data to main memory, don't they arbitrate the bus, become 
master, and blast it accross in chunks?  Doesn't onboard IDE (legacy?) use 
the DMA controller (8237 derivate I gues) to transfer?

On Wednesday 23 April 2003 06:11 pm, Alan Cox wrote:
> On Mer, 2003-04-23 at 23:13, joe briggs wrote:
> > Is this true??? Does onboard IDE controllers appear and work the same way
> > as IDE or PCI controllers with respect to IRQ, DMA, and memory access?
> They appear to. Most of them nowdays are wired directly to the
> north/southbridge link for performance.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to
> More majordomo info at
> Please read the FAQ at

Joe Briggs
Briggs Media Systems
105 Burnsen Ave.
Manchester NH 01304 USA
TEL/FAX 603-232-3115 MOBILE 603-493-2386

  reply	other threads:[~2003-04-24  9:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 19:22 [Motion] Re: IDE corruption during heavy bt878-induced interr upt load [LKM] David Brodbeck
2003-04-23 22:13 ` joe briggs
2003-04-23 22:11   ` Alan Cox
2003-04-24 10:31     ` joe briggs [this message]
2003-04-24 18:57       ` Alan Cox

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).