Re: [Arm-netbook] devicetree and testing

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Apr 18, 2018 at 2:50 PM, Jonathan Neuschäfer wrote: > On Tue, Apr 17, 2018 at 02:54:29PM -0600, Richard Wilbur wrote: > [...] >> So, sorry for being a bit thick headed, it just dawned on

Re: [Arm-netbook] devicetree and testing

On Tue, Apr 17, 2018 at 02:54:29PM -0600, Richard Wilbur wrote: [...] > So, sorry for being a bit thick headed, it just dawned on me what our > priorities have to be and why: > > 1. Hack together some tests under 3.4.104 that we can run on the extant > drivers. > 2. Work on getting extant A20

Re: [Arm-netbook] devicetree and testing

On Wed, Apr 18, 2018 at 1:46 PM, Richard Wilbur wrote: > I agree wholeheartedly with the modular mix and match overlay fragment > design but saw the software support for it in what I had labelled as > priority 4. Whereas I understood priority 3 to entail creating the >

Re: [Arm-netbook] devicetree and testing

On Apr 17, 2018, at 16:17, Luke Kenneth Casson Leighton wrote: On Tue, Apr 17, 2018 at 11:12 PM, Richard Wilbur wrote: In my estimation the tasks that can be completed relatively quickly are 1 and 3 as they don't require convincing anyone else of the

Re: [Arm-netbook] devicetree and testing

On Tue, Apr 17, 2018 at 11:12 PM, Richard Wilbur wrote: > I understand that people have been working on steps 2 and 4 for years and I > had no diminution of their efforts in mind. absolutely. > In my estimation the tasks that can be completed relatively quickly are

Re: [Arm-netbook] devicetree and testing

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Tue, Apr 17, 2018 at 9:54 PM, Richard Wilbur wrote: > On Apr 16, 2018, at 22:04, Luke Kenneth Casson Leighton > wrote: > On Tue, Apr 17, 2018 at 4:53 AM, Richard Wilbur