From: Adrian Cox <adrian@humboldt.co.uk>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Pegasos 2 support patch ...
Date: Wed, 30 Jun 2004 20:05:01 +0100 [thread overview]
Message-ID: <1088622301.28598.68.camel@localhost> (raw)
In-Reply-To: <20040630185231.GA29878@pegasos>
On Wed, 2004-06-30 at 19:52, Sven Luther wrote:
> On Wed, Jun 30, 2004 at 05:39:35PM +0100, Adrian Cox wrote:
> > The problem is that the via686 ide is hardwired to irqs 14 and 15 of the
> > i8259 interrupt controller internally, but the kernel believes that only
> > IDE controllers at the legacy address can have separate irqs for each
> > channel.
>
> Is this the case for each via ide controller ? If so why does it work on
> x86 ?
Because on x86 the BIOS places the IDE controller at the legacy
addresses (0x1f0, 0x170), and then setup-pci.c spots that the via ide
controller is also the legacy IDE controller, and thus uses the legacy
irq numbers 14 and 15.
What I'm looking for is a tidy way of achieving the same result on a
platform where the boot firmware did not put the via ide controller at
the legacy addresses.
- Adrian Cox
Humboldt Solutions Ltd.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-30 19:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 16:50 Pegasos 2 support patch Sven Luther
2004-06-29 20:42 ` Sven Luther
2004-06-30 2:57 ` Benjamin Herrenschmidt
2004-06-30 6:00 ` Sven Luther
2004-06-30 8:10 ` Geert Uytterhoeven
2004-06-30 8:21 ` Sven Luther
2004-06-30 9:18 ` Adrian Cox
2004-06-30 9:30 ` Sven Luther
2004-06-30 9:40 ` Adrian Cox
2004-06-30 9:45 ` Sven Luther
2004-06-30 15:50 ` Sven Luther
2004-06-30 16:12 ` Adrian Cox
2004-06-30 16:23 ` Sven Luther
2004-06-30 16:39 ` Adrian Cox
2004-06-30 18:52 ` Sven Luther
2004-06-30 19:05 ` Adrian Cox [this message]
2004-06-30 19:38 ` Sven Luther
2004-07-01 7:59 ` Geert Uytterhoeven
2004-07-01 8:42 ` Adrian Cox
2004-07-01 8:48 ` Geert Uytterhoeven
2004-07-01 8:57 ` Sven Luther
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=1088622301.28598.68.camel@localhost \
--to=adrian@humboldt.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sven.luther@wanadoo.fr \
/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).