From: "Shawn Jin" <shawnxjin@gmail.com>
To: ppcembed <linuxppc-embedded@ozlabs.org>,
ppcdev <linuxppc-dev@ozlabs.org>
Subject: MSI support on Linux PCI implementation for Ocotea
Date: Thu, 15 Jun 2006 14:14:17 -0700 [thread overview]
Message-ID: <c3d0340b0606151414q6d218554j255fa74a68a5c9af@mail.gmail.com> (raw)
Hi,
I'm looking at the linux PCI implementation, especially MSI support
for Ocotea. And I have some observations and questions about it. Maybe
somebody here can shed some light on them. Thanks.
1. Obviously MSI is supported in Linux 2.6.x, maybe even in 2.4.x. But
MSI implementation seems to support only IOxAPIC on x86 or IA64
architectures, though the implemenation is in generic drivers/pci
tree.
2. Why is the message data defined in a such way shown as follows? Or
does it just follow IOxAPIC's design? Further question is who defines
the format of the message data. The PCI/PCIe specs don't say anything
about the content of the message data register.
struct msg_data {
__u32 vector : 8;
__u32 delivery_mode : 3; /* 000b: FIXED | 001b: lowest prior */
__u32 reserved_1 : 3;
__u32 level : 1; /* 0: deassert | 1: assert */
__u32 trigger : 1; /* 0: edge | 1: level */
__u32 reserved_2 : 16;
} __attribute__ ((packed));
3. How is the pci subsystem initialized on a PPC platform? Is there
any existing document discussing PCI subsystem? Of course I've been
doing a lot internet search and couldn't find too much useful infor.
Thanks a lot,
-Shawn.
next reply other threads:[~2006-06-15 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 21:14 Shawn Jin [this message]
2006-06-15 23:22 ` MSI support on Linux PCI implementation for Ocotea Benjamin Herrenschmidt
2006-06-15 23:31 ` Roland Dreier
2006-06-16 0:45 ` Shawn Jin
2006-06-16 21:45 ` Shawn Jin
2006-06-16 22:13 ` Benjamin Herrenschmidt
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=c3d0340b0606151414q6d218554j255fa74a68a5c9af@mail.gmail.com \
--to=shawnxjin@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.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).