lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 16 Dec 2016 10:18:51 +0100
From:   "Luis R. Rodriguez" <mcgrof@...nel.org>
To:     Rafał Miłecki <zajec5@...il.com>
Cc:     Daniel Wagner <daniel.wagner@...-carit.de>,
        "Luis R. Rodriguez" <mcgrof@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Ming Lei <ming.lei@...onical.com>, Tom Gundersen <teg@...m.no>,
        Mauro Carvalho Chehab <mchehab@....samsung.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Vikram Mulukutla <markivx@...eaurora.org>,
        Stephen Boyd <stephen.boyd@...aro.org>,
        Mark Brown <broonie@...nel.org>, zohar@...ux.vnet.ibm.com,
        Takashi Iwai <tiwai@...e.de>,
        Johannes Berg <johannes@...solutions.net>,
        Christian Lamparter <chunkeey@...glemail.com>,
        Hauke Mehrtens <hauke@...ke-m.de>,
        Josh Boyer <jwboyer@...oraproject.org>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>,
        David Woodhouse <dwmw2@...radead.org>, jslaby@...e.com,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        luto@...capital.net, Fengguang Wu <fengguang.wu@...el.com>,
        Richard Purdie <rpurdie@...ys.net>,
        Jacek Anaszewski <j.anaszewski@...sung.com>,
        Abhay_Salunke@...l.com, Julia Lawall <Julia.Lawall@...6.fr>,
        Gilles.Muller@...6.fr, nicolas.palix@...g.fr, dhowells@...hat.com,
        bjorn.andersson@...aro.org,
        Arend Van Spriel <arend.vanspriel@...adcom.com>,
        Kalle Valo <kvalo@...eaurora.org>
Subject: Re: [PATCH 3/5] firmware: revamp firmware documentation

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@...-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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ