From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id EE368E0172C for ; Tue, 12 Nov 2013 05:21:24 -0800 (PST) Received: from e6520eb (unknown [88.170.243.169]) (Authenticated sender: eukrea) by smtp4-g21.free.fr (Postfix) with ESMTPSA id 097534C8216; Tue, 12 Nov 2013 14:21:16 +0100 (CET) Date: Tue, 12 Nov 2013 14:21:15 +0100 From: Eric =?ISO-8859-1?B?QuluYXJk?= To: Otavio Salvador Message-ID: <20131112142115.4da4c0c3@e6520eb> In-Reply-To: References: <1384188262-7571-1-git-send-email-mario@ossystems.com.br> <1384188262-7571-2-git-send-email-mario@ossystems.com.br> <20131112125151.5bc1d815@e6520eb> <20131112130530.4298eded@e6520eb> Organization: =?ISO-8859-1?B?RXVrculh?= Electromatique X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.22; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-arm-extra][PATCH 2/3] wandboard.inc: add X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Nov 2013 13:21:27 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Otavio, Le Tue, 12 Nov 2013 10:07:11 -0200, Otavio Salvador a =E9crit : > On Tue, Nov 12, 2013 at 10:05 AM, Eric B=E9nard wrote: > > Hi Otavio, > > > > Le Tue, 12 Nov 2013 09:54:16 -0200, > > Otavio Salvador a =E9crit : > >> It does not have the wifi module but it can be used (and is commonly > >> seen doing it) a usb dongle for it. So I think it is good to have the > >> wifi support in. > >> > > with this argument you can also keep bluetooth (or anything else which > > can be hotplug) as this also _can_ be plugged into an USB port ;-) >=20 > What you'd expect? Do you prefer to drop it? >=20 > I am fine with both ways. >=20 I think MACHINE_FEATURES must represent what the machine really have and not what it can have (IMHO, defining if an image must support wifi if the machine doesn't have it by default is more a DISTRO policy or an image level choice). in the wifi case I think this doesn't prevent wifi tools to be installed as packagegroup-base has : ${@base_contains('COMBINED_FEATURES', 'wifi', 'packagegroup-base-wifi', '',d)} \ -> wifi not installed in packagegroup-base if not present in both MACHINE & DISTRO features. but packagegroup-base also have : packagegroup-base-extended : if "wifi" in distro_features and not "wifi" in machine_features and ("pcmcia" in machine_features or "pci" in machine_features or "usbhost" in machine_features): d.setVar("ADD_WIFI", "packagegroup-base-wifi") So as we have usbhost (and pci) packagegroup-base-extended will get wifi tools even if MACHINE_FEATURES doesn't have it. in core-image.bbclass we have : CORE_IMAGE_BASE_INSTALL =3D '\ packagegroup-core-boot \ packagegroup-base-extended \ ..." so if I'm not wrong, even if MACHINE_FEATURES doesn't have wifi we will get wifi tools in the image if DISTRO_FEATURES contains wifi. Eric