From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:54252 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756613AbcKXL7L (ORCPT ); Thu, 24 Nov 2016 06:59:11 -0500 From: Kalle Valo To: IgorMitsyanko Cc: Johannes Berg , , , , , , Igor Mitsyanko , Kamlesh Rath , Sergey Matyukevich , Avinash Patil , Ben Hutchings , Kyle McMartin Subject: Re: [RFC] qtn: add FullMAC firmware for Quantenna QSR10G wifi device References: <1478700000-11624-1-git-send-email-igor.mitsyanko.os@quantenna.com> <1478706966.18306.1.camel@sipsolutions.net> <2fcb5f28-808e-f296-7e91-e5185e7577c9@quantenna.com> <1478725543.21403.4.camel@sipsolutions.net> <1478864146.4129.4.camel@sipsolutions.net> <87d1hmnrqj.fsf@purkki.adurom.net> Date: Thu, 24 Nov 2016 13:59:03 +0200 In-Reply-To: (IgorMitsyanko's message of "Wed, 23 Nov 2016 20:09:32 +0300") Message-ID: <87shqhf5rs.fsf@kamboji.qca.qualcomm.com> (sfid-20161124_125923_426770_F4633F9F) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: IgorMitsyanko writes: > On 11/23/2016 06:25 PM, Kalle Valo wrote: >> IgorMitsyanko writes: >> >>> To clarify with you and Kalle, as persons involved with >>> linux-wireless: is my understanding correct that submitting firmware >>> into linux-fimware repository is a prerequisite to accepting new >>> driver into linux-wireless? >> In my opinion the most important is that the device is usable with an >> upstream driver so that anyone can start using the driver (if they have >> the hardware). >> >>> There is an option to start Quantenna device from internal flash >>> memory, no external binary files involved. If we will introduce this >>> functionality and remove code handling external firmware for now >>> (until firmware problem resolved), would that allow driver to be >>> reviewed/accepted? >> Do all the publically available hardware contain the firmware in >> internal flash (flashed in the factory)? Or is this something which must >> be installed separately for each board's internal flash by the user? > > Each board must have flash installed on it, preflashed in the factory > with uboot and firmware binary, otherwise board won't boot Will the preflashed firmware binary will have all the normal functionality needed by this driver? I mean that you can start an AP interface etc. > (won't boot without uboot, firmware itself is not mandatory). Are you expecting that there are devices on the field which have uboot preflashed but not the firmware? > Booting from flash is default behavior on boards that are currently on > the market, but for developemnt purpuses it's not very convenient and > harder to upgrade. Sure, I understand. >> BTW, the original mail with the firmware image didn't make it to the >> list, I guess it was too big? It would be good if you could post the >> license separately so that people can see it. >> > > I resent the email without binary patch to linux-wireless. Saw it now, thanks. -- Kalle Valo