From: maximilian attems <maks@stro.at>
To: 982579@bugs.debian.org
Cc: Bernhard <bewoern1@gmail.com>,
vagrant@debian.org, linux-firmware@kernel.org
Subject: Re: Bug#982579: Solution for loading firmware
Date: Tue, 16 Feb 2021 19:46:20 +0100 [thread overview]
Message-ID: <YCwS/PcGa4uaQQsd@photino.stro.at> (raw)
In-Reply-To: <YCtw7RaNEyod8mxb@photino.stro.at>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
> > 1. Copy file brcmfmac43430-sdio.AP6212.txt from upstream to lib/firmware/brcm
>
> so indeed it is a bug that we don't ship this one from upstream,
> will fix this in next Debian upload.
this needs to go in the debian git, will do soonish. (:
> > 2. Create symbolic link named brcmfmac43430-sdio.sinovoip.bpi-m3.txt to the AP6212-file
I am confused by this, as you did *not* submit an error log that showed
a request for this file, is this to add support to another device,
please be specific.
> > 3. Create symbolic link named brcmfmac43430-sdio.sinovoip.bpi-m2-ultra.txt to the AP6212-file
> this should be reported upstream, so that everyone takes advantage of
> it, hence adding linux-firmware mailinglist on Cc, happy to cook up
> a patch next 24hs.
sent, to add that symlink upstream.
thank you!
--
maks
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-02-16 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6fe1da22eb783f020de8bfa3b9f2b1457e593a4b.camel@gmail.com>
[not found] ` <cbcb1fabd3a005142216213ca67c1a1664b7958a.camel@gmail.com>
2021-02-16 7:14 ` Bug#982579: Solution for loading firmware maximilian attems
2021-02-16 18:44 ` maximilian attems
2021-02-22 21:24 ` maximilian attems
2021-03-03 18:25 ` Josh Boyer
2021-03-03 19:56 ` maximilian attems
2021-02-16 18:46 ` maximilian attems [this message]
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=YCwS/PcGa4uaQQsd@photino.stro.at \
--to=maks@stro.at \
--cc=982579@bugs.debian.org \
--cc=bewoern1@gmail.com \
--cc=linux-firmware@kernel.org \
--cc=vagrant@debian.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;
as well as URLs for NNTP newsgroup(s).