[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52421829.4050708@zytor.com>
Date: Tue, 24 Sep 2013 15:54:33 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Pavel Machek <pavel@...x.de>
CC: Alan Tull <atull@...era.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Jason Cooper <jason@...edaemon.net>,
Michal Simek <michal.simek@...inx.com>,
linux-kernel@...r.kernel.org, monstr@...str.eu,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dinh Nguyen <dinguyen@...era.com>,
Philip Balister <philip@...ister.org>,
Alessandro Rubini <rubini@...dd.com>,
Mauro Carvalho Chehab <m.chehab@...sung.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Cesar Eduardo Barros <cesarb@...arb.net>,
Joe Perches <joe@...ches.com>,
"David S. Miller" <davem@...emloft.net>,
Stephen Warren <swarren@...dia.com>,
Arnd Bergmann <arnd@...db.de>,
David Brown <davidb@...eaurora.org>,
Dom Cobley <popcornmix@...il.com>
Subject: Re: [RFC PATCH] fpga: Introduce new fpga subsystem
On 09/19/2013 03:08 AM, Pavel Machek wrote:
>
>> The firmware approach is interesting. It might be less flexible
>> compared with my original code (see link to git below) that this is
>
> On the other hand... that's the interface world wants, right? To most
> users, fpga bitstream is just a firmware.
>
No, not really.
The typical assumption with the firmware interface is that there is
exactly one possible firmware for each device (possibly modulated by
driver version, but still.) This is blatantly not true for an FPGA in
the most extreme way possible -- there are an almost infinite number of
ways one can load an FPGA.
However, I have to question the whole idea of an "FPGA subsystem" --
there is an almost infinite number of ways to program an FPGA or FPGA
programming device (which may even be a commodity flash with a
microcontroller or CPLD, and may be shared with other devices), and it
really doesn't make any inherent sense to lump them together.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists