From: William Park <opengeometry@yahoo.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Lee Revell <rlrevell@joe-job.com>, linux-kernel@vger.kernel.org
Subject: Re: DMA in PCI chipset -- module vs. compiled-in
Date: Mon, 6 Feb 2006 21:04:41 -0500 [thread overview]
Message-ID: <20060207020441.GA3309@node1.opengeometry.net> (raw)
In-Reply-To: <1139255365.10437.49.camel@localhost.localdomain>
On Mon, Feb 06, 2006 at 07:49:25PM +0000, Alan Cox wrote:
> On Sul, 2006-02-05 at 23:32 -0500, Lee Revell wrote:
> > Generic and chipset specific support are not complementary, they are
> > mutually exclusive. Having generic PCI IDE support enabled will prevent
> > the chipset specific support from working properly.
>
> Untrue.
>
> The PCI generic driver by default grabs only hardware with PCI IDS it
> knows can be driven generically. That list purposefully has no overlaps
> with chipset drivers.
The kernel I'm using is 2.6.14. My chipset is Via 82c694x and 82c686b
(Abit VP6 dual-P3 with HighPoint 370). DMA is on only when 'via82cxxx'
and 'hpt366' are compiled in. Most importantly, DMA cannot be turned on
if loading by module.
Does it mean that this "bug" is pecular to my chipset?
--
William Park <opengeometry@yahoo.ca>, Toronto, Canada
ThinFlash: Linux thin-client on USB key (flash) drive
http://home.eol.ca/~parkw/thinflash.html
BashDiff: Super Bash shell
http://freshmeat.net/projects/bashdiff/
prev parent reply other threads:[~2006-02-07 2:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 3:43 DMA in PCI chipset -- module vs. compiled-in William Park
2006-02-06 4:32 ` Lee Revell
2006-02-06 19:31 ` Ingo Oeser
2006-02-06 20:26 ` Lee Revell
2006-02-06 19:49 ` Alan Cox
2006-02-06 20:25 ` Lee Revell
2006-02-07 8:14 ` Bartlomiej Zolnierkiewicz
2006-02-07 11:07 ` Alan Cox
2006-02-07 11:14 ` Bartlomiej Zolnierkiewicz
2006-02-08 4:37 ` William Park
2006-02-07 2:04 ` William Park [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=20060207020441.GA3309@node1.opengeometry.net \
--to=opengeometry@yahoo.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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