|
|
|
|
|
|
by chylat
1404 days ago
|
|
|
Disclaimer: I was in the Pine64 IRC channels at the time, so have some limited visibility, but not all visibility. Pine64 was looking for somebody to commit to maintain PineBook Pro support in Tow-Boot (a relatively new project) I don't know if the point-of-contact was made aware that PineBook Pro was not going to be shipped with Tow-Boot. |
|
|
2022-06-01, the Pine64 dev IRC chat:
> [T] <tl_lim> I pause on move forward due to no one commit to maintain. If MayueIC interest to maintain, lets move forward and include Tow-Boot into the PBP factory build. @MayeulIC, you can send an email to info@pine64.org, we will ship a free Pinebook Pro to you so that you can maintain the Tow-Boot.
> [T] <tl_lim> On the integration, just follow the recent PinePhone Pro way that flash OS build to eMMC then flash Tow-Boot to SPI Flash.
> [T] <tl_lim> Frankly speaking, I am happy on developer commit maintaining Tow-Boot on Pinebook Pro. Thanks and a big shout out to @MayeulIC.
2022-06-02, in the Tow-Boot chat, which was discussing tl_lim's above comment:
> spikerguy: Tllim asked on. 25th April about pbp tow boot support i replied it just work fine as it should. But just because i am the one to work on factory images plus i am the manjaro arm pkg maintainer maybe he didn't wanted to hear from me instead the community that was assuring him about tow boot and none replied
> The current batch factory image is already submitted. So hopefully we can keep things ready for the next batch
I don't see all comms, but overall I see Tow-Boot on SPI at factory-time as nice-to-have but not essential (users can easily do this, distros don't need to require it, and the next batch can improve it if needded), Pine64 has showed willingness to use Tow-Boot. Tow-Boot has 1 developer, and I'm not sure if they were willing to commit to support this. I understand if they weren't.
This issue is blown out of proportion.
Maybe a good step would be for Pine64 to fund Tow-Boot's support of Pinebook Pro.