Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Package unicsy_demo (basic hardware demo) #643
Thanks for packaging this!
Follow up questions:
- How about adding a
/usr/bin/unicsy_demoprogram, that launches the demo?
- What does
- How N900 specific is this package?
I added /usr/bin/unicsy_demo symlink for easy launch. Ultimately, it would be nice to have a button in weston-demo, or launch it by default. Unicsy is a word play at Unix, which itself is a word play at Multics, which means ... anyway what I wanted to say is that I plan to keep traditional Unix philosophy where possible: simple programs that do one thing and do it right and plain text configuration and user data files are important to me. More here: https://pavelmachek.livejournal.com/139660.html Demo should work on non-N900 machines -- I test PC from time to time. I expect hardware.py will need to be modified to support all features on different phones. Help will probably be needed there. I changed comment to be more specific, and changed to dash (not underscore), fixed url, and removed empty bulid function.
@drebrez Which device is that? Can you install the package and see what works? Yes, we'll need to do better job on different hardware, but I don't think we want to start mechanically moving strings to deviceinfo. For example... backlight. We probably want to just use /sys/class/backlight/*/ if there's just single entry there. No need to add that to deviceinfo. Situation might be different with accelerometer. There, we may want to list known accelerometer devices, and just use one that is available. Or laybe lis3lv02d is quite common and we'll not need to do a list. I did support on hardware I have working. More testing on different hardware is needed, and then we can select best solutions.
@pavelmachek I agree that we don't need all the paths in variables, it's better if the tool tries to find it by itself.
Autodetection where possible, and using the deviceinfo otherwise sounds good to me! I've merged this PR so we have an initial version, that works on the N900 and recommend that we discuss how to implement support for different devices in the program's own issue tracker: