From: Dan Malek <dan@embeddededge.com>
To: paulus@samba.org
Cc: Adrian Cox <adrian@humboldt.co.uk>, linuxppc-dev@lists.linuxppc.org
Subject: Re: ide_init_hwif_ports
Date: Thu, 29 Nov 2001 11:57:03 -0500 [thread overview]
Message-ID: <3C0668DF.9000100@embeddededge.com> (raw)
In-Reply-To: 15366.8953.429603.173303@gargle.gargle.HOWL
Paul Mackerras wrote:
> Ah, OK. Is this the 82c105? Are the two channels separate PCI
> functions in the device, or are they the same function?
It's part of the 83c553 bridge. IIRC, the interrupts from the IDE
can be routed in a couple of different ways, including directly into
the EPIC. You can kind of pretend it is a PCI-IDE controller, but there
isn't any PCI config register to read that will tell you the interrupt
number, so we need a way to tell the generic IDE code what to use (and
of course this number is suitably "faked" so it generates the proper
EPIC interrupt). The reason you want to use this configuration mode
on the Sandpoint is because it eliminates some other interrupt
multiplexing problems and board resource conflicts.
Custom boards that don't have a regular appearance in the source tree
have copied a similar design. I would like to vote for leaving this
interrupt mapping function in place as well.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-29 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Dan Malek [this message]
2001-11-29 16:20 ` ide_init_hwif_ports Joseph P. Garcia
2001-11-29 18:58 ` ide_init_hwif_ports Armin Kuster
-- strict thread matches above, loose matches on Subject: below --
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 21:42 ide_init_hwif_ports mod+linuxppc-dev
2001-11-29 22:21 ` ide_init_hwif_ports Adrian Cox
2001-11-29 22:15 ide_init_hwif_ports Michael Sokolov
2001-11-29 22:24 ide_init_hwif_ports Michael Sokolov
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=3C0668DF.9000100@embeddededge.com \
--to=dan@embeddededge.com \
--cc=adrian@humboldt.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).