linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joe briggs <jbriggs@briggsmedia.com>
To: David Brodbeck <DavidB@mail.interclean.com>,
	"'motion@lists.frogtown.com'" <motion@pdx.frogtown.com>,
	andras@t-online.de, linux-kernel@vger.kernel.org,
	motion@frogtown.com
Subject: Re: [Motion] Re: IDE corruption during heavy bt878-induced interr upt load [LKM]
Date: Wed, 23 Apr 2003 18:13:46 -0400	[thread overview]
Message-ID: <200304231813.46892.jbriggs@briggsmedia.com> (raw)
In-Reply-To: <C823AC1DB499D511BB7C00B0D0F0574C583D23@serverdell2200.interclean.com>

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?

On Wednesday 23 April 2003 03:22 pm, David Brodbeck wrote:
> > -----Original Message-----
> > From: joe briggs [mailto:jbriggs@briggsmedia.com]
> >
> > I am glad that you mentioned ext3 because while I curse
> > ReiserFS, I really
> > don't think that it is part of the problem. Definately
> > PCI-dma related, but
> > does onboard IDE (i.e., my system disk) use DMA in the same
> > way that a PCI
> > adapter such as Promise does?
>
> I'm not a hardware expert, but since on-board IDE controllers usually
> appear as PCI devices to the OS, I assume they do DMA the same way.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

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

  reply	other threads:[~2003-04-23 21:02 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 [this message]
2003-04-23 22:11   ` Alan Cox
2003-04-24 10:31     ` joe briggs
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:
  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=200304231813.46892.jbriggs@briggsmedia.com \
    --to=jbriggs@briggsmedia.com \
    --cc=DavidB@mail.interclean.com \
    --cc=andras@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=motion@frogtown.com \
    --cc=motion@pdx.frogtown.com \
    /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;
as well as URLs for NNTP newsgroup(s).