--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Sat, Mar 3, 2018 at 7:53 PM, Pablo Rath <[email protected]> wrote: > On Sat, Mar 03, 2018 at 03:46:33AM +0000, Luke Kenneth Casson Leighton wrote: >> On Sat, Mar 3, 2018 at 2:44 AM, Jonathan Neuschäfer >> <[email protected]> wrote: > > ... > >> > About DT fragments: I'm not sure what you mean exactly. Mainline support >> > devicetree overlays which should do (half of) the job for EOMA68, though. >> >> ah, yes, that's the official name. overlays. >> >> question: do you know if they've added the patches to *REMOVE* >> overlays yet? Cards could potentially be dynamically removed... or at >> least put into sleep / suspend only to wake up with a totally >> different Housing. > > The whole DT overlay discussion rang a bell somewhere in my brain and > now I had time to look it up. I read about a DT overlay hack here: > https://joeyh.name/blog/entry/easy-peasy-devicetree-squeezy/ > Please read the README for details. > Can the above hack be of some use to the EOMA project until "patches to > fully support overlays, including loading them on the fly into a running > system" are mainlined? as long as people are happy to have the linux kernel source tarball on their system... yes. and they are happy not to have 100% working hardware. > It seems we are not the only one with DT overlay problems: > https://elinux.org/BeagleBone_and_the_3.8_Kernel#Cape_Manager_and_Device_Tree_Overlays yyup. and they don't have the dynamic removal. l. _______________________________________________ arm-netbook mailing list [email protected] http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to [email protected]
