Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751502Ab3JDXuP (ORCPT ); Fri, 4 Oct 2013 19:50:15 -0400 Received: from quartz.orcorp.ca ([184.70.90.242]:37912 "EHLO quartz.orcorp.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751126Ab3JDXuN (ORCPT ); Fri, 4 Oct 2013 19:50:13 -0400 Date: Fri, 4 Oct 2013 17:49:29 -0600 From: Jason Gunthorpe To: Greg Kroah-Hartman Cc: "H. Peter Anvin" , monstr@monstr.eu, Pavel Machek , Michal Simek , linux-kernel@vger.kernel.org, Alan Tull , Dinh Nguyen , Philip Balister , Alessandro Rubini , Steffen Trumtrar , 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 Message-ID: <20131004234929.GB3652@obsidianresearch.com> 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> <524F04FD.5020804@zytor.com> <20131004233341.GA4028@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131004233341.GA4028@kroah.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Broken-Reverse-DNS: no host name found for IP address 10.0.0.161 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1219 Lines: 30 On Fri, Oct 04, 2013 at 04:33:41PM -0700, Greg Kroah-Hartman wrote: > > 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. > > Ideally I thought this would be just like "firmware", you dump the file > to the FPGA, it validates it and away you go with a new image running in > the chip. That is 99% of the use cases. The other stuff people are talking about is fringe. I've been doing FPGAs for > 10 years and I've never once used read back via the config bus. In fact all my FPGAs turn that feature off once they are loaded. Partial reconfiguration is very specialized, and hard to use from a FPGA design standpoint. I also think it is sensible to focus this interface on simple SRAM FPGAs, not FLASH based stuff, or whatever complex device required a byte code interpreter (never heard of that before). Jason -- 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/