From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: ide_init_hwif_ports
Date: Thu, 29 Nov 01 14:15:10 PST [thread overview]
Message-ID: <0111292215.AA01078@ivan.Harhan.ORG> (raw)
mod+linuxppc-dev@MissionCriticalLinux.com wrote:
> Not to quibble with your painfully accurate
> description of the VT82C686B, but might it be
> possible (using the IDE Interrupt Routing register
> at offset 0x4a in function 1) to arrange for both
> channels to use the same interrupt routing?
> Like force both to IRQ14? Just a thought...
>From what I could tell the IDE interrupt routing is fixed by the board
circuitry *outside* the chip and cannot be changed by any register diddling. As
I said, I don't think the VT82C686B even knows when an IDE interrupt has
occurred. The interrupt lines from the IDE connectors are tied directly to the
IRQ14 and IRQ15 pins, the same ones that go to the ISA slot connectors. If one
of these pins goes high, the VT82C686B has no way of knowing that it's IDE or
something else on ISA using this IRQ is signaling an interrupt.
Then what does the supposed IDE Interrupt Routing register (at offset 0x4A in
function 0, I assume that's what you really meant) do? I have no idea. I
suspect that Via *tried* to make it standards-compliant and support both AT-
compatible and pure PCI IDE interrupt routing, but never fully got it. Consider
function 1's Interrupt Pin register (offset 0x3D). The Via manual says:
00h Legacy mode interrupt routing
01h Native mode interrupt routing
Yet it always reads as 00 and I couldn't get it to read as 01 or as anything
else.
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-11-29 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 22:15 Michael Sokolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-29 22:24 ide_init_hwif_ports Michael Sokolov
2001-11-29 21:42 ide_init_hwif_ports mod+linuxppc-dev
2001-11-29 22:21 ` ide_init_hwif_ports Adrian Cox
2001-11-29 19:00 ide_init_hwif_ports Michael Sokolov
2001-11-29 21:55 ` ide_init_hwif_ports Paul Mackerras
2001-11-29 5:41 ide_init_hwif_ports Paul Mackerras
2001-11-29 8:55 ` ide_init_hwif_ports Adrian Cox
2001-11-29 11:58 ` ide_init_hwif_ports Paul Mackerras
2001-11-29 16:57 ` ide_init_hwif_ports Dan Malek
2001-11-29 16:20 ` ide_init_hwif_ports Joseph P. Garcia
2001-11-29 18:58 ` ide_init_hwif_ports Armin Kuster
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=0111292215.AA01078@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.