linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: ppcdev <linuxppc-dev@ozlabs.org>,
	ppcembed <linuxppc-embedded@ozlabs.org>
Subject: Re: MSI support on Linux PCI implementation for Ocotea
Date: Thu, 15 Jun 2006 16:31:01 -0700	[thread overview]
Message-ID: <ada3be6vvwq.fsf@cisco.com> (raw)
In-Reply-To: <1150413771.7725.20.camel@localhost.localdomain> (Benjamin Herrenschmidt's message of "Fri, 16 Jun 2006 09:22:51 +1000")

    Benjamin> Hi ! What is Ocotea ! :)

It's an eval board for some PowerPC 440 ... 440GX I think (which has
the HW capability to support MSI on PCI-X iirc)

 - R.

  reply	other threads:[~2006-06-15 23:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15 21:14 MSI support on Linux PCI implementation for Ocotea Shawn Jin
2006-06-15 23:22 ` Benjamin Herrenschmidt
2006-06-15 23:31   ` Roland Dreier [this message]
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=ada3be6vvwq.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=benh@kernel.crashing.org \
    --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).