Re: [beagleboard] Fundamental capemanager change between 4.1.x, and 4.4.x

2016-04-22 Thread William Hermans
Yeah, IDK, I'm beat for the night, but in my humble opinion, this is a show stopper. 4.4.x is not ready yet. Maybe tomorrow when better rested I'll be able to think of something else to test. In hopes of getting this fixed / resolved. On Thu, Apr 21, 2016 at 11:02 PM, William Hermans

Re: [beagleboard] Fundamental capemanager change between 4.1.x, and 4.4.x

2016-04-22 Thread William Hermans
It's not the device tree node which is in the include *am33xx.dtsi*, they both seem to be exactly the same. tscadc: tscadc@44e0d000 { compatible = "ti,am3359-tscadc"; reg = <0x44e0d000 0x1000>; interrupt-parent = <>; interrupts = <16>;

Re: [beagleboard] Fundamental capemanager change between 4.1.x, and 4.4.x

2016-04-21 Thread William Hermans
Just for added measure, yes the UIO driver does work . . william@beaglebone:~$ lsuio uio0: name=tscadc, version=devicetree, events=0 map[0]: addr=0x44E0D000, size=4096 On Thu, Apr 21, 2016 at 9:51 PM, William Hermans wrote: > Ok, so the following does *NOT* work on

[beagleboard] Fundamental capemanager change between 4.1.x, and 4.4.x

2016-04-21 Thread William Hermans
Ok, so the following does *NOT* work on a 4.4.x kernel, but does on a 4.1.x kernel. *Starting off with 4.4.x kernel* william@beaglebone:~$ cat ti/WH-ADC-00A0.dts /dts-v1/; /plugin/; / { compatible = "ti,beaglebone", "ti,beaglebone-black"; /* identification */