linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jake Magee <jakemagee@gmail.com>
To: Dan Wilson <dwilson@fulcrummicro.com>
Cc: Linuxppc-dev@lists.ozlabs.org
Subject: Re: Resetting PCI-E devices after linux boot
Date: Wed, 14 Apr 2010 08:55:28 -0500	[thread overview]
Message-ID: <t2wa8142e731004140655p230f7094idc29e489ea09e848@mail.gmail.com> (raw)
In-Reply-To: <4BAC0D4B.3030507@fulcrummicro.com>

[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]

Dan,

Were you able to get PCI-E hotplug working?  I could not get this working
myself and assumed that driver support was lacking.  I'm actually using a
PPC405.

Thanks,
Jake


On Thu, Mar 25, 2010 at 8:26 PM, Dan Wilson <dwilson@fulcrummicro.com>wrote:

> We are building a PCI-E device for use in an embedded system with an 85xx
> processor.  One of our customers is adamant that linux PCI-E hot-swap
> support will not allow us to either bring the device up after linux boot
> (i.e., the PCI-E device must be present when linux scans for PCI-E devices
> at startup) or to reset the device once linux is up.  It was our impression
> that the PCI-E hot-swap support should allow for devices to appear after
> linux boot, be properly initialized, and then later be able to shut them
> down and bring them back up again.
>
> Has anyone successfully used the PCI-E hot-swap capabilities in the linux
> kernel in a PPC 85xx environment?  Any known gotchas we need to be aware of?
>
> Thanks in advance for your responses,
>
> Dan.
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>

[-- Attachment #2: Type: text/html, Size: 1650 bytes --]

  reply	other threads:[~2010-04-14 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26  1:26 Resetting PCI-E devices after linux boot Dan Wilson
2010-04-14 13:55 ` Jake Magee [this message]
2010-04-14 22:25   ` Benjamin Herrenschmidt
2010-04-15 10:59     ` Stefan Roese

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=t2wa8142e731004140655p230f7094idc29e489ea09e848@mail.gmail.com \
    --to=jakemagee@gmail.com \
    --cc=Linuxppc-dev@lists.ozlabs.org \
    --cc=dwilson@fulcrummicro.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).