From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Davide Pesavento <davidepesa@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
<rworkman@slackware.com>
Subject: Re: crda packaging
Date: Mon, 24 Nov 2008 09:36:37 -0800 [thread overview]
Message-ID: <20081124173637.GA6245@tesla> (raw)
In-Reply-To: <2da21fe50811231040i45c3cda5l16379093b4e85265@mail.gmail.com>
On Sun, Nov 23, 2008 at 10:40:58AM -0800, Davide Pesavento wrote:
> On Mon, Nov 17, 2008 at 23:21, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> > On Mon, Nov 17, 2008 at 12:27 PM, Luis R. Rodriguez
> > <lrodriguez@atheros.com> wrote:
> >> On Sun, Nov 16, 2008 at 12:58:43PM -0800, Davide Pesavento wrote:
> >>> On Mon, Oct 20, 2008 at 02:28, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> >>> > On Sun, Oct 19, 2008 at 8:57 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
> >>> >>
> >>> >> Do you think the regulatory database should be split from the package
> >>> >> that contains the crda daemon? If so, regulatory.bin should be
> >>> >> versioned as well...
> >>> >
> >>> > Yes, absolutely, the idea is to split db.txt into a separate git tree
> >>> > too actually so that should help with keeping track of changes
> >>> > separately and thinking of them separately.
> >>> >
> >>> > We just need to get this git tree created. What crda will need though
> >>> > is to wget the RSA public key so it can be built with support for new
> >>> > arbitrary updates to the binary db. Give us a few days, we'll get this
> >>> > setup.
> >>> >
> >>> > Luis
> >>> >
> >>>
> >>> Any updates on this?
> >>
> >> I think we'll have this done by the end of the day.
> >
> > OK this is now done. We have a new git tree which John maintains for
> > the database:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-regdb.git
> >
> > All you need from that is the regulatory.bin, you don't need to run
> > make or anything, just cp the regulatory.bin to the preferred
> > location. Right now this is built into CRDA and its
> > /usr/lib/crda/regulatory.bin.
> >
> > Then do a git pull on crda and try to build and let us know if you run
> > into any issues for packaging. The documentation on the
> > wireless.kernel.org wiki needs some good updating.
> >
> > Luis
> >
>
> Great! Thanks a lot!
> Are there any tarballs around? I couldn't find them on
> http://wireless.kernel.org/download/...
I was working on that and now I'm done, heh. I'll send a new post
announcing these URLs.
Luis
prev parent reply other threads:[~2008-11-24 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 15:57 crda packaging Davide Pesavento
2008-10-20 1:28 ` Luis R. Rodriguez
2008-10-20 20:36 ` Davide Pesavento
2008-10-20 14:04 ` Luis R. Rodriguez
2008-10-20 21:48 ` Davide Pesavento
2008-10-20 22:15 ` Luis R. Rodriguez
2008-10-20 22:39 ` Davide Pesavento
2008-10-20 15:43 ` Luis R. Rodriguez
2008-10-25 9:54 ` Davide Pesavento
2008-10-28 1:38 ` Luis R. Rodriguez
2008-10-20 22:16 ` Luis R. Rodriguez
2008-11-16 20:58 ` Davide Pesavento
2008-11-17 20:27 ` Luis R. Rodriguez
2008-11-17 22:21 ` Luis R. Rodriguez
2008-11-17 22:25 ` Luis R. Rodriguez
2008-11-23 18:40 ` Davide Pesavento
2008-11-24 17:36 ` 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=20081124173637.GA6245@tesla \
--to=lrodriguez@atheros.com \
--cc=davidepesa@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=rworkman@slackware.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).