From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753157AbbHTVrE (ORCPT ); Thu, 20 Aug 2015 17:47:04 -0400 Received: from bear.ext.ti.com ([192.94.94.41]:43197 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751849AbbHTVrD (ORCPT ); Thu, 20 Aug 2015 17:47:03 -0400 Message-ID: <55D64AD2.9060900@ti.com> Date: Thu, 20 Aug 2015 17:46:58 -0400 From: Murali Karicheri Organization: Texas Instruments User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: , Subject: Question on adding a firmware ihex file in the kernel source Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org All, Please help me understand the procedure to add a firmware ihex file to kernel source tree under firmware/ folder. The README.AddingFirmware file explains that file should be added to git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git and the patch for the same to be send to linux-firmware@kernel.org. And this requires it to be in binary form. How does then that end up in the firmware/ folder of the Linux source tree as an ihex file? I would like to have one of the firmware statically built into the kernel as it is needed to be loaded even before file system is initialized in kernel (network driver firmware). Some other firmwares are to be used from the filesystem. Both would make use of the request_firmare() interface. Please help me understand the procedure. Thanks -- Murali Karicheri Linux Kernel, Keystone