From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id E2E3CE0095D; Tue, 19 May 2015 07:07:28 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 95875E0027F for ; Tue, 19 May 2015 07:07:24 -0700 (PDT) Received: from [192.168.0.62] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id 7B35B6000923; Tue, 19 May 2015 17:07:22 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1432044442; bh=aNx6oQDiYhD6hOGzoZeKZ0g/Vg50ZGwKRvZOegMlD3U=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=avkaBAQSPf+QRvOv0D+FjHDn76uZRSNLV2wJEX2UTNlWfQCicsh9oRiMHBGI00skA G5paB88Vyuy/np/FbdIRFDEhl0vBwSr895JM3LrjqVemPVlUm7SeKDyeoSu+eK9ogp BlqMaSNoX7UiSwBCJfH+NcwSWRj8LBZUftN+Hn8c= Message-ID: <555B439A.1000806@mail.bg> Date: Tue, 19 May 2015 17:07:22 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Daiane Angolini , Fabio Estevam References: <1431994798-5588-1-git-send-email-festevam@gmail.com> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" , Fabio Estevam , Otavio Salvador Subject: Re: [PATCH][meta-fsl-arm] imx53qsb: Remove firmware and features list 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, 19 May 2015 14:07:29 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Daiane, On 05/19/2015 04:31 PM, Daiane Angolini wrote: > On Tue, May 19, 2015 at 10:19 AM, Fabio Estevam > wrote: >> Hi Otavio, >> >> On Tue, May 19, 2015 at 9:05 AM, Otavio Salvador >> wrote: >> >>> This has been added, at that time, because Freescale used the >>> adaptor to do tests. I am not against removing this but several >>> boards we have included list the 'capability' of using WiFi / >>> Bluetooth, not strictly if it is at board or not. >>> >>> Let me know your thoughts on this. >> >> I would prefer to pass in MACHINE_FEATURES only the features that >> the boards support natively. >> >> Otherwise, every board with a USB port, SDIO or PCIe port could >> list many possible features of devices that could be potentially >> attached to it. >> >> If we restrict MACHINE_FEATURES to only the devices that are >> built-in, then we have a more common approach to the various >> supported machines. > > It is weird to see ~once again~ an old conversation taking place in > mailing list. > > I remember to have discussed about this few years ago. > > In my opinion, we have basically 2 kinds of boards: the products and > the references. > > And, in my opinion, the reference boards should include WIFI in > MACHINE_FEATURES even if they don't have it physically in the board. In order to support all kinds of WIFI devices, it will also require all kernel drivers for these devices to be enabled, and currently this is not the case. Another issue is that leaving/setting the WIFI feature and kernel drivers enabled implies that Freescale or the community board maintainer has tested all these devices on the reference builds, which I doubt is possible. In general, I tend to agree with Fabio that what's physically available on the board should be supported out of the box. Just kindly sharing my thoughts, please feel to disagree with me. > I mean, if board has a PCIe, it is one of the board goals to ~have > thing attached to it~, and one of the most often attached stuff is > WIFI or/and Bluetooth. > > For products, it's straightforward that the board maintainer decides > which is the best, as this is a gray area. Kind regards, Nikolay