From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Alan Tull <atull@kernel.org>
Cc: Moritz Fischer <mdf@kernel.org>,
linux-fpga@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>
Subject: Re: [PATCH] fpga: add simple userspace interface to trigger FPGA programming
Date: Mon, 4 Dec 2017 16:58:35 +0100 [thread overview]
Message-ID: <20171204165835.33824aa8@windsurf.lan> (raw)
In-Reply-To: <CANk1AXR==vnPTKA4EZZrebd9WViLiaZAxmnnSRyMPPBpJNA4pw@mail.gmail.com>
Hello,
On Mon, 4 Dec 2017 09:50:14 -0600, Alan Tull wrote:
> Hi Thomas,
>
> The problem I see with this is that it's allowing userspace to switch
> out what's on the FPGA without controlling bridges and without
> unloading drivers first.
Correct. Do you have an idea on how to handle this? I'm not sure there's
an easy way to do that, but simply preventing people from programming
their FPGAs seems like a rather poor solution to the problem :-)
Right now, the way it works for me is that at boot time the FPGA is
unprogrammed so the initial PCI enumeration doesn't find any PCI
device. The FPGA is programmed, and I then force a PCI bus rescan
using /sys/bus/pci/rescan, which detects the device and probes the
driver.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-04 15:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 15:43 [PATCH] fpga: add simple userspace interface to trigger FPGA programming Thomas Petazzoni
2017-12-04 15:50 ` Alan Tull
2017-12-04 15:58 ` Thomas Petazzoni [this message]
2017-12-04 16:25 ` Alan Tull
2017-12-04 16:49 ` Moritz Fischer
2017-12-04 17:30 ` Alan Tull
2017-12-09 18:05 ` Florian Fainelli
2017-12-10 4:03 ` Alan Tull
2017-12-10 22:44 ` Thomas Petazzoni
2017-12-10 22:59 ` Florian Fainelli
2017-12-11 22:05 ` Moritz Fischer
2017-12-11 23:32 ` Alan Tull
2017-12-13 6:30 ` yves.vandervennet
2017-12-13 5:23 ` Thomas Petazzoni
2017-12-13 15:59 ` Alan Tull
2017-12-14 5:27 ` Thomas Petazzoni
2017-12-14 20:10 ` Alan Tull
2017-12-10 22:42 ` Thomas Petazzoni
2018-08-11 15:01 ` Philippe De Muyter
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=20171204165835.33824aa8@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=atull@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-fpga@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=mdf@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).