From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Dan E <trg_info@mailhaven.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: CRDA question
Date: Mon, 8 Dec 2008 12:08:06 -0800 [thread overview]
Message-ID: <20081208200806.GI6035@tesla> (raw)
In-Reply-To: <1228687013.25070.1288752601@webmail.messagingengine.com>
On Sun, Dec 07, 2008 at 01:56:53PM -0800, Dan E wrote:
>
> On Fri, 5 Dec 2008 16:19:56 -0800, "Luis R. Rodriguez" wrote:
>
> > If you have actual issues to point out then please point them out or
> > better yet just send a patch for the solution.
>
> Indeed. I envision an alternative scheme that can be optionally
> selected as part of a "reduced footprint for embedded systems" patch
> set/git branch, but that's a ways off.
Keep in mind CRDA was designed with this in mind, you can already do it,
its why we let you customize your database and build your own CRDA. If
you're doing embedded you could just put together a database of the
things you wnat to support. You can also customize it further if you
have customer RFs for example which operate in strange licensed
frequencies too.
The database we provide is just what is used regularly throughout the
world for normal 802.11n operation.
> [OT: Is it correct to reply TO your email addy and CC the list address,
> or is it better to "Reply All"? I have to install a real email client
> and ditch the webmail interface soon for git purposes.]
It doesn't matter.
Luis
prev parent reply other threads:[~2008-12-09 4:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 5:17 CRDA question Dan E
2008-12-05 5:32 ` Luis R. Rodriguez
2008-12-05 22:15 ` Dan E
2008-12-06 0:19 ` Luis R. Rodriguez
2008-12-07 21:56 ` Dan E
2008-12-08 20:08 ` Luis R. Rodriguez [this message]
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=20081208200806.GI6035@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=trg_info@mailhaven.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;
as well as URLs for NNTP newsgroup(s).