From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Legacy ISA registers/interrupts in PCI device tree node
Date: Tue, 17 Jul 2007 07:35:05 +1000 [thread overview]
Message-ID: <1184621705.25235.76.camel@localhost.localdomain> (raw)
In-Reply-To: <469B336A.5060303@genesi-usa.com>
On Mon, 2007-07-16 at 09:59 +0100, Matt Sealey wrote:
> You could do a LOT worse than check the Pegasos.
Yes, mimmicing the pegasos will probably work
> Matt Sealey <matt@genesi-usa.com>
> Genesi, Manager, Developer Relations
>
> Gerhard Pircher wrote:
> > Hi,
> >
> > I wonder, if there is a recommended way to specify ISA register
> addresses
> > and interrupts for a PCI device (unlike for a PCI2ISA bridge)?
> > The device in question is the integrated IDE controller of the
> VIA686B
> > southbridge, which works in compatible/legacy mode and thus uses
> interrupts
> > 14 and 15 of the i8259 PIC. Should the fdt contain this information
> or
> > should I hardcode the values in the platform setup code?
You may need a fixup like pegasos does because that chip seems to use
14/15 even when in native mode, which is somewhat out of spec.
Cheers,
Ben.
next prev parent reply other threads:[~2007-07-16 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 7:53 Legacy ISA registers/interrupts in PCI device tree node Gerhard Pircher
2007-07-16 8:59 ` Matt Sealey
2007-07-16 21:35 ` Benjamin Herrenschmidt [this message]
2007-07-16 12:40 ` Segher Boessenkool
2007-07-16 13:29 ` Gerhard Pircher
2007-07-16 15:05 ` Segher Boessenkool
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=1184621705.25235.76.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.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 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).