From: "W. van den Akker" <listsrv@wilsoft.nl>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>
Subject: Re: Atheros Linux wireless support - ramifications of reverse engineering alien technology
Date: Wed, 1 Apr 2009 22:56:10 +0200 [thread overview]
Message-ID: <200904012256.10450.listsrv@wilsoft.nl> (raw)
In-Reply-To: <43e72e890904011147p5e22eaeejac3fddd2b9cddcfc@mail.gmail.com>
On Wednesday 01 April 2009 20:47:33 Luis R. Rodriguez wrote:
> Fellow Linux wireless hackers,
>
> We regret to inform you that Atheros is no longer going to be working
> with the upstream Linux kernel community. We have received notice from
> the Atheros Alien Reverse Engineering Division (AARED) that we have
> given away too much information by opening up our drivers, furthermore
> our batch of newly arrived organic-based wireless technology at AARED
> is far too advanced and current wireless research cannot explain our
> achieved max thoughput figures which violate The Shannon Theorem [1].
> The AARED also fears that the FOSS community will start creating
> communication portals to parallel universes with our hardware[2], a
> feature which is theoretically possible with our latest organic-based
> wireless technology, but unfortunately cannot be allowed due to
> regulatory consideration near the Council Chambers of Zion [3].
>
> We may be able to address the communication portal regulatory
> considerations through CRDA [4] and for this we do ask for you advice,
> but please be aware that we already are facing hard questions from the
> NSA, specifically from Agent Smith [5]. The NSA ultimately fears that
> the alien community we have reversed engineered their wireless
> technology from may be watching us and may soon start sending hostile
> ships to earth for retribution, these concerns are coming directly
> from The Architect [6].
>
> The Atheros Linux team
>
> [1] http://en.wikipedia.org/wiki/Shannon_theorem
> [2]
> http://www.sciam.com/article.cfm?id=the-great-cosmic-roller-coaster-ride
> [3] http://en.wikipedia.org/wiki/Zion_(The_Matrix)
> [4] http://wireless.kernel.org/en/developers/Regulatory/CRDA
> [5] http://en.wikipedia.org/wiki/Agent_Smith
> [6] http://en.wikipedia.org/wiki/Architect_(The_Matrix)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
April fool?? :D:D
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2009-04-01 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 18:47 Atheros Linux wireless support - ramifications of reverse engineering alien technology Luis R. Rodriguez
2009-04-01 18:54 ` [ath9k-devel] " Tyler Mills
2009-04-01 20:56 ` W. van den Akker [this message]
2009-04-02 19:51 ` Maxim Levitsky
2009-04-02 20:02 ` Larry Finger
2009-04-02 20:36 ` Maxim Levitsky
2009-04-02 21:00 ` David Miller
2009-04-09 15:30 ` Kristoffer Ericson
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=200904012256.10450.listsrv@wilsoft.nl \
--to=listsrv@wilsoft.nl \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.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