Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755783Ab3IYNzz (ORCPT ); Wed, 25 Sep 2013 09:55:55 -0400 Received: from mail-pd0-f172.google.com ([209.85.192.172]:52968 "EHLO mail-pd0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755619Ab3IYNzy (ORCPT ); Wed, 25 Sep 2013 09:55:54 -0400 MIME-Version: 1.0 In-Reply-To: <20130924221802.GC3837@kroah.com> References: <20130918191517.GQ19937@titan.lakedaemon.net> <20130918203247.GA11181@obsidianresearch.com> <1379539063.31417.23.camel@atx-linux-37> <20130919100833.GC19346@amd.pavel.ucw.cz> <523AD9C5.8060006@monstr.eu> <1379710523.21515.4.camel@atx-linux-37> <1380038126.13235.12.camel@atx-linux-37> <5241B6BC.1010301@monstr.eu> <1380039774.14129.6.camel@atx-linux-37> <20130924221802.GC3837@kroah.com> Date: Wed, 25 Sep 2013 08:55:53 -0500 Message-ID: Subject: Re: [RFC PATCH] fpga: Introduce new fpga subsystem From: Yves Vandervennet To: Greg Kroah-Hartman Cc: Alan Tull , Michal Simek , Pavel Machek , Jason Gunthorpe , Jason Cooper , Michal Simek , linux-kernel@vger.kernel.org, Dinh Nguyen , Philip Balister , Alessandro Rubini , Mauro Carvalho Chehab , Andrew Morton , Cesar Eduardo Barros , Joe Perches , "David S. Miller" , Stephen Warren , Arnd Bergmann , David Brown , Dom Cobley Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1331 Lines: 33 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. Regards Yves > > thanks, > > greg k-h > -- > 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/ -- 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/