Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755358AbaLHW6Y (ORCPT ); Mon, 8 Dec 2014 17:58:24 -0500 Received: from 251.110.2.81.in-addr.arpa ([81.2.110.251]:34698 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751103AbaLHW6V convert rfc822-to-8bit (ORCPT ); Mon, 8 Dec 2014 17:58:21 -0500 Date: Mon, 8 Dec 2014 22:55:19 +0000 From: One Thousand Gnomes To: Grant Likely Cc: Pavel Machek , atull@opensource.altera.com, Greg Kroah-Hartman , Jason Gunthorpe , "H. Peter Anvin" , Michal Simek , Michal Simek , Randy Dunlap , Linux Kernel Mailing List , "devicetree@vger.kernel.org" , Pantelis Antoniou , Rob Herring , Ira Snyder , "linux-doc@vger.kernel.org" , Mark Brown , philip@balister.org, rubini , Steffen Trumtrar , Jason , kyle.teske@ni.com, Nicolas Pitre , "Balbi, Felipe" , Mauro Carvalho Chehab , David Brown , Rob Landley , David Miller , cesarb@cesarb.net, "sameo@linux.intel.com" , Andrew Morton , Linus Walleij , Alan Tull , dinguyen@opensource.altera.com, Yves Vandervennet Subject: Re: [PATCH v2 2/3] fpga manager: framework core Message-ID: <20141208225519.64501d2d@lxorguk.ukuu.org.uk> In-Reply-To: References: <1414007405-32186-1-git-send-email-atull@opensource.altera.com> <1414007405-32186-3-git-send-email-atull@opensource.altera.com> <20141024105200.GA20775@amd> Organization: Intel Corporation X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.24; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 6 Dec 2014 13:00:17 +0000 Grant Likely wrote: > On Fri, Oct 24, 2014 at 11:52 AM, Pavel Machek wrote: > > Hi! > > > >> * /sys/class/fpga_manager//firmware > >> Name of FPGA image file to load using firmware class. > >> $ echo image.rbf > /sys/class/fpga_manager//firmware > > > > I .. still don't think this is good idea. What about namespaces? > > The path corresponds to path in which namespace? > > I don't understand your concern here. This allows userspace to name > the FPGA bitstream that the kernel will use during request_firmware(), > and it will show up as the $FIRMWARE value in the uevent file, but it > is still the responsibility of userspace to choose what to load, and > it can freely ignore the setting of $FIRMWARE if it needs to. I think the entire model here is basically pedicated on a bogus assumption that an FPGA is a one shot device. It's not. It's a fast reloadable reusable device. A lot of work being done with FPGAs in operating systems already involves basically task switching and scheduling FPGAs as a shared resource pool. Trying to nail something together with request_firmware is several years behind the curve. >From userspace it needs to be a open, load, use, close type model, not a static or semi-static pile of mappings. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/