Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751208Ab3JEEBq (ORCPT ); Sat, 5 Oct 2013 00:01:46 -0400 Received: from terminus.zytor.com ([198.137.202.10]:34787 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750741Ab3JEEBo (ORCPT ); Sat, 5 Oct 2013 00:01:44 -0400 User-Agent: K-9 Mail for Android In-Reply-To: <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> <20131004234929.GB3652@obsidianresearch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [RFC PATCH v2 0/1] FPGA subsystem core From: "H. Peter Anvin" Date: Fri, 04 Oct 2013 21:00:28 -0700 To: Jason Gunthorpe , Greg Kroah-Hartman CC: 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 Message-ID: <875b2a01-be5a-47d1-b89a-9385d54b9b64@email.android.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1514 Lines: 38 Every FPGA toolchain I know of has a way to emit JAM/STAPL bytecode files... and a fair number of programming scenarios need them. Jason Gunthorpe wrote: >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 -- Sent from my mobile phone. Please pardon brevity and lack of formatting. -- 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/