[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5242F880.4020902@monstr.eu>
Date: Wed, 25 Sep 2013 16:51:44 +0200
From: Michal Simek <monstr@...str.eu>
To: Yves Vandervennet <rocket.yvanderv@...il.com>
CC: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Tull <atull@...era.com>, Pavel Machek <pavel@...x.de>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Jason Cooper <jason@...edaemon.net>,
Michal Simek <michal.simek@...inx.com>,
linux-kernel@...r.kernel.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/25/2013 03:55 PM, Yves Vandervennet wrote:
> Greg,
>
>>> The default hotplug-script doesn't do anything special (that the kernel
>>> couldn't do by itself). What's great is that it could call another
>>> script that adds headers or does whatever other special un-gzipping or
>>> other massaging that the firmware image needs before it gets loaded.
>>
>> Only if you need to do something "special" like this could it justify
>> not using the in-kernel firmware loader. Also note that I think future
>> versions of udev will have the udev firmware loader removed entirely, so
>> watch out for that.
> If the bit stream is in raw format, the kernel can deal with it.
> however, there are "richer" formats for the FPGA bit streams that need
> to be parsed in order to extract the raw data that an FPGA accepts. In
> this case, user space must be involved.
For xilinx there are two fpga formats which are commonly used. BIT and BIN.
BIT format is that richer one but there is no public documentation available
for it. IRC hwicap just support BIT format and because of any unknown decision
zynq can work just with BIN.
But getting BIN from BIT is easy and currently we have the support
in our driver for doing it.
Not sure what options there are for cplds.
But anyway AFAIK richer formats are not problem for us.
The same situation should be for partial bitstreams too.
Thanks,
Michal
--
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
Download attachment "signature.asc" of type "application/pgp-signature" (264 bytes)
Powered by blists - more mailing lists