From: Abdelghani Ouchabane <abdelghani@ezono.com>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: PCIe can not rescan for new PCIe device ( FPGA board )
Date: Mon, 24 Oct 2011 11:20:37 +0200 [thread overview]
Message-ID: <4EA52DE5.2010204@ezono.com> (raw)
In-Reply-To: <4EA4F0D2.3070301@jp.fujitsu.com>
Hallo Kenji,
many thanks for your great supports. The new BIOS from Congatec solves
the problem.
I using both fakephp& pciehp drivers, Can I use both drivers at the
same time?
> I think, "no".
>
>> I am using fakephp because I need "/sys/bus/pci/slots/0000\:02\:00.0/power".
>>
>> Other thing: my Kernel has "CONFIG_ACPI_PROC_EVENT is not set", does
>> this explain why the scan is not performed automatically?
> Fakephp driver doesn't have any corresponding hotplug controller (hardware).
> So I don't think there is no way to detect presence change event on the slot.
>
>> [root@localhost ~]# modprobe acpiphp
>> FATAL: Error inserting acpiphp
>> (/lib/modules/2.6.40.3-0.119.delos.i686/kernel/drivers/pci/hotplug/acpiphp.ko):
>> No such device
>>
>> What is the advantage to use acpiphp ?
> Some platform only allows acpiphp, but doesn't allow PCIe native hotplug driver
> (like pciehp). The 'pciehp_force' specified your environment is to load pciehp
> forcibly on such platform. So I thought acpiphp might solve your problem.
>
> Regards,
> Kenji Kaneshige
>
Hallo
many thanks for your support, my system is working perfectly.
Cheers,
Ghani
next prev parent reply other threads:[~2011-10-24 9:20 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 [this message]
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
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=4EA52DE5.2010204@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).