All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: CompactPCI hotplug on PowerPC
Date: Sun, 25 Oct 2009 10:13:16 +0200	[thread overview]
Message-ID: <4AE4089C.4050000@embedded-sol.com> (raw)

Hi,

Can someone who used CompactPCI hotplug drivers on PowerPC
systems please share their experience ? Any pitfalls that
should be avoided, things to take into consideration, etc.

I may soon be involved in project using 460EX CPU, PLX6254
transparent PCI-PCI bridge, and CompactPCI cards. The system
should use ENUM# interrupt to detect card insertion/deletion.

I'm mostly concerned with PCI-PCI bridge and resource allocation
behind it. Is something that is known to work well ?

Also, cPCI hotplug drivers seem more x86 centric, and not immediately
usable with OF framework. There seems to be no way do pass ENUM# irq
number into the driver. How should one define ENUM# interrupt in
device tree ?

Thanks a lot in advance.

Felix.

                 reply	other threads:[~2009-10-25  8:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4AE4089C.4050000@embedded-sol.com \
    --to=felix@embedded-sol.com \
    --cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.