From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frank Rowand Subject: Re: Device Tree Evolution Project - call notes - 29th January Date: Tue, 11 Feb 2020 20:49:47 -0600 Message-ID: <36cb9cd4-542e-c8da-9615-f26d6ee3e44e@gmail.com> References: <20200130135605.GQ3697@linaro.org> <3b257f2a0ccc4f9f9ca0be2de8c9e382@ti.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=IWFw+dZD/AyL81KigWSRoTphkKqIHvvIUfgV8j6kmfg=; b=PQ1FdW9YU8Mh/peR3aas8N2hXe8F4N5qg39h/Ga5Yw2vb9DeBjQ0bnGu+bEBZcue/v fbR2ztHgnstRAVdrnbfmZe/2g36QjSPF9s04ZZkqssg3IAdSkstwZzMEqh7o07erIktx J1EUF7S0GmT0GgM6uCGvO5I1p0WI3wgrgST4TekKH2ADlLMJ9eA8P73f9fzZYvQFuHFc 3SGQp8n1N+rOuj+e/BjlCFD8xuuG8Cj092HTjboffzU/Ga19DMd6BrKiTNNDomGvuhsP 6AhUY6fr9Av4ZqxXuEq9yyI1ilPVtlQPQolA9wr/yXTk5Cwb9JjHWG5beddjB/NwLLTQ TBNQ== In-Reply-To: Content-Language: en-US Sender: devicetree-spec-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Rob Herring , "Mills, William" Cc: Steve McIntyre , "devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "dte-all-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org" , "Kristo, Tero" , "Valkeinen, Tomi" , "Menon, Nishanth" , "Murphy, Dan" , "tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org" , "tom.rini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org" On 2/11/20 10:31 AM, Rob Herring wrote: > On Mon, Feb 10, 2020 at 10:58 AM Mills, William wrote: >> >> Steve, >> >> Can TI get on the agenda for this week's meeting? >> >> We have a simple approach to make progress on boot loader applied overlays. >> It is a small repo with just the overlays. >> It builds the dtb's from the upstream kernel repo and the overlays from this repo. >> We are going to do this at git.ti.com so we can make progress. >> However we would like to suggest this as a simple way forward to collectively host things the kernel maintainers do not want in the kernel. > > For the record, I'm in favor of hosting overlays in the kernel (of > course I have opinions on the details). Frank is not in favor IIRC, > but Frank is only maintainer of 'drivers/of/' so ultimately not his > decision. I agree that the kernel is the place to host overlay sources. -Frank > >> Does it make sense to host something like this in devicetree.org github account? > > Yes, but I would like to see this coordinated with hosting > 'devicetree-rebasing' there. We should be able to use the same > makefiles from it. Perhaps the overlay repo should work as a git > submodule of it as well. That would help keep things in sync. > > A concern I have is what happens when someone wants to split some > portions of an existing dts into an overlay? Then the base dts becomes > incomplete. Users will have regressions from missing functionality if > they don't know to apply some overlay. And how do we track what base > DTs overlays apply to? Not that we have a solution when they are in > one tree, but 2 trees makes that harder. > > Rob >