Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] more hope for wifi
Date: Wed, 18 Mar 2015 12:50:23 -0700	[thread overview]
Message-ID: <CAA93jw5to+vJ_si5diBUapscjSttiar2mqi5m4YtwjT1Tn0xyA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 388 bytes --]

http://www.engineering.columbia.edu/new-technology-may-double-radio-frequency-data-capacity-0

(also being discussed on slashdot)

I think there was some other full duplex technology developed at stanford
discussed about 6 months back?

-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

[-- Attachment #2: Type: text/html, Size: 742 bytes --]

             reply	other threads:[~2015-03-18 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 19:50 Dave Taht [this message]
2015-03-18 19:51 ` Dave Taht

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=CAA93jw5to+vJ_si5diBUapscjSttiar2mqi5m4YtwjT1Tn0xyA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox