From: dk-arm-linux@gmx.de (Dieter Kiermaier)
To: linux-arm-kernel@lists.infradead.org
Subject: PCI hotplug supported on ARM (Kirkwood)? - fakephp?
Date: Fri, 13 Nov 2009 14:43:56 +0100 [thread overview]
Message-ID: <200911131443.56429.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <200911131221.43527.dk-arm-linux@gmx.de>
Am Freitag 13 November 2009 12:21:43 schrieb Dieter Kiermaier:
> Am Donnerstag 12 November 2009 20:01:32 schrieb Alexander Clouter:
>
> > Dieter Kiermaier <dk-arm-linux@gmx.de> wrote:
> > >
> > > 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?
> > >
> > I tried tackling this on my board by creating a new 'bus' and trying to
> > work around making the FPGA 'hotplugable' that way. As the bus would
> > know about the process of reprogramming the FPGA, it could cleanly
> > unload and reload everything.
> >
> > http://marc.info/?l=linux-kernel&m=124441477117607&w=2
Hm, your link seems to be down. Do you have a newer version of your code
somewhere?
> >
> > Never did get it to work and no one expressed any real interest in it
> > for the platform sadly; so I drifted off looking for other geeky things
> > to do.
> >
> > I am still personally keener on the bus model, but Geert suggested I
> > lump for a MFD.
>
> Hm, it looks like fakephp is what I was looking for but I see no way to compile
> this module on my arm (kirkwood).
>
fakephp seems to be integrated / ported into the pci layer?
I have a /sys/bus/pci interface:
It is possible to deactivate devices by doing:
echo 1 > /sys/bus/pci/devices/0000\:01\:08.0/remove
But it looks like there is no way of reactivating /rescanning it?
I've tried
echo 1 > /sys/bus/pci/rescan
but without any success.
Does anybody have an idea?
Many thanks,
Dieter
> Does anybody know a way to compile it?
>
> Many thanks,
> Dieter
>
>
>
> >
> > Whatever you do, if you can keep me in the loop then I can nick your
> > ideas/code and maybe get back into tinkering with my ARM board, that's
> > if I stop bricking my MIPS boards :-/
> >
> > Cheers
> >
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
prev parent reply other threads:[~2009-11-13 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 17:26 PCI hotplug supported on ARM (Kirkwood)? Dieter Kiermaier
2009-11-12 19:01 ` Alexander Clouter
2009-11-13 11:21 ` PCI hotplug supported on ARM (Kirkwood)? - fakephp? Dieter Kiermaier
2009-11-13 13:43 ` Dieter Kiermaier [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=200911131443.56429.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).