linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abdelghani Ouchabane <abdelghani@ezono.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Subject: Re: PCIe can not rescan for new PCIe device ( FPGA board )
Date: Fri, 14 Oct 2011 11:27:01 +0200	[thread overview]
Message-ID: <4E980065.3090509@ezono.com> (raw)
In-Reply-To: <CAErSpo5Q22-VtNd23-rmCUsJdQmN7VdmSAM806-_Po7=KK9Y0g@mail.gmail.com>


> Thanks for the details.
>
> If I understand correctly:
>
>    A - fails (card not present at power-on, added later)
>    B - works (card always present)
>    C - works (card present at power-on, later removed and re-added,
> requires manual rescan)
>
> I see this note in section 9.4.8 (BIOS setup) of the conga-BAF User's Guide:
>
>      Note: Unless the hotplug support for this port is enabled as well,
> an unpopulated
>      port will still be disabled if no PCI Express device is connected.
>
> If you don't have hotplug enabled in the BIOS setup, it sounds like it
> might result in the behavior you're seeing.  Do you have that enabled?
>
> Bjorn

Hallo Bjorn & Kenji,

    the hot-plug was enabled, but today I have received a new BIOS from 
Congatec which solves the problem.

Among the fix is:

_BBRAR009 to BBRAR110:_

2. Enabled PCIExpress / ExpressCard basic hotplug support. Enabled event 
handling support.

Now after the manual rescan my FPGA board gets detect correctly and I 
can access its registers in the correct way.


Many thanks for all your supports.

My best regards,
Ghani




      reply	other threads:[~2011-10-14  9:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07  7:16 PCIe can not rescan for new PCIe device ( FPGA board ) Abdelghani Ouchabane
2011-10-07 15:37 ` Bjorn Helgaas
2011-10-07 16:22   ` Abdelghani Ouchabane
2011-10-07 16:36     ` Bjorn Helgaas
2011-10-11  1:39       ` Kenji Kaneshige
2011-10-11  8:11         ` Abdelghani Ouchabane
2011-10-12  6:36           ` Kenji Kaneshige
2011-10-12  8:35             ` Abdelghani Ouchabane
2011-10-13 12:50               ` Kenji Kaneshige
2011-10-14  9:40                 ` Abdelghani Ouchabane
2011-10-24  5:00                   ` Kenji Kaneshige
2011-10-24  9:20                     ` Abdelghani Ouchabane
2011-10-11  8:10       ` Abdelghani Ouchabane
2011-10-11 15:22         ` Bjorn Helgaas
     [not found]           ` <4E954251.5020801@ezono.com>
2011-10-12  8:03             ` Abdelghani Ouchabane
2011-10-12 15:58               ` Bjorn Helgaas
2011-10-14  9:27                 ` Abdelghani Ouchabane [this message]

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=4E980065.3090509@ezono.com \
    --to=abdelghani@ezono.com \
    --cc=bhelgaas@google.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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).