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 file >> 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. >> > > 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 -- 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
Attachment:
signature.asc
Description: OpenPGP digital signature
