From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1760043AbcLPJS7 (ORCPT <rfc822;w@1wt.eu>);
        Fri, 16 Dec 2016 04:18:59 -0500
Received: from mx2.suse.de ([195.135.220.15]:36376 "EHLO mx2.suse.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1759928AbcLPJSz (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 16 Dec 2016 04:18:55 -0500
Date: Fri, 16 Dec 2016 10:18:51 +0100
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= <zajec5@gmail.com>
Cc: Daniel Wagner <daniel.wagner@bmw-carit.de>,
        "Luis R. Rodriguez" <mcgrof@kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Ming Lei <ming.lei@canonical.com>, Tom Gundersen <teg@jklm.no>,
        Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Vikram Mulukutla <markivx@codeaurora.org>,
        Stephen Boyd <stephen.boyd@linaro.org>,
        Mark Brown <broonie@kernel.org>, zohar@linux.vnet.ibm.com,
        Takashi Iwai <tiwai@suse.de>,
        Johannes Berg <johannes@sipsolutions.net>,
        Christian Lamparter <chunkeey@googlemail.com>,
        Hauke Mehrtens <hauke@hauke-m.de>,
        Josh Boyer <jwboyer@fedoraproject.org>,
        Dmitry Torokhov <dmitry.torokhov@gmail.com>,
        David Woodhouse <dwmw2@infradead.org>, jslaby@suse.com,
        Linus Torvalds <torvalds@linux-foundation.org>, luto@amacapital.net,
        Fengguang Wu <fengguang.wu@intel.com>,
        Richard Purdie <rpurdie@rpsys.net>,
        Jacek Anaszewski <j.anaszewski@samsung.com>, Abhay_Salunke@dell.com,
        Julia Lawall <Julia.Lawall@lip6.fr>, Gilles.Muller@lip6.fr,
        nicolas.palix@imag.fr, dhowells@redhat.com, bjorn.andersson@linaro.org,
        Arend Van Spriel <arend.vanspriel@broadcom.com>,
        Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [PATCH 3/5] firmware: revamp firmware documentation
Message-ID: <20161216091851.GN13946@wotan.suse.de>
References: <20161213030828.17820-1-mcgrof@kernel.org>
 <20161213030828.17820-4-mcgrof@kernel.org>
 <ab2f9c97-77a4-e451-c2e5-87076b66a8b6@bmw-carit.de>
 <CACna6rz_TwKkatteuN2f+_mG6gOaDRMuyKTiOb=e=PbRavrS6g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CACna6rz_TwKkatteuN2f+_mG6gOaDRMuyKTiOb=e=PbRavrS6g@mail.gmail.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Dec 13, 2016 at 02:30:22PM +0100, Rafał Miłecki wrote:
> On 13 December 2016 at 14:26, Daniel Wagner <daniel.wagner@bmw-carit.de> 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.

>>From what I recall in my 802.11 days this can be often very specific
per *batch* of cards not just chip/device model, so this depends on the
manufacturing process and date.

  Luis