From: Arend van Spriel <arend@broadcom.com>
To: Benjamin Adler <benadler@gmx.net>
Cc: brcm80211 development <brcm80211-dev-list@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BCM4330 linux support
Date: Sat, 7 Feb 2015 19:12:27 +0100 [thread overview]
Message-ID: <54D6558B.4010500@broadcom.com> (raw)
In-Reply-To: <54D57031.9090903@gmx.net>
On 02/07/15 02:53, Benjamin Adler wrote:
> >> Does AP also work for you?
> >
> > Yes, but not sure if your firmware supports it.
>
> Who can I ask for this information?
Can you do a hexdump of your firmware image, ie.:
hexdump -C 4330rtecdc.bin | tail -20
Regards,
Arend
next prev parent reply other threads:[~2015-02-07 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54D3FF89.502@phoenix-aerial.com>
2015-02-06 9:10 ` BCM4330 linux support Arend van Spriel
2015-02-06 14:45 ` Ben Adler
2015-02-06 16:00 ` Arend van Spriel
2015-02-07 1:53 ` Benjamin Adler
2015-02-07 18:12 ` Arend van Spriel [this message]
2015-02-07 19:14 ` Benjamin Adler
2015-02-07 19:37 ` Arend van Spriel
2015-02-07 22:20 ` Benjamin Adler
2015-02-06 16:06 ` Arend van Spriel
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=54D6558B.4010500@broadcom.com \
--to=arend@broadcom.com \
--cc=benadler@gmx.net \
--cc=brcm80211-dev-list@broadcom.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).