Re: RFC: build config via DT names

On 13.02.2018 15:19, Rob Herring wrote: Doubling the number of driver config options is not going to fly. These options would be in their own submenu (which could be disabled completely) and use their own prefix. IMHO, even if they grow into big numbers, the impact should be minimal. How

Re: RFC: build config via DT names

On 13.02.2018 15:19, Rob Herring wrote: Doubling the number of driver config options is not going to fly. These options would be in their own submenu (which could be disabled completely) and use their own prefix. IMHO, even if they grow into big numbers, the impact should be minimal. How

Re: RFC: build config via DT names

On Mon, Feb 12, 2018 at 5:13 PM, Frank Rowand wrote: > + devicetree mail list > > On 02/10/18 07:52, Enrico Weigelt, metux IT consult wrote: >> Hi folks, >> >> I've regularily have the task of configuring a kernel for a given DT. >> To make this a little bit easier, I'd

Re: RFC: build config via DT names

On Mon, Feb 12, 2018 at 5:13 PM, Frank Rowand wrote: > + devicetree mail list > > On 02/10/18 07:52, Enrico Weigelt, metux IT consult wrote: >> Hi folks, >> >> I've regularily have the task of configuring a kernel for a given DT. >> To make this a little bit easier, I'd like to do this

Re: RFC: build config via DT names

On 12.02.2018 23:24, Frank Rowand wrote: There is a tool to aid this process: scripts/dtc/dt_to_config. It is not a 100% solution, but it is very helpful. The problem is difficult enough that this tool led to a conference talk. The slides are at

Re: RFC: build config via DT names

On 12.02.2018 23:24, Frank Rowand wrote: There is a tool to aid this process: scripts/dtc/dt_to_config. It is not a 100% solution, but it is very helpful. The problem is difficult enough that this tool led to a conference talk. The slides are at

Re: RFC: build config via DT names

Hi Enrico, On 02/12/18 15:13, Frank Rowand wrote: > + devicetree mail list > > On 02/10/18 07:52, Enrico Weigelt, metux IT consult wrote: >> Hi folks, >> >> I've regularily have the task of configuring a kernel for a given DT. >> To make this a little bit easier, I'd like to do this

Re: RFC: build config via DT names

Hi Enrico, On 02/12/18 15:13, Frank Rowand wrote: > + devicetree mail list > > On 02/10/18 07:52, Enrico Weigelt, metux IT consult wrote: >> Hi folks, >> >> I've regularily have the task of configuring a kernel for a given DT. >> To make this a little bit easier, I'd like to do this

Re: RFC: build config via DT names

+ devicetree mail list On 02/10/18 07:52, Enrico Weigelt, metux IT consult wrote: > Hi folks, > > I've regularily have the task of configuring a kernel for a given DT. > To make this a little bit easier, I'd like to do this automatically. > > The tuff task here is getting a mapping between dt

Re: RFC: build config via DT names

+ devicetree mail list On 02/10/18 07:52, Enrico Weigelt, metux IT consult wrote: > Hi folks, > > I've regularily have the task of configuring a kernel for a given DT. > To make this a little bit easier, I'd like to do this automatically. > > The tuff task here is getting a mapping between dt

RFC: build config via DT names

Hi folks, I've regularily have the task of configuring a kernel for a given DT. To make this a little bit easier, I'd like to do this automatically. The tuff task here is getting a mapping between dt compatible strings and corresponding CONFIG_* flags. Automatically extracting it from the

RFC: build config via DT names

Hi folks, I've regularily have the task of configuring a kernel for a given DT. To make this a little bit easier, I'd like to do this automatically. The tuff task here is getting a mapping between dt compatible strings and corresponding CONFIG_* flags. Automatically extracting it from the