From: "Arend van Spriel" <arend@broadcom.com>
To: "John Talbut" <jt@dpets.co.uk>,
"Ben Hutchings" <ben@decadent.org.uk>,
"David Woodhouse" <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: brcmsmac: firmware
Date: Tue, 2 Apr 2013 12:55:08 +0200 [thread overview]
Message-ID: <515AB90C.7080509@broadcom.com> (raw)
In-Reply-To: <5157F5ED.1010505@dpets.co.uk>
On 03/31/2013 10:38 AM, John Talbut wrote:
> On 29/03/13 11:06, Arend van Spriel wrote:
>> On 03/29/2013 07:14 AM, John Talbut wrote:
>>>
>>> As a matter of curiosity, why is the code currently in the firmware not
>>> included in the kernel driver?
>>
>> Well. the kernel driver is what is running on the host. In your case on
>> the Atom processor. The firmware contains of initialization data for the
>> device and code that is using an instruction set that is dedicated to
>> the broadcom device so there is no way to move that into the driver
>> other than as a binary blob, but that is not acceptable in open-source
>> Linux drivers. So people in the community invented the user-space
>> firmware loading stuff.
>>
>> Gr. AvS
>
> Hi Arend
>
> Hmm. As I understand it, if the source code for the initialization data
> for the device and code that is using an instruction set that is
> dedicated to the broadcom device was released then the code could be
> compiled into the kernel.
>
> Do you have any sense of why Broadcom does not do this?
Well. Your understanding is different from mine. Here is mine: the linux
kernel aims for a separation between kernel code and firmware (mainly to
resolve licensing issues, I think) and all drivers with embedded
firmware have/are converted to using the request_firmware API. This is
described in [1].
Gr. AvS
[1]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/firmware/README.AddingFirmware
parent reply other threads:[~2013-04-02 10:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5157F5ED.1010505@dpets.co.uk>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=515AB90C.7080509@broadcom.com \
--to=arend@broadcom.com \
--cc=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=jt@dpets.co.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox