All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] firmware file for wifi
Date: Sun, 21 Jun 2015 12:16:02 +0200	[thread overview]
Message-ID: <20150621101602.GA3625@free.fr> (raw)
In-Reply-To: <20150621004956.GB23827@arthur-debian>

Arthur, All,

On 2015-06-21 02:49 +0200, Arthur LAMBERT spake thusly:
> Le Friday 19 Jun 2015 ?? 19:20:17 (+0200), Yann E. MORIN a ?crit :
> > On 2015-06-19 17:29 +0200, Arthur LAMBERT spake thusly:
> > > diff --git a/board/freescale/warpboard/rootfs_overlay/lib/firmware/brcm/brcmfmac4330-sdio.txt b/board/freescale/warpboard/rootfs_overlay/lib/firmware/brcm/brcmfmac4330-sdio.txt
> > > new file mode 100644
> > > index 0000000..9546246
> > > --- /dev/null
> > > +++ b/board/freescale/warpboard/rootfs_overlay/lib/firmware/brcm/brcmfmac4330-sdio.txt
> >
> > What is the purpose of this file?
> >
> > Is it really specific to the warpboard, or can it be used on other
> > boards? I mean, why do we need this file specifically on the warpboard?
> >
> > How is this file used by the firmware?
> >
> 
> This file is requested by the brcmfmac driver. It is not specific to warpboard, but specific to brcm4330.
> This txt file is also present in BR2_PACKAGE_LINUX_FIRMWARE_BRCM_BCM43XX so I can also remove it from the patch

No, this file is not present in linux-firmware, and is not installed by
Buildroot in any way.

Also, I had a look at the driver, and indeed it requests this file
unconditionally. I wonder what would be the best solution to provide
this file, since it is not installed by linux-firmware.

I'm a bit wary to provide a generic one, since I can see it contains:
  - vendor/product/etc.. IDs, not too problematic
  - macaddr, not too problematic; still...
  - a lot of magic numbers in platform-specific variables.

So, I think the best solution for now would be to keep that file in the
board directory, like you have for now.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-06-21 10:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 15:29 [Buildroot] [PATCH 1/4] defconfig for warpboard Arthur LAMBERT
2015-06-19 15:29 ` [Buildroot] [PATCH 2/4] README file for wifi/bluetooth support Arthur LAMBERT
2015-06-19 15:29 ` [Buildroot] [PATCH 3/4] fix bluetooth support on kernel 4.0, and warpboard kernel config Arthur LAMBERT
2015-06-19 15:29 ` [Buildroot] [PATCH 4/4] firmware file for wifi Arthur LAMBERT
2015-06-19 17:20   ` Yann E. MORIN
2015-06-21  0:49     ` Arthur LAMBERT
2015-06-21 10:16       ` Yann E. MORIN [this message]
2015-06-19 21:48 ` [Buildroot] [PATCH 1/4] defconfig for warpboard Arnout Vandecappelle
2015-06-19 22:00   ` Arnout Vandecappelle
2015-06-21  1:00     ` Arthur LAMBERT
2015-06-21 13:26       ` Arnout Vandecappelle
2015-06-20  9:44   ` Arnout Vandecappelle
2015-06-21  0:56   ` Arthur LAMBERT
2015-06-21 13:32     ` Arnout Vandecappelle

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=20150621101602.GA3625@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.