Return-path: Received: from mail-vk0-f66.google.com ([209.85.213.66]:34420 "EHLO mail-vk0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752964AbcF2Om6 (ORCPT ); Wed, 29 Jun 2016 10:42:58 -0400 MIME-Version: 1.0 In-Reply-To: <1467209074-15634-1-git-send-email-hdegoede@redhat.com> References: <1467209074-15634-1-git-send-email-hdegoede@redhat.com> From: Jonas Gorski Date: Wed, 29 Jun 2016 16:42:32 +0200 Message-ID: (sfid-20160629_164311_895731_86E3CAA8) Subject: Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property To: Hans de Goede Cc: "John W . Linville" , Arend van Spriel , Maxime Ripard , Chen-Yu Tsai , "linux-wireless@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , devicetree , linux-sunxi@googlegroups.com Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi, On 29 June 2016 at 16:04, Hans de Goede wrote: > Add a brcm,nvram_file_name dt property to allow overruling the default > nvram filename for sdio devices. The idea is that we can specify a > board specific nvram file, e.g. brcmfmac43362-ap6210.txt for boards > with an ap6210 wifi sdio module and ship this in linux-firmware, so > that wifi will work out of the box, without requiring users to find > and then manually install the right nvram file for their board. Directly defining a filename doesn't seem like a good OS-agnostic approach. Maybe an alternative would be to add a model-property to the nodes (this is allowed) and make brcmfmac to request "FWFILENAME-" as firmware if set? That would leave it to the OS on how the filename is set. Regards Jonas