Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] wireless-regdb: new package
Date: Sun, 07 Apr 2013 10:37:48 -0300	[thread overview]
Message-ID: <516176AC.5040604@zacarias.com.ar> (raw)
In-Reply-To: <1364165118-6984-1-git-send-email-dimitris@siganos.org>

On 03/24/2013 07:45 PM, Dimitrios Siganos wrote:

> +define WIRELESS_REGDB_INSTALL_TARGET_CMDS
> +    install -m 644 -D -T $(@D)/regulatory.bin $(TARGET_DIR)/usr/lib/crda/regulatory.bin
> +    install -m 644 -D -T $(@D)/linville.key.pub.pem $(TARGET_DIR)/usr/lib/crda/pubkeys/linville.key.pub.pem
> +endef

Hi.
Doesn't crda expect the pubkeys in /etc/wireless-regdb/pubkeys path?
At least that's the default and you didn't seem to change that in your
crda v2 package.
Regards.

  reply	other threads:[~2013-04-07 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24 22:45 [Buildroot] [PATCH v4] wireless-regdb: new package Dimitrios Siganos
2013-04-07 13:37 ` Gustavo Zacarias [this message]
2013-04-08 10:15   ` Dimitrios Siganos

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=516176AC.5040604@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.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