From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] owl-linux: new package
Date: Thu, 10 May 2012 09:16:32 +0200 [thread overview]
Message-ID: <20120510091632.2f277fa8@skate> (raw)
In-Reply-To: <1336580658-4324-1-git-send-email-spdawson@gmail.com>
Le Wed, 9 May 2012 17:24:18 +0100,
spdawson at gmail.com a ?crit :
> diff --git a/package/Config.in b/package/Config.in
> index fb1b08f..971b106 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -208,6 +208,7 @@ source "package/mtd/Config.in"
> source "package/ntfs-3g/Config.in"
> source "package/open2300/Config.in"
> source "package/openocd/Config.in"
> +source "package/owl-linux/Config.in"
> source "package/parted/Config.in"
> source "package/pciutils/Config.in"
> source "package/picocom/Config.in"
At some point maybe it'll make sense to have a section for Device
drivers, but we don't have enough at the moment to justify a separate
section, IMO.
> +config BR2_PACKAGE_OWL_LINUX
> + bool "H&D Wireless SPB104 SD-card WiFi SIP"
You should add a:
depends on BR2_LINUX_KERNEL
here.
> +define OWL_LINUX_BUILD_CMDS
> + $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) KERNELDIR=$(LINUX_DIR) CROSS_COMPILE=$(TARGET_CROSS) ARCH=$(KERNEL_ARCH)
> +endef
Any reason not to use $(LINUX_MAKE_FLAGS) here?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-05-10 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 16:24 [Buildroot] [PATCH] owl-linux: new package spdawson at gmail.com
2012-05-10 7:16 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-10 7:58 spdawson at gmail.com
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=20120510091632.2f277fa8@skate \
--to=thomas.petazzoni@free-electrons.com \
--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