Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754057Ab3JDSNX (ORCPT ); Fri, 4 Oct 2013 14:13:23 -0400 Received: from terminus.zytor.com ([198.137.202.10]:59282 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751169Ab3JDSNV (ORCPT ); Fri, 4 Oct 2013 14:13:21 -0400 Message-ID: <524F04FD.5020804@zytor.com> Date: Fri, 04 Oct 2013 11:12:13 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: monstr@monstr.eu CC: Greg Kroah-Hartman , Pavel Machek , Michal Simek , linux-kernel@vger.kernel.org, Alan Tull , Dinh Nguyen , Philip Balister , Alessandro Rubini , Steffen Trumtrar , Jason Gunthorpe , Jason Cooper , Yves Vandervennet , Kyle Teske , Josh Cartwright , Nicolas Pitre , Mark Langsdorf , Felipe Balbi , linux-doc@vger.kernel.org, Mauro Carvalho Chehab , David Brown , Rob Landley , "David S. Miller" , Joe Perches , Cesar Eduardo Barros , Samuel Ortiz , Andrew Morton Subject: Re: [RFC PATCH v2 0/1] FPGA subsystem core References: <524C6D64.8080801@zytor.com> <20131003064915.GB17155@amd.pavel.ucw.cz> <524EC965.70701@monstr.eu> <20131004141646.GA9396@kroah.com> <524ED081.1040600@monstr.eu> <524EF0CE.4040002@zytor.com> <524EFE76.70200@monstr.eu> In-Reply-To: <524EFE76.70200@monstr.eu> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1676 Lines: 38 On 10/04/2013 10:44 AM, Michal Simek wrote: > > If you look at it in general I believe that there is wide range of > applications which just contain one bitstream per fpga and the > bitstream is replaced by newer version in upgrade. For them > firmware interface should be pretty useful. Just setup firmware > name with bitstream and it will be automatically loaded in startup > phase. > > Then there is another set of applications especially in connection > to partial reconfiguration where this can be done statically by > pregenerated partial bitstreams or automatically generated on > target cpu. For doing everything on the target firmware interface > is not the best because everything can be handled by user > application and it is easier just to push this bitstream to do > device and not to save it to the fs. > > I think the question here is if this subsystem could have several > interfaces. For example Alan is asking for adding char support. > Does it even make sense to have more interfaces with the same > backend driver? When this is answered then we can talk which one > make sense to have. In v2 is sysfs and firmware one. Adding char > is also easy to do. > Greg, what do you think? I agree that the firmware interface makes sense when the use of the FPGA is an implementation detail in a fixed hardware configuration, but that is a fairly restricted use case all things considered. -hpa -- 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/