Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753343Ab3JHNBN (ORCPT ); Tue, 8 Oct 2013 09:01:13 -0400 Received: from mail-ee0-f48.google.com ([74.125.83.48]:63299 "EHLO mail-ee0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751746Ab3JHNBL (ORCPT ); Tue, 8 Oct 2013 09:01:11 -0400 Message-ID: <52540208.3090406@monstr.eu> Date: Tue, 08 Oct 2013 15:00:56 +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: Jason Gunthorpe , Greg Kroah-Hartman , 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 References: <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> <875b2a01-be5a-47d1-b89a-9385d54b9b64@email.android.com> <20131005051056.GA7698@obsidianresearch.com> <1c9db96e-7a36-4ec9-ab16-885780ce6de5@email.android.com> <524FB756.3040203@monstr.eu> <5252B2F4.7050600@monstr.eu> <5252CD30.3070305@monstr.eu> <708b6f80-97a7-41a7-9d5c-fa8bd2a8e0c5@email.android.com> In-Reply-To: <708b6f80-97a7-41a7-9d5c-fa8bd2a8e0c5@email.android.com> X-Enigmail-Version: 1.5.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mWOpBWwjeleVBMk70uvohuOcsnLaWcRnR" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2112 Lines: 58 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --mWOpBWwjeleVBMk70uvohuOcsnLaWcRnR Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 10/07/2013 05:07 PM, H. Peter Anvin wrote: > Special soft IP presenting a PCI device to the host. ok. It means that you should need just different backend for this device which is able to communicate over PCI. I still can't see why this case should be problematic for this fpga manager. As Jason pointed if this is just about JTAG emulation and your data is in different format then you have to create your backend which will support this configuration. I will want to look at gpio jtag emulation to be able to program different board. We have this support for u-boot and doing in Linux should be also possible. I think the question is if we can live with 2/3 user interfaces. I tend to keep firmware one because it is covering a lot of common use cases and it can be easily to use. And then I don't have any preference if sysfs or char device is better. 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 --mWOpBWwjeleVBMk70uvohuOcsnLaWcRnR 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/ iEYEARECAAYFAlJUAgkACgkQykllyylKDCGD6QCdGrqY0JsOhCD1k5wKxi1pRqjV LxMAnjDTdM61OWV/EpEPTU0o7LGYCV65 =ZPGO -----END PGP SIGNATURE----- --mWOpBWwjeleVBMk70uvohuOcsnLaWcRnR-- -- 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/