Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751504Ab3JEGtj (ORCPT ); Sat, 5 Oct 2013 02:49:39 -0400 Received: from mail-ee0-f44.google.com ([74.125.83.44]:53656 "EHLO mail-ee0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751378Ab3JEGti (ORCPT ); Sat, 5 Oct 2013 02:49:38 -0400 Message-ID: <524FB678.4020405@monstr.eu> Date: Sat, 05 Oct 2013 08:49:28 +0200 From: Michal Simek Reply-To: monstr@monstr.eu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 MIME-Version: 1.0 To: "H. Peter Anvin" 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> <524F04FD.5020804@zytor.com> <20131004233341.GA4028@kroah.com> <524F5442.20402@zytor.com> In-Reply-To: <524F5442.20402@zytor.com> X-Enigmail-Version: 1.5.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6EuwhS2b9SI0pjAObQITttQ6clq2xb96J" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2221 Lines: 64 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6EuwhS2b9SI0pjAObQITttQ6clq2xb96J Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 10/05/2013 01:50 AM, H. Peter Anvin wrote: > On 10/04/2013 04:33 PM, Greg Kroah-Hartman wrote: >> >> Ideally I thought this would be just like "firmware", you dump the fil= e >> to the FPGA, it validates it and away you go with a new image running = in >> the chip. >> >> But, it sounds like this is much more complicated, so much so that >> configfs might be the correct interface for it, as you can do lots of >> things there, and it is very flexible (some say too flexible...) >> >> A char device, with a zillion different custom ioctls is also a way to= >> do it, but one that I really want to avoid as that gets messy really >> quickly. >> >=20 > I'm not sure that a zillion custom ioctls are necessary, but I think we= > really need to get a better understanding of the various usage cases > (and there are going to be ones where an "FPGA driver" simply makes no > sense at all.) Isn't this a reason to add this to staging area a see where this can go? Thanks, Michal --=20 Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/ Maintainer of Linux kernel - Xilinx Zynq ARM architecture Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform --6EuwhS2b9SI0pjAObQITttQ6clq2xb96J Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJPtngACgkQykllyylKDCEANQCfTL+1S3p2bCvAPLEAJ6Iiacwo PGkAnA+TNkyug8ZqjBmm3IymwTpxw8RA =TXBH -----END PGP SIGNATURE----- --6EuwhS2b9SI0pjAObQITttQ6clq2xb96J-- -- 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/