Hi Stephen, Congratulations on finding that driver bug detail. I would like to know more about how you were able to find such a thing. I am really interested in being able to get to the level to do what you just did. Would you care to share your detailed experience on how you were able to find this? Some questions that I have is how in depth is your knowledge in the hardware, OS, and C language? and how did you get to that knowledge level? I know you said you are "not an accomplished c programmer" but you seem to be getting along really well.
> Reading the H3 datasheet would lead me to believe that the switwi driver should work. How did you come up with the idea to focus on the sxitwi driver? > I modified the dtb and the sxitwi driver to set up H3 compatibility, rebuilt the kernel... How did you know what/how to change in the dtb file? Did you cross-compile and how did you set that up? I imagine the development cycle is really slow having to cross-compile, copy files to an sd card, plug sd card into the pi, boot up, wait, and then... how do you know what is happening? maybe something in the dtb was wrong? how would you know exactly? and if something did go wrong then you would probably spend a massive amount of time hunting down the issue and then not to mention going through the bulky cycle of coding/compiling/copying/booting. How do you manage? > I changed the code to set the bit after a status change and the data started flowing! How did you figure a bit needed to be set after a status change when this fact is buried 445 pages deep in documentation? Thanks, -- -alfred
