From: David Lang <david@lang.hm>
To: Aaron Wood <woody77@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] might be a good thing
Date: Mon, 21 Mar 2016 04:45:17 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1603210443530.6230@nftneq.ynat.uz> (raw)
In-Reply-To: <CALQXh-MoA_918m1JKUUWfE=CZTujrpWm9=9B3Uu9fmh32Zc6wQ@mail.gmail.com>
[-- Attachment #1: Type: TEXT/Plain, Size: 1091 bytes --]
sounds like a good time for someone else to get in the mix, aiming for the low
end with a simple/cheap RF chipset that supports doing all the 'hard stuff' in
software. Someone who would be happy to have the community doing the hard stuff
for them.
David Lang
On Fri, 18 Mar 2016, Aaron Wood wrote:
> It will be interesting to see if that includes APs or just clients. The
> OEMs are going to lose one of their big levers on price, if they lose
> Broadcom from the mix (and Qualcomm is going to make some good money).
> Although Marvell's chunk of that space has been growing...
>
> -Aaron
>
> On Fri, Mar 18, 2016 at 3:46 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>>
>> http://www.bidnessetc.com/65767-apple-component-maker-broadcom-abandon-low-margin-wifi-operations/
>>
>>
>> --
>> Dave Täht
>> Let's go make home routers and wifi faster! With better software!
>> https://www.gofundme.com/savewifi
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>
[-- Attachment #2: Type: TEXT/PLAIN, Size: 164 bytes --]
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2016-03-21 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 22:46 Dave Taht
2016-03-19 2:40 ` Aaron Wood
2016-03-21 11:45 ` David Lang [this message]
2016-03-21 11:48 ` Outback Dingo
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1603210443530.6230@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=woody77@gmail.com \
/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