From: "David P. Reed" <dpreed@deepplum.com>
To: "David Lang" <david@lang.hm>
Cc: "Dave Taht" <dave.taht@gmail.com>,
"Rajkumar Manoharan" <rmanohar@codeaurora.org>,
"Make-Wifi-fast" <make-wifi-fast@lists.bufferbloat.net>,
"linux-wireless" <linux-wireless@vger.kernel.org>,
"ath10k" <ath10k@lists.infradead.org>,
"Ben Greear" <greearb@candelatech.com>,
"Felix Fietkau" <nbd@nbd.name>
Subject: Re: [Make-wifi-fast] [PATCH v3 3/6] mac80211: Add airtimeaccounting and scheduling to TXQs
Date: Wed, 21 Nov 2018 10:28:55 -0500 (EST) [thread overview]
Message-ID: <1542814135.446217011@apps.rackspace.com> (raw)
Really? Tires are Bluetooth? I don't think mine are, but now I want to figure out how that works. 1600Chips/sec is 600 microseconds per chip. They spin at up to, say, radial rates that are a 100 revs/sec and thus take maybe 10 msec. to travel 30 cm. How much warble in a chip frequency is there?
Ok, maybe they only need to work when the car is stopped.
I would design a tire pressure system that sends, maybe, 10 bits per second, at most. Or calibrate the sensor to produce 1 bit, and use the car metal frame to carry the signal to the computer as a single bit. A very slowly varying sensor can be sensed without needing a battery, by using some passive, tuned circuit.
Bluetooth is way overkill, but cheap. I doubt it works well in the application, though.
-----Original
From: "David Lang" <david@lang.hm>
Sent: Mon, Nov 19, 2018 at 9:12 pm
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "Dave Taht" <dave.taht@gmail.com>, "Rajkumar Manoharan" <rmanohar@codeaurora.org>, "Make-Wifi-fast" <make-wifi-fast@lists.bufferbloat.net>, "linux-wireless" <linux-wireless@vger.kernel.org>, "ath10k" <ath10k@lists.infradead.org>, "Ben Greear" <greearb@candelatech.com>, "Felix Fietkau" <nbd@nbd.name>
Subject: Re: [Make-wifi-fast] [PATCH v3 3/6] mac80211: Add airtimeaccounting and scheduling to TXQs
On Mon, 19 Nov 2018, Dave Taht wrote:
>> I'm not sure if this was a fluke or not, but at Starbucks recently I sat outside,
>> right next to their window, and could not scan their AP at all. Previously, I sat
>> inside, 3 feet away through the glass, and got great signal. I wonder what that was
>> all about! Maybe special tinting that blocks RF? Or just dumb luck of some sort.
>
> Ya know, I could definitely see a market for a material like that! I'd
> like it for my car, so bluetooth wouldn't escape.
That would break your tire pressure sensors (each car is rolling around
broadcasting 4 unique bluetooth IDs, not hard to track)
David Lang
_______________________________________________
Make-wifi-fast mailing list
Make-wifi-fast@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/make-wifi-fast
next reply other threads:[~2018-11-21 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 15:28 David P. Reed [this message]
2018-11-21 15:38 ` Dave Taht
2018-11-21 20:58 ` Sebastian Gottschall
2018-11-21 20:11 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
2018-11-21 15:14 David P. Reed
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1542814135.446217011@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=ath10k@lists.infradead.org \
--cc=dave.taht@gmail.com \
--cc=david@lang.hm \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=nbd@nbd.name \
--cc=rmanohar@codeaurora.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