linux-kernel - Re: PCIe can not rescan for new PCIe device ( FPGA board )

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 14 Oct 2011 11:27:01 +0200
From:	Abdelghani Ouchabane <abdelghani@...no.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
CC:	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
Subject: Re: PCIe can not rescan for new PCIe device ( FPGA board )


> 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



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/