From: vb <vb@vsbe.com>
To: "Darcy Watkins" <DWatkins@tranzeo.com>
Cc: linuxppc-embedded@ozlabs.org,
Mike Timmons <mike_timmons@trimble.com>,
Andy Schmidt <andrewgschmidt@gmail.com>
Subject: Re: PPC to PowerPC Migration
Date: Wed, 11 Jun 2008 09:03:31 -0700 [thread overview]
Message-ID: <f608b67d0806110903ta0054eke85eb33d411b638f@mail.gmail.com> (raw)
In-Reply-To: <D61182AC8012EA4EBC531B3AF23BE109603568@tranzeo-mail2.12stewart.tranzeo.com>
On Wed, Jun 11, 2008 at 8:45 AM, Darcy Watkins <DWatkins@tranzeo.com> wrote:
> Hello,
>
> And ... for mini PCI, you only have two entries per IDSEL instead of the
> usual four.
>
And of course in reality you need just one! :-)
/vb
> Regards,
>
> Darcy
>
>
> --snip!--
>
> my favorite was interrupt-map in PCI section: A typical value would
> look like this:
>
> interrupt-map = <
>
> /* IDSEL 0x10 */
> 08000 0 0 1 &mpic 0 1
> 08000 0 0 2 &mpic 1 1
> 08000 0 0 3 &mpic 2 1
> 08000 0 0 4 &mpic 3 1
>
>
> [ repeated per IDSEL ]
>
> >
>
> I don't see 'interrupt-map' mentioned anywhere in the ./Documentation
> tree - it took me a while to find out what these numbers actually
> meant.
>
> cheers,
> Vadim
>
> --snip!--
>
next prev parent reply other threads:[~2008-06-11 16:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 17:48 PPC to PowerPC Migration Andy Schmidt
2008-06-10 23:59 ` John Linn
2008-06-11 1:19 ` Mike Timmons
2008-06-11 13:55 ` vb
2008-06-11 14:03 ` Jon Loeliger
2008-06-11 15:33 ` vb
2008-06-11 15:45 ` Darcy Watkins
2008-06-11 16:03 ` vb [this message]
2008-06-11 16:07 ` Scott Wood
2008-06-11 14:38 ` Darcy Watkins
2008-06-11 16:32 ` Josh Boyer
2008-06-11 17:15 ` Darcy Watkins
2008-06-11 17:32 ` Josh Boyer
2008-06-11 17:52 ` Darcy Watkins
2008-06-11 17:56 ` Josh Boyer
2008-06-12 15:58 ` Darcy Watkins
2008-06-11 19:36 ` Andrew Schmidt
2008-06-12 8:14 ` Jens Wirth
2008-06-12 16:02 ` Grant Likely
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=f608b67d0806110903ta0054eke85eb33d411b638f@mail.gmail.com \
--to=vb@vsbe.com \
--cc=DWatkins@tranzeo.com \
--cc=andrewgschmidt@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mike_timmons@trimble.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).