From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id AD67DE017B6 for ; Wed, 30 Oct 2013 07:25:05 -0700 (PDT) Received: by mail-pd0-f175.google.com with SMTP id g10so1027778pdj.6 for ; Wed, 30 Oct 2013 07:25:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=csTciUJt2Sm4tAnWqCTw0ybrnQX1BL18mHd8arq4+Ps=; b=TnUI+yddt9E4IDVgEiZL6TBOl2asIbe2UyK7A/aFILeeyVuMDaSrRya4tPdyA9WkIt Qeh3++mciCkt9LoSK9zQl4E2G/+/M4g5G94NL9L0vSKNIihz+/rUkT8zV9U62fWNx5TJ JFNbICVMtfxewEWnNXmNGGQ6LXYSbEEoIwwDl4Ey/UJIGLOL3HuSNnsg+ZdN1NrZisMX wF9bzZTi4ywCOlDGQYqC01/Ign0BorgfcKoFrSRJjv/hDs0OuzMKY8jMyyS7+rXiN7j4 y6nQ9Fufi8xmTAbeJGwverp335CykQTGhYDHd5U8dTwrZUZTpfuPMRqMZRgSRIlLk0mY MSZw== X-Gm-Message-State: ALoCoQk2/ZmQfWsXtK3Q5rT/GSyNT7hATU9FvnI42kSqtEDaxhGA1mjYbmity8KRmiuWVQcnwryC X-Received: by 10.68.203.34 with SMTP id kn2mr5421884pbc.82.1383143105204; Wed, 30 Oct 2013 07:25:05 -0700 (PDT) Received: from [192.168.1.8] (ip98-167-230-131.ph.ph.cox.net. [98.167.230.131]) by mx.google.com with ESMTPSA id og5sm41759544pbb.10.2013.10.30.07.25.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Oct 2013 07:25:04 -0700 (PDT) Message-ID: <527116BE.7030303@boundarydevices.com> Date: Wed, 30 Oct 2013 07:25:02 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Otavio Salvador , Gary Thomas References: <52710C89.7030903@mlbassoc.com> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-arm-extra][PATCH] nitrogen6x.conf: Allow kernel provider override 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: Wed, 30 Oct 2013 14:25:07 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Otavio, On 10/30/2013 07:10 AM, Otavio Salvador wrote: > On Wed, Oct 30, 2013 at 11:41 AM, Gary Thomas wrote: >> This change lets the user override the choice of kernel in local.conf >> Without it, there is no way to build any kernel, e.g. linux-imx, other >> than the linux-boundary version. >> >> Signed-off-by: Gary Thomas > > I really dislike this. > > I understand your need, and it is a valid one, but it'd be better you > to make a new machine (which includes this one) and override it there. > I'm not sure I understand why. It seems perfectly reasonable to me to build a new kernel recipe and use it, while retaining other information from the machine configuration. I'm thinking specifically of a user who may have a custom kernel tree with pin-muxing based on their usage. > If we start allow all kind of override in machine configuration it > loses its meaning and complicates the support. > > Eric? comments? > I'm not sure I understand the concern. This seems pretty straightforward. The default is there, but a user can over-ride it. Regards, Eric