public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Park <opengeometry@yahoo.ca>
To: linux-kernel@vger.kernel.org
Subject: DMA in PCI chipset -- module vs. compiled-in
Date: Sun, 5 Feb 2006 22:43:12 -0500	[thread overview]
Message-ID: <20060206034312.GA2962@node1.opengeometry.net> (raw)

Dear experts,

Normally, my PCI chipset (ie. via82cxxx, hpt366) are compiled in, and it
correctly enables DMA of my harddisk.

But, for experiment, I tried compiling in only the "generic" options,
and moved all specific PCI chipsets as modules.  Hotplug loads the
modules, but with all 'hdparm' options turned off.  When I tried turning
on DMA, 
    $ hdparm -m 16 -c 1 -u 1 -d 1 /dev/hda
I get
    /dev/hda:
     setting 32-bit IO_support flag to 1
     setting multcount to 16
     setting unmaskirq to 1 (on)
     setting using_dma to 1 (on)
     HDIO_SET_DMA failed: Operation not permitted
     multcount    = 16 (on)
     IO_support   =  1 (32-bit)
     unmaskirq    =  1 (on)
     using_dma    =  0 (off)

Is this normal?  How do I turn on DMA, if I load my PCI chipset as
module?

-- 
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/

             reply	other threads:[~2006-02-06  3:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06  3:43 William Park [this message]
2006-02-06  4:32 ` DMA in PCI chipset -- module vs. compiled-in 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

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=20060206034312.GA2962@node1.opengeometry.net \
    --to=opengeometry@yahoo.ca \
    --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