**** BEGIN LOGGING AT Wed May 28 02:59:59 2014
May 28 09:20:51 <anujdeshpande> panto: ping
May 28 09:21:28 <panto> anujdeshpande, pong for a little while
May 28 09:31:40 <anujdeshpande> panto: i copied the register offsets and mode values from the capes that you have created in a dts https://pad.riseup.net/p/devicetree
May 28 09:32:15 <anujdeshpande> panto: i was wondering about the other data structures though
May 28 09:32:57 <anujdeshpande> I am using contents from PRU-04, and i think i need to copy the data structures like the definition of pru1 too.
May 28 09:33:36 <anujdeshpande> so what’s the difference between the ones in the capes and the ones found in the dts, i.e. the ones with & before them
May 28 09:39:00 <panto> there shouldn't be any differences
May 28 09:44:10 * anujdeshpande damn
May 28 09:45:52 <anujdeshpande> panto: did i miss something?
May 28 09:58:23 <panto> the cape mechanism is only providing a method to load DT information to the running kernel at runtime
May 28 09:58:47 <panto> there are no functional changes to each driver
May 28 09:59:12 <panto> but, the time when the changes are applied are different
May 28 09:59:31 <panto> so depending on the device initialization order there might be hidden differences
May 28 10:07:50 <vmayoral|pc> anujdeshpande: please take into account the issue i mentioned in Skype "Issue with the overlays. PRU-05 and BB-SPI1-SWP-01." when designing the DT
May 28 10:08:04 <vmayoral|pc> the conflict
May 28 10:08:27 <vmayoral|pc> probably some pins thing, i didn't had the time to look into it in much detail. Maybe next week
May 28 10:09:43 <anujdeshpande> panto: i see. will try out small changes and see if anything breaks
May 28 10:09:58 <anujdeshpande> vmayoral|pc: i’ll check the logs for more info then.
May 28 10:10:19 <vmayoral|pc> _)
May 28 10:10:21 <vmayoral|pc> :)
**** ENDING LOGGING AT Thu May 29 03:00:00 2014