From: dk-arm-linux@gmx.de (Dieter Kiermaier)
To: linux-arm-kernel@lists.infradead.org
Subject: PCI hotplug supported on ARM (Kirkwood)?
Date: Thu, 12 Nov 2009 18:26:06 +0100 [thread overview]
Message-ID: <200911121826.06792.dk-arm-linux@gmx.de> (raw)
Hi list,
is it possible to boot a FPGA which is connected to an PCI bus on a kirkwood cpu (via a pcie->pci bridge)
at runtime (I call it hotplug)?
And after booting the FPGA e.g. via slave serial protocol loading the pci driver and access the device?
This would be much easier to handle than flashing the fpga using u-boot.
Is there any special framework I have to use? How can I tell the kernel to reenumerate the bus and reasign
the pci resources?
I have googled a lot and also tried to find something at newsgroups or mailinglists but I haven't found some
valuable information - at least not for me ;).
Is this possible?
Many thanks,
Dieter
next reply other threads:[~2009-11-12 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 17:26 Dieter Kiermaier [this message]
2009-11-12 19:01 ` PCI hotplug supported on ARM (Kirkwood)? Alexander Clouter
2009-11-13 11:21 ` PCI hotplug supported on ARM (Kirkwood)? - fakephp? Dieter Kiermaier
2009-11-13 13:43 ` Dieter Kiermaier
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=200911121826.06792.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.de \
--cc=linux-arm-kernel@lists.infradead.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).