From: Paul Mackerras <paulus@samba.org>
To: msokolov@ivan.Harhan.ORG (Michael Sokolov)
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ide_init_hwif_ports
Date: Fri, 30 Nov 2001 08:55:18 +1100 (EST) [thread overview]
Message-ID: <15366.44742.923433.367449@gargle.gargle.HOWL> (raw)
In-Reply-To: <0111291900.AA00593@ivan.Harhan.ORG>
Michael Sokolov writes:
> to ISA slot connectors. This is what the Adirondack does, and the result is
> that no matter what you do in the PCI domain, the primary IDE interrupt will
> always come in as IRQ 14 and the secondary IDE interrupt will always come in as
> IRQ 15.
Thanks for the explanation. I'll ask Vojtech Pavlik and Andre Hedrick
if they can suggest a better way (drivers/ide/via82cxxx.c has
Vojtech's name on it).
Actually, I have just noticed this code in drivers/ide/ide-pci.c:
if (IDE_PCI_DEVID_EQ(d->devid, DEVID_UM8886A) ||
IDE_PCI_DEVID_EQ(d->devid, DEVID_UM8886BF) ||
IDE_PCI_DEVID_EQ(d->devid, DEVID_UM8673F)) {
hwif->irq = hwif->channel ? 15 : 14;
goto bypass_umc_dma;
}
We may be able to get something similar added for our case(s).
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-29 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 19:00 ide_init_hwif_ports Michael Sokolov
2001-11-29 21:55 ` Paul Mackerras [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 21:42 ide_init_hwif_ports mod+linuxppc-dev
2001-11-29 22:21 ` ide_init_hwif_ports Adrian Cox
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=15366.44742.923433.367449@gargle.gargle.HOWL \
--to=paulus@samba.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=msokolov@ivan.Harhan.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).