From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932854AbcLMNaY (ORCPT ); Tue, 13 Dec 2016 08:30:24 -0500 Received: from mail-oi0-f68.google.com ([209.85.218.68]:36226 "EHLO mail-oi0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752056AbcLMNaX (ORCPT ); Tue, 13 Dec 2016 08:30:23 -0500 MIME-Version: 1.0 In-Reply-To: References: <20161213030828.17820-1-mcgrof@kernel.org> <20161213030828.17820-4-mcgrof@kernel.org> From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Date: Tue, 13 Dec 2016 14:30:22 +0100 Message-ID: Subject: Re: [PATCH 3/5] firmware: revamp firmware documentation To: Daniel Wagner Cc: "Luis R. Rodriguez" , Greg Kroah-Hartman , Ming Lei , Tom Gundersen , Mauro Carvalho Chehab , Linux Kernel Mailing List , Vikram Mulukutla , Stephen Boyd , Mark Brown , zohar@linux.vnet.ibm.com, Takashi Iwai , Johannes Berg , Christian Lamparter , Hauke Mehrtens , Josh Boyer , Dmitry Torokhov , David Woodhouse , jslaby@suse.com, Linus Torvalds , luto@amacapital.net, Fengguang Wu , Richard Purdie , Jacek Anaszewski , Abhay_Salunke@dell.com, Julia Lawall , Gilles.Muller@lip6.fr, nicolas.palix@imag.fr, dhowells@redhat.com, bjorn.andersson@linaro.org, Arend Van Spriel , Kalle Valo Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13 December 2016 at 14:26, Daniel Wagner wrote: >> +* Some firmware files may be really large in size. The remote-proc >> subsystem >> + is an example subsystem which deals with these sorts of firmware >> +* The firmware may need to be scraped out from some device specific >> location >> + dynamically, an example is calibration data for for some WiFi chipsets. > > > Maybe it is worth to mention, that the calibration data is unique to a given > chip, so it is individual. That is you would need to built for each device > you sell its own kernel. It's commonly unique to the device model, not a chip. The same chip can be used with different power amplifiers or different antennas. That's why you need model (board) specific calibration data.