On 12/8/15 12:54 PM, Kevin Hilman wrote:
David Mandala firstname.lastname@example.org writes:
On 12/8/15 12:10 PM, Kevin Hilman wrote:
Rob Herring email@example.com writes:
On Thu, Dec 3, 2015 at 10:35 PM, David Mandala firstname.lastname@example.org wrote:
It's the reason why we have UDEV rules now making the two UARTs on the LS connector /dev/tty96B0 and /dev/tty96B1 get rid of the confusion and make it MUCH easier to document things.
Anything in userspace that is 96boards specific is a flawed solution. These problems have nothing to do with 96boards, but are shortcomings in the kernel interfaces. Lets fix those and not be working around them.
I agree that the kernel space is the proper place to fix this but it will likely take years for that to happen, feel free to shock me and have a fix in the next kernel cycle. ;-P
It's taking many years because 96boards kernel development isn't focused on upstream. Instead, it's focused primarily on Linaro releases. Getting a DT fix like this upstream could happen very quickly, but first there has to be a willingnes to submit it.
Also, the other problem with the userspace fix you propose it assumes folks are actually using Linaro releases and/or willing to modify their host systems in 96boards-specifid ways. Not always a safe assumption.
No for sure not a safe assumption, and while I've been known to be stupid, I'm not quite that stupid, so I make sure that all documentation I write, tells you how to tell if you need the udev file and points at github where the udev files and doc's are stored. If you are using your own build you can add the needed rule file and use it, or not if you prefer not to.