From: Adrian Cox <adrian@humboldt.co.uk>
To: mod+linuxppc-dev@MissionCriticalLinux.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ide_init_hwif_ports
Date: Thu, 29 Nov 2001 22:21:23 +0000 [thread overview]
Message-ID: <3C06B4E3.8000203@humboldt.co.uk> (raw)
In-Reply-To: 200111292142.QAA30752@missioncriticallinux.com
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...
Tried that on my 686A board. As far as I can tell that register does
nothing at all, and the physical wiring on the board is the only thing
that influences the interrupts. I think that register may be useful on
an i386 with IO-APIC, but I'm not sure.
--
Adrian Cox http://www.humboldt.co.uk/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-29 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 21:42 ide_init_hwif_ports mod+linuxppc-dev
2001-11-29 22:21 ` Adrian Cox [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 22:15 ide_init_hwif_ports Michael Sokolov
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=3C06B4E3.8000203@humboldt.co.uk \
--to=adrian@humboldt.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mod+linuxppc-dev@MissionCriticalLinux.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 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.