08-09-2023, 09:06 AM
Thanks for the replies. I am seeking to help. I do have limited time, just like most here!
So I want to make the best use of my limited time.
I figured I could 'test and provide feedback.'
But,
1. There really doesn't seem to be any kind of coordinated feedback structure set up. Not for testing and development, at least. There are the Matrix channels, and this forum so I figured I'd place feedback here or there.
2. I can't really test the hardware because I can't install the driver.
2a. I can't get the driver to build (make) and there are no clear instructions on how to do that. I realize the bes2600 driver is NOT PINE64 so it is NOT their driver. It is an independent project. But the build info on that page is very poor as well. Still, I will confine my questions to the gitlab page for the bes2600 driver.
3. I posted my question in the forum: "pine64/pinetab/hardware" So I thought this might be the place where the "pine64" community enthusiastic about the "pinetab" might welcome questions or feedback about the "hardware" on same.
So I want to make the best use of my limited time.
I figured I could 'test and provide feedback.'
But,
1. There really doesn't seem to be any kind of coordinated feedback structure set up. Not for testing and development, at least. There are the Matrix channels, and this forum so I figured I'd place feedback here or there.
2. I can't really test the hardware because I can't install the driver.
2a. I can't get the driver to build (make) and there are no clear instructions on how to do that. I realize the bes2600 driver is NOT PINE64 so it is NOT their driver. It is an independent project. But the build info on that page is very poor as well. Still, I will confine my questions to the gitlab page for the bes2600 driver.
3. I posted my question in the forum: "pine64/pinetab/hardware" So I thought this might be the place where the "pine64" community enthusiastic about the "pinetab" might welcome questions or feedback about the "hardware" on same.