From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Yan Luo <zaizailuo@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: Via IDE Bus Master controller IRQ number?
Date: Wed, 05 Jul 2006 18:29:34 +0400 [thread overview]
Message-ID: <44ABCCCE.1010005@ru.mvista.com> (raw)
In-Reply-To: <2f9b85b70607041831kaccea64o8d1a4b2309ce03d0@mail.gmail.com>
Yan Luo wrote:
> Hello,
>
> I have a question on enabling DMA access to IDE hard disk using VIA
> vt82c686 chipset. My platform is a single board computer AAEON
> PCM-6892 (VIA C3 CPU, via vt82c686b chipset). I am working on a
> IDE-DMA port to RTEMS.
> I am trying to find which irq number the IDE bus master controller
> (part of the vt82c686 chipset) uses. I read out PCI_INTERRUPT_PIN and
> PCI_INTERRUPT_LINE from its PCI configuration space. The
> PCI_INTERRUPT_PIN is found to be '0', and PCI_INTERRUPT_LINE as 'FF'. Does
> it mean this controller does not support interrupt? If so, who do I
> tell if the DMA transfer finishes??
It just means that it supports the "legacy" interrupts, i. e. IRQ14 for
primary and IRQ15 for the scondary channel. This should be indicated by the
bits 0 and 2 of its programming interface register in the PCI config. space
being set to zero.
> The experiment I did is to send ATA_COMMAND_READ_DMA to IDE0 command
> register (I/O address 0x1F7) and then write '1' to the last bit of
> IDE BM controller's command register (first register in the BM IDE I/O
> space) to start DMA transfer. But the DMA transfer hangs the system. I
> have installed an interrupt handler for IRQ 14, which seems not
> triggered.
Have you also set up the PRD list and written its address to the
corresponding BM IDE register?
> Please advise.
WBR, Sergei
next prev parent reply other threads:[~2006-07-05 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 1:31 Via IDE Bus Master controller IRQ number? Yan Luo
2006-07-05 14:29 ` Sergei Shtylyov [this message]
2006-07-07 3:11 ` Yan Luo
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=44ABCCCE.1010005@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-ide@vger.kernel.org \
--cc=zaizailuo@gmail.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).