diff --git a/content/blog/april-update-ce-fcc-software-update-and-diy-router.md b/content/blog/april-update-ce-fcc-software-update-and-diy-router.md index 326e7a04..3ce25670 100644 --- a/content/blog/april-update-ce-fcc-software-update-and-diy-router.md +++ b/content/blog/april-update-ce-fcc-software-update-and-diy-router.md @@ -18,10 +18,10 @@ tags: cover: image: "header.jpg" images: - - "/blog/images/header.jpg" + - "/blog/images/header_with_pinephone_and_pinebookpro.jpg" --- -![](/blog/images/header.jpg) +![](/blog/images/header_with_pinephone_and_pinebookpro.jpg) I hope and trust this update finds everyone well. Production in China is picking up pace and we expect to start shipping the Pinebook Pro with Manjaro and PinePhone UBports Community edition next month. I am happy to report that, for the time being, everything is proceeding  smoothly and we’re on track to ship devices in accordance with our original plans. Still, I encourage you to sign up to this blog to stay up-to-date on shipping information since anything can happen in the next 30 days.  diff --git a/content/blog/april-update-no-more-unicorns.md b/content/blog/april-update-no-more-unicorns.md index 82c4534f..a77dec3f 100644 --- a/content/blog/april-update-no-more-unicorns.md +++ b/content/blog/april-update-no-more-unicorns.md @@ -85,7 +85,7 @@ It is time for the second community quarterly Q&A. If you’re reading this on t We have upgraded the [main PINE64](https://app.element.io/#/room/#pine64:matrix.org) and [PinePhone](https://app.element.io/#/room/#pinephone:matrix.org) Matrix channels. Both of them previously ran version 1 of the Matrix protocol and this caused us all sorts of headaches, including moderators randomly losing their powers and people who left being forced back into the home server. Needless to say, an upgrade had to happen sooner or later. The new rooms now run version 6 of the Matrix protocol which will alleviate all the aforementioned problems. An unfortunate side-effect of the upgrade is that everyone who was part of the original channels will need to manually rejoin. An invite link is present in the original groups.  -As some of you noticed, there was no new [PineTalk](https://www.pine64.org/pinetalk/) episode last month. Those involved in the production of the podcast were busy with real-life things and simply didn’t get the chance to record. I’ve spoken to Brian and Justin and they both confirmed that a new episode will be coming later this month. If you haven’t done so yet, make sure to subscribe to [PineTalk’s RSS feed](https://www.pine64.org/feed/mp3/).  +As some of you noticed, there was no new [PineTalk](https://www.pine64.org/podcast/) episode last month. Those involved in the production of the podcast were busy with real-life things and simply didn’t get the chance to record. I’ve spoken to Brian and Justin and they both confirmed that a new episode will be coming later this month. If you haven’t done so yet, make sure to subscribe to [PineTalk’s RSS feed](https://www.pine64.org/feed/mp3/).  The product team is in advanced talks with a factory regarding resuming production of the Pinebook Pro. As I’ve promised countless times in the past, I’ll keep you updated on the progress regarding restarting the laptop’s production. I’m told the team is etching closer to strike a deal and that the production circumstances will require some alterations to parts of the hardware - keep an eye on our social media and news channels in the coming weeks. @@ -167,7 +167,7 @@ In other news, the [documentation of the PinePhone Pro](https://wiki.pine64.org/ **A functionality matrix has been added to the [PinePhone Pro Wiki](https://wiki.pine64.org/wiki/PinePhone_Pro) section** -The software section of the PinePhone Pro article, which was extended gradually, was rewritten as well to bring a more coherent information section with all relevant information. The section should now be considerably easier to read, especially in the parts, which were causing confusion in the previous instructions. Aside from a large number of improvements, the section now also received a dedicated troubleshooting subsection and numerous new information. The section can be found under [https://wiki.pine64.org/wiki/PinePhone\_Pro#Software](https://wiki.pine64.org/wiki/PinePhone_Pro#Software). As it is often asked where bugs can be reported and how projects can be supported, new articles regarding [where to report bugs](https://wiki.pine64.org/wiki/Where_to_Report_Bugs) and [how to contribute to projects](https://wiki.pine64.org/wiki/How_to_Contribute) were started as well, which will be gradually improved and extended over time. In this context it can be noted that all community projects are happy about any form of contribution. Knowledge of coding is not required, instead there are various ways to contribute to projects, for example with designs, ideas, translations, documentation, through hardware or with creative work, or by simply being a positive member of the community. On this note, I want to thank everyone for their unremitting help. Without your contributions, the community would simply not be what it is today. +The software section of the PinePhone Pro article, which was extended gradually, was rewritten as well to bring a more coherent information section with all relevant information. The section should now be considerably easier to read, especially in the parts, which were causing confusion in the previous instructions. Aside from a large number of improvements, the section now also received a dedicated troubleshooting subsection and numerous new information. The section can be found under [https://wiki.pine64.org/wiki/PinePhone\_Pro#Software](https://wiki.pine64.org/wiki/PinePhone_Pro#Software). As it is often asked where bugs can be reported and how projects can be supported, new articles regarding [where to report bugs](/documentation/Introduction/Where_to_report_bugs) and [how to contribute to projects](/documentation/Introduction/How_to_Contribute) were started as well, which will be gradually improved and extended over time. In this context it can be noted that all community projects are happy about any form of contribution. Knowledge of coding is not required, instead there are various ways to contribute to projects, for example with designs, ideas, translations, documentation, through hardware or with creative work, or by simply being a positive member of the community. On this note, I want to thank everyone for their unremitting help. Without your contributions, the community would simply not be what it is today. There is one more noteworthy piece of information concerning documentation of mobile Linux software: [LinuxPhoneApps.org](https://linuxphoneapps.org) finally quietly launched at the end of March. It [lists](https://linuxphoneapps.org/apps/) all the apps that were (and still are) listed on LINMOBapps. The list is presented in a way that is more friendly to PinePhone's Firefox browser, preventing it from asking whether it should kill the script that slows things down. The list now has more apps, with more being added slowly but steadily. Note that not all apps are packaged for your distribution nor are they all to be considered feature-complete. If you want to follow, join or help out the further development of the site, check out the [LinuxPhoneApps FAQ](https://linuxphoneapps.org/docs/help/faq/). diff --git a/content/blog/december-update-a-year-in-review.md b/content/blog/december-update-a-year-in-review.md index c66bf44a..0664ef9e 100644 --- a/content/blog/december-update-a-year-in-review.md +++ b/content/blog/december-update-a-year-in-review.md @@ -90,7 +90,7 @@ N.B. Comments on the blog post need to be in English and follow our [Community R Thank you to everyone who contributed to the projects in 2021. I particularly want to thank our admins, [Matthew (Fire219)](https://twitter.com/fire219_SIMPL) and [Marek (Gamiee)](https://twitter.com/gamelaster), for their work. For those who don’t know, they are the people who put out the occasional fires and make sure that the cogs of the project keep turning. And a big shout-out to the moderators, who are doing a great job keeping our communication protocols clutter-free and safe. I also want to thank all of our partner projects - [Manjaro](https://manjaro.org/) and [KDE](https://kde.org/) in particular - for their work on our devices and their commitment to our shared community. I cannot forget about all the contributors, whom there are too many to mention individually, that make projects such as the PinePhone (Pro), the PineTime, and PineDio possible. Lastly, I want to thank all of you in the community for actively supporting us - I hope we did right by you yet another year. My best wishes to everyone - have a great holiday season.  -This month’s [PineTalk](http://pine64.org/pinetalk/) will be recorded live on December 15th. Brian ([33YN2](https://mastodon.online/web/accounts/61817)) and Justin (Porky) will be using the ‘stage’ feature on [Discord](https://discord.gg/pine64), found at the bottom of the server’s channel list. I encourage you all to join in, ask questions and stick around afterwards for a chat with the hosts and other community members. In case you miss it, the episode will be available in an edited format a few days later on the podcast streaming platform of your choice, as per usual. +This month’s [PineTalk](http://pine64.org/podcast/) will be recorded live on December 15th. Brian ([33YN2](https://mastodon.online/web/accounts/61817)) and Justin (Porky) will be using the ‘stage’ feature on [Discord](https://discord.gg/pine64), found at the bottom of the server’s channel list. I encourage you all to join in, ask questions and stick around afterwards for a chat with the hosts and other community members. In case you miss it, the episode will be available in an edited format a few days later on the podcast streaming platform of your choice, as per usual. ![](/blog/images/Malware-notification-Telegram.png) ![](/blog/images/Malware-notification-discord-1024x94.png) diff --git a/content/blog/december-update-merry-christmas-and-happy-new-pinetab.md b/content/blog/december-update-merry-christmas-and-happy-new-pinetab.md index b608a663..81887202 100644 --- a/content/blog/december-update-merry-christmas-and-happy-new-pinetab.md +++ b/content/blog/december-update-merry-christmas-and-happy-new-pinetab.md @@ -156,13 +156,13 @@ For now our plans concern non-Pro devices, in part because no Pro-grade RISC-V c # PineTab2 -Before we get to discussing the new PineTab2 let me first explain what happened to its predecessor. The original PineTab was conceived alongside the PinePhone in early 2018 at a small pub in Brussels, and a little less than 2 years later the PinPhone and PineTab became available for order. At that time a global pandemic was something that could only be experienced through the medium of film. I think it is fair to say that none of us could have truly imagined what a global pandemic would entail for the entire world, let alone understood the consequences it would have for hardware production, electronics supply chains and global economics. There is no need for me to recap how the pandemic unfolded, what effect it had on production in mainland China or explain the hardships businesses had to endure as a consequence of this, but suffice to say that the original PineTab was a victim of COVID and its fallout. For those interested in the details, I encourage you to browse the blog’s [PineTab tag](https://www.pine64.org/tag/pinetab/)– I did my best to keep the community updated on the original device’s status throughout 2020-2021. In all fairness I should also make it clear that PineTab’s death was, in some part, a choice on our part as decisions were made to allocate resources to secure PinePhone’s availability throughout late 2020 and early 2021. +Before we get to discussing the new PineTab2 let me first explain what happened to its predecessor. The original PineTab was conceived alongside the PinePhone in early 2018 at a small pub in Brussels, and a little less than 2 years later the PinPhone and PineTab became available for order. At that time a global pandemic was something that could only be experienced through the medium of film. I think it is fair to say that none of us could have truly imagined what a global pandemic would entail for the entire world, let alone understood the consequences it would have for hardware production, electronics supply chains and global economics. There is no need for me to recap how the pandemic unfolded, what effect it had on production in mainland China or explain the hardships businesses had to endure as a consequence of this, but suffice to say that the original PineTab was a victim of COVID and its fallout. For those interested in the details, I encourage you to browse the blog’s [PineTab tag](https://www.pine64.org/tags/pinetab/)– I did my best to keep the community updated on the original device’s status throughout 2020-2021. In all fairness I should also make it clear that PineTab’s death was, in some part, a choice on our part as decisions were made to allocate resources to secure PinePhone’s availability throughout late 2020 and early 2021. ![](/blog/images/pPineTab2-pcb-1024x768.jpg) **A look at PineTab2's PCB** -By the time production of the PineTab became viable again we felt that the original design could and indeed should be improved on. By late 2021 there was also a great candidate SoC for a second generation PineTab – the RK3566. I have written extensively about the RK3566 in recent months in the [context of the Quartz64](https://www.pine64.org/category/quartz64/), but in a nutshell, it is a modern mid-range quad-core Cortex-A55 processor that integrates a Mali-G52 MP2 GPU and supports up-to 8GB of RAM. It is a dream-of-a-soc for small form-factor devices with space-constrained chassis since it runs cool, offers a wide variety of modern and fast IO, has a solid price-to-performance ratio and is genuinely future-proof. The one thing that the SoC didn’t have for a time was mature Linux support – but this is no longer the case (see _Newsflash_ section). Software development for the RK3566 platform is booming and Linux has now reached a high level of maturity with both mainline and BSP Linux supporting nearly all core functionality of the chipset. I feel it is fair to say that it is now a prime candidate for porting mobile OSes to. +By the time production of the PineTab became viable again we felt that the original design could and indeed should be improved on. By late 2021 there was also a great candidate SoC for a second generation PineTab – the RK3566. I have written extensively about the RK3566 in recent months in the [context of the Quartz64](https://www.pine64.org/tags/quartz64/), but in a nutshell, it is a modern mid-range quad-core Cortex-A55 processor that integrates a Mali-G52 MP2 GPU and supports up-to 8GB of RAM. It is a dream-of-a-soc for small form-factor devices with space-constrained chassis since it runs cool, offers a wide variety of modern and fast IO, has a solid price-to-performance ratio and is genuinely future-proof. The one thing that the SoC didn’t have for a time was mature Linux support – but this is no longer the case (see _Newsflash_ section). Software development for the RK3566 platform is booming and Linux has now reached a high level of maturity with both mainline and BSP Linux supporting nearly all core functionality of the chipset. I feel it is fair to say that it is now a prime candidate for porting mobile OSes to. ![](/blog/images/PineTab2-case-back-off-1024x768.jpg) diff --git a/content/blog/february-update-post-cny-and-fosdem-status-report.md b/content/blog/february-update-post-cny-and-fosdem-status-report.md index 44992711..5f436dfe 100644 --- a/content/blog/february-update-post-cny-and-fosdem-status-report.md +++ b/content/blog/february-update-post-cny-and-fosdem-status-report.md @@ -16,10 +16,10 @@ tags: cover: image: "Header.jpg" images: - - "/blog/images/Header.jpg" + - "/blog/images/header_with_pinephone.jpg" --- -![](/blog/images/Header.jpg) +![](/blog/images/header_with_pinephone.jpg) **Nemo Mobile and Ubuntu Touch on the PinePhone at FOSDEM 2020** @@ -68,7 +68,7 @@ As for the production and availability of the HardROCK64 and SOEdge AI module an There is plenty of good news, but let us start with the bad. The bad news is that we need to postpone the production of the RK3399 upgrade kit for the original Pinebook once again. Don’t worry, we’re not shelving it, we’re just prioritizing other things - such as the newly announced HardROCK64 and SOEdge - due to the limited manufacturing capacity (caused by the aforementioned pandemic in China). Having already postponed the release of the upgrade kit thrice now, I rather not promise something for a fourth time. Instead I’ll say: it's in the works, and as soon as I know something with a high degree of certainty I’ll make sure to let you all know.  -On to better news. We now have a solution to the original NVMe adapter problems, where the adapter with an NVMe SSD would not fit properly in the laptop chassis. The solution was surprisingly simple, but required us to manufacture a custom holder for the SSD. I apologize for not keeping you up-to-date on the status of this solution; I didn’t post anything on the subject because I had no insight into the process. If you have the original NVMe adapter for the Pinebook Pro, please send an email to [info@pine64.org](https://www.pine64.org/info@pine64.org) with the following in the subject field:  +On to better news. We now have a solution to the original NVMe adapter problems, where the adapter with an NVMe SSD would not fit properly in the laptop chassis. The solution was surprisingly simple, but required us to manufacture a custom holder for the SSD. I apologize for not keeping you up-to-date on the status of this solution; I didn’t post anything on the subject because I had no insight into the process. If you have the original NVMe adapter for the Pinebook Pro, please send an email to `info@pine64.org` with the following in the subject field:  **_Subject: New PBP NVMe adapter holder \[original order number\]_** diff --git a/content/blog/february-update-show-and-tell.md b/content/blog/february-update-show-and-tell.md index 8148f349..e63dea2e 100644 --- a/content/blog/february-update-show-and-tell.md +++ b/content/blog/february-update-show-and-tell.md @@ -65,7 +65,7 @@ This may just be the most news-packed update since July last year, so strap in f ### Housekeeping -I want to start by giving [Peter](https://twitter.com/linmobblog) and [Ezra](https://twitter.com/Elatronion) - our [PineTalk](https://www.pine64.org/pinetalk/) Podcast hosts - a huge shutout. They've worked really hard on the first two episodes of the podcast and, judging by the number of episode downloads, so far their style has resonated well with the community. In the last episode they spoke to [Dalton Durst](https://twitter.com/UnivrsalSuprBox) from UBports, discussed the recent announcement of [PinePhone Community Editions coming to a close](https://www.pine64.org/2021/02/02/the-end-of-community-editions/) and answered some questions from the community. PineTalk is now available on all major platforms, including Spotify and Apple's Podcast app, and I highly encourage you to subscribe to the [RSS feed](https://www.pine64.org/feed/mp3/).  +I want to start by giving [Peter](https://twitter.com/linmobblog) and [Ezra](https://twitter.com/Elatronion) - our [PineTalk](https://www.pine64.org/podcast/) Podcast hosts - a huge shutout. They've worked really hard on the first two episodes of the podcast and, judging by the number of episode downloads, so far their style has resonated well with the community. In the last episode they spoke to [Dalton Durst](https://twitter.com/UnivrsalSuprBox) from UBports, discussed the recent announcement of [PinePhone Community Editions coming to a close](https://www.pine64.org/2021/02/02/the-end-of-community-editions/) and answered some questions from the community. PineTalk is now available on all major platforms, including Spotify and Apple's Podcast app, and I highly encourage you to subscribe to the [RSS feed](https://www.pine64.org/feed/mp3/).  ![](/blog/images/PineTalkPP-1024x768.jpg) diff --git a/content/blog/images/Header.jpg b/content/blog/images/header_with_pinephone.jpg similarity index 100% rename from content/blog/images/Header.jpg rename to content/blog/images/header_with_pinephone.jpg diff --git a/content/blog/images/header.jpg b/content/blog/images/header_with_pinephone_and_pinebookpro.jpg similarity index 100% rename from content/blog/images/header.jpg rename to content/blog/images/header_with_pinephone_and_pinebookpro.jpg diff --git a/content/blog/july-update-a-pinecil-evolved.md b/content/blog/july-update-a-pinecil-evolved.md index e0bac22c..14c62122 100644 --- a/content/blog/july-update-a-pinecil-evolved.md +++ b/content/blog/july-update-a-pinecil-evolved.md @@ -80,7 +80,7 @@ https://www.youtube.com/watch?v=Tn4S1mdt7QQ ## Housekeeping -Before we get to all the news of this month there are a few housekeeping items. In case you missed it, the [most recent episode](https://www.pine64.org/pinetalk/) of the PineTalk was released earlier this month. In this month’s episode, Zed - the show's editor - replaces Brian as co-host and joins Justin in discussing PINE64 news, gaming on Linux and gaming-related Linux hardware. The latest episode can be found on [PineTalk’s page](https://www.pine64.org/pinetalk/) along with all previous episodes. If you haven’t done so already I suggest you subscribe to the [podcast’s RSS feed](https://www.pine64.org/feed/mp3/)or follow it on the streaming platform of your choice.  +Before we get to all the news of this month there are a few housekeeping items. In case you missed it, the [most recent episode](https://www.pine64.org/podcast/) of the PineTalk was released earlier this month. In this month’s episode, Zed - the show's editor - replaces Brian as co-host and joins Justin in discussing PINE64 news, gaming on Linux and gaming-related Linux hardware. The latest episode can be found on [PineTalk’s page](https://www.pine64.org/podcast/) along with all previous episodes. If you haven’t done so already I suggest you subscribe to the [podcast’s RSS feed](https://www.pine64.org/feed/mp3/)or follow it on the streaming platform of your choice.  It is time for the quarterly Q&A. The Q&A is a community event which provides you with an opportunity to ask questions live in the chat and have us answer you live. In theory, we should hold the Q&A this month, but due to the holiday season - Marek is unavailable at the end of this month and I’m away at the beginning of the next - we’ve decided to schedule the Q&A for August 13th, 8:00 PM CEST (UTC+2). Just as last time, you will be able to pose questions on Discord, IRC, Telegram and Matrix and we will be live-streaming on Youtube. Many people asked us to simultaneously also live-stream the Q&A session to PeerTube - we will try to accommodate this request. A reminder about the Q&A will be released closer to the date via Telegram, Discord News channels and Social Media. Stay tuned! diff --git a/content/blog/june-update-new-hardware-and-more-on-the-way.md b/content/blog/june-update-new-hardware-and-more-on-the-way.md index 020e5a75..20f01e73 100644 --- a/content/blog/june-update-new-hardware-and-more-on-the-way.md +++ b/content/blog/june-update-new-hardware-and-more-on-the-way.md @@ -63,7 +63,7 @@ I’d like to thank [JF](https://twitter.com/codingfield), [Alex](https://twitte A lot of work has gone into improving the Community website this past month. Product pages have been reworked to be more informative and to include additional resources. If you have any suggestions for further improvements to the product pages, make sure to leave them in the comments section. We also added a [shipment, stock and availability tracker](https://www.pine64.org/availability-and-shipping-status/) on the website, allowing users to check current stock levels, estimated availability dates for popular devices and shipping status information. The system will be further refined in the coming weeks, but I feel that this is a good starting point. If you’d like to see other devices on the webpage, leave your suggestion in the comments section.  -We also reworked the [_getting started_](https://www.pine64.org/gettings-started/) page on the website. The new page is a significant improvement in every respect. It offers a quick overview of individual devices' software maturity, recommended operating systems, and links to further resources. We also included all the necessary links to join the community. Once again, if you have suggestions for further improvements, leave them in the comments section. I am really keen to hear your feedback.  +We also reworked the [_getting started_](https://www.pine64.org/documentation/Introduction/Getting_started/ page on the website. The new page is a significant improvement in every respect. It offers a quick overview of individual devices' software maturity, recommended operating systems, and links to further resources. We also included all the necessary links to join the community. Once again, if you have suggestions for further improvements, leave them in the comments section. I am really keen to hear your feedback.  ![](/blog/images/Stock-n-shipping-898x1024.jpg) diff --git a/content/blog/june-update-who-likes-risc-v.md b/content/blog/june-update-who-likes-risc-v.md index fdfb2fd6..a8a4aad4 100644 --- a/content/blog/june-update-who-likes-risc-v.md +++ b/content/blog/june-update-who-likes-risc-v.md @@ -75,7 +75,7 @@ Last month I had the pleasure of bringing the much anticipated news that Pineboo **A peek at the Pinebook Pro's 2022 PCB - via dsimic** -In case you missed it, a [new PineTalk episode](https://www.pine64.org/pinetalk/) was released at the beginning of this month. In this month’s episode, Brian and Justin covered topics covered in the May community update and discussed their experience with open and security-focused Android ROMs. Justin also talks about an idea he pitched to me concerning a smart-speaker. The duo also promised to read and respond to the audience's questions, so make sure to bombard them with [emails](mailto:pinetalk@pine64.org), [toots](https://fosstodon.org/@talkpine) and [tweets](https://twitter.com/TalkPine). I too think that the show deserves a higher degree of community engagement. If you haven’t yet added PineTalk to your RSS feed, then here is a handy link: [https://www.pine64.org/feed/mp3/](https://www.pine64.org/feed/mp3/). +In case you missed it, a [new PineTalk episode](https://www.pine64.org/podcast/) was released at the beginning of this month. In this month’s episode, Brian and Justin covered topics covered in the May community update and discussed their experience with open and security-focused Android ROMs. Justin also talks about an idea he pitched to me concerning a smart-speaker. The duo also promised to read and respond to the audience's questions, so make sure to bombard them with [emails](mailto:pinetalk@pine64.org), [toots](https://fosstodon.org/@talkpine) and [tweets](https://twitter.com/TalkPine). I too think that the show deserves a higher degree of community engagement. If you haven’t yet added PineTalk to your RSS feed, then here is a handy link: [https://www.pine64.org/feed/mp3/](https://www.pine64.org/feed/mp3/). PINE64 EU is finally ready to open its doors for business. I don’t have a specified launch day yet, but it will be next week - it largely depends on how quickly I manage transport, unpack and inventory everything. I once again wish to apologise for the delay in the store’s opening - I ran into issues with EU regulation that needed to be addressed. Suffice to say, relevant institutions take their sweet time with every piece of submitted paperwork; in my case, it took some 4 weeks for a complete review. Anyways, here is what will be available for purchase on day one: PinePhone Pro, PinePhone, the Pinecil, PinePhone (Pro) keyboard case, protective cases for the phones as well as the PineTime. As I mentioned in the past, this is just the beginning, and the aim is to have the EU store grow its selection to include other hardware in the future. I should also mention that customers will be able to select from Mobian, Manjaro and postmarketOS to be installed on their PinePhone (Pro). I also have a small surprise which will be announced on the day of the store’s launch, so make sure to follow PINE64 EU on [Twitter](https://twitter.com/pine64eu), [Mastodon](https://fosstodon.org/web/@pine64eu) and [Telegram](https://t.me/pine64eu) (news channel, not a chat).  @@ -133,7 +133,7 @@ This is the final clue Let me open with a short update on Pinephone and PinePhone Pro’s availability; we currently expect to receive the next production-run in approximately mid July at which point shipping will commence. At the time of publishing this post, both [PinePhone and PinePhone Pro](https://pine64.com/product-category/smartphones/) should now be listed as being in-stock. -As most of you are aware, the PinePhone (Pro)’s Quectel EG25-G modem is effectively its own single-core Arm computer running a closed Linux-based firmware. Over the past 2 years the community put in an immense effort to improve and adapt the IoT modem’s firmware to better serve the PinePhone (Pro). Work by [Biktor](https://twitter.com/biktorgj) and [Konrad](https://twitter.com/konradybcio), as well as that of other contributors, opened the modem up to tinkering and thereby also to alterations and improvements to its software. Before I write another word, I need to underline that it is [PINE64’s and Pine Store’s position](https://wiki.pine64.org/wiki/PineModems#PINE64_position_on_alternative_firmware) that the licensed proprietary firmware on the modem should not be tampered with, and it is my duty to notify you that altering the modem’s firmware may violate your local laws, which in turn can have very real consequences. Therefore, please consider the following to be a progress report and a showcase, which I find to be fitting well with the community spirit of this blog, but it is not an enticement to use alternative firmware on your PinePhone (Pro). +As most of you are aware, the PinePhone (Pro)’s Quectel EG25-G modem is effectively its own single-core Arm computer running a closed Linux-based firmware. Over the past 2 years the community put in an immense effort to improve and adapt the IoT modem’s firmware to better serve the PinePhone (Pro). Work by [Biktor](https://twitter.com/biktorgj) and [Konrad](https://twitter.com/konradybcio), as well as that of other contributors, opened the modem up to tinkering and thereby also to alterations and improvements to its software. Before I write another word, I need to underline that it is [PINE64’s and Pine Store’s position](/documentation/General/PineModems#pine64_position_on_alternative_firmware) that the licensed proprietary firmware on the modem should not be tampered with, and it is my duty to notify you that altering the modem’s firmware may violate your local laws, which in turn can have very real consequences. Therefore, please consider the following to be a progress report and a showcase, which I find to be fitting well with the community spirit of this blog, but it is not an enticement to use alternative firmware on your PinePhone (Pro). Until recently it was very difficult to switch from the closed Quectel firmware to the much more [open firmware by Biktor](https://github.com/Biktorgj/pinephone_modem_sdk/releases/tag/0.6.7). This community firmware contains no binary blobs in the userspace, and significantly reduces the modem’s power consumption and heat output by running the SoC at just 100Mhz instead of the default 400Mhz/ 800Mhz. Until recently, installation of the community firmware required you to have a firm understanding of the command line and ADB. Now, however, the process has been completely streamlined and achievable via fwupd, and from a GUI no less. I decided to try the process on my own hardware running DanctNIX Arch Linux. The process is as simple as opening up the GNOME software centre, searching for “Firmware” and downloading the GUI utility. Upon launching the Firmware utility the Quectel modem is automatically listed as eligible for firmware updates. Tapping the modem provides information about the current vendor firmware, vendor ID as well as many other information. Scrolling down reveals available releases from Biktor. The installation is as simple as tapping the chosen release, reading the precaution popup, and agreeing to proceed with the installation. The installation takes approximately 10 minutes, and at the end of which the phone needs to be rebooted.  diff --git a/content/blog/march-update-introducing-the-quartzpro64.md b/content/blog/march-update-introducing-the-quartzpro64.md index 589b97a4..b84c16bf 100644 --- a/content/blog/march-update-introducing-the-quartzpro64.md +++ b/content/blog/march-update-introducing-the-quartzpro64.md @@ -73,7 +73,7 @@ I’m starting with a last-minute edit to this month's update; Shenzhen, the cit **Left: original text in Chinese // Right: auto-translation into English ('deep training' to be read as 'thorough testing')** -A new episode of the PineTalk is out. In this most recent entry to our community podcast, Justin and Brian discuss current PinePhone and PinePhone Pro developments, including Tow-boot and improvements to Mexapixels post-processing, as well as their own open-hardware ideas. While I do not think we’ll embark on a journey to create an open Google Glass-type device, as suggested by Brian, an open speaker with a personal assistant is actually a compelling idea (and one we discussed internally all the way back in 2020). A solid idea Justin and one perhaps worth visiting. Have a listen and let us know what you think about the show-hosts ideas for future hardware. The most recent episode can be found on [PineTalk’s page](https://www.pine64.org/pinetalk/); I also encourage you to subscribe to the [podcast’s RSS feed](https://www.pine64.org/feed/mp3/).  +A new episode of the PineTalk is out. In this most recent entry to our community podcast, Justin and Brian discuss current PinePhone and PinePhone Pro developments, including Tow-boot and improvements to Mexapixels post-processing, as well as their own open-hardware ideas. While I do not think we’ll embark on a journey to create an open Google Glass-type device, as suggested by Brian, an open speaker with a personal assistant is actually a compelling idea (and one we discussed internally all the way back in 2020). A solid idea Justin and one perhaps worth visiting. Have a listen and let us know what you think about the show-hosts ideas for future hardware. The most recent episode can be found on [PineTalk’s page](https://www.pine64.org/podcast/); I also encourage you to subscribe to the [podcast’s RSS feed](https://www.pine64.org/feed/mp3/).  During my absence (more on this a bit later), [Fire219](https://twitter.com/fire219_SIMPL) and [Gamiee](https://twitter.com/gamelaster) have done some solid improvements to our chat infrastructure. As I’ve reported [late last year](https://www.pine64.org/2021/11/15/november-update-first-impressions/), and as many of you know from first-hand experience, spam in the chat has been an issue in recent months. A part of the problem is our cross-platform bridge: not all moderators have moderation privileges on all platforms, and those that do aren’t always there to react. Moreover, it is easier to get the moderators’ attention on some platforms than others. Earlier this year Fire219 and Gamiee laid the foundations for automatically removing spam and flagging potential malware. This reduced the number of incidents but hasn’t fully eliminated the issue. Now, however, we’ve got two new weapons at our disposal: cross-platform deletion and a sophisticated and trained AI bot with cross-platform deletion permissions. This means that even if the, rather sophisticated, bot fails to catch the spam any moderator can delete any spam message on any platform. Long story short, the spam problem should be less intrusive moving forward.  diff --git a/content/blog/may-update-pinetab-pre-orders-pinephone-qi-charging-more.md b/content/blog/may-update-pinetab-pre-orders-pinephone-qi-charging-more.md index 4e20c088..325fbb12 100644 --- a/content/blog/may-update-pinetab-pre-orders-pinephone-qi-charging-more.md +++ b/content/blog/may-update-pinetab-pre-orders-pinephone-qi-charging-more.md @@ -67,7 +67,7 @@ Lastly, a quick word about our Wiki. If someone would find the time for tidying With the PinePhone UBports Community Edition and Manjaro Pinebook Pro batches now shipping, we turn our attention to the PineTab. If you follow this blog regularly, then you already know that the tablet has been stuck in a production limbo since summer last year. The decision to postpone PineTab production was made with the purpose to prioritize assembly and shipment of Pinebook Pro and PinePhone batches - as these are PINE64 flagship devices. In light of the global events, which caused subsequent logistics turmoil, production was pushed back nearly 9 months. With the COVID19 pandemic subsiding in China, and factory lines reopening for business, we’re now happy to announce that **we’ll be taking orders for the PineTab later this month.** -Although we’re skipping any formal naming of this PineTab batch, I need to underline that this is a limited-quantity pilot-production run. In other words, these PineTabs are similar in nature to Braveheart PinePhones - they are aimed at early adopters who understand the implications of purchasing an early production-run device. I have written a lot over the past 9 months about the PineTab, and about the gradual improvements we made to it and its keyboard while we waited for a suitable moment to start production. I suggest you go back and read the relevant posts for more details ([https://www.pine64.org/category/pinetab/](https://www.pine64.org/category/pinetab/)).  +Although we’re skipping any formal naming of this PineTab batch, I need to underline that this is a limited-quantity pilot-production run. In other words, these PineTabs are similar in nature to Braveheart PinePhones - they are aimed at early adopters who understand the implications of purchasing an early production-run device. I have written a lot over the past 9 months about the PineTab, and about the gradual improvements we made to it and its keyboard while we waited for a suitable moment to start production. I suggest you go back and read the relevant posts for more details ([https://www.pine64.org/tags/pinetab/](https://www.pine64.org/tags/pinetab/)).  ![](/blog/images/pinetab_KB_P64_UT.jpg) diff --git a/content/blog/november-update-first-impressions.md b/content/blog/november-update-first-impressions.md index 603c958e..d9c74156 100644 --- a/content/blog/november-update-first-impressions.md +++ b/content/blog/november-update-first-impressions.md @@ -128,7 +128,7 @@ Finally, the keyboard’s open firmware worked out of the box on my Manjaro Plas ## SOQuartz -I already spent much time on the SOQuartz and two of its hostboards in [last month’s follow-up](https://www.pine64.org/2021/10/29/october-update-follow-up/) post, so in this section I’ll be focusing on a new hostboard for the module - the Blade. If you missed the announcement of SOQuartz’s launch, please read the previous blog entry. The Blade hostboard is designed to fit into a 1U server rack and, in a sense, brings the legacy of the [SOPine and SOEdge Clusterboard](https://www.pine64.org/clusterboard/) to the next generation of PINE64 modules. More than a dozen Blade hostboards can be housed in a standard server rack, making any cluster compute project highly scalable depending on set requirements. Using the hostboard, new modules can also be easily added ad-hoc to the cluster setup.  +I already spent much time on the SOQuartz and two of its hostboards in [last month’s follow-up](https://www.pine64.org/2021/10/29/october-update-follow-up/) post, so in this section I’ll be focusing on a new hostboard for the module - the Blade. If you missed the announcement of SOQuartz’s launch, please read the previous blog entry. The Blade hostboard is designed to fit into a 1U server rack and, in a sense, brings the legacy of the [SOPine and SOEdge Clusterboard](https://www.pine64.org/Clusterboard/) to the next generation of PINE64 modules. More than a dozen Blade hostboards can be housed in a standard server rack, making any cluster compute project highly scalable depending on set requirements. Using the hostboard, new modules can also be easily added ad-hoc to the cluster setup.  ![](/blog/images/Soquartz-blade.jpg) diff --git a/content/blog/october-update-follow-up.md b/content/blog/october-update-follow-up.md index ccdd4b6b..190de801 100644 --- a/content/blog/october-update-follow-up.md +++ b/content/blog/october-update-follow-up.md @@ -26,7 +26,7 @@ Happy Halloween! As promised earlier this month, here is the follow-up to the [O ## Housekeeping  -PineTalk discussed the PinePhone Pro in last week's episode. At the time of writing, it is the most listened-to episode of our community-run podcast, and there is a reason for it - it is a very good episode. I encourage you to [have a listen](https://www.pine64.org/pinetalk/).   +PineTalk discussed the PinePhone Pro in last week's episode. At the time of writing, it is the most listened-to episode of our community-run podcast, and there is a reason for it - it is a very good episode. I encourage you to [have a listen](https://www.pine64.org/podcast/).   Earlier this week we had a guest post about the creation of the [_Meet the PinePhone Pro_](https://youtu.be/wP2-6Z74W44) announcement trailer. If you’re interested in learning how the trailer was made, and which software was used during its production, then I invite you to [have a read](https://www.pine64.org/2021/10/27/how-meet-the-pinephone-pro-was-made/).  diff --git a/content/blog/september-update-hurdles-and-successes.md b/content/blog/september-update-hurdles-and-successes.md index c7076c09..494fad42 100644 --- a/content/blog/september-update-hurdles-and-successes.md +++ b/content/blog/september-update-hurdles-and-successes.md @@ -77,7 +77,7 @@ But this isn’t the end of DevZone news. Once the system is populated with deve **DevZone [sign-ups](https://devzone.pine64.org/signup.php) will remain open indefinitely** -In other news, [PineTalk podcast](https://www.pine64.org/pinetalk/) is coming back after a two-month hiatus! The community-ran show that focuses on PINE64 news and related topics will resume shortly with new hosts and a reworked schedule. As it has been explained to me, the plan is to have an episode dedicated to discussion of news and the following one to community and partner-project topics. PineTalk is available on most popular streaming platforms such as [Spotify](https://open.spotify.com/show/4IXVMkSMAxsuLzIXuKI3IJ) as well as on our [YouTube](https://www.youtube.com/c/PINE64inc) and [Odysee](https://odysee.com/@PINE64:a) channels. A dedicated post announcing the return of the PineTalk and introducing the new hosts will go live shortly - stay tuned to learn more. If you haven’t done so yet, make sure to subscribe to the show’s [RSS MP3 feed](https://www.pine64.org/feed/mp3/).  +In other news, [PineTalk podcast](https://www.pine64.org/podcast/) is coming back after a two-month hiatus! The community-ran show that focuses on PINE64 news and related topics will resume shortly with new hosts and a reworked schedule. As it has been explained to me, the plan is to have an episode dedicated to discussion of news and the following one to community and partner-project topics. PineTalk is available on most popular streaming platforms such as [Spotify](https://open.spotify.com/show/4IXVMkSMAxsuLzIXuKI3IJ) as well as on our [YouTube](https://www.youtube.com/c/PINE64inc) and [Odysee](https://odysee.com/@PINE64:a) channels. A dedicated post announcing the return of the PineTalk and introducing the new hosts will go live shortly - stay tuned to learn more. If you haven’t done so yet, make sure to subscribe to the show’s [RSS MP3 feed](https://www.pine64.org/feed/mp3/).  ![](/blog/images/PineTalk-logo.png) diff --git a/content/devices/sopine_clusterboard.adoc b/content/devices/clusterboard.adoc similarity index 94% rename from content/devices/sopine_clusterboard.adoc rename to content/devices/clusterboard.adoc index b543ebcb..aeeef015 100644 --- a/content/devices/sopine_clusterboard.adoc +++ b/content/devices/clusterboard.adoc @@ -1,14 +1,17 @@ --- -title: "SOPINE Clusterboard" +title: "Clusterboard" categories: - "Clusters" cover: image: "/devices/images/sopine_clusterboard.jpg" images: - "/devices/images/sopine_clusterboard.jpg" +aliases: + - /devices/clusterboard + - /clusterboard --- -== SOPINE Clusterboard +== Clusterboard The Clusterboard is a gateway into the world of clusters in a tidy and compact package. The SOPINE Custerboard can host up-to 7 SOPINE modules. The Clusterboard can be powered either using a +5V 15A power supply with 6.3mm OD/3.0mm ID barrel type DC Jack or an ATX power supply*. Each of the SOPINE cluster nodes is able to interface with the entire system via the onboard Ethernet switch. Each node has a USB 2.0 host port and 20 GPIO pins exposed. diff --git a/content/devices/pinetab-v.adoc b/content/devices/pinetab-v.adoc index 63bc4adc..783fa075 100644 --- a/content/devices/pinetab-v.adoc +++ b/content/devices/pinetab-v.adoc @@ -20,5 +20,5 @@ The PineTab-V is PINE64’s first RISC-V tablet. It is based on the JH7110 64-bi | link:/documentation/PineTab-V/[PineTab-V] -| link:/documentation/PineTab-V/Schematics_and_certifications/[Schematics and certifications] +| link:/documentation/PineTab-V/Further_information/[Schematics and certifications] |=== diff --git a/content/documentation/Accessories/Cases/NASCase.adoc b/content/documentation/Accessories/Cases/NASCase.adoc index 7623ec2f..63cf0fa4 100644 --- a/content/documentation/Accessories/Cases/NASCase.adoc +++ b/content/documentation/Accessories/Cases/NASCase.adoc @@ -67,7 +67,7 @@ There are a few other things which you may wish to consider purchasing for your image:/documentation/images/OMVGUI.png[The OMV WebGUI is easy to understand but also very robust. It offers easy installation of plugins, system administration and overview of available services,title="The OMV WebGUI is easy to understand but also very robust. It offers easy installation of plugins, system administration and overview of available services",width=200] -If you are intending to build a home or small company NAS, then we strongly recommend you use link:/documentation/ROCKPro64/Software#OpenMediaVault[Open Media Vault (OMV)]. OMV is an open source NAS solution that makes setting up user accounts, network shares and services a breeze. It also simplifies installing additional features (called plugins), such as: PLEX media server; Remote Desktop; Encryption; RSync; etc. +If you are intending to build a home or small company NAS, then we strongly recommend you use link:/documentation/ROCKPro64/Software#openmediavault[Open Media Vault (OMV)]. OMV is an open source NAS solution that makes setting up user accounts, network shares and services a breeze. It also simplifies installing additional features (called plugins), such as: PLEX media server; Remote Desktop; Encryption; RSync; etc. Its worth noting that Nextcloud, or other similar Cloud storage solutions, can also be easily installed alongside the OMV OS Image. diff --git a/content/documentation/Accessories/POT.adoc b/content/documentation/Accessories/POT.adoc index 3056cefc..066db0fd 100644 --- a/content/documentation/Accessories/POT.adoc +++ b/content/documentation/Accessories/POT.adoc @@ -198,7 +198,7 @@ DC Jack socket (suitable for 4.0mm X 1.7mm DC Jack) for system power input UART Port connector ready for on chip programming using USB/UART Programming/Console Adapter (PMPROG01) 2pcs of XH 5pin 2.54 mm pitch connector to allow daisy chain of multiple I2C sensor ``` -Further Detail info on the module can be found at link:/documentation/Unsorted/Wifi_remote_i2c[WiFi Remote I2c Quick Start Guide] wiki page +Further Detail info on the module can be found at link:/documentation/Accessories/Wifi_remote_i2c[WiFi Remote I2c Quick Start Guide] wiki page === Related Specification and Document diff --git a/content/documentation/Accessories/Wifi_remote_i2c.adoc b/content/documentation/Accessories/Wifi_remote_i2c.adoc index 768ddac5..82669168 100644 --- a/content/documentation/Accessories/Wifi_remote_i2c.adoc +++ b/content/documentation/Accessories/Wifi_remote_i2c.adoc @@ -4,8 +4,8 @@ draft: false menu: docs: title: - parent: "Unsorted" - identifier: "Unsorted/Wifi_remote_i2c" + parent: "Accessories" + identifier: "Accessories/Wifi_remote_i2c" weight: --- @@ -57,7 +57,7 @@ Press Config Mode button to go into configuration mode === Setup the PineWifiServer -* link:/documentation/Unsorted/Wifi_remote_i2c#download[Download the PineWifiServer from the Download Section] +* link:/documentation/Accessories/Wifi_remote_i2c#download[Download the PineWifiServer from the Download Section] * Copy PineWifiServer xxxxxxxx.gz into your PineA64 with linux on it. (where xxxxxxxx is the version number) * Unzip the file using gunzip. * Add Execution flag on both of the file by @@ -77,7 +77,7 @@ image:/documentation/images/Wr_putty_login.JPG[PineWifiServer Login Screen,title === Running the WifiAppDemo -* link:/documentation/Unsorted/Wifi_remote_i2c#download[Download the PineWifiServer from the Download Section] +* link:/documentation/Accessories/Wifi_remote_i2c#download[Download the PineWifiServer from the Download Section] * Copy WifiAppDemo xxxxxxxx.gz into your same PineA64 board that currently running with PineWifiServer. (where xxxxxxxx is the version number) * Unzip both of the file using gunzip. * Add Execution flag on both of the file by @@ -113,7 +113,7 @@ Place the jumper J2 on USB/UART Programming/Console Adapter (PMPROG01) to 5V out === Software Setup -* Download the firmware from the link:/documentation/Unsorted/Wifi_remote_i2c#Download[download section] and unzip the file. +* Download the firmware from the link:/documentation/Accessories/Wifi_remote_i2c#download[download section] and unzip the file. * Download the windows Python base Flash Download Tools by Espressif from http://espressif.com/en/products/hardware/esp8266ex/resources[Espressif website]. * Setup the ESP Flash Download tools according to the screen short. diff --git a/content/documentation/Clusterboard/Further_information/_index.adoc b/content/documentation/Clusterboard/Further_information/_index.adoc index 6100cfd9..524765eb 100644 --- a/content/documentation/Clusterboard/Further_information/_index.adoc +++ b/content/documentation/Clusterboard/Further_information/_index.adoc @@ -9,6 +9,4 @@ menu: weight: --- -* link:Revisions[] -* link:FAQ[] -* link:Specifications[] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/Unsorted/Android_SDK_for_RK3566.adoc b/content/documentation/General/Android_SDK_for_RK3566.adoc similarity index 97% rename from content/documentation/Unsorted/Android_SDK_for_RK3566.adoc rename to content/documentation/General/Android_SDK_for_RK3566.adoc index 8ae591f2..5591b172 100644 --- a/content/documentation/Unsorted/Android_SDK_for_RK3566.adoc +++ b/content/documentation/General/Android_SDK_for_RK3566.adoc @@ -4,8 +4,8 @@ draft: false menu: docs: title: - parent: "Unsorted" - identifier: "Unsorted/Android_SDK_for_RK3566" + parent: "General" + identifier: "General/Android_SDK_for_RK3566" weight: --- diff --git a/content/documentation/General/Cross-compiling.adoc b/content/documentation/General/Cross-compiling.adoc index 24b405e6..286db5b2 100644 --- a/content/documentation/General/Cross-compiling.adoc +++ b/content/documentation/General/Cross-compiling.adoc @@ -63,7 +63,7 @@ In order to cross-compile Rust applications for the Pinephone, you need to have The cross-compiler might have a different name depending on the operating system. Further along this instruction the name for the gcc cross-compiler will be used. Replace all occurences of `$gcc_name` with the name on your distribution. -For how to install the gcc cross-compilation toolchain on your distribution, please see link:/documentation/General/Cross-compiling#Installing_The_Toolchain[Cross-compiling] +For how to install the gcc cross-compilation toolchain on your distribution, please see link:/documentation/General/Cross-compiling#installing_the_toolchain[Cross-compiling] === Installing Rust Dependencies diff --git a/content/documentation/Unsorted/PineModems.adoc b/content/documentation/General/PineModems.adoc similarity index 98% rename from content/documentation/Unsorted/PineModems.adoc rename to content/documentation/General/PineModems.adoc index 74cc7791..2806ff78 100644 --- a/content/documentation/Unsorted/PineModems.adoc +++ b/content/documentation/General/PineModems.adoc @@ -4,8 +4,8 @@ draft: false menu: docs: title: - parent: "Unsorted" - identifier: "Unsorted/PineModems" + parent: "General" + identifier: "General/PineModems" weight: --- @@ -173,7 +173,7 @@ Once in EDL mode, open a terminal, navigate to the root directory of the recover * If you use an ARM64 distribution (most likely): `sudo ./qfirehose -f ./` or `sudo ./qfirehose_arm64 -f ./` * If you use an ARMHF (32 bit) distribution: `sudo ./qfirehose_armhf -f ./` -It will reboot the modem after finished. After about 30 seconds, it will get back up and running. To check the firmware version after that, use an AT command `AT+QGMR` like at link:/documentation/PinePhone#Firmware_update[PinePhone]. +It will reboot the modem after finished. After about 30 seconds, it will get back up and running. To check the firmware version after that, use an AT command `AT+QGMR` like at link:/documentation/PinePhone/Modem/#firmware_update[PinePhone]. === Bootloader unlocking diff --git a/content/documentation/General/U-Boot.adoc b/content/documentation/General/U-Boot.adoc index dfd767e6..dc203c2f 100644 --- a/content/documentation/General/U-Boot.adoc +++ b/content/documentation/General/U-Boot.adoc @@ -17,7 +17,7 @@ TIP: It is helpful to have a debugging serial cable for this. These instructions are written with a host Arch Linux desktop system in mind. -This guide will be especially useful if you are looking to overclock the ram on your PinePhone following the information found link:/documentation/General/Overclocking#DRAM[here]. +This guide will be especially useful if you are looking to overclock the ram on your PinePhone following the information found link:/documentation/General/Overclocking#dram[here]. You must have these packages installed: `dtc swig bc aarch64-linux-gnu-gcc` diff --git a/content/documentation/Introduction/Getting_started.adoc b/content/documentation/Introduction/Getting_started.adoc index a5f00192..c871102c 100644 --- a/content/documentation/Introduction/Getting_started.adoc +++ b/content/documentation/Introduction/Getting_started.adoc @@ -211,7 +211,7 @@ A USB-to-eMMC adapter is available from purchase from the https://pine64.com/pro *This installation method works for all devices that support eMMC modules regardless of the chipset* and it is therefore the preferred way of flashing OS images to eMMC. All available OS images for your device can be installed on the eMMC module this way. -*This process of flashing an OS image to eMMC is *completely identical to imaging micro SD cards*, so please read link:/documentation/General/Getting_started#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards[Step-by-Step Instructions to Flashing Micro SD Cards] before you begin. +*This process of flashing an OS image to eMMC is *completely identical to imaging micro SD cards*, so please read link:/documentation/Introduction/Getting_started#step_by_step_instructions_for_flashing_microsd_cards[Step-by-Step Instructions to Flashing Micro SD Cards] before you begin. For this method you will need the following: @@ -239,11 +239,11 @@ There are *two ways* in which an OS image can be flashed from within a micro SD * Via a script called Pine64_install_to_eMMC.sh found in _/usr/local/sbin_. This script will install an Ubuntu Mate OS installation (identical to the on running on the SD) to the eMMC module. To execute the script navigate to its location in the terminal and type `sudo ./Pine64_install_to_eMMC.sh`. Follow the instructions. -* By manually downloading and flashing a OS image for your device using DD or the Disk GUI. This way of flashing an OS image to the eMMC is identical to that used on a Linux computer (e.g. for flashing an OS image to a SD card). For more information on how the process works please see the detailed guide on link:/documentation/General/Getting_started#Imaging_microSD_on_Linux[imaging OS images to SD card on Linux]. +* By manually downloading and flashing a OS image for your device using DD or the Disk GUI. This way of flashing an OS image to the eMMC is identical to that used on a Linux computer (e.g. for flashing an OS image to a SD card). For more information on how the process works please see the detailed guide on link:/documentation/Introduction/Getting_started#imaging_microsd_on_linux[imaging OS images to SD card on Linux]. For the latter of the two methods here is a summary of the process: -* Flash an OS image which recognizes eMMC as mounted storage to a micro SD card. For details on how to flash a micro SD card see link:/documentation/General/Getting_started#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards[section 3] +* Flash an OS image which recognizes eMMC as mounted storage to a micro SD card. For details on how to flash a micro SD card see link:/documentation/Introduction/Getting_started#step_by_step_instructions_for_flashing_microsd_cards[section 3] * Insert both the micro SD and eMMC module into your device and power it on. @@ -291,7 +291,7 @@ or Once your device mounts as UMS it will appear in your file manager. In CLI you can check if the storage is listed using _fdisk -l_. -This process of flashing an OS image to eMMC with the device in FEL mode and mounted as UMS is *literally identical to imaging micro SD cards*, so please read link:/documentation/General/Getting_started#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards[Step-by-Step Instructions to Flashing Micro SD Cards] and follow the procedure. You can use DD or Disks/ Disk Utility to flash the OS image directly to your device's eMMC. +This process of flashing an OS image to eMMC with the device in FEL mode and mounted as UMS is *literally identical to imaging micro SD cards*, so please read link:/documentation/Introduction/Getting_started#step_by_step_instructions_for_flashing_microsd_cards[Step-by-Step Instructions to Flashing Micro SD Cards] and follow the procedure. You can use DD or Disks/ Disk Utility to flash the OS image directly to your device's eMMC. Once the flashing process is completed, power down your device, remove the A-to-A USB OTG cable and after reapply power to boot your device from eMMC. @@ -369,7 +369,7 @@ Writing u-boot to SPI Flash can be achieved in two ways: === Using a Stand-Alone Image to Write u-boot to SPI -This may be the simplest method of flashing u-boot to SPI. Download a dedicated image labelled *u-boot-flash-spi.img.xz* from https://github.com/ayufan-rock64/linux-u-boot/releases[ayufan's github] and flash it to a microSD card, the same as you would with any OS image (to learn how to flash OS images to microSD please follow steps outlined in link:/documentation/General/Getting_started#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards[Section 3]. +This may be the simplest method of flashing u-boot to SPI. Download a dedicated image labelled *u-boot-flash-spi.img.xz* from https://github.com/ayufan-rock64/linux-u-boot/releases[ayufan's github] and flash it to a microSD card, the same as you would with any OS image (to learn how to flash OS images to microSD please follow steps outlined in link:/documentation/Introduction/Getting_started#step_by_step_instructions_for_flashing_microsd_cards[Section 3]. *Having flashed the image follow these steps*: @@ -384,7 +384,7 @@ The board is now ready to boot from USB 2.0/3.0 storage. === Using a Script on Linux OS Images -Most of recent (newer than 0.6.9) Linux OS images contain a script called *rock64_write_spi_flash.sh*, which is found in _/usr/local/sbin_ directory. To run the script you will first need to flash a Linux OS image to a micro SD card (to learn how to flash OS images to micro SD please following steps outlined in link:/documentation/General/Getting_started#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards[Section 3]). Before proceeding *make sure that the eMMC module is disconnected* from the board. Once you have booted into Linux on your PINE64 device all you have to do is run the aforementioned script using this command: +Most of recent (newer than 0.6.9) Linux OS images contain a script called *rock64_write_spi_flash.sh*, which is found in _/usr/local/sbin_ directory. To run the script you will first need to flash a Linux OS image to a micro SD card (to learn how to flash OS images to micro SD please following steps outlined in link:/documentation/Introduction/Getting_started#step_by_step_instructions_for_flashing_microsd_cards[Section 3]). Before proceeding *make sure that the eMMC module is disconnected* from the board. Once you have booted into Linux on your PINE64 device all you have to do is run the aforementioned script using this command: `sudo ./rock64_write_spi_flash.sh` @@ -409,7 +409,7 @@ To boot an OS image from USB 2.0/3.0 Storage such as a SSD/HDD or a thumbdrive y Once you have u-boot on your SPI, the process of booting is very similar to booting from microSD or eMMC. * Download one of the supported OS images for your PINE64 device -* Flash the OS image to your USB 2.0/USB 3.0 storage device (to learn how to flash OS images please following steps outlined in link:/documentation/General/Getting_started#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards[Section 3] The instructions are identical for all types of storage, including USB 2.0/USB 3.0 HDDs and thumb-drives.) +* Flash the OS image to your USB 2.0/USB 3.0 storage device (to learn how to flash OS images please following steps outlined in link:/documentation/Introduction/Getting_started#step_by_step_instructions_for_flashing_microsd_cards[Section 3] The instructions are identical for all types of storage, including USB 2.0/USB 3.0 HDDs and thumb-drives.) * Insert the USB storage device with the flashed OS image into one of the USB ports on your PINE64 device * Apply power diff --git a/content/documentation/Introduction/How_to_contribute.adoc b/content/documentation/Introduction/How_to_contribute.adoc index e207e998..dc0f2664 100644 --- a/content/documentation/Introduction/How_to_contribute.adoc +++ b/content/documentation/Introduction/How_to_contribute.adoc @@ -15,7 +15,7 @@ The following article contains a selection of common ways to contribute to the c Reporting issues is a great way to contribute (if done correctly). The software projects are using bug trackers to keep track of bugs and to link patches or changes with these bug reports. -See the article link:/documentation/General/Where_to_report_bugs[where to report bugs] to find out where you can report bugs. +See the article link:/documentation/Introduction/Where_to_report_bugs[where to report bugs] to find out where you can report bugs. == Contributing code diff --git a/content/documentation/Introduction/Where_to_report_bugs.adoc b/content/documentation/Introduction/Where_to_report_bugs.adoc index fb36185f..0145164b 100644 --- a/content/documentation/Introduction/Where_to_report_bugs.adoc +++ b/content/documentation/Introduction/Where_to_report_bugs.adoc @@ -22,7 +22,6 @@ Issues with the PinePhone and the PinePhone Pro can be reported on the following === Operating Systems and Distributions * Arch Linux ARM (DanctNIX): https://github.com/dreemurrs-embedded/Pine64-Arch/issues?q=is%3Aissue -* ExpidusOS: https://github.com/orgs/ExpidusOS/repositories * Fedora: https://github.com/nikhiljha/pp-fedora-sdsetup/issues?q=is%3Aissue * Gentoo: On the bug tracker of the corresponding unofficial overlay * GloDroid: https://github.com/GloDroid/glodroid_manifest/issues?q=is%3Aissue diff --git a/content/documentation/Introduction/_index.adoc b/content/documentation/Introduction/_index.adoc index 110998ca..8a8b381e 100644 --- a/content/documentation/Introduction/_index.adoc +++ b/content/documentation/Introduction/_index.adoc @@ -9,6 +9,4 @@ menu: weight: --- -* link:Where_to_report_bugs[Where to report bugs] -* link:How_to_contribute[How to contribute] -* link:Getting_started[Getting started] +{{< children >}} diff --git a/content/documentation/Ox64/Further_information/_index.adoc b/content/documentation/Ox64/Further_information/_index.adoc index ad0fe907..12855e39 100644 --- a/content/documentation/Ox64/Further_information/_index.adoc +++ b/content/documentation/Ox64/Further_information/_index.adoc @@ -9,8 +9,4 @@ menu: weight: 4 --- -* link:Compatible_UARTs[Compatible UARTs] -* link:Datasheets[] -* link:Resources[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:SoC_and_Memory_Specification[SoC and Memory Specification] +{{< children >}} diff --git a/content/documentation/Ox64/Software/_index.adoc b/content/documentation/Ox64/Software/_index.adoc index 864a60de..55093fcd 100644 --- a/content/documentation/Ox64/Software/_index.adoc +++ b/content/documentation/Ox64/Software/_index.adoc @@ -9,6 +9,4 @@ menu: weight: 2 --- -* link:Releases[] -* link:Building[] -* link:Flashing[] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/PINE_H64_Model_A/Further_information/_index.adoc b/content/documentation/PINE_H64_Model_A/Further_information/_index.adoc index 72bbccd6..72b0b3e5 100644 --- a/content/documentation/PINE_H64_Model_A/Further_information/_index.adoc +++ b/content/documentation/PINE_H64_Model_A/Further_information/_index.adoc @@ -9,6 +9,4 @@ menu: weight: --- -* link:Datasheets[] -* link:Schematics_and_Certifications[Schematics and Certifications] -* link:Mali-T720_driver[Mali-T720 driver] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/PINE_H64_Model_A/Software/_index.adoc b/content/documentation/PINE_H64_Model_A/Software/_index.adoc index f3842a18..88d635af 100644 --- a/content/documentation/PINE_H64_Model_A/Software/_index.adoc +++ b/content/documentation/PINE_H64_Model_A/Software/_index.adoc @@ -9,5 +9,4 @@ menu: weight: 2 --- -* link:Armbian[] -* link:Linux_BSP_SDK[Linux BSP SDK] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/PINE_H64_Model_B/Further_information/_index.adoc b/content/documentation/PINE_H64_Model_B/Further_information/_index.adoc index da4a63b1..f19dc55e 100644 --- a/content/documentation/PINE_H64_Model_B/Further_information/_index.adoc +++ b/content/documentation/PINE_H64_Model_B/Further_information/_index.adoc @@ -9,6 +9,4 @@ menu: weight: --- -* link:Datasheets[] -* link:Schematics_and_Certifications[Schematics and Certifications] -* link:Mali-T720_driver[Mali-T720 driver] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/PINE_H64_Model_B/Software/_index.adoc b/content/documentation/PINE_H64_Model_B/Software/_index.adoc index f348a4f3..0ad25424 100644 --- a/content/documentation/PINE_H64_Model_B/Software/_index.adoc +++ b/content/documentation/PINE_H64_Model_B/Software/_index.adoc @@ -9,6 +9,4 @@ menu: weight: 2 --- -* link:Releases[Releases] -* link:Linux_BSP_SDK[Linux BSP SDK] -* link:Android_SDK[Android SDK] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/Phone_Accessories/_index.adoc b/content/documentation/Phone_Accessories/_index.adoc index 9f9892c8..6404ef50 100644 --- a/content/documentation/Phone_Accessories/_index.adoc +++ b/content/documentation/Phone_Accessories/_index.adoc @@ -33,4 +33,4 @@ The following accessory is made by the community: * https://www.thingiverse.com/thing:4654013[PinePhone Development Stand at Thingverse] == Hubs -USB hubs do not require a custom driver and are therefore expected to be compatible with the PinePhone, as long as they are within the USB specification. On revisions the PinePhone mainboard revisions v1.1 and v1.2 the VCONN fix is required, on v1.2a and later the USB hub should work out of the box, see link:/documentation/PinePhone#Hardware_revisions[PinePhone]. \ No newline at end of file +USB hubs do not require a custom driver and are therefore expected to be compatible with the PinePhone, as long as they are within the USB specification. On revisions the PinePhone mainboard revisions v1.1 and v1.2 the VCONN fix is required, on v1.2a and later the USB hub should work out of the box, see link:/documentation/PinePhone/Revisions[PinePhone]. \ No newline at end of file diff --git a/content/documentation/PineBuds_Pro/Further_information/_index.adoc b/content/documentation/PineBuds_Pro/Further_information/_index.adoc index 83895f4d..eb57e1b4 100644 --- a/content/documentation/PineBuds_Pro/Further_information/_index.adoc +++ b/content/documentation/PineBuds_Pro/Further_information/_index.adoc @@ -9,7 +9,4 @@ menu: weight: 4 --- -* link:Datasheets[Datasheets] -* link:Information,_Schematics_and_Certifications[Schematics and Certifications] -* link:Disassembly_and_assembly[Disassembly and assembly] -* link:Cleaning[Cleaning] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/PineCone/Further_information/_index.adoc b/content/documentation/PineCone/Further_information/_index.adoc index f4f245ff..14ff519a 100644 --- a/content/documentation/PineCone/Further_information/_index.adoc +++ b/content/documentation/PineCone/Further_information/_index.adoc @@ -9,11 +9,4 @@ menu: weight: --- -* link:Articles_and_blogs[Articles and blogs] -* link:Development_efforts[Development efforts] -* link:Datasheets[] -* link:Pinenut-12S_Module_information[Pinenut-12S Module information] -* link:Pinenut-01S_Module_information_and_schematics[Pinenut-01S Module information and schematics] -* link:PineCone_BL602_EVB_information_and_schematics[PineCone BL602 EVB information and schematics] -* link:Pine64_USB_JTAG_Adapter_information_and_schematics[Pine64 USB JTAG Adapter information and schematics] -* link:BL602_specifications[BL602 specifications] +{{< children >}} diff --git a/content/documentation/PineCube/Cases.adoc b/content/documentation/PineCube/Cases.adoc index ba83fa2c..d193458f 100644 --- a/content/documentation/PineCube/Cases.adoc +++ b/content/documentation/PineCube/Cases.adoc @@ -9,8 +9,8 @@ menu: weight: 3 --- -image:images/PineCube_Case-1.jpg[] -image:images/PineCube_Case-2.jpg[] +image:/documentation/PineCube/images/PineCube_Case-1.jpg[] +image:/documentation/PineCube/images/PineCube_Case-2.jpg[] Model: diff --git a/content/documentation/PineCube/Further_information/_index.adoc b/content/documentation/PineCube/Further_information/_index.adoc index 4792d2ed..3df1a831 100644 --- a/content/documentation/PineCube/Further_information/_index.adoc +++ b/content/documentation/PineCube/Further_information/_index.adoc @@ -9,6 +9,4 @@ menu: weight: 99 --- -* link:Datasheets[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:Specifications[] +{{< children >}} diff --git a/content/documentation/PineCube/Pinout.adoc b/content/documentation/PineCube/Pinout.adoc index a6c79363..3d6497bf 100644 --- a/content/documentation/PineCube/Pinout.adoc +++ b/content/documentation/PineCube/Pinout.adoc @@ -9,7 +9,7 @@ menu: weight: 2 --- -image:images/PineCube_GPIO_Pinout.png[width=700] +image:/documentation/PineCube/images/PineCube_GPIO_Pinout.png[width=700] Note: Pin1 is marked on the board by a white dot on the PCB. See the https://wiki.pine64.org/wiki/File:PineCube_GPIO.pdf[PDF] and https://pine64.gami.ee/pinecube/gpio-pinout.html[HTML] for details. diff --git a/content/documentation/PineCube/Software/_index.adoc b/content/documentation/PineCube/Software/_index.adoc index 875e0a83..ab41207a 100644 --- a/content/documentation/PineCube/Software/_index.adoc +++ b/content/documentation/PineCube/Software/_index.adoc @@ -9,8 +9,4 @@ menu: weight: 1 --- -* link:Mainlining_Efforts[] -* link:Buildroot[] -* link:NixOS[] -* link:Armbian[] -* link:Armbian_notes[Armbian notes] +{{< children >}} diff --git a/content/documentation/PineCube/Tuning/_index.adoc b/content/documentation/PineCube/Tuning/_index.adoc index 1865a1d9..46281039 100644 --- a/content/documentation/PineCube/Tuning/_index.adoc +++ b/content/documentation/PineCube/Tuning/_index.adoc @@ -9,5 +9,4 @@ menu: weight: 6 --- -* link:Camera[] -* link:Sound_controls[Sound controls] \ No newline at end of file +{{< children >}} diff --git a/content/documentation/PineCube/_index.adoc b/content/documentation/PineCube/_index.adoc index 908e9b75..44dffd20 100644 --- a/content/documentation/PineCube/_index.adoc +++ b/content/documentation/PineCube/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:images/PineCube.jpg[The PineCube,title="The PineCube",width=400] +image:/documentation/PineCube/images/PineCube.jpg[The PineCube,title="The PineCube",width=400] The *PineCube* is a small, low-powered, open source IP camera. Whether you’re a parent looking for a FOSS baby-camera, a privacy oriented shop keeper, home owner looking for a security camera, or perhaps a tinkerer needing a camera for your drone – the CUBE can be the device for you. It features an 5MPx Omnivision sensor and IR LEDs for night vision, as well as Power Over Ethernet, as well as a microphone. diff --git a/content/documentation/PineNote/Development/Apps.adoc b/content/documentation/PineNote/Development/Apps.adoc index cc30dd44..110a3410 100644 --- a/content/documentation/PineNote/Development/Apps.adoc +++ b/content/documentation/PineNote/Development/Apps.adoc @@ -38,7 +38,7 @@ https://www.youtube.com/watch?v=ZCLyJfbzbrU[Here is a video] showing the perform ==== Getting touch + pen working on sway -If you notice that touching the screen works, but when you use the pen the mouse coordinates are inverted, don't worry! We can fix it! Set `rockchip_ebc.panel_reflection=0` on boot (see link:/documentation/PineNote/Development/Building_Kernel#Configuring_the_driver[this page] for more info). Add the following line to your sway config: +If you notice that touching the screen works, but when you use the pen the mouse coordinates are inverted, don't worry! We can fix it! Set `rockchip_ebc.panel_reflection=0` on boot (see link:/documentation/PineNote/Development/Building_kernel#Configuring_the_driver[this page] for more info). Add the following line to your sway config: # This line rotates the mouse input by 180 degrees. See https://wayland.freedesktop.org/libinput/doc/1.11.3/absolute_axes.html input "type:table_tool" calibration_matrix -1 0 1 0 -1 1 diff --git a/content/documentation/PineNote/Development/TODOs.adoc b/content/documentation/PineNote/Development/TODOs.adoc index 88340850..472f9c31 100644 --- a/content/documentation/PineNote/Development/TODOs.adoc +++ b/content/documentation/PineNote/Development/TODOs.adoc @@ -57,12 +57,12 @@ See link:/documentation/PineNote/Development/Apps#Gnome[here]. === Sway Configurations -See link:/documentation/wiki/PineNote/Development/Apps#Sway[here]. +See link:/documentation/PineNote/Development/Apps#Sway[here]. == Documentation TODOs * Pin Mesa Packages so they don't update when we upgrade other packages -** Add the information near step 5 link:/documentation/PineNote/Development/Building_Kernel#Steps_to_build[here]. +** Add the information near step 5 link:/documentation/PineNote/Development/Building_kernel#Steps_to_build[here]. * Control the backlight * Building alacritty correctly * Force a screen refresh? @@ -112,7 +112,7 @@ This table is a draft for the documentation development page: | `Bluetooth` 2+| Works, audio stutters -| link:/documentation/PineNote/Development/Building_Kernel#Fixing_Bluetooth[Switching the driver] provides stable connections for keyboards, but audio still stutters. Trying to fix this link:/documentation/PineNote/Development/Software_Tweaks#Preliminary_fix_for_stuttering_bluetooth_audio[here]. +| link:/documentation/PineNote/Development/Building_kernel#Fixing_Bluetooth[Switching the driver] provides stable connections for keyboards, but audio still stutters. Trying to fix this link:/documentation/PineNote/Development/Software_tweaks#Preliminary_fix_for_stuttering_bluetooth_audio[here]. | `Sensors` 2+| Unsure diff --git a/content/documentation/PineNote/Development/UART.adoc b/content/documentation/PineNote/Development/UART.adoc index 350a09c6..61882f64 100644 --- a/content/documentation/PineNote/Development/UART.adoc +++ b/content/documentation/PineNote/Development/UART.adoc @@ -23,7 +23,7 @@ A PineNote UART dongle enables you to: Since the PineNote is an embedded system, interfacing with it during boot is more complicated than with an ordinary computer. The UART dongle enables you to do this. -The PineNote factory firmware runs UART at a baud rate of 1500000 bps, 8 data bits, 1 stop bit, no parity and no flow control. The process by which the PineNote design was modified to include closed-case UART is documented link:/documentation/PineNote/Hardware_Changes/Closed_Case_UART[here]. +The PineNote factory firmware runs UART at a baud rate of 1500000 bps, 8 data bits, 1 stop bit, no parity and no flow control. The process by which the PineNote design was modified to include closed-case UART is documented link:/documentation/PineNote/Further_information/Closed_Case_UART[here]. == Stock dongle diff --git a/content/documentation/PineNote/Development_efforts.adoc b/content/documentation/PineNote/Development_efforts.adoc index ab2878ab..426bacb4 100644 --- a/content/documentation/PineNote/Development_efforts.adoc +++ b/content/documentation/PineNote/Development_efforts.adoc @@ -66,7 +66,7 @@ This section includes discussions and their results regarding hardware changes a The following topics have resolved: -* link:/documentation/PineNote/Hardware_Changes/Closed_Case_UART[PineNote/Hardware Changes/Closed Case UART] +* link:/documentation/PineNote/Further_information/Closed_Case_UART[PineNote/Hardware Changes/Closed Case UART] * *Could the USB-C port support USB 3.1 5Gbps?* Yes and no. The RK3566 only has a host-mode 5Gbps controller, meaning it can only negotiate such a high data rate with a device such as a flash drive. When the RK3566 is acting as a device, it only supports 480Mbps transfer rates. The hardware required to switch between these modes would raise the PineNote's price unreasonably. Therefore, the USB-C port will remain at USB 2.0 speeds for Host and Device mode. * *Could the USB-C port output DisplayPort?* Yes and no. The hardware required to support such a feature would raise the PineNote's price unreasonably. Therefore, DisplayPort output will not be possible through the USB-C port. * *Where is the microSD card slot?* The case design of the PineNote is fixed, making physical changes like adding a microSD card slot would raise the cost unreasonably. diff --git a/content/documentation/PineNote/Further_information/Closed_Case_UART.adoc b/content/documentation/PineNote/Further_information/Closed_Case_UART.adoc index 99da85c4..c3f26de3 100644 --- a/content/documentation/PineNote/Further_information/Closed_Case_UART.adoc +++ b/content/documentation/PineNote/Further_information/Closed_Case_UART.adoc @@ -26,7 +26,8 @@ Recent PINE64 devices have included a hardware UART connected to their 3.5mm TRR We decided to ask the PineNote product team to explore USB-C Debug Accessory Mode, where the product changes the USB-C port's personality when both CC1 and CC2 are pulled high. In normal usage, either CC1 or CC2 will be floating since these are the connector rotation pins. When both are detected, there is a very good chance that a debug harness is connected. This decision requires the PineNote motherboard to be able to detect an AND condition between CC1 and CC2 and connect one of the SOC's UARTs to pins on the USB-C connector. In all other cases, the UART should be disconnected. It also requires the PINE64 Store ship a simple one-sided (no magical flipping here, sorry) connector board which breaks out USB 2.0 and UART. -IRC logs of this discussion can be found at link:/documentation/PineNote/Hardware_Changes/2021-08-15[PineNote/Hardware Changes/Closed Case UART/2021-08-15]. + +// IRC logs of this discussion can be found at link:/documentation/PineNote/Hardware_Changes/2021-08-15[PineNote/Hardware Changes/Closed Case UART/2021-08-15]. === August 16-18, 2021 diff --git a/content/documentation/PineNote/Further_information/Closed_Case_UART_2021-08-15.adoc b/content/documentation/PineNote/Further_information/Closed_Case_UART_2021-08-15.adoc index 1e269141..9d945cb7 100644 --- a/content/documentation/PineNote/Further_information/Closed_Case_UART_2021-08-15.adoc +++ b/content/documentation/PineNote/Further_information/Closed_Case_UART_2021-08-15.adoc @@ -9,7 +9,7 @@ menu: weight: 6 --- -For some relevant takeaways from this discussion, see link:/documentation/PineNote/Hardware_Changes/Closed_Case_UART#August_15,_2021[PineNote/Hardware Changes/Closed Case UART] +For some relevant takeaways from this discussion, see link:/documentation/PineNote/Further_information/Closed_Case_UART#August_15,_2021[PineNote/Hardware Changes/Closed Case UART] Times are in UTC-5 diff --git a/content/documentation/PinePhone/Accessory.adoc b/content/documentation/PinePhone/Accessory.adoc index d43e0d3f..1d17054d 100644 --- a/content/documentation/PinePhone/Accessory.adoc +++ b/content/documentation/PinePhone/Accessory.adoc @@ -16,9 +16,7 @@ The PinePhone (and PinePhone Pro) is compatible with the official add-on cases, * link:/documentation/Phone_Accessories/[Accessories] * link:/documentation/Phone_Accessories/Keyboard[Keyboard] -== PinePhone Accessories - -See link:/documentation/Phone_Accessories/Hardware_accessory_compatibility[Hardware accessory compatibility] for a list of devices working with the PinePhone (depending on their OS support). +== USB The USB-C can be used to power the device, and offers USB2 host and OTG capabilities, and also can make use of the USB-C capability to integrate HDMI signals. Some USB-C hubs are available that offer power throughput, USB connection, an HDMI port and Ethernet connection. diff --git a/content/documentation/PinePhone/Battery.adoc b/content/documentation/PinePhone/Battery.adoc index aedf09c1..b9880abd 100644 --- a/content/documentation/PinePhone/Battery.adoc +++ b/content/documentation/PinePhone/Battery.adoc @@ -9,7 +9,7 @@ menu: weight: --- -The phone ships with a protective plastic sticker between the battery and the phone to protect the device from turning on during shipping. You need to gently open the back cover, then remove the battery and finally remove the sticker and check that the pins aren't bent. Note: If the battery is stuck inside the phone, the mid screw in the lower part of the midframe needs to be slightly loosened, see link:/documentation/PinePhone/FAQ#The_battery_is_stuck_inside_the_phone[here]. +The phone ships with a protective plastic sticker between the battery and the phone to protect the device from turning on during shipping. You need to gently open the back cover, then remove the battery and finally remove the sticker and check that the pins aren't bent. Note: If the battery is stuck inside the phone, the mid screw in the lower part of the midframe needs to be slightly loosened, see link:/documentation/PinePhone/FAQ#the_battery_is_stuck_inside_the_phone[here]. NOTE: The EG25-G modem and the RTL8723CS WiFi and Bluetooth do not work without a battery and with a drained battery, even when enough power is supplied to the PinePhone via the USB Type-C port. Most operating systems won't boot without a battery or with a drained battery. diff --git a/content/documentation/PinePhone/FAQ.adoc b/content/documentation/PinePhone/FAQ.adoc index 3a16bccd..a91c0fab 100644 --- a/content/documentation/PinePhone/FAQ.adoc +++ b/content/documentation/PinePhone/FAQ.adoc @@ -175,7 +175,7 @@ There was a project by Danct12 which allowed the user to select different operat This can be the result of at least one situation: . The eMMC installation became corrupt or otherwise unbootable -. An SD card is present but not bootable (consider link:/documentation/PinePhone#detailed_usage_instructions[PinePhone]) +. An SD card is present but not bootable (consider link:/documentation/PinePhone/Troubleshooting[PinePhone Troubleshooting]) If there is an installation of Manjaro on both the eMMC & an SD card, the SD card will always boot first on the device. Try taking the SD card out and booting the installation that is on the eMMC. If the problem persists, it is likely there is an issue with both installations and you will need to reinstall your distribution. You may also want to check with your distribution's maintainers if boot issues are a common problem in a recent update. @@ -199,7 +199,7 @@ This is caused by corruption on the userdata partition. Normally this should be ==== The PinePhone does not boot -Most operating systems on the PinePhone do not boot if the battery is not connected or if it is fully drained. If you received a new PinePhone make sure to remove the battery isolator as explained under link:/documentation/PinePhone#first_time_installation[PinePhone]. +Most operating systems on the PinePhone do not boot if the battery is not connected or if it is fully drained. If you received a new PinePhone make sure to remove the battery isolator as explained under link:/documentation/PinePhone/Getting_started[PinePhone Getting started]. If you removed the battery isolator and the battery contacts are intact, the battery is either fully drained or there is no valid OS (or a corrupted OS or bootloader) installed on the eMMC or the SD card. Make sure to charge the phone with a compatible charger (500 mAh is not enough for modern phones), as well as the installation instruction under link:/documentation/PinePhone/Installation_instructions[Installation instructions]. If the OS got corrupted it is highly recommend to simply reflash. @@ -210,7 +210,7 @@ image:/documentation/images/Pinephone_backside.png[The microSD belongs in the up ==== Can I install a different OS on my Community Edition? -Yes|While all the Community Edition PinePhones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see link:/documentation/PinePhone/Installation_instructions[Installation instructions] and link:/documentation/PinePhone/Software/Operating_systems[Operating systems] on how to install them. +Yes|While all the Community Edition PinePhones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see link:/documentation/PinePhone/Installation_instructions[Installation instructions] and link:/documentation/PinePhone/Software/Releases[Operating systems] on how to install them. === Other @@ -324,9 +324,4 @@ Currently the PinePhone battery is known to be compatible with replacement batte ==== Will PINE64 sell other add-ons made for the PinePhone? -Yes, currently there is a keyboard case https://forum.pine64.org/showthread.php?tid=8537&pid=55396#pid55396[with similarities to the Psion 5] which includes an internal battery, and a https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/[Qi wireless charging] add-on planned, both of which PINE64 intends to directly sell. There is the potential for future add-ons such as a game pad, however that is currently just an idea and not in any way planned. - -==== Which 3rd party hardware can connect to my PinePhone? - -See link:/documentation/Phone_Accessories/Hardware_accessory_compatibility[Hardware accessory compatibility]. - +Yes, currently there is a keyboard case https://forum.pine64.org/showthread.php?tid=8537&pid=55396#pid55396[with similarities to the Psion 5] which includes an internal battery, and a https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/[Qi wireless charging] add-on planned, both of which PINE64 intends to directly sell. There is the potential for future add-ons such as a game pad, however that is currently just an idea and not in any way planned. \ No newline at end of file diff --git a/content/documentation/PinePhone/Further_information/Components.adoc b/content/documentation/PinePhone/Further_information/Components.adoc index 8dfb487e..60189b34 100644 --- a/content/documentation/PinePhone/Further_information/Components.adoc +++ b/content/documentation/PinePhone/Further_information/Components.adoc @@ -451,7 +451,7 @@ Source: https://forums.puri.sm/t/component-counts-in-the-librem-5-and-pinephone/ === Other components not in the schematics * SGMICRO http://www.sg-micro.com/uploads/soft/20190829/1567071622.pdf[SGM3140] 500mA buck/boost charge pump LED driver for camera flash and torch, TDFN-10 3x3x0.75 mm -* Note: The link:/documentation/PinePhone#Components[PinePhone page] lists the SGM3140, but the schematics contain the U1000: awinic AW3641EDNR, so it is unclear why the SGM3140 is needed. +* Note: The link:/documentation/PinePhone/Further_information/Components/[PinePhone page] lists the SGM3140, but the schematics contain the U1000: awinic AW3641EDNR, so it is unclear why the SGM3140 is needed. * Goodix http://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf[GT917S] touch controller * Sitronix http://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf[ST7703] MIPI LCD driver * Xingbangda https://lkml.org/lkml/2020/6/16/1654[XBD599] 5.99″ IPS LCD, 720x1440 pixels, 16.7M colors, hardened glass \ No newline at end of file diff --git a/content/documentation/PinePhone/Further_information/Datasheets.adoc b/content/documentation/PinePhone/Further_information/Datasheets.adoc index 2b2f5bd9..80f21ec7 100644 --- a/content/documentation/PinePhone/Further_information/Datasheets.adoc +++ b/content/documentation/PinePhone/Further_information/Datasheets.adoc @@ -76,5 +76,5 @@ Case information: Other components: -* See the link:/documentation/PinePhone/Further_information/Components_list[Component List] +* See the link:/documentation/PinePhone/Further_information/Components[Component List] diff --git a/content/documentation/PinePhone/Further_information/Press.adoc b/content/documentation/PinePhone/Further_information/Press.adoc index e3052bcf..6b0feaa0 100644 --- a/content/documentation/PinePhone/Further_information/Press.adoc +++ b/content/documentation/PinePhone/Further_information/Press.adoc @@ -14,7 +14,7 @@ Vector images and pictures of the link:/documentation/PinePhone[PinePhone] and l == PinePhone Pro image:/documentation/images/Pinephone_airplane.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_unbranded.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +image:/documentation/images/pinephone_unbranded.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] image:/documentation/images/Pinephone_table.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] image:/documentation/images/Pinephone_killswitches.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] image:/documentation/images/Pinephone_convergence.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] diff --git a/content/documentation/PinePhone/Further_information/Resources.adoc b/content/documentation/PinePhone/Further_information/Resources.adoc index d9ff2b76..126a15d7 100644 --- a/content/documentation/PinePhone/Further_information/Resources.adoc +++ b/content/documentation/PinePhone/Further_information/Resources.adoc @@ -9,13 +9,6 @@ menu: weight: --- -The following articles contain more specific information: - -* link:/documentation/PinePhone/Accessibility[Accessibility] -* link:/documentation/PinePhone/Software_tricks/Power_management[Power management] -* link:/documentation/PinePhone/Software_tricks/Security[Security] -* link:/documentation/PinePhone/Further_information/Ubuntu_Touch_design[Ubuntu Touch design] - The following resources have been made available by Ondřej Jirman, a developer for the Pinephone: * https://xnux.eu/howtos/pine64-pinephone-getting-started.html[Getting started with PinePhone Hardware] diff --git a/content/documentation/PinePhone/Further_information/Schematics_and_certifications.adoc b/content/documentation/PinePhone/Further_information/Schematics_and_certifications.adoc index 47be9a10..37ebf8c4 100644 --- a/content/documentation/PinePhone/Further_information/Schematics_and_certifications.adoc +++ b/content/documentation/PinePhone/Further_information/Schematics_and_certifications.adoc @@ -18,7 +18,7 @@ PinePhone mainboard schematic: * https://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf["Braveheart" PinePhone mainboard Schematic ver 1.1] * https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf["Braveheart" PinePhone mainboard component top placement drawing ver 1.1] * https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf["Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1] -* link:/documentation/PinePhone/Further_information/Components_list[Components list] +* link:/documentation/PinePhone/Further_information/Components[Components list] PinePhone USB-C small board schematic: diff --git a/content/documentation/PinePhone/Further_information/_index.adoc b/content/documentation/PinePhone/Further_information/_index.adoc index ff6a4e42..9fb46f76 100644 --- a/content/documentation/PinePhone/Further_information/_index.adoc +++ b/content/documentation/PinePhone/Further_information/_index.adoc @@ -9,14 +9,4 @@ menu: weight: --- -* link:External_links[External links] -* link:Resources[] -* link:Datasheets[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:Modifications_and_repairs[Modifications and repairs] -* link:Components[] -* link:Specifications[] -* link:Components_list[Components list] -* link:Ubuntu_Touch_design[Ubuntu Touch design] -* link:Sensors_and_navigation[Sensors and navigation] -* link:Press[] +{{< children >}} diff --git a/content/documentation/PinePhone/Hardware_fixes_and_mods/Hardware_issues.adoc b/content/documentation/PinePhone/Hardware_fixes_and_mods/Hardware_issues.adoc index 18d65650..56945d5a 100644 --- a/content/documentation/PinePhone/Hardware_fixes_and_mods/Hardware_issues.adoc +++ b/content/documentation/PinePhone/Hardware_fixes_and_mods/Hardware_issues.adoc @@ -40,8 +40,8 @@ Place new issues here. == See Also -* link:/documentation/PinePhone#Modifications_and_repairs[PinePhone] +* link:/documentation/PinePhone/Hardware_fixes_and_mods[PinePhone] * link:/documentation/PinePhone/Revisions/PinePhone_v1.2[PinePhone v1.2] -* link:/documentation/PinePhone/Revisions/PinePhone_v1.2a#Known_issues[PinePhone v1.2a] -* link:/documentation/PinePhone/Revisions/PinePhone_v1.2b#Known_issues[PinePhone v1.2b] +* link:/documentation/PinePhone/Revisions/PinePhone_v1.2a/#known_issues[PinePhone v1.2a] +* link:/documentation/PinePhone/Revisions/PinePhone_v1.2b/#known_issues[PinePhone v1.2b] diff --git a/content/documentation/PinePhone/Hardware_fixes_and_mods/Modifications_and_repairs.adoc b/content/documentation/PinePhone/Hardware_fixes_and_mods/Modifications_and_repairs.adoc index 75bf3274..7b35e67c 100644 --- a/content/documentation/PinePhone/Hardware_fixes_and_mods/Modifications_and_repairs.adoc +++ b/content/documentation/PinePhone/Hardware_fixes_and_mods/Modifications_and_repairs.adoc @@ -52,7 +52,7 @@ and executing as root ("sudo su") on the phone: ==== Method 2 -Booting a factory test image will automatically flash the ANX7688 chip. See link:/documentation/PinePhone/Software/Operating_systems#Factory_Test_OS[Factory Test OS] for such an image. +Booting a factory test image will automatically flash the ANX7688 chip. See link:/documentation/PinePhone/Software/Releases#Factory_Test_OS[Factory Test OS] for such an image. == Replacing the screen diff --git a/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.1_VBUS_power_usage_Hardware_Fix.adoc b/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.1_VBUS_power_usage_Hardware_Fix.adoc index 3e9ff674..14eaf595 100644 --- a/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.1_VBUS_power_usage_Hardware_Fix.adoc +++ b/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.1_VBUS_power_usage_Hardware_Fix.adoc @@ -10,7 +10,7 @@ menu: weight: --- -This page details a hardware fix for an issue that affects some early link:/documentation/PinePhone#Hardware_revisions[v1.1 Braveheart] units (fixed since link:/documentation/PinePhone/Revisions/PinePhone_v1.2[1.2 community edition] included). +This page details a hardware fix for an issue that affects some early link:/documentation/PinePhone/Revisions[v1.1 Braveheart] units (fixed since link:/documentation/PinePhone/Revisions/PinePhone_v1.2[1.2 community edition] included). The issue was _PinePhone_v1.1_-_Braveheart#Excess_power_usage_while_driving_VBUS_ by megi. diff --git a/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2_VCONN_Hardware_Fix.adoc b/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2_VCONN_Hardware_Fix.adoc index 1c767fa3..2160d667 100644 --- a/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2_VCONN_Hardware_Fix.adoc +++ b/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2_VCONN_Hardware_Fix.adoc @@ -10,7 +10,7 @@ menu: weight: --- -This page details a hardware fix for an issue that was found on early PinePhone hardware revisions (see link:/documentation/PinePhone#Hardware_revisions[PinePhone] for an overview of the different revisions) and has been fixed since the 1.2a hardware revision. +This page details a hardware fix for an issue that was found on early PinePhone hardware revisions (see link:/documentation/PinePhone/Revisions/[PinePhone] for an overview of the different revisions) and has been fixed since the 1.2a hardware revision. The issue was _PinePhone_v1.1_-_Braveheart#USB-C_CC_pins_are_pulled_to_the_GND_by_AW3512_.28VCONN_switches.29_when_VCONN_is_off_ by megi. diff --git a/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2b_R1318_backlight_Hardware_Fix.adoc b/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2b_R1318_backlight_Hardware_Fix.adoc index 7136fed6..3225c7d2 100644 --- a/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2b_R1318_backlight_Hardware_Fix.adoc +++ b/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2b_R1318_backlight_Hardware_Fix.adoc @@ -10,7 +10,7 @@ menu: weight: --- -This page details a hardware fix for an issue that was found on early link:/documentation/PinePhone[PinePhone] hardware revisions (see link:/documentation/PinePhone#Hardware_revisions[PinePhone] for an overview of the different revisions) and has been fixed since the 1.2b hardware revision. +This page details a hardware fix for an issue that was found on early link:/documentation/PinePhone[PinePhone] hardware revisions (see link:/documentation/PinePhone/Revisions/[PinePhone] for an overview of the different revisions) and has been fixed since the 1.2b hardware revision. == Affected Units diff --git a/content/documentation/PinePhone/Modem/Carrier_support.adoc b/content/documentation/PinePhone/Modem/Carrier_support.adoc index b611d808..765b668c 100644 --- a/content/documentation/PinePhone/Modem/Carrier_support.adoc +++ b/content/documentation/PinePhone/Modem/Carrier_support.adoc @@ -12,7 +12,7 @@ menu: {{% docs/construction %}} This page contains hints on setting up cellular network connectivity for specific carriers. -For more general information, see the carrier support section of link:/documentation/PinePhone#Modem[PinePhone]. For the APN settings see link:/documentation/PinePhone/Modem/APN_settings[APN settings]. +For more general information, see the carrier support section of link:/documentation/PinePhone/Modem[PinePhone]. For the APN settings see link:/documentation/PinePhone/Modem/APN_settings[APN settings]. == Check compatibility diff --git a/content/documentation/PinePhone/Modem/_index.adoc b/content/documentation/PinePhone/Modem/_index.adoc index aadc7785..4ac508bb 100644 --- a/content/documentation/PinePhone/Modem/_index.adoc +++ b/content/documentation/PinePhone/Modem/_index.adoc @@ -143,11 +143,11 @@ The modem will automatically reboot after the update process is done. The boot p == Firmware modifications -See link:/documentation/Unsorted/PineModems[PineModems] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery. +See link:/documentation/General/PineModems[PineModems] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery. == GPS / GNSS -The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem can be controlled via a separate set of AT commands, or via qmi. The A-GPS data upload uses the file management AT commands, which also have their own manual. These are linked in the link:/documentation/PinePhone#Datasheets_for_components_and_peripherals[documentation section] below. +The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem can be controlled via a separate set of AT commands, or via qmi. The A-GPS data upload uses the file management AT commands, which also have their own manual. These are linked in the link:/documentation/PinePhone/Further_information/Datasheets/[documentation section] below. As with most smartphones, the PinePhone has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. The _eg25-mananger_ is configured to upload A-GPS data by default (see https://gitlab.com/mobian1/eg25-manager/-/merge_requests/15[here]). diff --git a/content/documentation/PinePhone/Revisions/PinePhone_v1.0_-Dev.adoc b/content/documentation/PinePhone/Revisions/PinePhone_v1.0_-Dev.adoc index 5347baf0..b0695918 100644 --- a/content/documentation/PinePhone/Revisions/PinePhone_v1.0_-Dev.adoc +++ b/content/documentation/PinePhone/Revisions/PinePhone_v1.0_-Dev.adoc @@ -12,7 +12,7 @@ menu: The PinePhone v1.0 is the developer hardware revision of the link:/documentation/PinePhone[PinePhone]. -This page contains resources which are exclusive to the 1.0 revision of the PinePhone. For other revisions, or for resources related to all PinePhone revisions, see link:/documentation/PinePhone#Hardware_revisions[PinePhone]. +This page contains resources which are exclusive to the 1.0 revision of the PinePhone. For other revisions, or for resources related to all PinePhone revisions, see link:/documentation/PinePhone/Revisions/[PinePhone]. == Schematic diff --git a/content/documentation/PinePhone/Revisions/PinePhone_v1.1_-_Braveheart.adoc b/content/documentation/PinePhone/Revisions/PinePhone_v1.1_-_Braveheart.adoc index 501d9db5..76683e12 100644 --- a/content/documentation/PinePhone/Revisions/PinePhone_v1.1_-_Braveheart.adoc +++ b/content/documentation/PinePhone/Revisions/PinePhone_v1.1_-_Braveheart.adoc @@ -12,7 +12,7 @@ menu: The PinePhone v1.1 "Braveheart" is a hardware revision of the link:/documentation/PinePhone[PinePhone] that shipped in January 2020. -This page contains resources which are exclusive to the 1.1 revision of the PinePhone. For newer revisions or for resources related to other PinePhone revisions see link:/documentation/PinePhone#Hardware_revisions[PinePhone]. +This page contains resources which are exclusive to the 1.1 revision of the PinePhone. For newer revisions or for resources related to other PinePhone revisions see link:/documentation/PinePhone/Revisions/[PinePhone]. == Schematic diff --git a/content/documentation/PinePhone/Revisions/PinePhone_v1.2.adoc b/content/documentation/PinePhone/Revisions/PinePhone_v1.2.adoc index 8b550930..d202cdab 100644 --- a/content/documentation/PinePhone/Revisions/PinePhone_v1.2.adoc +++ b/content/documentation/PinePhone/Revisions/PinePhone_v1.2.adoc @@ -12,7 +12,7 @@ menu: The PinePhone v1.2 is a hardware revision of the link:/documentation/PinePhone[PinePhone] that was shipped in 2020 as UBports Community Edition. -This page contains information and resources which are specific to the UBports Community Edition (v1.2 PCB) revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see link:/documentation/PinePhone#Hardware_revisions[PinePhone]. +This page contains information and resources which are specific to the UBports Community Edition (v1.2 PCB) revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see link:/documentation/PinePhone/Revisions/[PinePhone]. == Schematics diff --git a/content/documentation/PinePhone/Revisions/PinePhone_v1.2a.adoc b/content/documentation/PinePhone/Revisions/PinePhone_v1.2a.adoc index 785cb082..0f3d2f4c 100644 --- a/content/documentation/PinePhone/Revisions/PinePhone_v1.2a.adoc +++ b/content/documentation/PinePhone/Revisions/PinePhone_v1.2a.adoc @@ -12,7 +12,7 @@ menu: The PinePhone v1.2a is a hardware revision of the link:/documentation/PinePhone[PinePhone] that started shipping in Q3 2020. -This page contains information and resources which are specific to the v1.2a revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see link:/documentation/PinePhone#Hardware_revisions[PinePhone]. +This page contains information and resources which are specific to the v1.2a revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see link:/documentation/PinePhone/Revisions[PinePhone]. == Schematics @@ -27,5 +27,5 @@ This page contains information and resources which are specific to the v1.2a rev == Known issues -The backlight issue of v1.2 is still present, see link:/documentation/PinePhone/Revisions/PinePhone_v1.2#Backlight[PinePhone v1.2]. There is also another backlight issue, where the brightness is lower when connecting a VBUS powered device, https://xnux.eu/log/#022. See link:/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2b_R1318_backlight_Hardware_Fix[PinePhone 1.2b R1318 backlight hardware fix]. +The backlight issue of v1.2 is still present, see link:/documentation/PinePhone/Revisions/PinePhone_v1.2#backlight[PinePhone v1.2]. There is also another backlight issue, where the brightness is lower when connecting a VBUS powered device, https://xnux.eu/log/#022. See link:/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2b_R1318_backlight_Hardware_Fix[PinePhone 1.2b R1318 backlight hardware fix]. diff --git a/content/documentation/PinePhone/Revisions/PinePhone_v1.2b.adoc b/content/documentation/PinePhone/Revisions/PinePhone_v1.2b.adoc index d894eaf6..5fd0f252 100644 --- a/content/documentation/PinePhone/Revisions/PinePhone_v1.2b.adoc +++ b/content/documentation/PinePhone/Revisions/PinePhone_v1.2b.adoc @@ -12,7 +12,7 @@ menu: The PinePhone v1.2b is a hardware revision of the link:/documentation/PinePhone[PinePhone] that started shipping in Q4 2020. -This page contains information and resources which are specific to the v1.2b revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see link:/documentation/PinePhone#Hardware_revisions[PinePhone]. +This page contains information and resources which are specific to the v1.2b revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see link:/documentation/PinePhone/Revisions/[PinePhone]. == Schematics diff --git a/content/documentation/PinePhone/Revisions/Project_Anakin.adoc b/content/documentation/PinePhone/Revisions/Project_Anakin.adoc index c23385a8..1ae53e22 100644 --- a/content/documentation/PinePhone/Revisions/Project_Anakin.adoc +++ b/content/documentation/PinePhone/Revisions/Project_Anakin.adoc @@ -50,9 +50,6 @@ Under link:/documentation/Accessories/Accessories_Step_by_Step_Guides['Guides fo * Based on Allwinner A64/R18 * R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor. -image:/documentation/images/Allwinner_A64.jpg[] -image:/documentation/images/Allwinner_R18.png[] - === CPU Architecture * https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php[Quad-core ARM Cortex-A53 Processor@1152Mhz] diff --git a/content/documentation/PinePhone/Revisions/Project_Dont_be_evil.adoc b/content/documentation/PinePhone/Revisions/Project_Dont_be_evil.adoc index 600d688f..f29c2198 100644 --- a/content/documentation/PinePhone/Revisions/Project_Dont_be_evil.adoc +++ b/content/documentation/PinePhone/Revisions/Project_Dont_be_evil.adoc @@ -53,9 +53,6 @@ Pin assignment: Based on the Allwinner A64/R18. The R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor. -image:/documentation/images/Allwinner_A64.jpg[] -image:/documentation/images/Allwinner_R18.png[] - === CPU Architecture * https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php[Quad-core ARM Cortex-A53 Processor@1152Mhz] diff --git a/content/documentation/PinePhone/Software/Crust.adoc b/content/documentation/PinePhone/Software/Crust.adoc index 4f0a226e..977bb78e 100644 --- a/content/documentation/PinePhone/Software/Crust.adoc +++ b/content/documentation/PinePhone/Software/Crust.adoc @@ -1,6 +1,7 @@ --- title: "Crust" -draft: true # NOT PUBLISHED +draft: false +hidden: true menu: docs: title: diff --git a/content/documentation/PinePhone/Software/Releases.adoc b/content/documentation/PinePhone/Software/Releases.adoc index ce71b649..b524cc39 100644 --- a/content/documentation/PinePhone/Software/Releases.adoc +++ b/content/documentation/PinePhone/Software/Releases.adoc @@ -48,7 +48,7 @@ Get both stable and test builds at https://github.com/dreemurrs-embedded/Pine64- === Fedora -image:/documentation/images/Fedora1.png[width=100] +image:/documentation/images/fedora1.png[width=100] An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/[some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution. @@ -620,7 +620,7 @@ There are software tools, that can be booted on the PinePhone. === JumpDrive -JumpDrive can be used to flash the eMMC (and the microSD card), see link:/documentation/PinePhone/Installation_instructions#Using_JumpDrive[Installation instructions]. +JumpDrive can be used to flash the eMMC (and the microSD card), see link:/documentation/PinePhone/Installation/Installation_to_the_eMMC/#using_jumpdrive[Installation instructions]. See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image. Make sure to download the "PinePhone" image and to unpack the archive before flashing. diff --git a/content/documentation/PinePhone_Pro/Factory_tests/_index.adoc b/content/documentation/PinePhone_Pro/Factory_tests/_index.adoc index d9970d15..d84b3efa 100644 --- a/content/documentation/PinePhone_Pro/Factory_tests/_index.adoc +++ b/content/documentation/PinePhone_Pro/Factory_tests/_index.adoc @@ -9,5 +9,4 @@ menu: weight: 96 --- -* link:Factory_test_battery_charging[Factory test battery charging] -* link:Factory_test_hardware_checking[Factory test hardware checking] +{{< children >}} diff --git a/content/documentation/PinePhone_Pro/Modem.adoc b/content/documentation/PinePhone_Pro/Modem.adoc index 7047d921..2d80e14d 100644 --- a/content/documentation/PinePhone_Pro/Modem.adoc +++ b/content/documentation/PinePhone_Pro/Modem.adoc @@ -136,7 +136,7 @@ The modem will automatically reboot after the update process is done. The boot p == Firmware modifications -See link:/documentation/PineModems[PineModems] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery. +See link:/documentation/General/PineModems[PineModems] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery. == GPS / GNSS diff --git a/content/documentation/PinePhone_Pro/Software/Installation_instructions.adoc b/content/documentation/PinePhone_Pro/Software/Installation_instructions.adoc index b2a3be3c..2e086839 100644 --- a/content/documentation/PinePhone_Pro/Software/Installation_instructions.adoc +++ b/content/documentation/PinePhone_Pro/Software/Installation_instructions.adoc @@ -48,7 +48,7 @@ The eMMC can be overwritten by booting an image from the microSD card and overwr This installation method is *recommended*. -. Boot an operating system link:/documentation/PinePhone_Pro#Flashing_to_microSD_card[from the microSD card]. If there is already a bootloader on the eMMC installed see the section link:/documentation/PinePhone_Pro#Boot_order[Boot order] to bypass it. +. Boot an operating system link:/documentation/PinePhone_Pro/Software/Installation/Installation_to_the_microSD_card/[from the microSD card]. If there is already a bootloader on the eMMC installed see the section link:/documentation/PinePhone_Pro/Software/Boot_order/[Boot order] to bypass it. . Download or copy the desired image to the microSD card as file . Check if the eMMC appears under `lsblk`. If it doesn't appear in the output of the command, the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot . *Important:* Typically the image will be compressed in an archive file to reduce the download size (such as _.gz_ or _.xz_). Extract the image from its archive file to get the file with the file extension _.img_. diff --git a/content/documentation/PinePhone_Pro/Software/Software_state.adoc b/content/documentation/PinePhone_Pro/Software/Software_state.adoc index 47bd637f..b3146b28 100644 --- a/content/documentation/PinePhone_Pro/Software/Software_state.adoc +++ b/content/documentation/PinePhone_Pro/Software/Software_state.adoc @@ -20,7 +20,7 @@ The following table lists the feature functionality status of the unaltered pre- * Matrix: https://app.element.io/#/room/#pinephone:matrix.org * Telegram: https://t.me/pinephone -TIP: The software is *written by the community*, any contributions towards the community projects are greatly appreciated! Please see "link:/documentation/General/How_to_contribute[How to Contribute]" to learn about how to contribute to the software projects and "link:/documentation/General/Where_to_report_bugs[Where to Report Bugs]" to learn about where to report bugs. +TIP: The software is *written by the community*, any contributions towards the community projects are greatly appreciated! Please see "link:/documentation/Introduction/How_to_contribute[How to Contribute]" to learn about how to contribute to the software projects and "link:/documentation/Introduction/Where_to_report_bugs[Where to Report Bugs]" to learn about where to report bugs. [cols="2,2,1,1,4"] |=== @@ -106,7 +106,7 @@ TIP: The software is *written by the community*, any contributions towards the c | `GNSS/GPS` 2+| WIP -| aGPS to be implemented^link:/documentation/PinePhone#GPS_/_GNSS[See original PinePhone article]^; long loading times to get a GPS fix^[Citation]^; No preinstalled application^[Citation]^ +| aGPS to be implemented^link:/documentation/PinePhone/Modem/#gps_gnss[See original PinePhone article]^; long loading times to get a GPS fix^[Citation]^; No preinstalled application^[Citation]^ | `Sensors` 2+| WIP diff --git a/content/documentation/PinePower/Versions/_index.adoc b/content/documentation/PinePower/Versions/_index.adoc index e73596c4..a6da17c6 100644 --- a/content/documentation/PinePower/Versions/_index.adoc +++ b/content/documentation/PinePower/Versions/_index.adoc @@ -9,5 +9,4 @@ menu: weight: --- -* link:120W_Desktop_Power_Supply[120W Desktop Power Supply] -* link:65W_GaN_Charger[65W GaN Charger] +{{< children >}} diff --git a/content/documentation/PineTab-V/Further_information/_index.adoc b/content/documentation/PineTab-V/Further_information/_index.adoc index 9984b19d..edd71ea5 100644 --- a/content/documentation/PineTab-V/Further_information/_index.adoc +++ b/content/documentation/PineTab-V/Further_information/_index.adoc @@ -9,5 +9,4 @@ menu: weight: 99 --- -* link:Certifications[] -* link:Schematics[] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/PineTab-V/Software/_index.adoc b/content/documentation/PineTab-V/Software/_index.adoc index 710062d4..48c6ae6a 100644 --- a/content/documentation/PineTab-V/Software/_index.adoc +++ b/content/documentation/PineTab-V/Software/_index.adoc @@ -9,5 +9,4 @@ menu: weight: 3 --- -* link:Software_state[Software state] -* link:Releases[] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/PineTab/Further_information/_index.adoc b/content/documentation/PineTab/Further_information/_index.adoc index 5a86906d..68f907b5 100644 --- a/content/documentation/PineTab/Further_information/_index.adoc +++ b/content/documentation/PineTab/Further_information/_index.adoc @@ -9,7 +9,4 @@ menu: weight: --- -* link:External_Links[External Links] -* link:Datasheets[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:Specifications[] +{{< children >}} diff --git a/content/documentation/PineTab2/Further_information/_index.adoc b/content/documentation/PineTab2/Further_information/_index.adoc index eabc716a..b448c1b3 100644 --- a/content/documentation/PineTab2/Further_information/_index.adoc +++ b/content/documentation/PineTab2/Further_information/_index.adoc @@ -9,10 +9,4 @@ menu: weight: --- -image:/documentation/PineTab2/images/PPineTab2-pcb.jpg[PineTab2 Board,title="PineTab2 Board",width=450] - -* link:Certifications[] -* link:Datasheets[] -* link:Disassembly_guide[Disassembly guide] -* link:Schematics[] -* link:Specifications[] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/PineTab2/Software/Installation_instructions.adoc b/content/documentation/PineTab2/Software/Installation_instructions.adoc index 65ac1177..c7ba5701 100644 --- a/content/documentation/PineTab2/Software/Installation_instructions.adoc +++ b/content/documentation/PineTab2/Software/Installation_instructions.adoc @@ -37,7 +37,7 @@ Then insert the microSD card into the PineTab2. [NOTE] ==== -image:/documentation/PineTab2/PineTab2_USB_UARTv2.jpg[The UART adapter,title="The UART adapter",width=450] +image:/documentation/PineTab2/images/PineTab2_USB_UARTv2.jpg[The UART adapter,title="The UART adapter",width=450] Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image. ==== diff --git a/content/documentation/PineTab2/Software/_index.adoc b/content/documentation/PineTab2/Software/_index.adoc index d346265e..d606fe39 100644 --- a/content/documentation/PineTab2/Software/_index.adoc +++ b/content/documentation/PineTab2/Software/_index.adoc @@ -9,6 +9,4 @@ menu: weight: 2 --- -* link:Installation_instructions[Installation instructions] -* link:Releases[Releases] -* link:Tutorials_and_FAQ[Tutorials and FAQ] +{{< children >}} diff --git a/content/documentation/PineTime/Development/Compatibility.adoc b/content/documentation/PineTime/Development/Compatibility.adoc index 2f0cfd41..207cc2db 100644 --- a/content/documentation/PineTime/Development/Compatibility.adoc +++ b/content/documentation/PineTime/Development/Compatibility.adoc @@ -17,4 +17,4 @@ To keep track of what, how and why things work like they do across the different == Compatibility with companions apps and Bluetooth communication -There are a lot of different firmware running on the Pinetime that implement different BLE APIs (for example for time synchronization and notifications). Companion apps must be able to differentiate between different firmware and forks of the same firmware. See link:/documentation/PineTime/Bluetooth[Bluetooth]. +There are a lot of different firmware running on the Pinetime that implement different BLE APIs (for example for time synchronization and notifications). Companion apps must be able to differentiate between different firmware and forks of the same firmware. See link:/documentation/PineTime/Software/Bluetooth[Bluetooth]. diff --git a/content/documentation/PineTime/FAQ.adoc b/content/documentation/PineTime/FAQ.adoc index 6df59f25..540fb3a5 100644 --- a/content/documentation/PineTime/FAQ.adoc +++ b/content/documentation/PineTime/FAQ.adoc @@ -34,7 +34,7 @@ If you have a Sealed PineTime, flash only tested PineTime Firmware to your PineT There is a lot of different software for flashing. Check out link:/documentation/PineTime/Development[Development] page for a list of companion software. -Also see link:/documentation/PineTime/Reprogramming[this page to see various methods of reprogramming the devkit PineTime the wired way]. +Also see link:/documentation/PineTime/Software/Reprogramming/[this page to see various methods of reprogramming the devkit PineTime the wired way]. Remember to validate the firmware after flashing: Swipe up to show the menu, tap the checkmark icon, tap "Validate". @@ -62,7 +62,7 @@ The back cover of the PineTime devkit is exposed so that you can flash and debug == What hardware should I use to flash code to the PineTime? -There are several ways you can do this, check out link:/documentation/PineTime/Reprogramming[Reprogramming the PineTime] +There are several ways you can do this, check out link:/documentation/PineTime/Software/Reprogramming/[Reprogramming the PineTime] == How do I connect the PineTime to a programmer? @@ -158,7 +158,7 @@ Please use https://xpack.github.io/openocd[xPack OpenOCD] with PineTime. Other v PineTime watches shipped before 20 Sep 2020 have flash protection enabled. -The flash protection can be removed using multiple different methods. If you don't have anything except the PineTime, not even a Raspberry Pi, then you have to order a programmer online: you can use a J-Link, CMSIS-DAP dongle and various other programmers. See link:/documentation/PineTime/Reprogramming[this page to see various methods of reprogramming the PineTime]. +The flash protection can be removed using multiple different methods. If you don't have anything except the PineTime, not even a Raspberry Pi, then you have to order a programmer online: you can use a J-Link, CMSIS-DAP dongle and various other programmers. See link:/documentation/PineTime/Software/Reprogramming/[this page to see various methods of reprogramming the PineTime]. If your PineTime was shipped after 20 Sep 2020, you don't need to remove flash protection. They are shipped with flash protection disabled. You can flash and debug PineTime right away with ST-Link, JLink and Raspberry Pi. diff --git a/content/documentation/PineTime/Further_information/Devkit_wiring.adoc b/content/documentation/PineTime/Further_information/Devkit_wiring.adoc index 18bed6bc..ee6e0db7 100644 --- a/content/documentation/PineTime/Further_information/Devkit_wiring.adoc +++ b/content/documentation/PineTime/Further_information/Devkit_wiring.adoc @@ -49,9 +49,9 @@ To connect PineTime Pogo Pins to PineTime's SWD Port: . To orientate the pins, stick a piece of *Sticky Tape* to the Pogo Pins as shown above. The Sticky Tape should point *away from PineTime's Battery*. Orientation is important. You may damage PineTime with the incorrect orientation! . With the Battery at left and Sticky Tape pointing right, the SWD Pins will be arranged left to right as: *SWDIO, SWDCLK, 3.3V, GND* -. Connect the other end of the Pogo Pins to the Jumper Cable that's bundled with PineTime. Connect the Jumper Cable to ST-Link v2 or JLink: SWDIO, SWDCLK, 3.3V, GND. See link:/documentation/PineTime/Reprogramming[Reprogramming the PineTime] +. Connect the other end of the Pogo Pins to the Jumper Cable that's bundled with PineTime. Connect the Jumper Cable to ST-Link v2 or JLink: SWDIO, SWDCLK, 3.3V, GND. See link:/documentation/PineTime/Software/Reprogramming/[Reprogramming the PineTime] . With the *Sticky Tape pointing right* (away from the Battery), tap and hold the Pogo Pins firmly on PineTime's SWD Port. *But not too hard* because the PCB or screen may break. Stabilise the Pogo Pins with your pinky finger as shown above. -. PineTime should light up and reboot when the Pogo Pins are connected. You may flash and debug PineTime now. See link:/documentation/PineTime/Reprogramming[Reprogramming the PineTime] +. PineTime should light up and reboot when the Pogo Pins are connected. You may flash and debug PineTime now. See link:/documentation/PineTime/Software/Reprogramming/[Reprogramming the PineTime] The tips of the Pogo Pins will partially penetrate the SWD holes like this. Don't force them in! diff --git a/content/documentation/PineTime/Further_information/Specifications.adoc b/content/documentation/PineTime/Further_information/Specifications.adoc index 8acf7fe8..62505eb9 100644 --- a/content/documentation/PineTime/Further_information/Specifications.adoc +++ b/content/documentation/PineTime/Further_information/Specifications.adoc @@ -20,7 +20,7 @@ menu: * *System on Chip:* Nordic Semiconductor nRF52832 * *Flash:* 512KB with additional 4MB SPI NOR * *RAM:* 64KB -* *Bluetooth:* link:/documentation/PineTime/Bluetooth[5.0 (including Bluetooth Low Energy)] +* *Bluetooth:* link:/documentation/PineTime/Software/Bluetooth[5.0 (including Bluetooth Low Energy)] * *Sensors:* Accelerometer, Heart rate sensor * *Feedback:* Vibration motor * *Battery:* 170-180mAh 3.8V LiPo diff --git a/content/documentation/PineTime/Getting_started.adoc b/content/documentation/PineTime/Getting_started.adoc index e0e59f19..aca23ed1 100644 --- a/content/documentation/PineTime/Getting_started.adoc +++ b/content/documentation/PineTime/Getting_started.adoc @@ -13,8 +13,8 @@ Read these first: * link:/documentation/PineTime/Software/Upgrade_to_InfiniTime_1_0_0[Upgrading your new PineTime to InfiniTime 1.0.0] * link:/documentation/PineTime/Further_information/Devkit_wiring[Devkit wiring] -* link:/documentation/PineTime/Reprogramming[Reprogramming the PineTime (development kit)] -* link:/documentation/PineTime/Switching_between_InfiniTime_and_Wasp-os[Switching your PineTime between InfiniTime and Wasp-os] +* link:/documentation/PineTime/Software/Reprogramming/[Reprogramming the PineTime (development kit)] +* link:/documentation/PineTime/Software/Switching_between_InfiniTime_and_Wasp-os[Switching your PineTime between InfiniTime and Wasp-os] The frequently asked question can be found in the article link:/documentation/PineTime/FAQ[FAQ]. diff --git a/content/documentation/PineTime/Watchfaces/Custom_watchface.adoc b/content/documentation/PineTime/Watchfaces/Custom_watchface.adoc index 148aeec6..7c960b23 100644 --- a/content/documentation/PineTime/Watchfaces/Custom_watchface.adoc +++ b/content/documentation/PineTime/Watchfaces/Custom_watchface.adoc @@ -670,7 +670,7 @@ Information about how to compile the firmware is included on the https://github. ==== Installing the new firmware -A holistic guide on how to install different firmware using various hardware programmers is available here: link:/documentation/PineTime/Reprogramming[Reprogramming the PineTime]. +A holistic guide on how to install different firmware using various hardware programmers is available here: link:/documentation/PineTime/Software/Reprogramming/[Reprogramming the PineTime]. If you would like to install the firmware by OTA/DFU, you can follow these steps: diff --git a/content/documentation/Pine_A64-LTS/Further_information/_index.adoc b/content/documentation/Pine_A64-LTS/Further_information/_index.adoc index f0b1a7ca..71a9b4f4 100644 --- a/content/documentation/Pine_A64-LTS/Further_information/_index.adoc +++ b/content/documentation/Pine_A64-LTS/Further_information/_index.adoc @@ -9,8 +9,4 @@ menu: weight: --- -* link:Pine_A64_POT[Pine A64 POT] -* link:Other_resources[Other resources] -* link:Datasheets[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:SoC_and_Memory_Specification[SoC and Memory Specification] +{{< children >}} diff --git a/content/documentation/Pine_A64/Further_information/SoC_and_Memory_Specification.adoc b/content/documentation/Pine_A64/Further_information/SoC_and_Memory_Specification.adoc index 653eb509..dd58b2e0 100644 --- a/content/documentation/Pine_A64/Further_information/SoC_and_Memory_Specification.adoc +++ b/content/documentation/Pine_A64/Further_information/SoC_and_Memory_Specification.adoc @@ -9,9 +9,7 @@ menu: weight: --- -* Based on Allwinner A64 - -image:/documentation/images/Allwinner_A64.jpg[right,title="right"] +The Pine A64 is based on the _Allwinner A64_. == CPU Architecture diff --git a/content/documentation/Pine_A64/Further_information/_index.adoc b/content/documentation/Pine_A64/Further_information/_index.adoc index ef5e045c..317a0f2c 100644 --- a/content/documentation/Pine_A64/Further_information/_index.adoc +++ b/content/documentation/Pine_A64/Further_information/_index.adoc @@ -9,9 +9,4 @@ menu: weight: --- -* link:Other_resources[Other resources] -* link:Pine_A64_POT[Pine A64 POT] -* link:Heat_sinks[Heat sinks] -* link:Datasheets[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:SoC_and_Memory_Specification[SoC and Memory Specification] +{{< children >}} \ No newline at end of file diff --git a/content/documentation/Pine_A64/Software.adoc b/content/documentation/Pine_A64/Software.adoc index fb842501..e37b400f 100644 --- a/content/documentation/Pine_A64/Software.adoc +++ b/content/documentation/Pine_A64/Software.adoc @@ -73,7 +73,7 @@ Instructions: ** For Mac: `gzcat firmware.pine64_plus.img.gz partition.img.gz > complete_image.img` * Write the image to your boot device: ** For Linux: `dd if=complete_image.img of=your_chosen_boot_device bs=4M` -** For Mac: see link:/documentation/General/Getting_started[Getting started] +** For Mac: see link:/documentation/Introduction/Getting_started[Getting started] Notes: @@ -180,7 +180,7 @@ Notes: === openSUSE -image:/documentation/images/Opensuse-distribution.png[width=100] +image:/documentation/images/opensuse-distribution.png[width=100] *openSUSE* is a free and open source RPM-based Linux distribution developed by the openSUSE project. More details can be found under https://en.opensuse.org/HCL:Pine64. diff --git a/content/documentation/Pinebook/Further_information/_index.adoc b/content/documentation/Pinebook/Further_information/_index.adoc index 340ddea2..9e1bcb75 100644 --- a/content/documentation/Pinebook/Further_information/_index.adoc +++ b/content/documentation/Pinebook/Further_information/_index.adoc @@ -9,7 +9,4 @@ menu: weight: 6 --- -* link:Specifications[] -* link:Datasheets[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:Other_resources[Other resources] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/Pinebook_Pro/Accessory/Compatibility.adoc b/content/documentation/Pinebook_Pro/Accessory/Compatibility.adoc index dd1822d5..c7d6fd94 100644 --- a/content/documentation/Pinebook_Pro/Accessory/Compatibility.adoc +++ b/content/documentation/Pinebook_Pro/Accessory/Compatibility.adoc @@ -1,6 +1,6 @@ --- title: "Hardware Accessory Compatibility" -draft: true # NOT PUBLISHED +draft: false menu: docs: title: @@ -216,7 +216,7 @@ Please see link:/documentation/Pinebook_Pro/Troubleshooting#NVMe_SSD_issues[a se | 2280 | WD PC SN530 | 256GB | SDBPNPZ-256G-1002 | good | Works on AC power with defaults settings, but causes kernel panics on battery, unlesss limited to PS 1 that fixes this. a| * APSTE enabled by default + * PS 0: 3.5W + * PS 1: 2.4W + -* PS 2: 1.9W | No. Fixed by systemd script, see link:/documentation/Pinebook_Pro/Using-the-optional-NVMe-adapter/[Post NVMe install power limiting]. +* PS 2: 1.9W | No. Fixed by systemd script, see link:/documentation/Pinebook_Pro/Guides/Using-the-optional-NVMe-adapter/[Post NVMe install power limiting]. | 2280 | WD PC SN730 | 512GB | SDBPNTY-512G-1032 | good | No touchpad issues. Works after latest updates. a| * APST enabled by default + * PS 0: 5.50W + diff --git a/content/documentation/Pinebook_Pro/Accessory/_index.adoc b/content/documentation/Pinebook_Pro/Accessory/_index.adoc index c49f06f5..596cc94c 100644 --- a/content/documentation/Pinebook_Pro/Accessory/_index.adoc +++ b/content/documentation/Pinebook_Pro/Accessory/_index.adoc @@ -9,4 +9,4 @@ menu: weight: --- -* link:Compatibility[] +{{< children >}} diff --git a/content/documentation/Pinebook_Pro/Further_information/Specifications.adoc b/content/documentation/Pinebook_Pro/Further_information/Specifications.adoc index c3e2a9df..13f32528 100644 --- a/content/documentation/Pinebook_Pro/Further_information/Specifications.adoc +++ b/content/documentation/Pinebook_Pro/Further_information/Specifications.adoc @@ -79,7 +79,7 @@ Storage Memory: SPI flash: -* link:/documentation/Pinebook_Pro/SPI[SPI] +* link:/documentation/Pinebook_Pro/Features/SPI[SPI] * 128Mbit / 16MByte * 1 bit interface * Bootable, (first boot device, ahead of eMMC & SD card) diff --git a/content/documentation/Pinebook_Pro/Guides/Using the optional NVMe adapter.adoc b/content/documentation/Pinebook_Pro/Guides/Using the optional NVMe adapter.adoc index 2a33d5f2..2b19210d 100644 --- a/content/documentation/Pinebook_Pro/Guides/Using the optional NVMe adapter.adoc +++ b/content/documentation/Pinebook_Pro/Guides/Using the optional NVMe adapter.adoc @@ -86,7 +86,7 @@ As long as the kernel in use has both the PCIe and NVMe drivers, you should be a == Using as OS root drive -The SoC does not include the NVMe boot code, so the NVMe is not in the SoC's boot order. However, using the https://github.com/mrfixit2001/updates_repo/blob/v1.1/pinebook/filesystem/mrfixit_update.sh[U-Boot update script] from the mrfixit2001 Debian or https://pastebin.com/raw/EeK074XB[Arglebargle's modified script], and https://github.com/pcm720/rockchip-u-boot/releases[the modified u-boot images] provided by forum user pcm720, you can now add support to boot from an NVMe drive. Binary images are useable with SD, eMMC, and link:/documentation/Pinebook_Pro/SPI[SPI flash]. For OS images using the mainline kernel, there are a few variants of U-Boot available that also support NVMe as the OS drive. Though these may require writing the U-Boot to the SPI flash for proper use of the NVMe as the OS drive. +The SoC does not include the NVMe boot code, so the NVMe is not in the SoC's boot order. However, using the https://github.com/mrfixit2001/updates_repo/blob/v1.1/pinebook/filesystem/mrfixit_update.sh[U-Boot update script] from the mrfixit2001 Debian or https://pastebin.com/raw/EeK074XB[Arglebargle's modified script], and https://github.com/pcm720/rockchip-u-boot/releases[the modified u-boot images] provided by forum user pcm720, you can now add support to boot from an NVMe drive. Binary images are useable with SD, eMMC, and link:/documentation/Pinebook_Pro/Features/SPI[SPI flash]. For OS images using the mainline kernel, there are a few variants of U-Boot available that also support NVMe as the OS drive. Though these may require writing the U-Boot to the SPI flash for proper use of the NVMe as the OS drive. The current boot order, per last testing, for this modified U-Boot is: diff --git a/content/documentation/Pinebook_Pro/Guides/Using_the_SPI_flash_device.adoc b/content/documentation/Pinebook_Pro/Guides/Using_the_SPI_flash_device.adoc index 2bd53b84..4c3d18c0 100644 --- a/content/documentation/Pinebook_Pro/Guides/Using_the_SPI_flash_device.adoc +++ b/content/documentation/Pinebook_Pro/Guides/Using_the_SPI_flash_device.adoc @@ -11,7 +11,7 @@ menu: WARNING: When removing the large RF shield found on the mainboard, to be able to short the pins on the SPI chip, make absolutely sure to align it correctly while putting it back. Failing to do so can result in shorting the battery to the ground, due to the close proximity of the solder pads for the bypass cables, which would prevent the normal operation and effectively cause a fire hazard. It is highly recommended to disconnect the battery before removing the RF shield, and before putting it back. -See link:/documentation/Pinebook_Pro/SPI[SPI] for details. +See link:/documentation/Pinebook_Pro/Features/SPI[SPI] for details. The Pinebook Pro comes with a 128Mbit, (16MByte), flash device suitable for initial boot target, to store the bootloader. The SoC used on the Pinebook Pro boots from this SPI flash device first, before eMMC or SD card. At present, April 19, 2020, the Pinebook Pros ship without anything programmed in the SPI flash device. So the SoC moves on to the next potential boot device, the eMMC. ARM/ARM64 computers do not have a standardized BIOS, yet. diff --git a/content/documentation/Pinebook_Pro/Keyboard/_index.adoc b/content/documentation/Pinebook_Pro/Keyboard/_index.adoc index bf2173d3..d1b0f1b5 100644 --- a/content/documentation/Pinebook_Pro/Keyboard/_index.adoc +++ b/content/documentation/Pinebook_Pro/Keyboard/_index.adoc @@ -15,7 +15,7 @@ The keyboard firmware binary can be flashed from userspace using the provided op WARNING: DO NOT update the keyboard firmware before checking which keyboard IC your Pinebook Pro has. Some Pinebook Pro were delivered with a _SH61F83_ instead of a _SH68F83_. The SH61F83 can only be written 8 times, this will render the keyboard and touchpad unusable if this limit is reached when step 1 is flashed, see the https://reddit.com/r/PINE64official/comments/loq4db/very_disappointed/[Reddit SH61F83 thread]. The keyboard IC corresponds to _U23_ on the link:#Pinebook_Pro_Schematics_and_Certifications[top layer silkscreen of the main board]. It is located under the keyboard flat flexible cable. -Documentation for the keyboard can be found in link:#Datasheets_for_Components_and_Peripherals[Datasheets for Components and Peripherals] and details regarding the assembly can be found under link:/documentation/Pinebook_Pro/Keyboard_assembly[Keyboard assembly]. +Documentation for the keyboard can be found in link:#Datasheets_for_Components_and_Peripherals[Datasheets for Components and Peripherals] and details regarding the assembly can be found under link:/documentation/Pinebook_Pro/Keyboard/Assembly[Keyboard assembly]. == Typing special characters @@ -23,59 +23,56 @@ The UK ISO Layout does not have dedicated keys for characters like the German um [cols="1,1"] |=== -|Character -|Key combination/sequence +|Character|Key combination/sequence |Ä, Ö, Ü, ä, ö, ü -|[AltGr]+'[' followed by [A], [O], [U], [a], [o] or [u] +|`AltGr` + `[` followed by `A`, `O`, `U`, `a`, `o` or `u` |µ -|[AltGr]+[m] +|`AltGr` + `m` |Ø, ø -|[AltGr]+[O], [AltGr]+[o] +|`AltGr` + `O`, `AltGr` + `o` |@ -|[AltGr]+[q] (as on the German layout) +|`AltGr` + `q` (as on the German layout) |ß -|[AltGr]+[s] +|`AltGr` + `s` |§ -|[AltGr]+[S] +|`AltGr` + `S` |° -|[AltGr]+[)] +|`AltGr` + `)` |=== == Privacy Switches There are three privacy switches mapped to the F10, F11 and F12 keys on the Pinebook Pro keyboard. They de/activate the following: -[cols="1,1,1,1,1"] +.Privacy switch function and description +[cols="1,1,1,1"] |=== -|+ Privacy switch function and description -|Combination -|Effect -|Description -|Notes +|Combination|Effect|Description|Notes -|scope=row | PINE64 logo key+F10 +| PINE64 logo key+F10 | Microphone Privacy switch | CAPs lock LED blinks. 2 blinks = enabled, 3 blinks = disabled +| -|scope=row | PINE64 logo key+F11 +| PINE64 logo key+F11 | WiFi Privacy switch | NUM lock LED blinks. 2 blinks = WiFi enabled / privacy switch disabled, 3 blinks = WiFi disabled / privacy switch enabled. -| Re-enabling requires reboot (or a [//forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645 command line hack to bind/unbind]). +| Re-enabling requires reboot (or a link:https://forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645[command line hack to bind/unbind]). -|scope=row | PINE64 logo key+F12 +| PINE64 logo key+F12 | Camera privacy switch | CAPs lock and NUM lock LEDs blink together. 2 blinks = enabled, 3 blinks = disabled | Can use tools like `lsusb` to detect camera's presence. If not detected, check privacy switch. |=== -(Press the PINE64 logo key plus F10/F11/F12) for 3 seconds) +NOTE: Press the PINE64 logo key plus F10/F11/F12 for 3 seconds The keyboard operates on firmware independent of the operating system. It detects if one of the F10, F11 or F12 keys is pressed in combination with the Pine key for 3 seconds. Doing so disables power to the appropriate peripheral, thereby disabling it. This has the same effect as cutting off the power to each peripheral with a physical switch. This implementation is very secure, since the firmware that determines whether a peripheral gets power is not part of the Pinebook Pro’s operating system. So the power state value for each peripheral cannot be overridden or accessed from the operating system. The power state setting for each peripheral is stored across reboots inside the keyboard's firmware flash memory. diff --git a/content/documentation/Pinebook_Pro/Power_and_charging.adoc b/content/documentation/Pinebook_Pro/Power_and_charging.adoc index 7c20dfba..9afd2686 100644 --- a/content/documentation/Pinebook_Pro/Power_and_charging.adoc +++ b/content/documentation/Pinebook_Pro/Power_and_charging.adoc @@ -44,7 +44,7 @@ With the external chargers disconnected the system is powered by the battery, so === Overview -image:/documentation/Pinebook_Pro/images/pbp-charging-simplified.png[title="Pinebook Pro simplified charging schematics",width=300] +image:/documentation/Pinebook_Pro/images/Pbp-charging-simplified.png[title="Pinebook Pro simplified charging schematics",width=300] When an external charger is connected, the battery charging process is automatically activated, it doesn't depend on any software interactions and works all the same even with the main SoC powered down. The system automatically chooses between the barrel socket (limiting current draw to 3 A) and Type-C source (limited to 2.5 A), with the former preferred when both are connected at the same time (but the current limit is enforced as if Type-C was used). diff --git a/content/documentation/Pinebook_Pro/Software/Releases.adoc b/content/documentation/Pinebook_Pro/Software/Releases.adoc index e05be316..e0995317 100644 --- a/content/documentation/Pinebook_Pro/Software/Releases.adoc +++ b/content/documentation/Pinebook_Pro/Software/Releases.adoc @@ -13,7 +13,7 @@ This page contains a list of all available releases and tools for the link:/docu == Linux OS Image Releases -For information on how to install these images onto your device, please see the link:/documentation/General/Getting_started[Getting started] Page, which includes information on writing images to the device eMMC or an SD card +For information on how to install these images onto your device, please see the link:/documentation/Introduction/Getting_started[Getting started] Page, which includes information on writing images to the device eMMC or an SD card === Manjaro ARM diff --git a/content/documentation/Pinebook_Pro/Troubleshooting.adoc b/content/documentation/Pinebook_Pro/Troubleshooting.adoc index 83cea69c..be4e80b0 100644 --- a/content/documentation/Pinebook_Pro/Troubleshooting.adoc +++ b/content/documentation/Pinebook_Pro/Troubleshooting.adoc @@ -22,9 +22,9 @@ If you have an old Manjaro installation then it will have the wrong repositories === New from the factory - Pinebook Pro won't boot / power on * Some Pinebook Pros came from the factory with the eMMC switch in the disabled position. It should be switched towards the back / hinge to enable the eMMC. -* The eMMC may have come loose during shipment. link:/documentation/Pinebook_Pro#Accessing_the_Internals_-_Disassembly_and_Reassembly[Open the back] and verify that the eMMC is firmly seated. +* The eMMC may have come loose during shipment. link:/documentation/Pinebook_Pro/Guides/Disassembly_and_Reassembly[Open the back] and verify that the eMMC is firmly seated. * You may want to try unplugging the SD card daughterboard ribbon cable and see if it powers on (remove the battery and peel off a bit of the tape before unplugging it to avoid damage). If it does, try reseating it on both sides. It might have come loose during shipping. -* It's possible that your eMMC is empty from the factory. Simply create a bootable link:/documentation/Pinebook_Pro#Pinebook_Pro_images[SD card] and see if your Pinebook Pro link:/documentation/Pinebook_Pro#Boot_sequence_details[Getting started]. +* It's possible that your eMMC is empty from the factory. Simply create a bootable link:/documentation/Pinebook_Pro/Software/Releases[SD card] and see if your Pinebook Pro link:/documentation/Pinebook_Pro/Troubleshooting[Getting started]. === Pinebook Pro will not power on after toggling the eMMC enable/disable switch diff --git a/content/documentation/Pinecil/Further_information/_index.adoc b/content/documentation/Pinecil/Further_information/_index.adoc index 38cb09da..b110ef1c 100644 --- a/content/documentation/Pinecil/Further_information/_index.adoc +++ b/content/documentation/Pinecil/Further_information/_index.adoc @@ -9,8 +9,4 @@ menu: weight: --- -* link:Pinecil_in_the_Media[Pinecil in the Media] -* link:History_of_hardware_changes[History of hardware changes] -* link:Certifications[] -* link:Specifications[] -* link:Pictures[] +{{< children >}} diff --git a/content/documentation/Pinecil/Modifications/_index.adoc b/content/documentation/Pinecil/Modifications/_index.adoc index 6f5a0065..dd80ceed 100644 --- a/content/documentation/Pinecil/Modifications/_index.adoc +++ b/content/documentation/Pinecil/Modifications/_index.adoc @@ -9,5 +9,4 @@ menu: weight: --- -* link:Optional_advanced_modifications[Optional advanced modifications] -* link:Hall_effect_sensor[Hall effect sensor] +{{< children >}} diff --git a/content/documentation/Pinecil/Power_supplies/_index.adoc b/content/documentation/Pinecil/Power_supplies/_index.adoc index 0ee6d75c..0dbe6934 100644 --- a/content/documentation/Pinecil/Power_supplies/_index.adoc +++ b/content/documentation/Pinecil/Power_supplies/_index.adoc @@ -9,5 +9,4 @@ menu: weight: 5 --- -* link:Power_supplies_and_watts[Power supplies and watts] -* link:Power_supplies[Power supplies] +{{< children >}} diff --git a/content/documentation/Pinecil/Purchase/_index.adoc b/content/documentation/Pinecil/Purchase/_index.adoc index d0f9798d..ec2dd2ec 100644 --- a/content/documentation/Pinecil/Purchase/_index.adoc +++ b/content/documentation/Pinecil/Purchase/_index.adoc @@ -9,5 +9,4 @@ menu: weight: --- -* link:Where_to_buy[Where to buy] -* link:Shipping_and_tracking[Shipping and tracking] +{{< children >}} diff --git a/content/documentation/Quartz64/Accessories/_index.adoc b/content/documentation/Quartz64/Accessories/_index.adoc index 8155e9a2..49ff581e 100644 --- a/content/documentation/Quartz64/Accessories/_index.adoc +++ b/content/documentation/Quartz64/Accessories/_index.adoc @@ -9,4 +9,4 @@ menu: weight: --- -* link:Premium_aluminium_case[Premium aluminium case] +{{< children >}} diff --git a/content/documentation/Quartz64/Further_information/_index.adoc b/content/documentation/Quartz64/Further_information/_index.adoc index 6427881c..83368eb6 100644 --- a/content/documentation/Quartz64/Further_information/_index.adoc +++ b/content/documentation/Quartz64/Further_information/_index.adoc @@ -9,6 +9,4 @@ menu: weight: --- -* link:Datasheets[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:Specifications[] +{{< children >}} diff --git a/content/documentation/Quartz64/Troubleshooting.adoc b/content/documentation/Quartz64/Troubleshooting.adoc index 467557bc..7b1b059f 100644 --- a/content/documentation/Quartz64/Troubleshooting.adoc +++ b/content/documentation/Quartz64/Troubleshooting.adoc @@ -19,7 +19,7 @@ NOTE: This affects only Model A Make sure the kernel is built with `CONFIG_MOTORCOMM_PHY` set to `y`. Building it as a module (`m`) and then relying on module auto-loading is unlikely to work, because if the generic PHY driver is built in it will bind to the PHY first, unless you include the motorcomm module in your initramfs. -Note: Starting with https://salsa.debian.org/kernel-team/linux/-/merge_requests/551[Debian's `6.1~rc3-1~exp1` kernel] the module is included, but set to `m` and I (Diederik) have verified that it gets included in the initramfs and *works* on Model-A and Model-B with the link:/documentation/Quartz64#Plebian[Quartz64] images. +Note: Starting with https://salsa.debian.org/kernel-team/linux/-/merge_requests/551[Debian's `6.1~rc3-1~exp1` kernel] the module is included, but set to `m` and I (Diederik) have verified that it gets included in the initramfs and *works* on Model-A and Model-B with the link:/documentation/Quartz64/Software/Releases/#plebian[Quartz64] images. == "Model A" Acrylic Case Doesn't Fit diff --git a/content/documentation/QuartzPro64/TODOs.adoc b/content/documentation/QuartzPro64/TODOs.adoc index bcc9f8c7..bfbe7fa1 100644 --- a/content/documentation/QuartzPro64/TODOs.adoc +++ b/content/documentation/QuartzPro64/TODOs.adoc @@ -11,7 +11,7 @@ menu: == Enable cpufreq Stuff -Current neggles kernel has the CPU at 1.2 GHz, apparently SRE has patches to enable cpufreq? (see below, in link:/documentation/QuartzPro64#Kernel[Resources]) +Current neggles kernel has the CPU at 1.2 GHz, apparently SRE has patches to enable cpufreq? (see in link:/documentation/QuartzPro64/Resources/#kernel[Resources]) == Add RK3588 Support To VOP2 diff --git a/content/documentation/ROCK64/Further_information/Premium_aluminum_casing.adoc b/content/documentation/ROCK64/Cases/Premium_aluminum_casing.adoc similarity index 97% rename from content/documentation/ROCK64/Further_information/Premium_aluminum_casing.adoc rename to content/documentation/ROCK64/Cases/Premium_aluminum_casing.adoc index 20adacfe..d969d05b 100644 --- a/content/documentation/ROCK64/Further_information/Premium_aluminum_casing.adoc +++ b/content/documentation/ROCK64/Cases/Premium_aluminum_casing.adoc @@ -4,8 +4,8 @@ draft: false menu: docs: title: - parent: "ROCK64/Further_information" - identifier: "ROCK64/Further_information/Premium_aluminium_casing" + parent: "ROCK64/Cases" + identifier: "ROCK64/Cases/Premium_aluminum_casing" weight: --- diff --git a/content/documentation/ROCK64/Enclosures.adoc b/content/documentation/ROCK64/Cases/_index.adoc similarity index 65% rename from content/documentation/ROCK64/Enclosures.adoc rename to content/documentation/ROCK64/Cases/_index.adoc index 11ab9444..e22a5bca 100644 --- a/content/documentation/ROCK64/Enclosures.adoc +++ b/content/documentation/ROCK64/Cases/_index.adoc @@ -1,11 +1,11 @@ --- -title: "Enclosures" +title: "Cases" draft: false menu: docs: title: parent: "ROCK64" - identifier: "ROCK64/Enclosures" + identifier: "ROCK64/Cases" weight: 5 --- @@ -15,4 +15,4 @@ The ROCK64 fits in three officially sold cases. * "Model B" Acrylic Open Enclosure, https://pine64.com/product/model-b-acrylic-open-enclosure/[Store] * "Model B" Aluminum Waterproof Enclosure, https://pine64.com/product/model-b-aluminum-waterproof-enclosure/[Store] -* link:/documentation/ROCK64/Premium_aluminium_casing[Premium Aluminium Casing], https://pine64.com/product/model-b-premium-aluminum-casing/?v=0446c16e2e66[Store] \ No newline at end of file +* link:/documentation/ROCK64/Cases/Premium_aluminum_casing[Premium Aluminium Casing], https://pine64.com/product/model-b-premium-aluminum-casing/?v=0446c16e2e66[Store] \ No newline at end of file diff --git a/content/documentation/ROCK64/Further_information/_index.adoc b/content/documentation/ROCK64/Further_information/_index.adoc index aea41976..03f59a41 100644 --- a/content/documentation/ROCK64/Further_information/_index.adoc +++ b/content/documentation/ROCK64/Further_information/_index.adoc @@ -9,5 +9,4 @@ menu: weight: 99 --- -* link:Other_resources[Other resources] -* link:Premium_aluminum_casing[Premium aluminum casing] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/ROCKPro64/Board/Features.adoc b/content/documentation/ROCKPro64/Board/Features.adoc index 41c1d330..497d27d0 100644 --- a/content/documentation/ROCKPro64/Board/Features.adoc +++ b/content/documentation/ROCKPro64/Board/Features.adoc @@ -135,7 +135,7 @@ ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new) | | | Configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s -| link:/documentation/ROCKPro64#OTG_mode[ROCKPro64] +| link:/documentation/ROCKPro64/Getting_started/#otg_mode[ROCKPro64] | | USB Mass Storage USB2/USB3 diff --git a/content/documentation/ROCKPro64/Getting_started.adoc b/content/documentation/ROCKPro64/Getting_started.adoc index f1bda27c..3c8989cc 100644 --- a/content/documentation/ROCKPro64/Getting_started.adoc +++ b/content/documentation/ROCKPro64/Getting_started.adoc @@ -87,7 +87,7 @@ The RockPro64 boot sequence has been documented https://github.com/sigmaris/u-bo == OTG Mode -You can boot your ROCKPro64 into OTG mode with the use of the Recover button (see switch 28 under link:/documentation/ROCKPro64/Board/Layout#Switches[Layout#Switches]). Note that there are 2 OTG ports on your ROCKPro64: the type-C USB 3 socket is definitely one. From the schematic it appears the USB 3 (type A) socket is the other, but this has yet to be confirmed. +You can boot your ROCKPro64 into OTG mode with the use of the Recover button (see switch 28 under link:/documentation/ROCKPro64/Board/Layout#switches[Layout#Switches]). Note that there are 2 OTG ports on your ROCKPro64: the type-C USB 3 socket is definitely one. From the schematic it appears the USB 3 (type A) socket is the other, but this has yet to be confirmed. The method is to power off the board. Then push and hold the Recover button and push and release the Power button. diff --git a/content/documentation/ROCKPro64/Software/Releases.adoc b/content/documentation/ROCKPro64/Software/Releases.adoc index 427421d5..7ac7e31a 100644 --- a/content/documentation/ROCKPro64/Software/Releases.adoc +++ b/content/documentation/ROCKPro64/Software/Releases.adoc @@ -70,7 +70,7 @@ Instructions: ** For Mac: `gzcat firmware.rockpro64-rk3399.img.gz partition.img.gz > complete_image.img` * Write the image to your boot device: ** For Linux: `dd if=complete_image.img of=your_chosen_boot_device bs=4M` -** For Mac: see link:/documentation/General/Getting_started[Getting started] +** For Mac: see link:/documentation/Introduction/Getting_started[Getting started] Notes: diff --git a/content/documentation/RockBox/Development/_index.adoc b/content/documentation/RockBox/Development/_index.adoc index c0495daa..3d0a8df7 100644 --- a/content/documentation/RockBox/Development/_index.adoc +++ b/content/documentation/RockBox/Development/_index.adoc @@ -9,5 +9,4 @@ menu: weight: 4 --- -* link:Mainline_Linux[Mainline Linux] -* link:Disassembly[] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/SOEDGE/Further_information/_index.adoc b/content/documentation/SOEDGE/Further_information/_index.adoc index 83b247ac..df182220 100644 --- a/content/documentation/SOEDGE/Further_information/_index.adoc +++ b/content/documentation/SOEDGE/Further_information/_index.adoc @@ -9,6 +9,4 @@ menu: weight: --- -* link:Datasheets[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:Specification[] +{{< children >}} diff --git a/content/documentation/SOEDGE/Releases.adoc b/content/documentation/SOEDGE/Releases.adoc index d98c885d..9f0ba717 100644 --- a/content/documentation/SOEDGE/Releases.adoc +++ b/content/documentation/SOEDGE/Releases.adoc @@ -44,7 +44,7 @@ Download: Notes: * Please unzip first and then using Rockchip tool to flash in -* link:/documentation/General/Getting_started#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29[Guide to flashing eMMC using Rockchip Tools] +* link:/documentation/Introduction/Getting_started#flashing_to_emmc_using_rockchip_tools_rock64_only[Guide to flashing eMMC using Rockchip Tools] === BSP Linux ver 1.1 Build as USB Stick application from SDK @@ -55,7 +55,7 @@ Download: Notes: * Please unzip first and then using Rockchip tool to flash in -* link:/documentation/General/Getting_started#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29[Guide to flashing eMMC using Rockchip Tools] +* link:/documentation/Introduction/Getting_started#flashing_to_emmc_using_rockchip_tools_rock64_only[Guide to flashing eMMC using Rockchip Tools] === BSP Linux ver 1.1 Build from SDK @@ -66,7 +66,7 @@ Download: Notes: * Please unzip first and then using Rockchip tool to flash in -* link:/documentation/General/Getting_started#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29[Guide to flashing eMMC using Rockchip Tools] +* link:/documentation/Introduction/Getting_started#flashing_to_emmc_using_rockchip_tools_rock64_only[Guide to flashing eMMC using Rockchip Tools] === BSP Linux ver 1.1 Build as USB Stick application from SDK @@ -77,7 +77,7 @@ Download: Notes: * Please unzip first and then using Rockchip tool to flash in -* link:/documentation/General/Getting_started#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29[Guide to flashing eMMC using Rockchip Tools] +* link:/documentation/Introduction/Getting_started#flashing_to_emmc_using_rockchip_tools_rock64_only[Guide to flashing eMMC using Rockchip Tools] == Linux BSP SDK diff --git a/content/documentation/SOEDGE_Baseboard/Features/_index.adoc b/content/documentation/SOEDGE_Baseboard/Features/_index.adoc index 18e28b21..0a98ee0b 100644 --- a/content/documentation/SOEDGE_Baseboard/Features/_index.adoc +++ b/content/documentation/SOEDGE_Baseboard/Features/_index.adoc @@ -9,6 +9,4 @@ menu: weight: 1 --- -* link:Expansion_ports[Expansion ports] -* link:Storage[] -* link:Network[] +{{< children >}} \ No newline at end of file diff --git a/content/documentation/SOPINE/Further_information/_index.adoc b/content/documentation/SOPINE/Further_information/_index.adoc index c051f830..44c522ca 100644 --- a/content/documentation/SOPINE/Further_information/_index.adoc +++ b/content/documentation/SOPINE/Further_information/_index.adoc @@ -9,6 +9,4 @@ menu: weight: --- -* link:Resources[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:Specification[] +{{< children >}} diff --git a/content/documentation/SOPINE/Pins_and_GPIOs.adoc b/content/documentation/SOPINE/Pins_and_GPIOs.adoc index e2e98f9c..6aef5d97 100644 --- a/content/documentation/SOPINE/Pins_and_GPIOs.adoc +++ b/content/documentation/SOPINE/Pins_and_GPIOs.adoc @@ -865,7 +865,7 @@ For Edge Finger view, see: | USB0-DM | USB0-DM | USB | B22 | A I/O | USB 0 Data Negative |174 -| GPIO0-link:/documentation/SOPINE/GPIO_alternate_functions_table#LDO[LDO] | GPIO0 | POWER | ? | P | 3.3V@100mA from LDO for Capacitive Touch Screen I2C interface as pull-up and other purposes with low power consumption +| GPIO0-LDO | GPIO0 | POWER | ? | P | 3.3V@100mA from LDO for Capacitive Touch Screen I2C interface as pull-up and other purposes with low power consumption |175 | CHG_LED | CHGLED | OTHER | 53 | O | Charger status indication diff --git a/content/documentation/SOPINE/Software/_index.adoc b/content/documentation/SOPINE/Software/_index.adoc index 4f55e4bd..16b56929 100644 --- a/content/documentation/SOPINE/Software/_index.adoc +++ b/content/documentation/SOPINE/Software/_index.adoc @@ -9,5 +9,4 @@ menu: weight: 1 --- -* link:Releases[Releases] -* link:Armbian_LCD_and_camera[Armbian LCD and camera] +{{< children >}} \ No newline at end of file diff --git a/content/documentation/SOQuartz/Baseboards/_index.adoc b/content/documentation/SOQuartz/Baseboards/_index.adoc index 950ba31a..c4b90d0a 100644 --- a/content/documentation/SOQuartz/Baseboards/_index.adoc +++ b/content/documentation/SOQuartz/Baseboards/_index.adoc @@ -9,6 +9,4 @@ menu: weight: 4 --- -* link:Blade[] -* link:Model-A[] -* link:Various_CM4_carrier_boards[Various CM4 carrier boards] \ No newline at end of file +{{< children >}} \ No newline at end of file diff --git a/content/documentation/SOQuartz/Further_information/_index.adoc b/content/documentation/SOQuartz/Further_information/_index.adoc index 14685c0c..b582d752 100644 --- a/content/documentation/SOQuartz/Further_information/_index.adoc +++ b/content/documentation/SOQuartz/Further_information/_index.adoc @@ -9,6 +9,4 @@ menu: weight: 99 --- -* link:Datasheets[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:Specifications[] +{{< children >}} diff --git a/content/documentation/SOQuartz/Software/_index.adoc b/content/documentation/SOQuartz/Software/_index.adoc index 8937a512..3d174fc5 100644 --- a/content/documentation/SOQuartz/Software/_index.adoc +++ b/content/documentation/SOQuartz/Software/_index.adoc @@ -9,7 +9,5 @@ menu: weight: 1 --- -* link:Releases[] -* link:Android_SDK[] -* link:BSP_Linux_SDK[] +{{< children >}} diff --git a/content/documentation/STAR64/Further_information/_index.adoc b/content/documentation/STAR64/Further_information/_index.adoc index b4a7f5f6..1cff76c5 100644 --- a/content/documentation/STAR64/Further_information/_index.adoc +++ b/content/documentation/STAR64/Further_information/_index.adoc @@ -9,6 +9,4 @@ menu: weight: 99 --- -* link:Datasheets[] -* link:Schematics_and_certifications[Schematics and certifications] -* link:Specification[] +{{< children >}} diff --git a/content/documentation/images/Fedora1.png b/content/documentation/images/Fedora1.png deleted file mode 100644 index 53e67144..00000000 Binary files a/content/documentation/images/Fedora1.png and /dev/null differ diff --git a/content/documentation/images/Netbsd.png b/content/documentation/images/Netbsd.png deleted file mode 100644 index 26ceeab1..00000000 Binary files a/content/documentation/images/Netbsd.png and /dev/null differ diff --git a/content/documentation/images/Opensuse-distribution.png b/content/documentation/images/Opensuse-distribution.png deleted file mode 100644 index 60e2ba47..00000000 Binary files a/content/documentation/images/Opensuse-distribution.png and /dev/null differ diff --git a/content/documentation/images/Pinephone_unbranded.png b/content/documentation/images/Pinephone_unbranded.png deleted file mode 100644 index 82d42cf3..00000000 Binary files a/content/documentation/images/Pinephone_unbranded.png and /dev/null differ diff --git a/content/documentation/images/Plebian-logo.svg b/content/documentation/images/Plebian-logo.svg new file mode 100644 index 00000000..321f4275 --- /dev/null +++ b/content/documentation/images/Plebian-logo.svg @@ -0,0 +1,17 @@ + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/content/podcast/_index.adoc b/content/podcast/_index.adoc index 05b039bb..2a84b7b1 100644 --- a/content/podcast/_index.adoc +++ b/content/podcast/_index.adoc @@ -3,4 +3,6 @@ title: "The PineTalk podcast" date: draft: false description: "We discuss PINE64 hardware, software development and open source in general. Send in your questions! A community ran podcast for the community." +aliases: + - /pinetalk --- \ No newline at end of file diff --git a/content/podcast/s01e11.adoc b/content/podcast/s01e11.adoc index 212fd4d6..0107d85a 100644 --- a/content/podcast/s01e11.adoc +++ b/content/podcast/s01e11.adoc @@ -63,7 +63,7 @@ BTW: There's a project that tries to recreate the Windows Phone Live Tile experi === Housekeeping -* https://www.pine64.org/gettings-started/[Getting started] +* link:/documentation/Introduction/Getting_started/[Getting started] === Quartz64