From 5f7b57c86de1c064831105899478e301cc400007 Mon Sep 17 00:00:00 2001 From: x1y <23239177+x1y@users.noreply.github.com> Date: Thu, 31 Oct 2024 12:19:04 +0100 Subject: [PATCH] Updated links, minor improvements --- README.md | 4 +- content/blog/a_new_design.md | 4 +- content/blog/april-update-no-more-unicorns.md | 4 +- ...ting-into-a-rhythm-and-not-slowing-down.md | 4 +- .../august-update-kept-you-waiting-huh.md | 4 +- content/blog/august-update-risc-and-reward.md | 2 +- .../blog/brave-heart-edition-pinephones.md | 8 +- .../blog/december-update-a-year-in-review.md | 2 +- .../december-update-thank-you-for-2019.md | 2 +- content/blog/january-update-happy-new-gear.md | 6 +- content/blog/july-update.md | 2 +- ...arch-update-introducing-the-quartzpro64.md | 2 +- content/blog/march-update-making-waves.md | 6 +- ...jaro-on-pinebook-pro-pinephone-software.md | 2 +- content/blog/march-update.md | 2 +- .../blog/november-update-first-impressions.md | 4 +- content/blog/november-update-tuned-in.md | 4 +- ...er-update-introducing-the-pinephone-pro.md | 4 +- ...pdate-pinetime-delays-and-shipping-news.md | 2 +- .../blog/rockpro64-cluster-move-june-5-10.md | 2 +- content/blog/september_2024.md | 2 +- ...-next-level-with-rockpro64-and-roshambo.md | 2 +- content/blog/update-new-hacktober-gear.md | 2 +- content/blog/welcome-new-community-members.md | 7 +- .../Accessories_Step_by_Step_Guides.md | 16 +-- .../Accessories/Cases/NASCase.md | 4 +- .../Accessories/Wifi_remote_i2c.md | 21 ++-- .../General/Android_SDK_for_RK3566.md | 4 +- content/documentation/General/Mali_driver.md | 8 +- .../PINE_H64_Model_B/Software/Releases.md | 2 +- .../Phone_Accessories/Keyboard.md | 6 +- .../PineNote/Development/Flashing.md | 2 +- .../PineNote/Development_efforts.md | 6 +- .../Further_information/Datasheets.md | 2 +- .../Further_information/Components.md | 18 +-- .../PinePhone/Further_information/Safety.md | 2 +- .../Sensors_and_navigation.md | 3 +- .../documentation/PinePhone/Modem/_index.md | 2 +- .../documentation/PinePhone/Repairs/_index.md | 2 +- .../Revisions/PinePhone_v1.1_-_Braveheart.md | 2 +- .../PinePhone/Revisions/PinePhone_v1.2.md | 2 +- .../PinePhone/Revisions/PinePhone_v1.2a.md | 2 +- .../PinePhone/Software/Releases.md | 8 +- .../Factory_test_battery_charging.md | 2 +- .../Factory_test_hardware_checking.md | 2 +- content/documentation/PinePhone_Pro/Modem.md | 2 +- .../PineTab/Operating_systems.md | 2 +- content/documentation/PineTime/FAQ.md | 4 +- .../PineTime/Software/Reprogramming.md | 2 +- .../documentation/Pinebook/Service_guides.md | 12 +- .../Pinebook_Pro/Features/Touchpad.md | 3 +- .../Pinebook_Pro/Guides/Caring.md | 6 +- .../Software/Installing_Arch_Linux_ARM.md | 118 ++++++++++++------ .../Pinebook_Pro/Software/Tuning.md | 103 ++++++++------- .../Quartz64/Software/Releases.md | 8 +- .../documentation/QuartzPro64/Resources.md | 2 +- .../QuartzPro64/Ways_to_do_things.md | 6 +- .../ROCK64/Software/MAC_address.md | 4 +- .../documentation/ROCKPro64/Board/Features.md | 2 +- .../Further_information/Datasheets.md | 6 +- .../Further_information/Other_resources.md | 2 +- .../Schematics_and_certifications.md | 2 +- .../ROCKPro64/Software/Releases.md | 74 +++++------ .../RockBox/External_resources.md | 1 - .../SOEDGE/Further_information/Datasheets.md | 2 +- content/documentation/SOEDGE/Releases.md | 10 +- .../Further_information/Specification.md | 6 +- .../documentation/SOPINE/Pins_and_GPIOs.md | 2 +- .../documentation/SOPINE/Software/Releases.md | 12 +- .../documentation/SOPINE/Troubleshooting.md | 4 +- .../SOQuartz/Software/Android_SDK.md | 2 +- .../SOQuartz/Software/BSP_Linux_SDK.md | 2 +- content/documentation/Unsorted/PhoenixCard.md | 4 +- content/podcast/s01e09.md | 2 +- content/podcast/s01e10.md | 6 +- content/podcast/s01e12.md | 2 +- content/podcast/s01e13.md | 12 +- themes/pinetheme/assets/css/style.css | 2 - themes/pinetheme/static/podlove/README.md | 44 ------- 79 files changed, 341 insertions(+), 329 deletions(-) delete mode 100644 themes/pinetheme/static/podlove/README.md diff --git a/README.md b/README.md index 86f3eea3..030a9d45 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ Install `git` and check out the website repository using the following command: ```sh git clone https://github.com/pine64/website.git -cd website-main +cd website ``` ### Get Hugo @@ -52,7 +52,7 @@ hugo ## Site structure ``` -website-main/ +website/ ├── archetypes/ │ └── default.md ├── assets/ diff --git a/content/blog/a_new_design.md b/content/blog/a_new_design.md index 598f16c0..d330638e 100644 --- a/content/blog/a_new_design.md +++ b/content/blog/a_new_design.md @@ -74,7 +74,7 @@ git clone https://github.com/pine64/website.git Then change the directory into the folder: ``` -cd website-main +cd website ``` And then preview the website using: @@ -92,7 +92,7 @@ The complete process is explained in details under https://github.com/pine64/web The project is structured the following: ``` -website-main/ +website/ ├── archetypes/ │ └── default.md ├── assets/ diff --git a/content/blog/april-update-no-more-unicorns.md b/content/blog/april-update-no-more-unicorns.md index bd1f00fb..bdff3b6a 100644 --- a/content/blog/april-update-no-more-unicorns.md +++ b/content/blog/april-update-no-more-unicorns.md @@ -78,7 +78,7 @@ I’d like to thank [JF](https://twitter.com/codingfield), [Peter](https://twitt In case you missed it, we ran a little [April fool’s spoof](https://www.pine64.org/2022/04/01/introducing-the-pinebuds-and-pinepod-seriously/) at the beginning of the month. I must admit that I am not a fan of the April fool’s tradition and we, as a project, haven’t really dabbled in pranks before. So, then, why did we publish the post and why am I mentioning it now? - because, as with any good joke, the April fools post contained an element of truth to it. More on this later on the update, seriously.  -It is time for the second community quarterly Q&A. If you’re reading this on the day of the community update’s publication, then make sure to stick around and join in later today/ tonight on [Youtube](https://www.youtube.com/c/PINE64inc), [Discord](http://discord.gg/pine64) or [PeerTube](https://tilvids.com/a/pine64tilvids/video-channels). We’ll be going live at 19:00 GMT/ 12:00 PT. The point of the Q&A is for us to take questions live and answer them then and there. I’ll be taking questions live from the chats - you have a choice of [Discord](http://discord.gg/pine64), [IRC](https://wiki.pine64.org/wiki/Main_Page#Chat_Platforms) and [Telegram](https://t.me/pine64QA). From [previous experience](https://youtu.be/tORlxpzmF3U) I know that the chat will more than likely turn into a wall of text in a matter of minutes - I therefore ask that you ‘at’ me (@lukasz) before writing your question, otherwise I will more than likely miss it. I will likely bring in developers to answer questions too - make sure to ping people you direct questions to. Once the Q&A is over we'll head over to one of the casual voice chats and hang out for the rest of the evening. I hope to see you there. +It is time for the second community quarterly Q&A. If you’re reading this on the day of the community update’s publication, then make sure to stick around and join in later today/ tonight on [Youtube](https://www.youtube.com/c/PINE64inc), [Discord](https://discord.gg/pine64) or [PeerTube](https://tilvids.com/a/pine64tilvids/video-channels). We’ll be going live at 19:00 GMT/ 12:00 PT. The point of the Q&A is for us to take questions live and answer them then and there. I’ll be taking questions live from the chats - you have a choice of [Discord](https://discord.gg/pine64), [IRC](https://wiki.pine64.org/wiki/Main_Page#Chat_Platforms) and [Telegram](https://t.me/pine64QA). From [previous experience](https://youtu.be/tORlxpzmF3U) I know that the chat will more than likely turn into a wall of text in a matter of minutes - I therefore ask that you ‘at’ me (@lukasz) before writing your question, otherwise I will more than likely miss it. I will likely bring in developers to answer questions too - make sure to ping people you direct questions to. Once the Q&A is over we'll head over to one of the casual voice chats and hang out for the rest of the evening. I hope to see you there. {{< youtube id="tORlxpzmF3U" >}} @@ -94,7 +94,7 @@ The product team is in advanced talks with a factory regarding resuming producti **Yes, there will be bundles** -Lastly, I am thrilled to let you know that [PINE64 EU](http://pine64eu.com) will be going live on May 10, 2022. By the time you read this, the Polish state should already have listed PINE64 EU as a registered company and all required paperwork should be in place to start sales. The website and logistics are also all ready to go. However, I am still awaiting approval from the debit/credit card payment gate, which takes a long time. I am also waiting for the hardware itself. With less than a month to go, I’ll be posting frequent updates on the store’s [Twitter](https://twitter.com/pine64eu) and the newly set-up [Telegram news](https://t.me/pine64eu) channel. I don’t foresee any issues at this stage, but should any problems arise (I am thinking about customs in particular) I will make sure to communicate it publicly via social media. Telegram and Twitter is where you will find all future communication from PINE64 EU. +Lastly, I am thrilled to let you know that [PINE64 EU](https://pine64eu.com) will be going live on May 10, 2022. By the time you read this, the Polish state should already have listed PINE64 EU as a registered company and all required paperwork should be in place to start sales. The website and logistics are also all ready to go. However, I am still awaiting approval from the debit/credit card payment gate, which takes a long time. I am also waiting for the hardware itself. With less than a month to go, I’ll be posting frequent updates on the store’s [Twitter](https://twitter.com/pine64eu) and the newly set-up [Telegram news](https://t.me/pine64eu) channel. I don’t foresee any issues at this stage, but should any problems arise (I am thinking about customs in particular) I will make sure to communicate it publicly via social media. Telegram and Twitter is where you will find all future communication from PINE64 EU. ## QuartzPro64 diff --git a/content/blog/august-update-getting-into-a-rhythm-and-not-slowing-down.md b/content/blog/august-update-getting-into-a-rhythm-and-not-slowing-down.md index d9030998..900e9d2c 100644 --- a/content/blog/august-update-getting-into-a-rhythm-and-not-slowing-down.md +++ b/content/blog/august-update-getting-into-a-rhythm-and-not-slowing-down.md @@ -53,7 +53,7 @@ I’d also like to thank [JF](https://twitter.com/codingfield) for covering the A recent series of events led me to rethink our formal rules of community engagement. As the community grows - and at a rapid pace at that - moderators and community members need to have clear guidelines to reference concerning the type of engagements we, as a community, are willing to accept. Before I write anything else, let me start by saying I am not a fan of heavy-handed moderation; I believe that just as in everyday life you’ll eventually run into a jerk in any community. This is just how life is, and I don’t believe that it's the role of moderators to educate people about civil conduct. But there are certainly some new and worrying trends that need to be addressed, so I’ll be writing up a new code of conduct / community rules in the coming weeks. The reason why I am mentioning it in this section, is because I’ll be [posting the draft](https://forum.pine64.org/showthread.php?tid=11034) of the new rules on the forum so that we can debate various aspects of the rules and (hopefully) agree on some of the more nuanced points I intend to make.  -The second topic I wanted to touch upon in this section concerns the use of the PINE64 logo and brand-name. We have recently experienced three types of infringements: 1) online resellers selling PINE64 hardware pretending to be Pine Store Ltd.; 2) merchandise sellers using our logo on swag without consent and; 2) our logo being used and misused without our consent in undesired contexts. In result, we are currently working on precise guidelines pertaining to the use of our logo and brand-name. This will arm PINE64 community and Pine Store Ltd., with the necessary documentation to tackle instances of infringements (e.g. when sending out _Cease and Desist_ notices to parties at fault) and when seeking legal recourse. This documentation will be available on the [PINE64 Wiki](http://wiki.pine64.org) next month. For those of you who wonder, here are the general rules concerning the use of the PINE64 logo and brand-name. You are allowed to use, alter and replicate both the logo and brand-name for non-commercial use without any prior consent. This extends to both software and non-software material. If you are one of our partner projects you’re welcome to use our logo alongside your own in commercial software or in promotional materials. For small-scale commercial use benefiting the community - such as, for instance swag, hardware add-ons or embellishments (e.g. protective vinyls) - you’ll receive consent after contacting us. All other use of the PINE64 logo or brand-name in a commercial context requires consent which can only be granted by Pine Store Ltd., in a legally binding document.   +The second topic I wanted to touch upon in this section concerns the use of the PINE64 logo and brand-name. We have recently experienced three types of infringements: 1) online resellers selling PINE64 hardware pretending to be Pine Store Ltd.; 2) merchandise sellers using our logo on swag without consent and; 2) our logo being used and misused without our consent in undesired contexts. In result, we are currently working on precise guidelines pertaining to the use of our logo and brand-name. This will arm PINE64 community and Pine Store Ltd., with the necessary documentation to tackle instances of infringements (e.g. when sending out _Cease and Desist_ notices to parties at fault) and when seeking legal recourse. This documentation will be available on the [PINE64 Wiki](https://wiki.pine64.org) next month. For those of you who wonder, here are the general rules concerning the use of the PINE64 logo and brand-name. You are allowed to use, alter and replicate both the logo and brand-name for non-commercial use without any prior consent. This extends to both software and non-software material. If you are one of our partner projects you’re welcome to use our logo alongside your own in commercial software or in promotional materials. For small-scale commercial use benefiting the community - such as, for instance swag, hardware add-ons or embellishments (e.g. protective vinyls) - you’ll receive consent after contacting us. All other use of the PINE64 logo or brand-name in a commercial context requires consent which can only be granted by Pine Store Ltd., in a legally binding document.   Lastly, if you haven’t done so yet I’d like to invite you to watch Matthew (fire219) Petry’s talk on Matrix’s Youtube channel. Matthew spoke about the PINE64 community, the separation of competences between the community and Pine Store Ltd., as well as his hurdles with getting the ROCKPro64 cluster fully functional.  @@ -65,7 +65,7 @@ https://www.youtube.com/watch?v=tJ8tthkVAOQ&t=1s Let me start by assuring you that the current Pinebook Pro batch is still [on schedule](https://www.pine64.org/2020/07/20/pinebook-pro-pre-orders-open-with-shipping-in-august-2020/) and will be delivered to us, from the factory, on August 24. This is yet another large batch of Pinebook Pros, and it will surely bring in new developers to the existing talent pool as well as draw the attention of prospectus partner projects. As you will find out further on in this section, this is also arguably the best time to be getting your unit as support for the device is growing. As for the hardware itself; for this batch of Pinebook Pros - as well as for all future production-runs - we are using a third-party QA service to give the laptops a thorough check prior to shipments going out. This is an arrangement which we reached via a mutual understanding with the new Pinebook Pro factory. We trust this will further reduce reports of DOA units and other types of hardware failures. -The big news of this month is that elementary is currently testing a pre-release of elementary OS 6 _Odin_ for the Pinebook Pro. For those of you unfamiliar with elementary OS, it is a sleek distribution built on Ubuntu LTS, which ships with a (subjectively) beautiful and simple GTK desktop environment called Pantheon and a tailored store - the AppCenter.  When the build becomes publicly available, it will offer a tailored experience for the Pinebook Pro, featuring countless tweaks to make Pantheon run well on the hardware. I also feel it is worth mentioning that the Pinebook Pro is the first Arm device to receive support from elementary. Needless to say, we are thrilled to see another highly requested OS land on our platform, and we’re thankful to the devs for all their effort in making this happen. I have now been running elementary OS on my Pinebook Pro for the past couple of weeks and I am happy to report that the experience is already very solid. I highly encourage you to visit [elementary’s website](https://elementary.io/) and join their friendly [community](https://www.reddit.com/r/elementaryos/). If you can’t wait to try the build out, then please consider supporting elementary via GitHub sponsors - [builds.elementary.io](http://builds.elementary.io) - as this will grant you early access to the OS image. +The big news of this month is that elementary is currently testing a pre-release of elementary OS 6 _Odin_ for the Pinebook Pro. For those of you unfamiliar with elementary OS, it is a sleek distribution built on Ubuntu LTS, which ships with a (subjectively) beautiful and simple GTK desktop environment called Pantheon and a tailored store - the AppCenter.  When the build becomes publicly available, it will offer a tailored experience for the Pinebook Pro, featuring countless tweaks to make Pantheon run well on the hardware. I also feel it is worth mentioning that the Pinebook Pro is the first Arm device to receive support from elementary. Needless to say, we are thrilled to see another highly requested OS land on our platform, and we’re thankful to the devs for all their effort in making this happen. I have now been running elementary OS on my Pinebook Pro for the past couple of weeks and I am happy to report that the experience is already very solid. I highly encourage you to visit [elementary’s website](https://elementary.io/) and join their friendly [community](https://www.reddit.com/r/elementaryos/). If you can’t wait to try the build out, then please consider supporting elementary via GitHub sponsors - [builds.elementary.io](https://builds.elementary.io) - as this will grant you early access to the OS image. ![](/blog/images/elementarydocked.jpg) diff --git a/content/blog/august-update-kept-you-waiting-huh.md b/content/blog/august-update-kept-you-waiting-huh.md index 6e94d127..e084e0ea 100644 --- a/content/blog/august-update-kept-you-waiting-huh.md +++ b/content/blog/august-update-kept-you-waiting-huh.md @@ -66,9 +66,9 @@ Speaking of deadlines, this update didn't have a very long time in the proverbia ### Rework of the community website and logo -If you missed the announcement, an initial rework of the community website was announced. The announcement blog post can be read exclusively on the new beta site: https://pine64.org/2023/04/13/a_new_design/ +If you missed the announcement, an initial rework of the community website was announced. The announcement blog post can be read [exclusively on the new beta site](/2023/04/13/a_new_design/). -The overall idea of the reworked community website is to move away from a WordPress site and to open up the site to contributions from all community members. This is done by hosting the website on Git and by generating the contents using the blazing-fast framework *Hugo*. Large parts of the website are created from simple markdown files, which are easy to understand and to edit. Alongside the rework of the community website, there was also a challenge launched, which has the goal of improving the appearance of the community logo. The details can be read under https://pine64.org/contests/the-logo-challenge/. Bring in your best ideas if you haven't done so yet. Ideas are best submitted to https://github.com/pine64/website/issues/12. +The overall idea of the reworked community website is to move away from a WordPress site and to open up the site to contributions from all community members. This is done by hosting the website on Git and by generating the contents using the blazing-fast framework *Hugo*. Large parts of the website are created from simple markdown files, which are easy to understand and to edit. Alongside the rework of the community website, there was also a challenge launched, which has the goal of improving the appearance of the community logo. The details can be read under [the logo challenge](/contests/the-logo-challenge/). Bring in your best ideas if you haven't done so yet. Ideas are best submitted to https://github.com/pine64/website/issues/12. Since the last blog post, there has been various improvements made to the beta community website. The improvements include changes to the style of various sites, improvements to the front site slider and inclusion of more slides, rewrite of pages as markdown files (such as the index page), creation of more board graphics and many more changes. diff --git a/content/blog/august-update-risc-and-reward.md b/content/blog/august-update-risc-and-reward.md index 317cbd66..2936f4e7 100644 --- a/content/blog/august-update-risc-and-reward.md +++ b/content/blog/august-update-risc-and-reward.md @@ -108,7 +108,7 @@ In other hardware news, the most recent production run of the PinePhone Pro has **Nano SIM slot on the PinePhone Pro** -There are a few software news I’d also like to cover this month. The most notable of which, and one which will eventually surely find its way into all OSes, concerns sound on the PinePhone Pro. [Megi](http://xnux.eu/) has recently released a set of patches that address some of the issues people have been experiencing: sound codec not working after boot (prior to an app playing audio), changing controls while headphone or speaker output is active breaks audio, sound stutter when serial console is enabled in CLI, OUTMIX and RECMIX drivers not matching the schematic and microphone quality. I invite you to read and follow [megi’s development (b)log](https://xnux.eu/log/#074) to learn of the details but, in short, the patches ought to improve the sound situation on the PinePhone Pro. I hope to see them make their way into individual OSes soon.  +There are a few software news I’d also like to cover this month. The most notable of which, and one which will eventually surely find its way into all OSes, concerns sound on the PinePhone Pro. [Megi](https://xnux.eu/) has recently released a set of patches that address some of the issues people have been experiencing: sound codec not working after boot (prior to an app playing audio), changing controls while headphone or speaker output is active breaks audio, sound stutter when serial console is enabled in CLI, OUTMIX and RECMIX drivers not matching the schematic and microphone quality. I invite you to read and follow [megi’s development (b)log](https://xnux.eu/log/#074) to learn of the details but, in short, the patches ought to improve the sound situation on the PinePhone Pro. I hope to see them make their way into individual OSes soon.  As for the OSes, we’ve seen a few releases for the PinePhone and PinePhone Pro this past month. This includes (at least to my knowledge - there may be others) postmarketOS, Manjaro, OpenSUSE and DanctNIX (Arch). Most of the distributions shipping the Phosh mobile environment have now updated to the newest version which adds swiping motions; I haven’t had the opportunity to try the newest version of Phosh myself, but I hear very good things about it. I would also like to note that OpenSUSE shared an image of the PinePhone charging wirelessly using the Qi wireless charging case (currently out of stock), which is super cool to see. I am including a picture from the tweet below. diff --git a/content/blog/brave-heart-edition-pinephones.md b/content/blog/brave-heart-edition-pinephones.md index 7e7f8c57..183db147 100644 --- a/content/blog/brave-heart-edition-pinephones.md +++ b/content/blog/brave-heart-edition-pinephones.md @@ -122,7 +122,7 @@ With that out of the way, I’m happy to announce that the **Brave Heart product ![](/blog/images/timer.png) -**Timer on [main page](https://pine64.org) counting down to pre-orders  opening** +**Timer on [main page](/) counting down to pre-orders  opening** So, what can _Brave Heart_ adopters look forward to and what should they be aware of? Let’s talk about the hardware first: the _Brave Heart_ PinePhones will, by and large, be identical to PinePhones produced in 2020 and onwards. This applies to the case molding, PCB, LCD assembly, cooling, as well as various other components making up the phones, including aesthetic ones. These are effectively considered ‘final’. That said, as I already mentioned, we will likely be further tweaking 2G antennas to improve reception of the respective bands and we reserve the right to fix any issues that may be uncovered in the hardware. We do not, however, deem it likely that any major issues will transpire or affect end-users. Still, keep in mind that this batch is called _Brave heart_ for a reason - we’re looking for those brave enough to be the first adopters of this hardware. If bravery is not in your nature, or this isn’t something you’re willing to take a risk on, then please sit this one out and wait until March 2020 to get your production unit.  @@ -130,9 +130,9 @@ As for the software, I have nothing but good news to relay. It is my understandi Finishing off this already lengthy PinePhone section, I completely forgot to mention that _Brave Heart_ schematics and other associated documents have now been made available. I am linking them below for you to view and comment on:  -- [PinePhone Brave Heart Schematic](http://files.pine64.org/doc/PinePhone/PinePhone_Schematic_v1.1_20191031.pdf) -- [PinePhone Brave Heart Changes (vs prototype units)](http://files.pine64.org/doc/PinePhone/PinePhone_BraveHeart_edition_version_1.1_change_list.pdf) -- [PinePhone Exploded Diagram of Brave Heart edition PinePhones](http://files.pine64.org/doc/PinePhone/PinePhone_Exploded_Diagram_ver_1.0.pdf) +- [PinePhone Brave Heart Schematic](https://files.pine64.org/doc/PinePhone/PinePhone_Schematic_v1.1_20191031.pdf) +- [PinePhone Brave Heart Changes (vs prototype units)](https://files.pine64.org/doc/PinePhone/PinePhone_BraveHeart_edition_version_1.1_change_list.pdf) +- [PinePhone Exploded Diagram of Brave Heart edition PinePhones](https://files.pine64.org/doc/PinePhone/PinePhone_Exploded_Diagram_ver_1.0.pdf) #### PineTab diff --git a/content/blog/december-update-a-year-in-review.md b/content/blog/december-update-a-year-in-review.md index 3a343fb1..cb66deeb 100644 --- a/content/blog/december-update-a-year-in-review.md +++ b/content/blog/december-update-a-year-in-review.md @@ -91,7 +91,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/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. +This month’s [PineTalk](/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-thank-you-for-2019.md b/content/blog/december-update-thank-you-for-2019.md index 07bd51c1..345c81c1 100644 --- a/content/blog/december-update-thank-you-for-2019.md +++ b/content/blog/december-update-thank-you-for-2019.md @@ -131,7 +131,7 @@ Speaking of OSs available for the Pinebook Pro, their number is steadily growing ![](/blog/images/Arch.jpeg) -**Arch Linux on the Pinebook Pro via Screenshot via [@AndreVallestero](https://twitter.com/AndreVallestero) [http://github.com/AndreVallestero](https://t.co/FFNvdJNGi0?amp=1 "http://github.com/AndreVallestero")** +**Arch Linux on the Pinebook Pro via Screenshot via [@AndreVallestero](https://twitter.com/AndreVallestero) [https://github.com/AndreVallestero](https://t.co/FFNvdJNGi0?amp=1 "https://github.com/AndreVallestero")** The past month has also seen a very important development on the hardware front. Namely,  problems with missing keypresses and an unwieldy trackpad have now been resolved and are a thing of the past. The firmware fix for both inputs has been delivered thanks to the hard work of a dedicated group of people: TL Lim, anarsoul, Xalius and ayufan. Everyone who has already gotten their Pinebook Pro should install the new trackpad and keyboard firmware. The firmware update can be performed from any Linux OS and process itself is very simple only requiring running two scripts between reboots. Please reference the [forum thread that describes the process in detail](https://forum.pine64.org/showthread.php?tid=8407) for more information. Future Pinebook Pros, starting with units shipped in December of 2019, will arrive with the new firmware pre-flashed.   diff --git a/content/blog/january-update-happy-new-gear.md b/content/blog/january-update-happy-new-gear.md index 5af77ae8..b6346cba 100644 --- a/content/blog/january-update-happy-new-gear.md +++ b/content/blog/january-update-happy-new-gear.md @@ -85,7 +85,7 @@ PinePhone KDE Community Edition should start shipping shortly following a two we **PineTalk Podcast Logo** -Lastly, I am happy to announce that Ezra from [Elatronion](https://www.youtube.com/channel/UCLN0SPhQo4jAPpTFNsxUnMg) and Peter from [LINMOBnet](https://www.youtube.com/user/EtlamRetep) will be hosting the PineTalk - a PINE64 podcast by community members for the community. Episodes of the podcast will be available bi-weekly - as in, available every other week - and will be available on Youtube, Peertube, LBRY, Spotify and Apple Podcasts. Peter and Ezra are working out the details at this time, but you can expect the first episode to drop sometime in February. Make sure to check out the [PineTalk page](https://pine64.org/pinetalk) for more details.  +Lastly, I am happy to announce that Ezra from [Elatronion](https://www.youtube.com/channel/UCLN0SPhQo4jAPpTFNsxUnMg) and Peter from [LINMOBnet](https://www.youtube.com/user/EtlamRetep) will be hosting the PineTalk - a PINE64 podcast by community members for the community. Episodes of the podcast will be available bi-weekly - as in, available every other week - and will be available on Youtube, Peertube, LBRY, Spotify and Apple Podcasts. Peter and Ezra are working out the details at this time, but you can expect the first episode to drop sometime in February. Make sure to check out the [PineTalk page](/pinetalk) for more details.  ### Pinebook Pro  @@ -171,11 +171,11 @@ Pre-orders for the Mobian Community Edition PinePhone will open in three days ti **$199** – 3GB RAM + 32GB eMMC Convergence Package with an included USB-C dock -You can expect a blog post entry on the day this community edition goes live, followed by information on [Twitter](https://twitter.com/thepine64), [Mastodon](https://fosstodon.org/@PINE64), our [Telegram News Channel](http://t.me/PINE64_News), the [PINE64 forum](https://forum.pine64.org/) and elsewhere. As was the case with all previous community editions, we will be donating $10 per unit sold to the Mobian project, to support development of mobile Linux on all platforms. Now head over to [Mobian’s blog and read](https://blog.mobian-project.org/posts/2021/01/15/mobian-community-edition/) what they’ve got to say about the state of their operating system and development for the PinePhone.  +You can expect a blog post entry on the day this community edition goes live, followed by information on [Twitter](https://twitter.com/thepine64), [Mastodon](https://fosstodon.org/@PINE64), our [Telegram News Channel](https://t.me/PINE64_News), the [PINE64 forum](https://forum.pine64.org/) and elsewhere. As was the case with all previous community editions, we will be donating $10 per unit sold to the Mobian project, to support development of mobile Linux on all platforms. Now head over to [Mobian’s blog and read](https://blog.mobian-project.org/posts/2021/01/15/mobian-community-edition/) what they’ve got to say about the state of their operating system and development for the PinePhone.  I’d like to thank all projects who participated in the community edition scheme: [UBports Foundation](https://ubports.com/), [postmarketOS](https://postmarketos.org/), [Manjaro Linux](https://manjaro.org/), [KDE Community](https://kde.org/) and the [Mobian Project](https://mobian-project.org/). Thanks to your efforts we’ve managed to breathe new life into the dream of Linux on mobile and started something completely extraordinary. We’ve on track to ship a staggering number of PinePhones, and fully appreciate that the success of the PinePhone is as much yours as it is ours. Congratulations on a job well done!  -For a change, I will start with discussing software news this month. There is much to write about since important progress has been made in the past 30 days, but the most important development of all (at least in my view) is that the PinePhone’s modem is now capable of running mainline Linux. Thanks to work by [Biktor](https://github.com/Biktorgj) and [Konrad Dybcio](http://twitter.com/konradybcio) the first step in opening up the modem has begun. I spoke to Konrad, who asked me to emphasize that presently this is very much a proof of concept, but that an effort is being made to have a community-built mainline Linux which will equal the modem’s proprietary firmware in terms of functionality. This means that users will, eventually, be able to replace the modem’s firmware with a community-built one on their own. Be aware, it is unlikely that we’ll be able to ship it on the device due to various legal constraints. Some parts of the modem, such as DSP firmware, will most likely have to remain closed. Regardless, these implications are obviously massive. At the time of writing this, you can install an operating system, such as postmarketOS, on the modem and even run a Minecraft server on it!  +For a change, I will start with discussing software news this month. There is much to write about since important progress has been made in the past 30 days, but the most important development of all (at least in my view) is that the PinePhone’s modem is now capable of running mainline Linux. Thanks to work by [Biktor](https://github.com/Biktorgj) and [Konrad Dybcio](https://twitter.com/konradybcio) the first step in opening up the modem has begun. I spoke to Konrad, who asked me to emphasize that presently this is very much a proof of concept, but that an effort is being made to have a community-built mainline Linux which will equal the modem’s proprietary firmware in terms of functionality. This means that users will, eventually, be able to replace the modem’s firmware with a community-built one on their own. Be aware, it is unlikely that we’ll be able to ship it on the device due to various legal constraints. Some parts of the modem, such as DSP firmware, will most likely have to remain closed. Regardless, these implications are obviously massive. At the time of writing this, you can install an operating system, such as postmarketOS, on the modem and even run a Minecraft server on it!  ![](/blog/images/Modem510-936x1024.jpg) diff --git a/content/blog/july-update.md b/content/blog/july-update.md index 7f9bd62d..6bab53da 100644 --- a/content/blog/july-update.md +++ b/content/blog/july-update.md @@ -137,7 +137,7 @@ The big software news of this month is that the PinePhone is now capable of acce https://www.youtube.com/watch?v=BvmRV6IIGGo -**Hardware accelerated video in Clapper - by [Brian Daniels](http://briandaniels.me/)** +**Hardware accelerated video in Clapper - by [Brian Daniels](https://briandaniels.me/)** In other news, there is now an Arch Linux ARM OS image featuring Plasma Mobile; this is something that many users have been interested in seeing for quite some time. The image features the newest Plasma Mobile UI (5.22) and joins the existing selection of Phosh and barebones installations - it can be downloaded from [here](https://github.com/dreemurrs-embedded/Pine64-Arch/releases)!  diff --git a/content/blog/march-update-introducing-the-quartzpro64.md b/content/blog/march-update-introducing-the-quartzpro64.md index b623538d..39f43216 100644 --- a/content/blog/march-update-introducing-the-quartzpro64.md +++ b/content/blog/march-update-introducing-the-quartzpro64.md @@ -151,7 +151,7 @@ Battery capacity reporting for the keyboard case now works in the UI on the Pine {{< youtube id="oq9m3nn-02M" >}} -**LibeELEC on the original PinePhone - original video by [Megi](http://xnux.eu/)** +**LibeELEC on the original PinePhone - original video by [Megi](https://xnux.eu/)** Lastly, an alternative X86/X86-64 emulator for ARM64 called [Fex-EMU](https://github.com/FEX-Emu/FEX) (Compared to Box86/64 it aims to be faster), has seen major improvements leading towards the goal of getting full Proton and Steam compatibility. It is great to see further work being done in this space. And although it’s being mentioned here, this obviously not only benefits the PinePhone, but any ARM64 device out there! diff --git a/content/blog/march-update-making-waves.md b/content/blog/march-update-making-waves.md index 08ed8f0c..fcaa6ca8 100644 --- a/content/blog/march-update-making-waves.md +++ b/content/blog/march-update-making-waves.md @@ -40,7 +40,7 @@ The PineVox is a BL606P based home assistant smart speaker. Designed to help bui Currently a small number of developer seed units have been given out. Work is ongoing by Ralim & Gamiee to get a minimal firmware image ready to allow for demonstration and to prove all hardware fully functional etc. -More information on the unit should be available soon on our new [documentation page](https://pine64.org/documentation). Features of note include the hardware microphone kill switch, and the ability to debug the unit externally. The hardware microphone killswitch allows the software to mute the microphone but unmuting has to be performed using the button on the device. Muting the microphone disables the clock connection to the microphone, giving peace of mind that it really, really isnt listening to you. +More information on the unit should be available soon on our new [documentation page](/documentation). Features of note include the hardware microphone kill switch, and the ability to debug the unit externally. The hardware microphone killswitch allows the software to mute the microphone but unmuting has to be performed using the button on the device. Muting the microphone disables the clock connection to the microphone, giving peace of mind that it really, really isnt listening to you. Giving users control of the smart devices in their home and allowing for _you_ to control the security is important, and we are working on the PineVox to help enable that future. @@ -228,7 +228,7 @@ Currently more testing is desired to help find remaining bugs and resolve first- On the 20th of January 2024 at 10:30 PM CET, most of the DB based services went down and started throwing errors when attempting to connect to the MySQL databases. After some analysis, all of the nodes in the cluster had failed, making the rootfs mount as read-only. In the current cluster setup every node has its rootfs mounted over the network, this leads to one likely culpret, that something had gone wrong with the storage node. I wasn't able to connect to the storage node, so I went to the datacentre where the cluster is hosted. Once on site, I found that the storage node's SSD (which hosts all of the data for the other nodes) had switched to read-only mode reporting issues about writing to SSD. -Thankfully as the [temporary cluster](https://pine64.org/2021/09/01/clusters-build-log-moving-to-temporary-cluster/) is only a small number of nodes, I took it home so I could recover the data. +Thankfully as the [temporary cluster](/2021/09/01/clusters-build-log-moving-to-temporary-cluster/) is only a small number of nodes, I took it home so I could recover the data. Before the shutdown of remaining cluster nodes, I took a moment to make a screenshot of the main node's (gateway & firewall) uptime: ![Cluster main node uptime](/blog/images/2024-march-update/cluster-main-node-uptime.jpg) @@ -272,7 +272,7 @@ We still plan to host our services on the cluster, but before that, we need to f ![Cluster photo](/blog/images/2024-march-update/cluster-photo.jpg) -In September 2021, I wrote the [blog post](https://pine64.org/2021/09/01/clusters-build-log-moving-to-temporary-cluster/), about building the new "temporary cluster", and exchanging it with the "final one". I recommend reading the blog post, it explains a lot about the cluster and the reason we moved to the temporary cluster. In short, unfortunately, the cluster was deployed in a hurry, and things like power management for the nodes were not finished. For proper implementation, it would have been best to have had the cluster at my place, so a temporary cluster was built. (The temporary cluster was in the server housing until the failure) +In September 2021, I wrote the [blog post](/2021/09/01/clusters-build-log-moving-to-temporary-cluster/), about building the new "temporary cluster", and exchanging it with the "final one". I recommend reading the blog post, it explains a lot about the cluster and the reason we moved to the temporary cluster. In short, unfortunately, the cluster was deployed in a hurry, and things like power management for the nodes were not finished. For proper implementation, it would have been best to have had the cluster at my place, so a temporary cluster was built. (The temporary cluster was in the server housing until the failure) Sadly, life got busy, and there was not a lot of progress on the cluster until 2023. Me and Ralimtek started working on a new PCB, which will serve as the "motherboard" of the cluster. This is for managing the power supply, communication with power management boards and a UART output logger for all nodes. For the first revision, this board was designed as a daughterboard for SOPine A64 Baseboard, the final version will be a PCB that will house a SOPine A64 module. A few weeks ago, I managed to assemble the daughterboard and perform some tests. Aside from some very minor issues, the board works pretty well! diff --git a/content/blog/march-update-manjaro-on-pinebook-pro-pinephone-software.md b/content/blog/march-update-manjaro-on-pinebook-pro-pinephone-software.md index 47966472..66d60735 100644 --- a/content/blog/march-update-manjaro-on-pinebook-pro-pinephone-software.md +++ b/content/blog/march-update-manjaro-on-pinebook-pro-pinephone-software.md @@ -62,7 +62,7 @@ We’re excited and proud to announce that future Pinebook Pros will ship with M **ANSI (left) and ISO (right) Pinebook Pros running Manjaro with KDE Plasma** -If Manjaro isn’t your OS of choice, then you’re of course welcome to try any of the [many options](https://wiki.pine64.org/index.php/Pinebook_Pro_Software_Release) available for the Pinebook Pro. Nearly all available OSes can be booted from a SD card and, once you find what you’re looking for, the chosen distribution or \*BSC can be installed to eMMC flash memory. The list of available software is continually growing with new, novel and interesting releases becoming available weekly. Two notable releases from the past couple of weeks include [Recalbox (pre-release)](https://github.com/mrfixit2001/recalbox-rockchip/releases) by the one and only [MrFixIt](https://github.com/mrfixit2001/), as well as [postmarketOS](http://images.postmarketos.org/pinebookpro/) and [Slackware](https://gitlab.com/sndwvs/slackware_arm_build_kit). So if you’re keen on trying something different (and yet familiar - since posmarketOS is built on Alpine Linux), or experience Slack nostalgia, then here’s your chance. I am also sure that retrogaming enthusiasts will be happy to see a dedicated Recalbox image for the Pinebook Pro; the Pinebook Pro is able to run Dreamcast and PSP games at upscaled resolutions at full speed, making it a great on-the-go gaming system. One of the cool features of Recalbox is that if you boot with either an USB-C-to-HDMI dongle or a USB-C dock connected, then the output will automatically switch to the external monitor.    +If Manjaro isn’t your OS of choice, then you’re of course welcome to try any of the [many options](https://wiki.pine64.org/index.php/Pinebook_Pro_Software_Release) available for the Pinebook Pro. Nearly all available OSes can be booted from a SD card and, once you find what you’re looking for, the chosen distribution or \*BSC can be installed to eMMC flash memory. The list of available software is continually growing with new, novel and interesting releases becoming available weekly. Two notable releases from the past couple of weeks include [Recalbox (pre-release)](https://github.com/mrfixit2001/recalbox-rockchip/releases) by the one and only [MrFixIt](https://github.com/mrfixit2001/), as well as [postmarketOS](https://images.postmarketos.org/pinebookpro/) and [Slackware](https://gitlab.com/sndwvs/slackware_arm_build_kit). So if you’re keen on trying something different (and yet familiar - since posmarketOS is built on Alpine Linux), or experience Slack nostalgia, then here’s your chance. I am also sure that retrogaming enthusiasts will be happy to see a dedicated Recalbox image for the Pinebook Pro; the Pinebook Pro is able to run Dreamcast and PSP games at upscaled resolutions at full speed, making it a great on-the-go gaming system. One of the cool features of Recalbox is that if you boot with either an USB-C-to-HDMI dongle or a USB-C dock connected, then the output will automatically switch to the external monitor.    ![](/blog/images/RB.jpg) diff --git a/content/blog/march-update.md b/content/blog/march-update.md index 19bf122b..0f5def5f 100644 --- a/content/blog/march-update.md +++ b/content/blog/march-update.md @@ -129,7 +129,7 @@ We are hoping to open Pinebook Pro pre-orders this month, however as I explained The good news is that this is a great time to pick up a Pinebook Pro. Armbian has recently released [new OS images](https://forum.armbian.com/topic/17192-first-panfrost-enabled-desktop-builds/?tab=comments&_fromLogin=1) featuring Panfrost acceleration. This includes a version of Armbian that ships with the GNOME desktop environment. I have now spent over a week testing out the image featuring GNOME and I have to say that it has been a very pleasant experience overall. I need to come clean at this point, and admit my preference for Manjaro and Plasma desktop, but the GNOME on Armbian runs just as fast as Plasma on Manjaro and all applications, including firefox, are just as responsive. Overall, I must say that I am highly impressed. So to those of you who have been longing for a traditional (and well supported) Ubuntu-like experience on the Pinebook Pro, I finally get to say that this is now a reality. If you already got a Pinebook Pro, then you can get the Armbian Focal with GNOME [here](https://redirect.armbian.com/region/EU/pinebook-pro/Focal_current_gnome). I should mention that Armbian also offers OS images with XFCE and MATE, as well as testing images with Cinnamon and Budgie desktops.  -In other Pinebook Pro software news, we now have a [postmarketOS image](http://images.postmarketos.org/bpo/edge/) featuring kernel 5.11.x and GNOME desktop for the Pinebook Pro. Both a ‘live’ and an ‘installer’ OS image is available. The installer OS image allows you to encrypt your filesystem, set your user name and password as well as tweak a few other variables. Although postmarketOS is primarily a mobile operating system, it is lightweight and tailored to run on ARM systems thanks to its Alpine Linux base. This makes it a natural candidate for running on the Pinebook Pro. I encourage you all to have a look at postmarketOS on the Pinebook Pro - images can be found [here](http://images.postmarketos.org/bpo/edge/). +In other Pinebook Pro software news, we now have a [postmarketOS image](https://images.postmarketos.org/bpo/edge/) featuring kernel 5.11.x and GNOME desktop for the Pinebook Pro. Both a ‘live’ and an ‘installer’ OS image is available. The installer OS image allows you to encrypt your filesystem, set your user name and password as well as tweak a few other variables. Although postmarketOS is primarily a mobile operating system, it is lightweight and tailored to run on ARM systems thanks to its Alpine Linux base. This makes it a natural candidate for running on the Pinebook Pro. I encourage you all to have a look at postmarketOS on the Pinebook Pro - images can be found [here](https://images.postmarketos.org/bpo/edge/). https://www.youtube.com/watch?v=hjzNr7wnBpk diff --git a/content/blog/november-update-first-impressions.md b/content/blog/november-update-first-impressions.md index 4587183b..2db12c41 100644 --- a/content/blog/november-update-first-impressions.md +++ b/content/blog/november-update-first-impressions.md @@ -95,13 +95,13 @@ I am also happy to report that my device doesn’t run hot. Warm, circumstantial **From left to right: Temps under load, after one minute and after ten minutes of cool-down**  -I am not going to write about battery life just yet, since the battery and charging kernel driver as well as various settings still need tweaking. [Megi](https://xnux.eu/) told me that the current software will “_happily charge out of spec_”, which also means that charging to (what the kernel thinks is…) full battery capacity isn’t a great idea. Besides, any numbers I’d provide at this point would be meaningless in 3 months time. Since I already started listing things that need work, here’s the rest of things that currently do not work fully or partially: 1) sound (which also means no…) 2) phone voice calls, 3) cameras, 4) USB for data, video or OTG 5) torch/ camera flash. Some of these are already worked on and will be resolved quickly, while others may take longer. While we need to acknowledge that there is a lot of work ahead of developers, we simultaneously have to appreciate how far development on the original PinePhone has gotten us. +I am not going to write about battery life just yet, since the battery and charging kernel driver as well as various settings still need tweaking. [Megi](https://xnux.eu/) told me that the current software will “_happily charge out of spec_”, which also means that charging to (what the kernel thinks is…) full battery capacity isn’t a great idea. Besides, any numbers I’d provide at this point would be meaningless in 3 months time. Since I already started listing things that need work, here’s the rest of things that currently do not work fully or partially: 1) sound (which also means no…) 2) phone voice calls, 3) cameras, 4) USB for data, video or OTG 5) torch / camera flash. Some of these are already worked on and will be resolved quickly, while others may take longer. While we need to acknowledge that there is a lot of work ahead of developers, we simultaneously have to appreciate how far development on the original PinePhone has gotten us. ![](/blog/images/pppguts-1.jpg) **PinePhone Pro with back case and battery removed** -Returning to the subject of the hardware, I have a few observations that pictures or renders cannot convey. The panel is really bright and the colours are rich; the vibration motor is much more powerful than on the original PinePhone; 5Ghz WiFi connectivity has been exceptionally good even when compared with my 2 year old flagship Android phone; and the phone has some heft to it, which is a good thing. There are also a handful of other external changes from the original PinePhone’s design. I’ll omit the big and obvious things that you can read about on the [PinePhone Pro’s main page](http://pine64.org/pinephonepro), and instead focus on some tiny details I previously omitted to mention. The thermal pad on the back case is much larger and appears to distribute the heat well. The battery is different and is labeled with the new phone model. The sim card and SD slot are slightly different as are the buttons at the leading edge of the phone (they have a more distinct actuation point). Lastly, the WiFi / BT antenna layout on the midframe has been altered for 5GHz connectivity.  +Returning to the subject of the hardware, I have a few observations that pictures or renders cannot convey. The panel is really bright and the colours are rich; the vibration motor is much more powerful than on the original PinePhone; 5Ghz WiFi connectivity has been exceptionally good even when compared with my 2 year old flagship Android phone; and the phone has some heft to it, which is a good thing. There are also a handful of other external changes from the original PinePhone’s design. I’ll omit the big and obvious things that you can read about on the [PinePhone Pro’s main page](/devices/pinephone_pro/), and instead focus on some tiny details I previously omitted to mention. The thermal pad on the back case is much larger and appears to distribute the heat well. The battery is different and is labeled with the new phone model. The sim card and SD slot are slightly different as are the buttons at the leading edge of the phone (they have a more distinct actuation point). Lastly, the WiFi / BT antenna layout on the midframe has been altered for 5GHz connectivity.  Before moving onto the next topic, the packaging is made out of recycled material, including all of the cardboard and most of the plastics. I know that it matters to many of you in the community, so I felt it is worth a mention.   diff --git a/content/blog/november-update-tuned-in.md b/content/blog/november-update-tuned-in.md index d1081754..ab742d4a 100644 --- a/content/blog/november-update-tuned-in.md +++ b/content/blog/november-update-tuned-in.md @@ -82,11 +82,11 @@ You may have noticed that the PINE64 community website hasn’t received an upda **Pinecil stock will regularly be added throughout November and December** -[PINE64 EU](http://pine64eu.com) is having a full restock this week, with PinePhone, PinePhone Pro, Pinebook Pro PinePower, PineTime, the Pinecil V2 and various accessories available again. The reason why it took longer to restock than in the previous months is related to changes in the customs process - more specifically, the paperwork related to the Low Voltage Directive and Radio Equipment Directive is now more complex. I’ll compensate for this in the future to avoid periods where multiple items are out of stock. The good news is that the store’s stock, bar the Pinecil, should last until Christmas. As for the Pinecil, the first sub-batch will be available immediately on the day of the restock (it is difficult to provide an exact date as I am writing well in advance, but likely on November 15th) following which additional stock will be added on the following dates: November 19, November 24,  November 29, December 4 and December 9  +[PINE64 EU](https://pine64eu.com) is having a full restock this week, with PinePhone, PinePhone Pro, Pinebook Pro PinePower, PineTime, the Pinecil V2 and various accessories available again. The reason why it took longer to restock than in the previous months is related to changes in the customs process - more specifically, the paperwork related to the Low Voltage Directive and Radio Equipment Directive is now more complex. I’ll compensate for this in the future to avoid periods where multiple items are out of stock. The good news is that the store’s stock, bar the Pinecil, should last until Christmas. As for the Pinecil, the first sub-batch will be available immediately on the day of the restock (it is difficult to provide an exact date as I am writing well in advance, but likely on November 15th) following which additional stock will be added on the following dates: November 19, November 24,  November 29, December 4 and December 9  ## Newsflash  -_\[_**_Foreword:_** _This is a new section of the community update and one I’m particularly happy about. Newsflash is effectively a quick descriptive summary of things happening in the project - things which would otherwise not get exposure on the monthly blog. These are often developments which are either too small to warrant their individual section, simply do not fit an existing part of the update, or are not a natural fit for housekeeping. Until now, omission of such news was effectively dictated by the scope and time-constraints of the monthly update. Writing the update takes approximately 5 evenings from start to finish, and this is all the time that can realistically be allocated to the writing process. It is simply impossible to report on everything in the PINE64 realm during such a short time span. As a result, many cool projects and information pertinent to the community was lost in the past. The contents of Newsflash will range from cool community projects and interesting software developments to small announcements by the Pine Store or partner projects. On occasion, I may also include commercial products designed for PINE64 hardware if I find them particularly interesting (as I did this month). Anything goes really, and there is no strict structure or order to this section. I should also mention that we’re really happy to accept contributions to this section - all it takes are a few short lines about what you want to report on and links to further reading. Please ping the mods to have the content spotted and delivered to Marek or me\]_ +**_Foreword:_** _This is a new section of the community update and one I’m particularly happy about. Newsflash is effectively a quick descriptive summary of things happening in the project - things which would otherwise not get exposure on the monthly blog. These are often developments which are either too small to warrant their individual section, simply do not fit an existing part of the update, or are not a natural fit for housekeeping. Until now, omission of such news was effectively dictated by the scope and time-constraints of the monthly update. Writing the update takes approximately 5 evenings from start to finish, and this is all the time that can realistically be allocated to the writing process. It is simply impossible to report on everything in the PINE64 realm during such a short time span. As a result, many cool projects and information pertinent to the community was lost in the past. The contents of Newsflash will range from cool community projects and interesting software developments to small announcements by the Pine Store or partner projects. On occasion, I may also include commercial products designed for PINE64 hardware if I find them particularly interesting (as I did this month). Anything goes really, and there is no strict structure or order to this section. I should also mention that we’re really happy to accept contributions to this section - all it takes are a few short lines about what you want to report on and links to further reading. Please ping the mods to have the content spotted and delivered to Marek or me_ Community member Andrew, going by the handle [RuShan](https://twitter.com/RuShan_EE) on Twitter and @ahall#7894 on Discord, created a light attachment for the Pinecil V2 allowing you to work on projects in dim environments. The ring attachment is fitted at the base of the tip’s shaft where it meets the body of the iron. The ring features two little LEDs which are powered directly from the Pinecil V2 - more specifically from the 4.6V source on the PCB. It looks like a really fun project that could prove quite useful to many in the community - especially those who sometimes use their iron on-the-go. Andrew writes that the light will work with the V1 and V2, albeit the implementation differs on both models. If you want to make this modification yourself then head over to [Andrew’s GitHub](https://github.com/Herushan/Pinecil_LED_Ring) and download the KiCad file. Be warned, however, this voids your warranty. Andrew wrote a very detailed article about the process behind creating this mod, which I am [linking here](https://files.pine64.org/blog/Pinecil_LED_Ring_writeup.pdf) and I encourage you to have a read. diff --git a/content/blog/october-update-introducing-the-pinephone-pro.md b/content/blog/october-update-introducing-the-pinephone-pro.md index 84dfb832..108103b0 100644 --- a/content/blog/october-update-introducing-the-pinephone-pro.md +++ b/content/blog/october-update-introducing-the-pinephone-pro.md @@ -42,7 +42,7 @@ I’d like to thank [JF](https://twitter.com/codingfield), [Alex](https://twitte - KDE turns 25! Happy birthday!  - Good job on the PinePhone Pro launch team! - **PinePhone Pro** - - PinePhone Pro announced - start by reading the [PinePhone Pro website](http://pine64.org/pinephonepro) + - PinePhone Pro announced - start by reading the [PinePhone Pro website](/devices/pinephone_pro/) - Features RK3399S SoC made by Rockchip for to the PinePhone Pro - Ships with 4GB LPDDR4, 128GB eMMC, Gorilla Glass 4™ IPS panel, 13MP main camera, USB 3.0 via USB-C, native video out via USB-C + countless improvements   - Pogo pins & privacy switches are present: the PinePhone Pro is compatible with the keyboard and back cases @@ -79,7 +79,7 @@ Finally, I want to say thank you to our team for doing a great job on the PinePh This month I have the pleasure to introduce the newest member of the PINE64 family - the PinePhone Pro. It is a fast smartphone with premium features, built from the ground up to run mainline Linux operating systems. In anticipation of great interest in the nitty-gritty hardware details, we published a dedicated webpage complete with specifications, availability information, device renders and an extensive FAQ. I strongly suggest you go and read that prior to continuing with this section. Seriously, go read it first. -**PinePhone Pro webpage:** [**https://pine64.org/pinephonepro**](https://pine64.org/pinephonepro) +**PinePhone Pro webpage:** [**https://pine64.org/pinephonepro**](/devices/pinephone_pro/) Instead of reiterating the information on PinePhone Pro’s website, I’ll use this section of the community update to explain why we decided to introduce a more powerful smartphone and discuss some of the key design choices.  diff --git a/content/blog/october-update-pinetime-delays-and-shipping-news.md b/content/blog/october-update-pinetime-delays-and-shipping-news.md index b3975a4c..a722df84 100644 --- a/content/blog/october-update-pinetime-delays-and-shipping-news.md +++ b/content/blog/october-update-pinetime-delays-and-shipping-news.md @@ -37,7 +37,7 @@ On the other hand, (and I have no intention of sugar-coating the situation) thin ##### Pinebook Pro shipping delay detailed explanation -Let me give you a run-down of the events that caused the delay in the shipment of Pinebook Pros to customers. The delay was caused by a series of intertwined events, so it's just appropriate that I list them in chronological order. The first issue we encountered during production was that the Pinebook Pro doesn’t power on with the battery disconnected. This isn’t an issue that will affect the majority of users, but it had to be addressed nonetheless. Finding and implementing a solution (a bypass cable - please see the [engineering notice](http://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf)) set us back a few days.   +Let me give you a run-down of the events that caused the delay in the shipment of Pinebook Pros to customers. The delay was caused by a series of intertwined events, so it's just appropriate that I list them in chronological order. The first issue we encountered during production was that the Pinebook Pro doesn’t power on with the battery disconnected. This isn’t an issue that will affect the majority of users, but it had to be addressed nonetheless. Finding and implementing a solution (a bypass cable - please see the [engineering notice](https://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf)) set us back a few days.   However, the majority of time was lost on the second issue. To understand the problem you first need a little technical background; the RK3399, which is the SOC used in the Pinebook Pro, has a hardwired boot sequence that prioritizes eMMC over SD. This means that, unless the bootloader on the eMMC is altered to seek out bootable SD or USB 2.0/3.0 flash (such as uboot on the Debian + MATE build), the OS residing on eMMC will always boot prior to bootable micro SD or USB 2.0/3.0 flash. diff --git a/content/blog/rockpro64-cluster-move-june-5-10.md b/content/blog/rockpro64-cluster-move-june-5-10.md index bf33a401..3c092b89 100644 --- a/content/blog/rockpro64-cluster-move-june-5-10.md +++ b/content/blog/rockpro64-cluster-move-june-5-10.md @@ -23,7 +23,7 @@ In practice, this means that at different times during this move key parts of th I'll do my best to give you a heads-up when portions of the system are scheduled to go down for maintenance on [Twitter](https://twitter.com/thepine64) and [Mastodon](https://fosstodon.org/@PINE64). I'll also issue notices in the [news section](https://forum.pine64.org/forumdisplay.php?fid=2) of the forums. -Lastly, I'd like to note that the [PINE store](https://pine64.com/) and [ticket filing system](http://support.pine64.org), as well as our info and support emails will remain operational though the entire server move. +Lastly, I'd like to note that the [PINE store](https://pine64.com/) and [ticket filing system](https://support.pine64.org), as well as our info and support emails will remain operational though the entire server move. Thank you in advance for your patience. diff --git a/content/blog/september_2024.md b/content/blog/september_2024.md index ccc3531b..5c90d0e9 100644 --- a/content/blog/september_2024.md +++ b/content/blog/september_2024.md @@ -345,7 +345,7 @@ Pine64 has a line of LoRa boards under the "PineDio" name which unfortunately la We are looking for people interested in Meshtastic and LoRa to help with the PineDio USB Adapter as it needs a stable driver for users to easily use the device. -If you're interested please come visit the [Pine64 LoRa channels](https://pine64.org/community/) or join the [Meshtastic Discord server](https://discord.com/invite/ktMAKGBnBs). +If you're interested please come visit the [Pine64 LoRa channels](/community/) or join the [Meshtastic Discord server](https://discord.com/invite/ktMAKGBnBs). ## Community Updates diff --git a/content/blog/taking-retoemulation-to-the-next-level-with-rockpro64-and-roshambo.md b/content/blog/taking-retoemulation-to-the-next-level-with-rockpro64-and-roshambo.md index 3afd5c38..7d53ee0a 100644 --- a/content/blog/taking-retoemulation-to-the-next-level-with-rockpro64-and-roshambo.md +++ b/content/blog/taking-retoemulation-to-the-next-level-with-rockpro64-and-roshambo.md @@ -93,7 +93,7 @@ If you want to learn more about RetroGaming on a RockPro64, Rock64, or even othe ### Useful Links and Resources -[Subreddit: /r/sbcgaming](http://www.reddit.com/r/sbcgaming) +[Subreddit: /r/sbcgaming](https://www.reddit.com/r/sbcgaming) [/r/sbcgaming Discord](https://discord.gg/5dSUjmk) diff --git a/content/blog/update-new-hacktober-gear.md b/content/blog/update-new-hacktober-gear.md index 5ea7126f..1dcdf9bd 100644 --- a/content/blog/update-new-hacktober-gear.md +++ b/content/blog/update-new-hacktober-gear.md @@ -65,7 +65,7 @@ There are a handful of important housekeeping topics to discuss this month. For Seeing as I know someone will ask about this; we are still working towards a cryptocurrency payment arrangement that would work well for us and our community members. We are talking to multiple parties and trying to find some sustainable arrangement - I hope that one can be reached in the coming weeks.  -As many of you have noticed, the Pine Store has also moved to a dedicated .com domain - [pine64.com](http://pine64.com) - from its previous subdomain at _store.pine64.org_. The purpose of moving the store to a commercial domain is to denote its separation from all community-run services and subdomains at [pine64.org](https://www.pine64.org/). We hope that this will help distinguish the two sides of PINE64 - that of a business and a community run project.  +As many of you have noticed, the Pine Store has also moved to a dedicated .com domain - [pine64.com](https://pine64.com) - from its previous subdomain at _store.pine64.org_. The purpose of moving the store to a commercial domain is to denote its separation from all community-run services and subdomains at [pine64.org](https://www.pine64.org/). We hope that this will help distinguish the two sides of PINE64 - that of a business and a community run project.  I’ve also been working towards setting up a dedicated European Pine Store for a couple of months. Under normal circumstances the process would be relatively trivial, but unfortunately current travel restrictions are making it difficult to complete all formalities involved with getting this off the ground. Without getting into unnecessary detail - the store will be registered in a different EU country to where I reside, and physical presence is required to complete portions of the paperwork submissions. Given current travel restrictions in Europe, I think it will be a couple of months before I get everything sorted - I’ll make sure you know when it is all ready to go. diff --git a/content/blog/welcome-new-community-members.md b/content/blog/welcome-new-community-members.md index 916111d4..5e063b02 100644 --- a/content/blog/welcome-new-community-members.md +++ b/content/blog/welcome-new-community-members.md @@ -47,7 +47,7 @@ For more general information about Manjaro Linux distribution please see:  Manjaro is just one of many options at your disposal. The Pinebook Pro is able to run a vast number of other Linux and BSD operating systems, which can be booted from a SD card or installed to internal flash storage instead of Manjaro. For instance, you can boot Recalbox from SD (or USB) for recreation and retro gaming while keeping your full operating system on the Pinebook Pro’s internal flash storage.  -You can find an [up-to-date list of available operating systems](https://wiki.pine64.org/index.php/Pinebook_Pro_Software_Release) on [PINE64 Wiki](http://wiki.pine64.org).   +You can find an [up-to-date list of available operating systems](https://wiki.pine64.org/index.php/Pinebook_Pro_Software_Release) on [PINE64 Wiki](https://wiki.pine64.org).   The [Pinebook Pro sub-section](https://wiki.pine64.org/index.php/Pinebook_Pro) of the [PINE64 Wiki](https://wiki.pine64.org/index.php/Main_Page) also contains a wide variety of information concerning the laptop’s hardware, including:  @@ -61,7 +61,8 @@ The greatest resource we have to offer, however, is our community. There are lit Here are your options: -- [Forum](http://forum.pine64.org) +- [Forum](- [Forum](https://forum.pine64.org) +) - [Official Reddit](https://www.reddit.com/r/PINE64official/) - [IRC Webchat](https://www.pine64.org/web-irc/) - [Telegram](https://t.me/mtx_pinebook) @@ -85,7 +86,7 @@ For general news and to follow ongoing development: Although this Community Edition ships with Ubuntu Touch, you can use many different mobile OSes on your device. Most if not all well established Linux-based systems are represented on the PinePhone so there are plenty of options to choose from. You can give any - or all - of them a risk-free spin by booting from a SD card.  -You can find an [up-to-date list of operating systems](https://wiki.pine64.org/index.php/PinePhone_Software_Releases) on [PINE64 Wiki](http://wiki.pine64.org) +You can find an [up-to-date list of operating systems](https://wiki.pine64.org/index.php/PinePhone_Software_Releases) on [PINE64 Wiki](https://wiki.pine64.org) The [PinePhone sub-section](https://wiki.pine64.org/index.php/PinePhone) of the Wiki is a valuable community maintained information hub which, amongst others, includes: diff --git a/content/documentation/Accessories/Accessories_Step_by_Step_Guides.md b/content/documentation/Accessories/Accessories_Step_by_Step_Guides.md index 46559c6d..eaf6c8b7 100644 --- a/content/documentation/Accessories/Accessories_Step_by_Step_Guides.md +++ b/content/documentation/Accessories/Accessories_Step_by_Step_Guides.md @@ -13,11 +13,11 @@ Accessories Step by Step Guides ## Wi-Fi/Bluetooth module: -* [Step by Step Installation Guide](http://files.pine64.org/doc/guide/PINE64_Wi-Fi_Bluetooth_Installation_Guide.pdf) +* [Step by Step Installation Guide](https://files.pine64.org/doc/guide/PINE64_Wi-Fi_Bluetooth_Installation_Guide.pdf) ## Acrylic Open Enclosure: -* [Step by Step Installation Guide](http://files.pine64.org/doc/guide/PINE64_Acrylic_Open_Enclosure_Installation_Guide.pdf) +* [Step by Step Installation Guide](https://files.pine64.org/doc/guide/PINE64_Acrylic_Open_Enclosure_Installation_Guide.pdf) If you wish to stack two or more of these enclosures, the screws that serve as feet can be replaced by M8-1.25x16mm grub screws. @@ -29,24 +29,24 @@ Images: https://imgur.com/a/Zka1qfb ## Simple 3D Printed Case by Harlandraka -* [3D printing schematics](http://www.thingiverse.com/thing:1831345) +* [3D printing schematics](https://www.thingiverse.com/thing:1831345) ## Sliding 3D Printed Case by Harlandraka -* [3D printing schematics](http://www.thingiverse.com/thing:1694943) +* [3D printing schematics](https://www.thingiverse.com/thing:1694943) ## C4 Labs Case for the Pine -* [Forum thread including instructions](http://forum.pine64.org/showthread.php?tid=2277) +* [Forum thread including instructions](https://forum.pine64.org/showthread.php?tid=2277) ## 7" LCD Touch Screen Panel: -* [Step by Step Installation Guide](http://files.pine64.org/doc/guide/PINE64_7_inches_LCD_Touch_Screen_Panel_Installation_Guide.pdf) +* [Step by Step Installation Guide](https://files.pine64.org/doc/guide/PINE64_7_inches_LCD_Touch_Screen_Panel_Installation_Guide.pdf) ## Real Time Clock (RTC) battery holder (AAA battery type): -* [Step by Step Installation Guide](http://files.pine64.org/doc/guide/PINE64_RTC_Backup_Battery_AAA_Installation_Guide.pdf) +* [Step by Step Installation Guide](https://files.pine64.org/doc/guide/PINE64_RTC_Backup_Battery_AAA_Installation_Guide.pdf) ## Real Time Clock (RTC) battery holder (CR-2032 Coin Cell battery type): -* [Step by Step Installation Guide](http://files.pine64.org/doc/guide/PINE64_RTC_Backup_Battery_CR2032_Installation_Guide.pdf) +* [Step by Step Installation Guide](https://files.pine64.org/doc/guide/PINE64_RTC_Backup_Battery_CR2032_Installation_Guide.pdf) diff --git a/content/documentation/Accessories/Cases/NASCase.md b/content/documentation/Accessories/Cases/NASCase.md index d2758acf..6faf0ffa 100644 --- a/content/documentation/Accessories/Cases/NASCase.md +++ b/content/documentation/Accessories/Cases/NASCase.md @@ -11,7 +11,7 @@ menu: The PINE64 NAS Case is intended for either a Network Attached Storage (NAS) or Desktop application, but it can also be used in a number of other server capacities. It is built from precision-cut and powder-coated aluminum. The physical dimensions are 232.4mm (Width) x 105.0mm (Height) x 145.2mm (Depth). -An exploded view of the NAS Case, illustrating how all the components come together, can be found [here](http://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf). Please refer back to this PDF document during assembly to verify correct orientation of individual components. +An exploded view of the NAS Case, illustrating how all the components come together, can be found [here](https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf). Please refer back to this PDF document during assembly to verify correct orientation of individual components. {{< figure src="/documentation/images/NASCaseMain.png" title="Front View of the PINE64 NAS Case for the ROCKPro64" width="400" >}} @@ -80,7 +80,7 @@ To download the latest OMV build OR one of the numerous available Linux Distribu ## Step-by-Step Assembly Instructions -If you prefer a video tutorial or just want an overview of the process before you start [check out this instructional video](http://www.youtube.com/watch?v=_UeeklKo0Og). +If you prefer a video tutorial or just want an overview of the process before you start [check out this instructional video](https://www.youtube.com/watch?v=_UeeklKo0Og). ### Step 1. Preparation of the NAS Case for Installation diff --git a/content/documentation/Accessories/Wifi_remote_i2c.md b/content/documentation/Accessories/Wifi_remote_i2c.md index f955c58f..38c1a22f 100644 --- a/content/documentation/Accessories/Wifi_remote_i2c.md +++ b/content/documentation/Accessories/Wifi_remote_i2c.md @@ -31,8 +31,7 @@ Place the jumper J2 on USB/UART Programming/Console Adapter (PMPROG01) to 5V out {{< figure src="/documentation/images/Wr_Termite2.JPG" title="Termite Setup Screen" >}} {{< figure src="/documentation/images/Wr_cfghelp_scr.JPG" title="Help Command" >}} -* For windows system, you can use terminal emulator program Termite to configure the device. -* Termite can be downloaded at [CompuPhase Website ](http://www.compuphase.com/software_termite.htm) +* For windows system, you can use terminal emulator program _Termite_ to configure the device. * Make sure the 'Port' setting is refer to the USB/UART Programming/Console Adapter (PMPROG01)'s Virtual Comm Port. * Follow the setting according to the setup screen capture. (57600Baud 8-N-1) * Once Termite configuration is done, press 'OK' to save the setting. @@ -113,7 +112,7 @@ Place the jumper J2 on USB/UART Programming/Console Adapter (PMPROG01) to 5V out ### Software Setup * Download the firmware from the [download section](/documentation/Accessories/Wifi_remote_i2c#download) and unzip the file. -* Download the windows Python base Flash Download Tools by Espressif from [Espressif website](http://espressif.com/en/products/hardware/esp8266ex/resources). +* Download the windows Python base Flash Download Tools by Espressif from [Espressif website](https://espressif.com/en/products/hardware/esp8266ex/resources). * Setup the ESP Flash Download tools according to the screen short. {{< figure src="/documentation/images/Esp_prog_tool.JPG" width="400" >}} @@ -139,19 +138,19 @@ Place the jumper J2 on USB/UART Programming/Console Adapter (PMPROG01) to 5V out ### Program/Driver * [Termite a simple RS232 terminal](http://www.compuphase.com/software_termite.htm) -* [Flash Download Tools v2.4](http://espressif.com/en/products/hardware/esp8266ex/resources) Under Tools Section +* [Flash Download Tools v2.4](https://espressif.com/en/products/hardware/esp8266ex/resources) Under Tools Section * [Silicon Lab CP2102 Virtual COM Port Driver](https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx) -* [WifiAppDemo.gz](http://files.pine64.org/doc/POT/WifiAppDemo.gz) -* [PineWifiServer.gz](http://files.pine64.org/doc/POT/PineWifiServer.gz) -* [PMWF01A Firmware](http://files.pine64.org/doc/POT/PMWF01A%20Firmware.zip) -* [PMWF01A Firmware Source](http://files.pine64.org/doc/POT/PMWF01A%20Firmware%20Source.zip) -* [PineWifiRemoteI2c Server Source.tar.gz](http://files.pine64.org/doc/POT/PineWifiRemoteI2c%20Server%20Source.tar.gz) +* [WifiAppDemo.gz](https://files.pine64.org/doc/POT/WifiAppDemo.gz) +* [PineWifiServer.gz](https://files.pine64.org/doc/POT/PineWifiServer.gz) +* [PMWF01A Firmware](https://files.pine64.org/doc/POT/PMWF01A%20Firmware.zip) +* [PMWF01A Firmware Source](https://files.pine64.org/doc/POT/PMWF01A%20Firmware%20Source.zip) +* [PineWifiRemoteI2c Server Source.tar.gz](https://files.pine64.org/doc/POT/PineWifiRemoteI2c%20Server%20Source.tar.gz) ### Datasheet/Related Information * [TE PCJ-105D3M Relay Datasheet](http://www.te.com/commerce/DocumentDelivery/DDEController?Action=srchrtrv&DocNm=PCJ_series_relay_data_sheet_E&DocType=DS&DocLang=EN) * [ESP8266 Datasheet](https://drive.google.com/file/d/0B0cEs0lxTtL3SDdCcWd0LVI2bk0/view?usp=sharing) * [ESP8266 forum](http://bbs.espressif.com/) -* [ESP8266 Flash Download Tools, Please refer to the Tools section](http://espressif.com/en/products/hardware/esp8266ex/resources) -* [ESP8266 Resources](http://espressif.com/en/products/hardware/esp8266ex/resources) +* [ESP8266 Flash Download Tools, Please refer to the Tools section](https://espressif.com/en/products/hardware/esp8266ex/resources) +* [ESP8266 Resources](https://espressif.com/en/products/hardware/esp8266ex/resources) * [CP2102 Datasheet](https://www.silabs.com/Support%20Documents/TechnicalDocs/CP2102-9.pdf) diff --git a/content/documentation/General/Android_SDK_for_RK3566.md b/content/documentation/General/Android_SDK_for_RK3566.md index 803d9cd8..d1d51ab3 100644 --- a/content/documentation/General/Android_SDK_for_RK3566.md +++ b/content/documentation/General/Android_SDK_for_RK3566.md @@ -17,7 +17,7 @@ Two Android SDKs are available from Pine64 for RK3566 devices: For Quartz64 model A SBC and SOQuartz -* [Direct Download from pine64.org](http://files.pine64.org/SDK/Quartz64/QUARTZ64_SDK_android11.tar.gz) +* [Direct Download from pine64.org](https://files.pine64.org/SDK/Quartz64/QUARTZ64_SDK_android11.tar.gz) * MD5 (TAR-GZip file): 77c2ff57ea3372fb04da7fb49e17d12b * File Size: 79.00GB * Just the boot blobs (<1MB): https://wiki.pine64.org/wiki/File:Rk35-blobs.tar.gz @@ -29,7 +29,7 @@ For Quartz64 model A SBC and SOQuartz For PineNote and Quart64 model A SBC -* [Direct Download from pine64.org](http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz) +* [Direct Download from pine64.org](https://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz) * MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672 * File Size: 72.88GB * Just the boot blobs (<1MB): https://wiki.pine64.org/wiki/File:Rk35-blobs.tar.gz diff --git a/content/documentation/General/Mali_driver.md b/content/documentation/General/Mali_driver.md index f470ea0f..e5e1b679 100644 --- a/content/documentation/General/Mali_driver.md +++ b/content/documentation/General/Mali_driver.md @@ -15,13 +15,13 @@ Here is the DRM video presentation by Free Electron: https://www.youtube.com/wat ## Wayland MALI Driver -* [MALI-400 R6P2 Kernel Mode Setting binary download](http://files.pine64.org/doc/MALI/mali400-r6p2-01rel0-km-003.tar.7z) (1.86MB, MD5 _523276872A9A11D1831ACE42F95DBBB1_) -* [MALI-400 R6P2 WAYLAND 64-bit binary driver and binary download](http://files.pine64.org/doc/MALI/mali400-r6p2-01rel0-um009-wayland.tar.bz2) (179KB, MD5 _1698E8C54BDC6FE0804699F545FFE793_) +* [MALI-400 R6P2 Kernel Mode Setting binary download](https://files.pine64.org/doc/MALI/mali400-r6p2-01rel0-km-003.tar.7z) (1.86MB, MD5 _523276872A9A11D1831ACE42F95DBBB1_) +* [MALI-400 R6P2 WAYLAND 64-bit binary driver and binary download](https://files.pine64.org/doc/MALI/mali400-r6p2-01rel0-um009-wayland.tar.bz2) (179KB, MD5 _1698E8C54BDC6FE0804699F545FFE793_) ## X11 MALI Driver -* [MALI EULA document](http://files.pine64.org/doc/MALI/MALI%20EULA.pdf) -* [MALI-400 64-bit binary driver and binary download](http://files.pine64.org/doc/MALI/x11_pine.tar.bz2) from _pine64.org_ (1.7MB, MD5 _4F56AE6FB793E7D946867942AF58FEAC_) +* [MALI EULA document](https://files.pine64.org/doc/MALI/MALI%20EULA.pdf) +* [MALI-400 64-bit binary driver and binary download](https://files.pine64.org/doc/MALI/x11_pine.tar.bz2) from _pine64.org_ (1.7MB, MD5 _4F56AE6FB793E7D946867942AF58FEAC_) ## X11 Notice diff --git a/content/documentation/PINE_H64_Model_B/Software/Releases.md b/content/documentation/PINE_H64_Model_B/Software/Releases.md index a81787b1..e21f0552 100644 --- a/content/documentation/PINE_H64_Model_B/Software/Releases.md +++ b/content/documentation/PINE_H64_Model_B/Software/Releases.md @@ -85,7 +85,7 @@ Notes: Download: -* [Direct download latest release build from NetBSD by select PINE H64](http://www.armbsd.org/) +* [Direct download latest release build from NetBSD by select PINE H64](https://nycdn.netbsd.org/pub/arm/) Notes: diff --git a/content/documentation/Phone_Accessories/Keyboard.md b/content/documentation/Phone_Accessories/Keyboard.md index 58e50eea..56eb7347 100644 --- a/content/documentation/Phone_Accessories/Keyboard.md +++ b/content/documentation/Phone_Accessories/Keyboard.md @@ -28,7 +28,7 @@ The keyboard case works with both the PinePhone and PinePhone Pro and features a You do not lose access to the PinePhone (Pro)’s USB-C port, speaker, microphone, or any external features, such as volume and lock buttons, with the keyboard attached. There is also a cut-out for the camera, torch, and headphone jack. The USB-C port on the keyboard is capable of powering both the keyboard and PinePhone (Pro) simultaneously. This means that you can plug in a USB-C charger into the keyboard to charge the keyboard’s internal battery, while the PinePhone (Pro) is charging via the internal connection between phone and keyboard. {{< admonition type="warning" >}} - Do not plug in a charger into the keyboard and the phone at the same time. Using the USB-C port of the PinePhone (Pro) while a charger to is connected to the USB-C port of the keyboard is also discouraged for the same reason. Technical details regarding the issue can be found in the blog post of the developer _megi_ [here](http://xnux.eu/log/072.html), in [this](https://www.pine64.org/2022/05/31/may-update-worth-the-wait/) blog post and the safety section. + Do not plug in a charger into the keyboard and the phone at the same time. Using the USB-C port of the PinePhone (Pro) while a charger to is connected to the USB-C port of the keyboard is also discouraged for the same reason. Technical details regarding the issue can be found in the blog post of the developer _megi_ [here](https://xnux.eu/log/072.html), in [this](https://www.pine64.org/2022/05/31/may-update-worth-the-wait/) blog post and the safety section. {{< /admonition >}} Please keep in mind that the keyboard case transforms the PinePhone (Pro) into a PDA, which means that taking calls will likely prove awkward without a wired or wireless headset connected (try speakerphone button if available). @@ -72,7 +72,7 @@ For any software issue please see the [Software support section](/documentation/ ## Safety -Do not plug in a charger into the keyboard and the phone at the same time. Doing so may result in damage or loss of the keyboard charging functionality. Using the USB-C port of the PinePhone (Pro) while a charger to is connected to the USB-C port of the keyboard is also discouraged for the same reason. Technical details regarding the issue can be found in the blog post of the developer _megi_ [here](http://xnux.eu/log/072.html) and [this](https://www.pine64.org/2022/05/31/may-update-worth-the-wait/) blog post. +Do not plug in a charger into the keyboard and the phone at the same time. Doing so may result in damage or loss of the keyboard charging functionality. Using the USB-C port of the PinePhone (Pro) while a charger to is connected to the USB-C port of the keyboard is also discouraged for the same reason. Technical details regarding the issue can be found in the blog post of the developer _megi_ [here](https://xnux.eu/log/072.html) and [this](https://www.pine64.org/2022/05/31/may-update-worth-the-wait/) blog post. Please note: Only use mild isopropyl alcohol when wiping down the clamshell of the device. Stronger solutions may partially strip the coatings. Do not lube the keyboard with GPL 205G0 switch grease, it can cause problems with the key responsiveness and tactility. @@ -138,7 +138,7 @@ but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See GNU General Public License for more details. -GNU General Public License http://www.gnu.org/licenses/ +GNU General Public License https://www.gnu.org/licenses/ ``` ## Hardware diff --git a/content/documentation/PineNote/Development/Flashing.md b/content/documentation/PineNote/Development/Flashing.md index 5ce6bf47..4444ed9e 100644 --- a/content/documentation/PineNote/Development/Flashing.md +++ b/content/documentation/PineNote/Development/Flashing.md @@ -47,7 +47,7 @@ sudo udevadm control --reload ## Entering Maskrom/Rockusb mode -Interfacing with the PineNote over USB using `rkdeveloptool` requires first booting the PineNote into [an alternative operating mode](http://opensource.rock-chips.com/wiki_Rockusb) called Maskrom or Rockusb mode. +Interfacing with the PineNote over USB using `rkdeveloptool` requires first booting the PineNote into [an alternative operating mode](https://opensource.rock-chips.com/wiki_Rockusb) called Maskrom or Rockusb mode. ### Possible methods diff --git a/content/documentation/PineNote/Development_efforts.md b/content/documentation/PineNote/Development_efforts.md index 70403752..b645403c 100644 --- a/content/documentation/PineNote/Development_efforts.md +++ b/content/documentation/PineNote/Development_efforts.md @@ -23,7 +23,7 @@ The following page discusses the development efforts for the PineNote: * [RK3566 EBC Reverse-Engineering](/documentation/General/RK3566_EBC_reverse-engineering) for the EBC (eInk Panel) driver. * [PineNote Development/Building Kernel](/documentation/PineNote/Development/Building_kernel) * BSP Linux SDK version 4.19 for the PineNote and [Quartz64 Model A](/documentation/Quartz64): - * [Direct download](http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz) from _pine64.org_ (32.67GB, MD5 of the TAR-GZip file _24554419aec29700add97167a3a4c9ed_) + * [Direct download](https://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz) from _pine64.org_ (32.67GB, MD5 of the TAR-GZip file _24554419aec29700add97167a3a4c9ed_) * [Mirror by mwfc](https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz) * An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [here](https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent) (100GB). @@ -45,7 +45,7 @@ Android 11 e-ink SDK for the PineNote and Quartz64 Model A. This is the Android Download: -* [Direct download](http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz) from _pine64.org_ (72.88GB, MD5 of the TAR-GZip file _293a550584298de4fb95ceae18103672_) +* [Direct download](https://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz) from _pine64.org_ (72.88GB, MD5 of the TAR-GZip file _293a550584298de4fb95ceae18103672_) * [Mirror by mwfc](https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz) * An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [here](https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent) (100GB). * Just the boot blobs (<1MB): https://wiki.pine64.org/wiki/File:Rk35-blobs.tar.gz @@ -70,7 +70,7 @@ The following topics have resolved: * **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. -* **How will I install software to the PineNote?** This is a hardware and software question. If the software on your PineNote is completely broken and cannot boot to a recoverable state, a Hall (magnet) sensor was fitted to the PineTab motherboard as U9009. This sensor is attached to SARADC_VIN0_KEY/RECOVERY on the RK3566. With the device powered off, and screen face down, holding a magnet over U9009 and plugging in a USB-C cable causes the device to boot into ["rockusb"](http://opensource.rock-chips.com/wiki_Rockusb) flash mode. With proper flashing software and drivers, it should be possible to load a new operating system using rockusb if the system is soft-bricked. Of course, software vendors will need to be more careful with flashing firmware and providing useful "recovery" options on this device due to this process’s relative difficulty to other PINE64 devices. +* **How will I install software to the PineNote?** This is a hardware and software question. If the software on your PineNote is completely broken and cannot boot to a recoverable state, a Hall (magnet) sensor was fitted to the PineTab motherboard as U9009. This sensor is attached to SARADC_VIN0_KEY/RECOVERY on the RK3566. With the device powered off, and screen face down, holding a magnet over U9009 and plugging in a USB-C cable causes the device to boot into ["rockusb"](https://opensource.rock-chips.com/wiki_Rockusb) flash mode. With proper flashing software and drivers, it should be possible to load a new operating system using rockusb if the system is soft-bricked. Of course, software vendors will need to be more careful with flashing firmware and providing useful "recovery" options on this device due to this process’s relative difficulty to other PINE64 devices. ### Unresolved issues diff --git a/content/documentation/PineNote/Further_information/Datasheets.md b/content/documentation/PineNote/Further_information/Datasheets.md index 31d7ecdf..4f91e95a 100644 --- a/content/documentation/PineNote/Further_information/Datasheets.md +++ b/content/documentation/PineNote/Further_information/Datasheets.md @@ -41,7 +41,7 @@ WiFi/BT module information: G Sensor information: -* [Silan SC7A20 3-Axis MEMS Accelerometer](http://www.silan.com.cn/en/product/details/47.html#app01) +* [Silan SC7A20 3-Axis MEMS Accelerometer](https://www.silan.com.cn/en/product/details/47.html#app01) Audio Amplifier information: diff --git a/content/documentation/PinePhone/Further_information/Components.md b/content/documentation/PinePhone/Further_information/Components.md index e4f8aec6..b011bce7 100644 --- a/content/documentation/PinePhone/Further_information/Components.md +++ b/content/documentation/PinePhone/Further_information/Components.md @@ -59,14 +59,14 @@ Note: The title of this schematic page should be changed from "LPDDR3 FPGA178" t DU1: -* Artmem [ATL3A1632H12A](http://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf) 2GB 800MHz LPDDR3-1600 SDRAM, FBGA-178 11.0x11.5x0.93 mm +* Artmem [ATL3A1632H12A](https://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf) 2GB 800MHz LPDDR3-1600 SDRAM, FBGA-178 11.0x11.5x0.93 mm * Note: RAM will be clocked slower, since the Allwinner A64 only supports up to 3GB DDR3-1333 (666.5MHz) and doesn’t specify the top supported LPDDR3 speed. ### P.5 CPU U1: -* Allwinner [A64](http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf) 1.2Ghz 4x Cortex-A53, 64-bit, superscalar, 32KB instruction & 32KB data L1 cache per core, 512KB L2 shared cache, ARM Mali-400 MP2 (Utgard) GPU, HDMI 1.4 (up to 4K@30), USB 2.0 with OTG, MIPI CSI, 4 channels in/out, 24-bit, 8-48 KHz audio, video encode: H.264 1080p@60, video decode: H.265 4K@30, H.265 1080p@120, H.264, MPEG1/2/4 / VP8 / AVS / AVS+ 1080p@60, FBGA-396 15x15 mm +* Allwinner [A64](https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf) 1.2Ghz 4x Cortex-A53, 64-bit, superscalar, 32KB instruction & 32KB data L1 cache per core, 512KB L2 shared cache, ARM Mali-400 MP2 (Utgard) GPU, HDMI 1.4 (up to 4K@30), USB 2.0 with OTG, MIPI CSI, 4 channels in/out, 24-bit, 8-48 KHz audio, video encode: H.264 1080p@60, video decode: H.265 4K@30, H.265 1080p@120, H.264, MPEG1/2/4 / VP8 / AVS / AVS+ 1080p@60, FBGA-396 15x15 mm * Note: Clocked at 1.152Ghz on the PinePhone. X501: @@ -119,7 +119,7 @@ D600: U700: -* Kimtigo [KM110SS0016GxA-DDD00WT](http://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf) 16GB eMMC 5.1 TLC NAND Flash memory, FBGA-153 11.5×13.0×1.0 mm. +* Kimtigo [KM110SS0016GxA-DDD00WT](https://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf) 16GB eMMC 5.1 TLC NAND Flash memory, FBGA-153 11.5×13.0×1.0 mm. * Note 1: The schematic says the package is BGA-169, but the Kimtigo documentation says it is FBGA-153. * Note 2: The A64 only supports up to eMMC 5.0. * Note 3: The schematic lists the part as KM110SS0016GxA-DDD00WT, but [these photos](https://xnux.eu/devices/photos/pp-1.1.html) show that its variant, the KM111SS0016GxA-DDD00WT, is being used in the 16GB PinePhone. @@ -173,12 +173,12 @@ J901: J1000: * T03-1025-FG01 27-pin connector to the rear camera. -* Note: The schematic says "GC2035-200W", which is a mistake because the rear camera is the OmniVision [OV6540](http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf). +* Note: The schematic says "GC2035-200W", which is a mistake because the rear camera is the OmniVision [OV6540](https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf). J1001: * T03-1025-FG01 27-pin connector to the front camera. -* Note: The schematic says "GC2035-200W", which is a mistake because the rear camera is the GalaxyCore [GC2145](http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf), not the GalaxyCore [GC2035](https://g2g9w6w7.stackpathcdn.com/pdf-down/G/C/2/GC2035-GalaxyCore.pdf). +* Note: The schematic says "GC2035-200W", which is a mistake because the rear camera is the GalaxyCore [GC2145](https://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf), not the GalaxyCore [GC2035](https://g2g9w6w7.stackpathcdn.com/pdf-down/G/C/2/GC2035-GalaxyCore.pdf). U1000: @@ -207,7 +207,7 @@ ED1100, ED1101, ED1102, ED1103: U1100: -* Chipown [AP3127B025](http://www.datasheet39.com/download.php?id=924200) step-up DC/DC converter series, white LED backlight driver, 6-pin SOT-23-6L package. +* Chipown [AP3127B025](https://www.datasheet39.com/download.php?id=924200) step-up DC/DC converter series, white LED backlight driver, 6-pin SOT-23-6L package. ### P.12 SENSORS/MT/KEY @@ -300,7 +300,7 @@ X1300: U1400: -* Realtek [RTL8723CS](http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf) 802.11 b/g/n, single-band (2.4 GHz), Bluetooth 4.0, with SDIO for WiFi and UART for Bluetooth, LGA-40 12x12x1.6 mm. +* Realtek [RTL8723CS](https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf) 802.11 b/g/n, single-band (2.4 GHz), Bluetooth 4.0, with SDIO for WiFi and UART for Bluetooth, LGA-40 12x12x1.6 mm. X1400: @@ -385,6 +385,6 @@ Source: [Amos Batto](https://forums.puri.sm/t/component-counts-in-the-librem-5-a * SGMICRO [SGM3140](http://www.sg-micro.com/uploads/soft/20190829/1567071622.pdf) 500mA buck/boost charge pump LED driver for camera flash and torch, TDFN-10 3x3x0.75 mm * Note: The [PinePhone page](/documentation/PinePhone/Further_information/Components/) lists the SGM3140, but the schematics contain the U1000: awinic AW3641EDNR, so it is unclear why the SGM3140 is needed. -* Goodix [GT917S](http://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf) touch controller -* Sitronix [ST7703](http://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf) MIPI LCD driver +* Goodix [GT917S](https://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf) touch controller +* Sitronix [ST7703](https://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf) MIPI LCD driver * Xingbangda [XBD599](https://lkml.org/lkml/2020/6/16/1654) 5.99″ IPS LCD, 720x1440 pixels, 16.7M colors, hardened glass diff --git a/content/documentation/PinePhone/Further_information/Safety.md b/content/documentation/PinePhone/Further_information/Safety.md index 9fe2716d..24989dc2 100644 --- a/content/documentation/PinePhone/Further_information/Safety.md +++ b/content/documentation/PinePhone/Further_information/Safety.md @@ -21,6 +21,6 @@ The PinePhone supports up to 5V 3A (15W) Quick Charge, it follows the USB Power With the Allwinner A64 being an older generation SoC with a large 40nm chip, the phone produces quite some heat with medium or higher use and especially also during charging or when using USB accessories, like a docking station. Measurements to prevent damage to the phone and to its surroundings need to be taken by the user. This includes especially a proper handling of the phone: do not charge the phone in a way where heat builds up around the phone without being able to escape. Especially don’t charge your phone under a pillow, blankets, in pockets or bags. Charging the phone produces heat and charging the phone in a way, where the excessive heat can’t dispose around the phone poses an immediate fire risk. -The user might notice that the phone gets warm under usage, compared to phones with more up-to-date hardware. Under normal circumstances these temperatures don’t pose a risk while being in the levels within the safe operating temperatures (which lay far beyond the point where components can be too hot to touch). Higher temperatures might especially be experienced on the top side of the screen and on the inside of the phone at the RF shield of the modem. The higher temperature of the RF shield of the modem is commonly caused by the SoC on the opposite side of the mainboard, the RF shield of the modem is used to disperse heat of the SoC. In newer mainboard revisions starting from 1.2a there are also thermal pads on the back cover and between the SoC’s RF shield and the screen, dispersing heat on the screen and on the back cover. In the past there has been safety issues regarding thermal safety functions, causing temperature reads to not properly work over an extended period of time, which was causing heat damage in some cases (see the documentation of that issue by the developer Megous [here](http://xnux.eu/log/#018) and [here](http://xnux.eu/log/#017)). While the developers are working hard to prevent such issues, they can’t be excluded under all circumstances. The users are expected to monitor their phones' thermal safety at every point at this state of the software. +The user might notice that the phone gets warm under usage, compared to phones with more up-to-date hardware. Under normal circumstances these temperatures don’t pose a risk while being in the levels within the safe operating temperatures (which lay far beyond the point where components can be too hot to touch). Higher temperatures might especially be experienced on the top side of the screen and on the inside of the phone at the RF shield of the modem. The higher temperature of the RF shield of the modem is commonly caused by the SoC on the opposite side of the mainboard, the RF shield of the modem is used to disperse heat of the SoC. In newer mainboard revisions starting from 1.2a there are also thermal pads on the back cover and between the SoC’s RF shield and the screen, dispersing heat on the screen and on the back cover. In the past there has been safety issues regarding thermal safety functions, causing temperature reads to not properly work over an extended period of time, which was causing heat damage in some cases (see the documentation of that issue by the developer Megous [here](https://xnux.eu/log/#018) and [here](https://xnux.eu/log/#017)). While the developers are working hard to prevent such issues, they can’t be excluded under all circumstances. The users are expected to monitor their phones' thermal safety at every point at this state of the software. It is highly recommend to update the phone on a regular basis to always get the latest improvements. The default settings to throttle the performance and to shut down the phone when reaching critical temperatures might be set to a too high point depending on the specific usage and usage length. Under GNU/Linux the phone’s thermal management behavior can be modified via the Thermal Sysfs driver to achieve lower temperatures and preventing the screen and other components to potentially take damage, see [Thermal tweaks](/documentation/PinePhone/Software_tricks/Thermal_tweaks) for the details. diff --git a/content/documentation/PinePhone/Further_information/Sensors_and_navigation.md b/content/documentation/PinePhone/Further_information/Sensors_and_navigation.md index 9d14f456..97337cb3 100644 --- a/content/documentation/PinePhone/Further_information/Sensors_and_navigation.md +++ b/content/documentation/PinePhone/Further_information/Sensors_and_navigation.md @@ -69,7 +69,8 @@ TODO: i2cdev, linux-iio, support matrix * /dev/ttyUSB2: AT command interface * /dev/ttyUSB1: default NMEA data output * MPU6050:inv_mpu6050, inv_mpu6050_i2c, industrialio - ``` + +``` iio:device2: mpu6050 (buffer capable) 9 channels found: accel_x: (input, index: 0, format: be:S16/16>>0) diff --git a/content/documentation/PinePhone/Modem/_index.md b/content/documentation/PinePhone/Modem/_index.md index cbab5cd5..b97d21c0 100644 --- a/content/documentation/PinePhone/Modem/_index.md +++ b/content/documentation/PinePhone/Modem/_index.md @@ -13,7 +13,7 @@ The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate ## AT commands -A list of documented AT commands can be found for example in this [AT commands documentation](https://wiki.pine64.org/wiki/File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf) from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi’s website [here](http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands). +A list of documented AT commands can be found for example in this [AT commands documentation](https://wiki.pine64.org/wiki/File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf) from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi’s website [here](https://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands). To send AT commands to the modem under Linux, `minicom` or the often-preinstalled `atinout` utility can be used. diff --git a/content/documentation/PinePhone/Repairs/_index.md b/content/documentation/PinePhone/Repairs/_index.md index ea16f8b0..f873d89d 100644 --- a/content/documentation/PinePhone/Repairs/_index.md +++ b/content/documentation/PinePhone/Repairs/_index.md @@ -230,7 +230,7 @@ There are now a few documented ways, There are hopefully videos coming doing it the proper way, and so they can be linked here. -After this the firmware for the power negotiation chip needs to be upgraded, this can be done by running the factory test image, version http://images.postmarketos.org/pinephone/pine64-pinephone-20200724-factorytest55.img.xz or higher. This will do the firmware flashing and respond with a message indicating the state. After this the phone is ready for its added functions. +After this the firmware for the power negotiation chip needs to be upgraded, this can be done by running the factory test image, version https://images.postmarketos.org/pinephone/pine64-pinephone-20200724-factorytest55.img.xz or higher. This will do the firmware flashing and respond with a message indicating the state. After this the phone is ready for its added functions. ANX states: * No CC Fix - Fix not applied diff --git a/content/documentation/PinePhone/Revisions/PinePhone_v1.1_-_Braveheart.md b/content/documentation/PinePhone/Revisions/PinePhone_v1.1_-_Braveheart.md index fb826e4c..8e32f377 100644 --- a/content/documentation/PinePhone/Revisions/PinePhone_v1.1_-_Braveheart.md +++ b/content/documentation/PinePhone/Revisions/PinePhone_v1.1_-_Braveheart.md @@ -16,7 +16,7 @@ This page contains resources which are exclusive to the 1.1 revision of the Pine ## Schematic -[Hardware schematic](http://files.pine64.org/doc/PinePhone/PinePhone_Schematic_v1.1_20191031.pdf) +[Hardware schematic](https://files.pine64.org/doc/PinePhone/PinePhone_Schematic_v1.1_20191031.pdf) ## Changes from 1.0 diff --git a/content/documentation/PinePhone/Revisions/PinePhone_v1.2.md b/content/documentation/PinePhone/Revisions/PinePhone_v1.2.md index baf16df8..f40acbc3 100644 --- a/content/documentation/PinePhone/Revisions/PinePhone_v1.2.md +++ b/content/documentation/PinePhone/Revisions/PinePhone_v1.2.md @@ -16,7 +16,7 @@ This page contains information and resources which are specific to the UBports C ## Schematics -* [Hardware schematic v1.2](http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf) (2020-03-10, for the UBports Community Edition) +* [Hardware schematic v1.2](https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf) (2020-03-10, for the UBports Community Edition) ## Changes from v1.1 diff --git a/content/documentation/PinePhone/Revisions/PinePhone_v1.2a.md b/content/documentation/PinePhone/Revisions/PinePhone_v1.2a.md index 6639d84f..11ba1a67 100644 --- a/content/documentation/PinePhone/Revisions/PinePhone_v1.2a.md +++ b/content/documentation/PinePhone/Revisions/PinePhone_v1.2a.md @@ -16,7 +16,7 @@ This page contains information and resources which are specific to the v1.2a rev ## Schematics -* [Hardware schematic v1.2a](http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf) (2020-06-08, for the postmarketOS Community Edition) +* [Hardware schematic v1.2a](https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf) (2020-06-08, for the postmarketOS Community Edition) ## Changes from v1.2 diff --git a/content/documentation/PinePhone/Software/Releases.md b/content/documentation/PinePhone/Software/Releases.md index e9640d67..4edfa63a 100644 --- a/content/documentation/PinePhone/Software/Releases.md +++ b/content/documentation/PinePhone/Software/Releases.md @@ -164,7 +164,7 @@ The default user interface stack is [Hildon](https://en.wikipedia.org/wiki/Hildo #### Download -* [Maemo Leste test builds](http://maedevu.maemo.org/images/pinephone/) +* [Maemo Leste test builds](https://maedevu.maemo.org/images/pinephone/) There is also an [image builder](https://github.com/maemo-leste/image-builder), see the wiki for instructions on how to [build a custom image](https://leste.maemo.org/Image_Builder). For current status and instructions, please read their [PinePhone wiki page](https://leste.maemo.org/PinePhone). @@ -250,8 +250,6 @@ This is also a good build for charging depleted battery. Just boot up this build For more info on this build, please visit its entry the "News" section of its [web page](https://xnux.eu/p-boot-demo/). * [Download torrent file from author's website](https://dl.xnux.eu/p-boot-multi-2022-01-26.torrent) -* [Download img.zst from author's website](http://dl.xnux.eu/p-boot-multi-2022-01-26/) (speed limited to 512KiB/s) -* [Download torrent and img.zst from discord user uxes' mirror](http://mirror.uxes.cz/dl.xnux.eu/) ** *File name:* multi.img.zst ** *SHA-256:* 39915b9d2aa2f33fd78552ac9a0e665c4aef97dd68a9f9a6c76f9fa2f0ac049e ** *File Size:* 6.9GiB @@ -284,7 +282,7 @@ Also see [Installation instructions](/documentation/PinePhone/Installation_instr {{< figure src="/documentation/images/nemo_mobile.png" width="100" >}} -Nemo Mobile is the open source build of Sailfish OS with a open source UI called [Glacier](http://nemomobile.net/glacier-home/), [based on Manjaro](http://nemomobile.net/pages/Hello_manjaro/). +Nemo Mobile is the open source build of Sailfish OS with a open source UI called [Glacier](https://nemomobile.net/glacier-home/), [based on Manjaro](https://nemomobile.net/pages/Hello_manjaro/). #### Download @@ -519,7 +517,7 @@ The boot-up OS is upgraded independently from the containers. #### Download -* http://dl.fail.pp.ua/slackware/images/pinephone/ +* https://dl.irradium.org//slackware/images/pinephone/ #### Notes diff --git a/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_battery_charging.md b/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_battery_charging.md index d27aa974..a2ce87b5 100644 --- a/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_battery_charging.md +++ b/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_battery_charging.md @@ -15,7 +15,7 @@ Please note that this Android build solely for PinePhone Pro hardware checking p Download: -* [Direct download](http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz) from _pine64.org_ (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file _214e063c8205c1a98d44b2015a21bb5d_) +* [Direct download](https://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz) from _pine64.org_ (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file _214e063c8205c1a98d44b2015a21bb5d_) Instructions: diff --git a/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_hardware_checking.md b/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_hardware_checking.md index 06653a0a..6d0a73f8 100644 --- a/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_hardware_checking.md +++ b/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_hardware_checking.md @@ -15,7 +15,7 @@ Please note that this Android build solely for PinePhone Pro hardware checking p Download: -* [Direct download](http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz) from _pine64.org_ (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file _214e063c8205c1a98d44b2015a21bb5d_) +* [Direct download](https://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz) from _pine64.org_ (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file _214e063c8205c1a98d44b2015a21bb5d_) Instructions: diff --git a/content/documentation/PinePhone_Pro/Modem.md b/content/documentation/PinePhone_Pro/Modem.md index f8e2771d..78111d9d 100644 --- a/content/documentation/PinePhone_Pro/Modem.md +++ b/content/documentation/PinePhone_Pro/Modem.md @@ -13,7 +13,7 @@ The PinePhone Pro uses Quectel EG25-G as modem. AT commands are used to communic ## AT commands -A list of documented AT commands can be found for example in this [AT commands documentation](https://wiki.pine64.org/wiki/File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf) from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi’s website [here](http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands). +A list of documented AT commands can be found for example in this [AT commands documentation](https://wiki.pine64.org/wiki/File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf) from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi’s website [here](https://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands). To send AT commands to the modem under Linux, `minicom` or the often-preinstalled `atinout` utility can be used. diff --git a/content/documentation/PineTab/Operating_systems.md b/content/documentation/PineTab/Operating_systems.md index 2c4d63ba..bb5f208e 100644 --- a/content/documentation/PineTab/Operating_systems.md +++ b/content/documentation/PineTab/Operating_systems.md @@ -97,7 +97,7 @@ You can get **SailfishOS** on your with the flash-it script, which will write an There is a forum discussion with further information. -http://forum.pine64.org/showthread.php?tid=11850 +https://forum.pine64.org/showthread.php?tid=11850 Many things are still broken but Bluetooth, Audio, Rotation and Keyboard are working. diff --git a/content/documentation/PineTime/FAQ.md b/content/documentation/PineTime/FAQ.md index f6bfcaf2..aef1a55a 100644 --- a/content/documentation/PineTime/FAQ.md +++ b/content/documentation/PineTime/FAQ.md @@ -149,11 +149,11 @@ Yes, use version 9-2020-q2-update of the [Arm Embedded Toolchain arm-none-eabi-g ## What is ARM Semihosting? -We use the SWD (Single Wire Debug) protocol created by ARM for flashing and debugging PineTime’s nRF52832 microcontroller, which contains an ARM CPU. (SWD is derived from standard JTAG, but with fewer wires) With ARM CPUs you can trigger a software breakpoint, and allow the debugger (OpenOCD) to do something really nifty: Display a message, read console input, dump out a file, even read a file. That’s called ARM Semihosting. [More about ARM Semihosting](http://www.keil.com/support/man/docs/armcc/armcc_pge1358787046598.htm) +We use the SWD (Single Wire Debug) protocol created by ARM for flashing and debugging PineTime’s nRF52832 microcontroller, which contains an ARM CPU. (SWD is derived from standard JTAG, but with fewer wires) With ARM CPUs you can trigger a software breakpoint, and allow the debugger (OpenOCD) to do something really nifty: Display a message, read console input, dump out a file, even read a file. That’s called ARM Semihosting. [More about ARM Semihosting](https://developer.arm.com/documentation/dui0375/g/What-is-Semihosting-/What-is-semihosting-) ## What is OpenOCD? -OpenOCD is Open On-Chip Debugger. It’s the software that drives your microcontroller debugger/flasher. We need it for running any kind of flashing and debugging with Pi or ST-Link. gdb talks to OpenOCD for debugging firmware. gdb also works with VSCode for debugging firmware visually. [More about OpenOCD](http://openocd.org/doc-release/html/About.html#What-is-OpenOCD_003f) +OpenOCD is Open On-Chip Debugger. It’s the software that drives your microcontroller debugger/flasher. We need it for running any kind of flashing and debugging with Pi or ST-Link. gdb talks to OpenOCD for debugging firmware. gdb also works with VSCode for debugging firmware visually. [More about OpenOCD](https://openocd.org/doc-release/html/About.html#What-is-OpenOCD_003f) Please use [xPack OpenOCD](https://xpack.github.io/openocd) with PineTime. Other versions of OpenOCD seem to have problems with PineTime. diff --git a/content/documentation/PineTime/Software/Reprogramming.md b/content/documentation/PineTime/Software/Reprogramming.md index ec9ef840..e1581437 100644 --- a/content/documentation/PineTime/Software/Reprogramming.md +++ b/content/documentation/PineTime/Software/Reprogramming.md @@ -67,7 +67,7 @@ Unlocking the device and erase the memory. ## OpenOCD -OpenOCD, the Open On-Chip Debugger supports multiple different adapters. You can read more about it here: http://openocd.org/ +OpenOCD, the Open On-Chip Debugger supports multiple different adapters. You can read more about it here: https://openocd.org/ ### Adapters diff --git a/content/documentation/Pinebook/Service_guides.md b/content/documentation/Pinebook/Service_guides.md index 6b86b724..7871c418 100644 --- a/content/documentation/Pinebook/Service_guides.md +++ b/content/documentation/Pinebook/Service_guides.md @@ -17,12 +17,12 @@ These are instruction guides for the disassembly: 11.6″ Pinebook: -* [Lithium Battery Pack Removal Guide](http://files.pine64.org/doc/pinebook/guide/Pinebook_11.6-Battery_Removal_Guide.pdf) -* [LCD Panel Screen Removal Guide](http://files.pine64.org/doc/pinebook/guide/Pinebook_11.6-Screen_Removal_Guide.pdf) -* [eMMC Module Removal Guide](http://files.pine64.org/doc/pinebook/guide/Pinebook_11.6-eMMC_Removal_Guide.pdf) +* [Lithium Battery Pack Removal Guide](https://files.pine64.org/doc/pinebook/guide/Pinebook_11.6-Battery_Removal_Guide.pdf) +* [LCD Panel Screen Removal Guide](https://files.pine64.org/doc/pinebook/guide/Pinebook_11.6-Screen_Removal_Guide.pdf) +* [eMMC Module Removal Guide](https://files.pine64.org/doc/pinebook/guide/Pinebook_11.6-eMMC_Removal_Guide.pdf) 14″ Pinebook: -* [Lithium Battery Pack Removal Guide](http://files.pine64.org/doc/pinebook/guide/Pinebook_14-Battery_Removal_Guide.pdf) -* [LCD Panel Screen Removal Guide](http://files.pine64.org/doc/pinebook/guide/Pinebook_14-Screen_Removal_Guide.pdf) -* [eMMC Module Removal Removal Guide](http://files.pine64.org/doc/pinebook/guide/Pinebook_14-eMMC_Removal_Guide.pdf) +* [Lithium Battery Pack Removal Guide](https://files.pine64.org/doc/pinebook/guide/Pinebook_14-Battery_Removal_Guide.pdf) +* [LCD Panel Screen Removal Guide](https://files.pine64.org/doc/pinebook/guide/Pinebook_14-Screen_Removal_Guide.pdf) +* [eMMC Module Removal Removal Guide](https://files.pine64.org/doc/pinebook/guide/Pinebook_14-eMMC_Removal_Guide.pdf) diff --git a/content/documentation/Pinebook_Pro/Features/Touchpad.md b/content/documentation/Pinebook_Pro/Features/Touchpad.md index cb50d1d3..9e3faddd 100644 --- a/content/documentation/Pinebook_Pro/Features/Touchpad.md +++ b/content/documentation/Pinebook_Pro/Features/Touchpad.md @@ -25,7 +25,8 @@ If you are having trouble using 2 fingers to scroll or emulate the click of a mo * Individual programs might need to be configured specially. *. For smooth scrolling and gestures under X-Windows, _Firefox_ should be launched with with the following environment variable assignment: - `MOZ_USE_XINPUT2=1` +`MOZ_USE_XINPUT2=1` + * Experiment with other settings, via X-Windows Configuration or some other system preferences. For example, you could disable double-finger scrolling, and instead enable scrolling by sliding one finger along the edge of the touchpad. ## Firmware diff --git a/content/documentation/Pinebook_Pro/Guides/Caring.md b/content/documentation/Pinebook_Pro/Guides/Caring.md index 92da594b..0b8f2bd7 100644 --- a/content/documentation/Pinebook_Pro/Guides/Caring.md +++ b/content/documentation/Pinebook_Pro/Guides/Caring.md @@ -27,8 +27,8 @@ When removing the large RF shield found on the mainboard, for example when short These are self-service instruction guides for the disassembly of the 14-inch Pinebook, but they still almost directly apply to the Pinebook Pro: -* [Lithium Battery Pack Removal Guide](http://files.pine64.org/doc/pinebook/guide/Pinebook_14-Battery_Removal_Guide.pdf) -* [LCD Panel Screen Removal Guide](http://files.pine64.org/doc/pinebook/guide/Pinebook_14-Screen_Removal_Guide.pdf) -* [eMMC Module Removal Removal Guide](http://files.pine64.org/doc/pinebook/guide/Pinebook_14-eMMC_Removal_Guide.pdf) +* [Lithium Battery Pack Removal Guide](https://files.pine64.org/doc/pinebook/guide/Pinebook_14-Battery_Removal_Guide.pdf) +* [LCD Panel Screen Removal Guide](https://files.pine64.org/doc/pinebook/guide/Pinebook_14-Screen_Removal_Guide.pdf) +* [eMMC Module Removal Removal Guide](https://files.pine64.org/doc/pinebook/guide/Pinebook_14-eMMC_Removal_Guide.pdf) Assembling it back requires the described steps to be performed in the reverse order. diff --git a/content/documentation/Pinebook_Pro/Software/Installing_Arch_Linux_ARM.md b/content/documentation/Pinebook_Pro/Software/Installing_Arch_Linux_ARM.md index c5899bbe..7f86d543 100644 --- a/content/documentation/Pinebook_Pro/Software/Installing_Arch_Linux_ARM.md +++ b/content/documentation/Pinebook_Pro/Software/Installing_Arch_Linux_ARM.md @@ -31,7 +31,9 @@ $ tar xf pine64-pinebookPro-2021.10-004.tar.xz Flash Tow-Boot to **/dev/sdb** (replace this with the device you actually intend to use). - # dd if=pine64-pinebookPro-2021.10-004/shared.disk-image.img of=/dev/sdb bs=1M oflag=direct,sync +```console +# dd if=pine64-pinebookPro-2021.10-004/shared.disk-image.img of=/dev/sdb bs=1M oflag=direct,sync +``` This creates the partition table for the device, with the first partition serving to protect Tow-Boot. Do not move or write to this partition. @@ -39,14 +41,16 @@ This creates the partition table for the device, with the first partition servin Use `fdisk` to add partitions to **/dev/sdb**. - # fdisk /dev/sdb +```console +# fdisk /dev/sdb +``` Create the **/boot** partition. * Type **n** to create a new partition. * Press enter for partition number two. * Press enter for the default start sector. -* Type **+256M** to make the new partition 256 MiB. +* Type **+512M** to make the new partition with 512 MiB. Mark the **/boot** partition bootable. @@ -69,28 +73,46 @@ Write the changes to disk. ### Formatting the partitions Format the **/boot** partition as a filesystem supported by your U-Boot. ext4 is recommended: - # mkfs.ext4 /dev/sdb2 + +```console +# mkfs.ext4 /dev/sdb2 +``` Format the root partition as any filesystem supported by Arch Linux ARM. btrfs for example: - # mkfs.btrfs /dev/sdb3 + +```console +# mkfs.btrfs /dev/sdb3 +``` ## Installing the root filesystem ### Mounting the partitions - # mount /dev/sdb3 /mnt - # mkdir /mnt/boot - # mount /dev/sdb2 /mnt/boot + +```console +# mount /dev/sdb3 /mnt +# mkdir /mnt/boot +# mount /dev/sdb2 /mnt/boot +``` ### Downloading and verifying the rootfs tarball Download the tarball and its PGP signature. - $ wget http://os.archlinuxarm.org/os/ArchLinuxARM-aarch64-latest.tar.gz{,.sig} + +```console +$ wget http://os.archlinuxarm.org/os/ArchLinuxARM-aarch64-latest.tar.gz{,.sig} +``` Import the Arch Linux ARM signing key. - $ gpg --keyserver keyserver.ubuntu.com --recv-keys 68B3537F39A313B3E574D06777193F152BDBE6A6 + +```console +$ gpg --keyserver keyserver.ubuntu.com --recv-keys 68B3537F39A313B3E574D06777193F152BDBE6A6 +``` Verify the tarball’s authenticity. - $ gpg --verify ArchLinuxARM-aarch64-latest.tar.gz.sig + +```console +$ gpg --verify ArchLinuxARM-aarch64-latest.tar.gz.sig +``` Verifying the authenticity of the tarball protects you in two ways: @@ -100,45 +122,57 @@ Verifying the authenticity of the tarball protects you in two ways: ### Extracting and configuring the root filesystem #### Extracting the root filesystem - # bsdtar -xpf ArchLinuxARM-aarch64-latest.tar.gz -C /mnt + +```console +# bsdtar -xpf ArchLinuxARM-aarch64-latest.tar.gz -C /mnt +``` #### Editing fstab Find the partitions' UUIDs with `blkid`. - # blkid /dev/sdb3 /dev/sdb2 +```console +# blkid /dev/sdb3 /dev/sdb2 +``` Example output: - /dev/sdb3: UUID="c1ec9712-5c64-46da-852c-9d665416e8a6" UUID_SUB="90e5b654-6967-471a-9d35-8997488b1ba8" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="885dd863-a550-2d47-89dd-f54fd6744ca5" - /dev/sdb2: UUID="21bbff3f-b82e-416e-93c8-e6d44c3daf82" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="be571200-1a56-5d4c-9a5b-88a5f36a295e" +```console +/dev/sdb3: UUID="c1ec9712-5c64-46da-852c-9d665416e8a6" UUID_SUB="90e5b654-6967-471a-9d35-8997488b1ba8" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="885dd863-a550-2d47-89dd-f54fd6744ca5" +/dev/sdb2: UUID="21bbff3f-b82e-416e-93c8-e6d44c3daf82" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="be571200-1a56-5d4c-9a5b-88a5f36a295e" +``` Add the following lines to **/mnt/etc/fstab**, substituting the example UUIDs with those you received from `blkid`. - UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 / btrfs defaults 0 1 - UUID=21bbff3f-b82e-416e-93c8-e6d44c3daf82 /boot ext4 defaults 0 2 +```console +UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 / btrfs defaults 0 1 +UUID=21bbff3f-b82e-416e-93c8-e6d44c3daf82 /boot ext4 defaults 0 2 +``` #### Creating extlinux.conf Create a file **/mnt/boot/extlinux/extlinux.conf** with the following contents, replacing the example UUID with the one for **/dev/sdb3** from `blkid`. - DEFAULT arch - MENU TITLE Boot Menu - PROMPT 0 - TIMEOUT 50 - - LABEL arch - MENU LABEL Arch Linux ARM - LINUX /Image - INITRD /initramfs-linux.img - FDT /dtbs/rockchip/rk3399-pinebook-pro.dtb - APPEND root=UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 rw - - LABEL arch-fallback - MENU LABEL Arch Linux ARM with fallback initramfs - LINUX /Image - INITRD /initramfs-linux-fallback.img - FDT /dtbs/rockchip/rk3399-pinebook-pro.dtb - APPEND root=UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 rw + +```console +DEFAULT arch +MENU TITLE Boot Menu +PROMPT 0 +TIMEOUT 50 + +LABEL arch +MENU LABEL Arch Linux ARM +LINUX /Image +INITRD /initramfs-linux.img +FDT /dtbs/rockchip/rk3399-pinebook-pro.dtb +APPEND root=UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 rw + +LABEL arch-fallback +MENU LABEL Arch Linux ARM with fallback initramfs +LINUX /Image +INITRD /initramfs-linux-fallback.img +FDT /dtbs/rockchip/rk3399-pinebook-pro.dtb +APPEND root=UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 rw +``` ## Booting and finishing setup @@ -146,12 +180,16 @@ Boot into Arch Linux ARM and log in as **root** with password **root**. Initialize the pacman keyring. - # pacman-key --init - # pacman-key --populate archlinuxarm +```console +# pacman-key --init +# pacman-key --populate archlinuxarm +``` For security, change the default passwords for root and the default user **alarm**. - # passwd - # passwd alarm +```console +# passwd +# passwd alarm +``` -Congratulations, you have now installed Arch Linux ARM on your PineBook Pro! +You have now installed Arch Linux ARM on your PineBook Pro. diff --git a/content/documentation/Pinebook_Pro/Software/Tuning.md b/content/documentation/Pinebook_Pro/Software/Tuning.md index baea2e7e..50693af8 100644 --- a/content/documentation/Pinebook_Pro/Software/Tuning.md +++ b/content/documentation/Pinebook_Pro/Software/Tuning.md @@ -90,9 +90,9 @@ When you first get your Pinebook Pro, you should consider setting strong passwor * Press Alt-Ctrl-F7 to go back to the login screen and then login as the normal user * Open text terminal to fix login error: "Configured directory for incoming files does not exist": - ```console - $ blueman-services - ``` +```console +$ blueman-services +``` Select "Transfer" tab and set "Incoming Folder" to yourself or if adduser is in the distributions, create an user with `sudo adduser $USER` (fill out variables as required), then add the user to the groups using `sudo adduser $USER $GROUP` by adding one group at a time. @@ -150,38 +150,45 @@ The default boot splash picture can be replaced using the following instructions * Install _ImageMagick_ which will do the conversion - ```console - $ sudo apt-get install imagemagick - ``` +```console +$ sudo apt-get install imagemagick +``` + * Create a 1920 x 1080 picture. For the best results, use a PNG image (It supports lossless compression). * From the directory in which your new image is stored run the following commands * Convert your image to the bootsplash raw format using imagemagick convert. - ```console - $ convert yoursplashimage.png -separate +channel -swap 0,2 -combine -colorspace sRGB RGBO:splash.fb - ``` +```console +$ convert yoursplashimage.png -separate +channel -swap 0,2 -combine -colorspace sRGB RGBO:splash.fb +``` + * Create a backup copy of your current splash screen - ```console - $ sudo cp /usr/share/backgrounds/splash.fb /usr/share/backgrounds/splash_original.fb - ``` +```console +$ sudo cp /usr/share/backgrounds/splash.fb /usr/share/backgrounds/splash_original.fb +``` + * Copy your new splash screen into place - ```console - $ sudo cp splash.fb /usr/share/backgrounds/splash.fb - ``` +```console +$ sudo cp splash.fb /usr/share/backgrounds/splash.fb +``` + * Set the correct permissions on the splash.fb file - ```console - $ sudo chmod 644 /usr/share/backgrounds/splash.fb - ``` +```console +$ sudo chmod 644 /usr/share/backgrounds/splash.fb +``` + * If you do not want to see kernel console text messages, make sure you don’t have _Plymouth_ installed ### Watching Amazon Prime videos with Chromium When you create a new user, it will be necessary to launch the Chromium browswer with a specific user agent like below: - chromium-browser --user-agent="Mozilla/5.0 (X11; CrOS armv7l 6946.63.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36" +```console +chromium-browser --user-agent="Mozilla/5.0 (X11; CrOS armv7l 6946.63.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36" +``` There may be more tweaks needed. @@ -193,24 +200,32 @@ By default, most Linux distributions have a boot screen with a picture. To see a * Backup and edit the U-Boot configuration file: - cp -p /etc/default/u-boot /etc/default/u-boot.`date +%Y%m%d` - chmod a-w /etc/default/u-boot.`date +%Y%m%d` - vi /etc/default/u-boot +```console +cp -p /etc/default/u-boot /etc/default/u-boot.`date +%Y%m%d` +chmod a-w /etc/default/u-boot.`date +%Y%m%d` +vi /etc/default/u-boot +``` Remove the _quiet_ and _splash_ parameters. Leave everything else alone. * Update the U-Boot configuration: - u-boot-update +```console +u-boot-update +``` + * Test and verify you get what you think you should be seeing. #### Manjaro * Backup and edit the U-Boot configuration file: - cp -p /boot/extlinux/extlinux.conf /boot/extlinux/extlinux.conf.`date +%Y%m%d` - chmod a-w /boot/extlinux/extlinux.conf.`date +%Y%m%d` - vi /boot/extlinux/extlinux.conf +```console +cp -p /boot/extlinux/extlinux.conf /boot/extlinux/extlinux.conf.`date +%Y%m%d` +chmod a-w /boot/extlinux/extlinux.conf.`date +%Y%m%d` +vi /boot/extlinux/extlinux.conf +``` + * Change **console=ttyS2,1500000** to **console=tty1** * Remove the **bootsplash.bootfile** option and it’s parameter. * You can add verbose logging by appending **ignore_loglevel** to the line where boot splash was. @@ -248,21 +263,23 @@ However, do not change the resolution of the LCD screen, otherwise you may end u From the [official Debian image](https://github.com/mrfixit2001/updates_repo/blob/v1.8/pinebook/filesystem/default): - --disable-low-res-tiling \ - --num-raster-threads=6 \ - --profiler-timing=0 \ - --disable-composited-antialiasing \ - --test-type \ - --show-component-extension-options \ - --ignore-gpu-blacklist \ - --use-gl=egl \ - --ppapi-flash-path=/usr/lib/chromium-browser/pepper/libpepflashplayer.so \ - --ppapi-flash-version=32.0.0.255 \ - --enable-pinch \ - --flag-switches-begin \ - --enable-gpu-rasterization \ - --enable-oop-rasterization \ - --flag-switches-end +```console +--disable-low-res-tiling \ +--num-raster-threads=6 \ +--profiler-timing=0 \ +--disable-composited-antialiasing \ +--test-type \ +--show-component-extension-options \ +--ignore-gpu-blacklist \ +--use-gl=egl \ +--ppapi-flash-path=/usr/lib/chromium-browser/pepper/libpepflashplayer.so \ +--ppapi-flash-version=32.0.0.255 \ +--enable-pinch \ +--flag-switches-begin \ +--enable-gpu-rasterization \ +--enable-oop-rasterization \ +--flag-switches-end +``` Note that in some cases, this may also decrease performance substantially, as observed when using these flags on the Manjaro KDE desktop. Feel free to experiment to find what is smoothest for you personally. @@ -273,7 +290,9 @@ Simply revert back to using GTK2, (how to do so is somewhat Linux distro-specifi Another solution may be to run gVim with - GDK_RENDERING=image +```console +GDK_RENDERING=image +``` environment variable set. It seems that this improves the performance by reverting back to software-only rendering. diff --git a/content/documentation/Quartz64/Software/Releases.md b/content/documentation/Quartz64/Software/Releases.md index f480774a..ae431fdb 100644 --- a/content/documentation/Quartz64/Software/Releases.md +++ b/content/documentation/Quartz64/Software/Releases.md @@ -90,7 +90,7 @@ as well as minimal image without desktop. Download: -* [NetBSD daily builds top level](http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/) from inside here, navigate to a date, and inside the images/ subdirectory are installable images. Use the one called "NetBSD--evbarm-aarch64-install.img.gz". +* [NetBSD daily builds top level](https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/) from inside here, navigate to a date, and inside the images/ subdirectory are installable images. Use the one called "NetBSD--evbarm-aarch64-install.img.gz". Notes: @@ -136,7 +136,7 @@ The *BSP Linux SDK ver 4.19_ for the Quartz64 Model A. Download: -* [Direct download](http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz) from _pine64.org_ (32.67GB, MD5 of the TAR-GZip file _24554419aec29700add97167a3a4c9ed_) +* [Direct download](https://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz) from _pine64.org_ (32.67GB, MD5 of the TAR-GZip file _24554419aec29700add97167a3a4c9ed_) ## Android SDK @@ -146,7 +146,7 @@ The **Android 11 SDK** for the Quartz64 Model A SBC. Download: -* [Direct download](http://files.pine64.org/SDK/Quartz64/QUARTZ64_SDK_android11.tar.gz) from _pine64.org_ (79.00GB, MD5 of the TAR-GZip file _77c2ff57ea3372fb04da7fb49e17d12b_) +* [Direct download](https://files.pine64.org/SDK/Quartz64/QUARTZ64_SDK_android11.tar.gz) from _pine64.org_ (79.00GB, MD5 of the TAR-GZip file _77c2ff57ea3372fb04da7fb49e17d12b_) * Just the boot blobs (<1MB): https://wiki.pine64.org/wiki/File:Rk35-blobs.tar.gz ### Android 11 Production Test Builds @@ -188,7 +188,7 @@ The ***Android 13 SDK*** for the Quartz64 Model "Zero" SBC. Download: -* [Direct download](http://files.pine64.org/SDK/Quartz64/Quartz64-Zero_Android13_SDK.tar.gz) from _pine64.org_ (111GB, MD5 of the TAR-GZip file _0cd965cf68145cc62876d50f320a715a_) +* [Direct download](https://files.pine64.org/SDK/Quartz64/Quartz64-Zero_Android13_SDK.tar.gz) from _pine64.org_ (111GB, MD5 of the TAR-GZip file _0cd965cf68145cc62876d50f320a715a_) #### Android 13 Stock diff --git a/content/documentation/QuartzPro64/Resources.md b/content/documentation/QuartzPro64/Resources.md index 39a0aeeb..328421a2 100644 --- a/content/documentation/QuartzPro64/Resources.md +++ b/content/documentation/QuartzPro64/Resources.md @@ -11,7 +11,7 @@ menu: ## Kernel -* [The linux-rockchip mailing list archives](http://lists.infradead.org/pipermail/linux-rockchip/) +* [The linux-rockchip mailing list archives](https://lists.infradead.org/pipermail/linux-rockchip/) * [linux-rockchip patchwork](https://patchwork.kernel.org/project/linux-rockchip/list/) * [neggles / neg2led’s mainline kernel repository with patches picked from the mailing list](https://github.com/neg2led/linux-quartz64) * [Sebastian Reichel’s (SRE) rk3588 branch](https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-misc.git/log/?h=rk3588) diff --git a/content/documentation/QuartzPro64/Ways_to_do_things.md b/content/documentation/QuartzPro64/Ways_to_do_things.md index 5392296e..66905026 100644 --- a/content/documentation/QuartzPro64/Ways_to_do_things.md +++ b/content/documentation/QuartzPro64/Ways_to_do_things.md @@ -110,9 +110,11 @@ then, make the filesystem on it. CounterPillow went for ext4 because nobody has $ mkfs.ext4 rootpart.bin ``` -Cool, now mount it: +Now mount it: - # mount rootpart.bin /mnt/emmc-root +```console +# mount rootpart.bin /mnt/emmc-root +``` Now we’ll download the Arch Linux ARM generic rootfs tarball and go to town: diff --git a/content/documentation/ROCK64/Software/MAC_address.md b/content/documentation/ROCK64/Software/MAC_address.md index 0d6a6ec0..81c97094 100644 --- a/content/documentation/ROCK64/Software/MAC_address.md +++ b/content/documentation/ROCK64/Software/MAC_address.md @@ -11,8 +11,8 @@ menu: To set the MAC address on ROCK64 with the "Android eMMC" image: -1. [Windows ADB driver package](http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip) installation is required as prerequisite -2. Download and unzip [WNpctool_V1.1.2_1226.zip](http://files.pine64.org/doc/rock64/tools/WNpctool_V1.1.2_1226.zip). Run WNpctool.exe "as Administrator" on Windows OS +1. [Windows ADB driver package](https://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip) installation is required as prerequisite +2. Download and unzip [WNpctool_V1.1.2_1226.zip](https://files.pine64.org/doc/rock64/tools/WNpctool_V1.1.2_1226.zip). Run WNpctool.exe "as Administrator" on Windows OS 3. Press recovery button on ROCK64 and power ON the ROCK64. After 2 seconds release the recovery button 4. Plug the USB Cable from Top USB2 slot of ROCK64 to PC USB slot (WNpctool will show "Found one loader" at the bottom) 5. Fill in LANMAC: with small letter MacAddress (e.g. 01234567abcd) then press on Write button diff --git a/content/documentation/ROCKPro64/Board/Features.md b/content/documentation/ROCKPro64/Board/Features.md index e1b6eaa6..7630dfa9 100644 --- a/content/documentation/ROCKPro64/Board/Features.md +++ b/content/documentation/ROCKPro64/Board/Features.md @@ -128,4 +128,4 @@ The ROCKPro64 is based on the Rockchip RK3399. | Real Time Clock (RTC) battery backup | | | | | | | [RTC Backup Battery Holder CR2032](https://pine64.com/product/rtc-backup-battery-holder-cr-2032/) | | Boot from USB/PXE | | | | | | | | -RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [in their wiki here](http://opensource.rock-chips.com/wiki_Status_Matrix). +RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [in their wiki here](https://opensource.rock-chips.com/wiki_Status_Matrix). diff --git a/content/documentation/ROCKPro64/Further_information/Datasheets.md b/content/documentation/ROCKPro64/Further_information/Datasheets.md index 1642eaea..0326d580 100644 --- a/content/documentation/ROCKPro64/Further_information/Datasheets.md +++ b/content/documentation/ROCKPro64/Further_information/Datasheets.md @@ -12,8 +12,8 @@ menu: Rockchip RK3399 SoC information: * [Rockchip RK3399 SoC Brief](https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html) -* [Rockchip RK3399 Datasheet V2.1](http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf) -* [Rockchip RK3399 Technical Reference Manual part 1](http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf) +* [Rockchip RK3399 Datasheet V2.1](https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf) +* [Rockchip RK3399 Technical Reference Manual part 1](https://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf) * [Rockchip RK808 Datasheet V0.8](https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf) LPDDR4 (200 Balls) SDRAM: @@ -40,7 +40,7 @@ Heatsink related info: Wireless related info: -* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [(v. 1.3)](https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf) [(v. 1.7)](http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf) +* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [(v. 1.3)](https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf) [(v. 1.7)](https://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf) Ethernet related info: diff --git a/content/documentation/ROCKPro64/Further_information/Other_resources.md b/content/documentation/ROCKPro64/Further_information/Other_resources.md index 5e6f5343..20e34427 100644 --- a/content/documentation/ROCKPro64/Further_information/Other_resources.md +++ b/content/documentation/ROCKPro64/Further_information/Other_resources.md @@ -12,7 +12,7 @@ menu: * [ROCKPro64 Forum](https://forum.pine64.org/forumdisplay.php?fid=98) * [PINE64 shop](https://pine64.com/?post_type=product) * [Rockchip Linux GitHub Repo](https://github.com/rockchip-linux) -* [Rockchip Open Source Wiki](http://opensource.rock-chips.com/) +* [Rockchip Open Source Wiki](https://opensource.rock-chips.com/wiki_Main_Page) * ExplainingComputers have a video review [of the RockPro64 here, including linux first boot.](https://www.youtube.com/watch?v=CeoNHGFN_30) ## Useful articles and blog posts diff --git a/content/documentation/ROCKPro64/Further_information/Schematics_and_certifications.md b/content/documentation/ROCKPro64/Further_information/Schematics_and_certifications.md index e3b631f5..da38ffe1 100644 --- a/content/documentation/ROCKPro64/Further_information/Schematics_and_certifications.md +++ b/content/documentation/ROCKPro64/Further_information/Schematics_and_certifications.md @@ -17,7 +17,7 @@ menu: * [ROCKPro64 v2.1 Board Top Outline in PDF format](https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf) * [ROCKPro64 v2.1 Board Bottom Outline in PDF format](https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf) * [ROCKPro64 Schematic v2.0 (Pilot Production Release)](https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf) - * [ROCKPro64 v2.0 Board Top Silkscreen in PDF format](http://files.pine64.org/doc/rockpro64/Rockpro64-ver2.0-topsilk_ref.pdf) (contains component labels) + * [ROCKPro64 v2.0 Board Top Silkscreen in PDF format](https://files.pine64.org/doc/rockpro64/Rockpro64-ver2.0-topsilk_ref.pdf) (contains component labels) * [Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe](https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf) * [ROCKPro64 AP6359SA Wifi/BT Schematic](https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf) * [ROCKPro64 Pi-2 Pin assignment and definition](https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png) diff --git a/content/documentation/ROCKPro64/Software/Releases.md b/content/documentation/ROCKPro64/Software/Releases.md index a0f805e2..4a4dc038 100644 --- a/content/documentation/ROCKPro64/Software/Releases.md +++ b/content/documentation/ROCKPro64/Software/Releases.md @@ -160,7 +160,7 @@ Download: Notes: * You need to enable root login in OMV WebGUI -* [OpenMediaVault Plugins](http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable) +* OpenMediaVault Plugins can enhance the system | Default credentials | | | -------- | ------- | @@ -215,7 +215,9 @@ Download: ### SkiffOS -{{< figure src="/documentation/images/SkiffOS-Icon-1.png" width="100]_Minimal_cross-compiled_OS_optimized_for_hosting_distributions_in_Docker_containers._Provides_the_reliability_of_firmware_with_the_ease-of-use of package managers. Uses the http://buildroot.org[Buildroot" >}} cross-compilation tool for support for all Pine64 boards. +{{< figure src="/documentation/images/SkiffOS-Icon-1.png" width="100" >}} + +Minimal cross-compiled OS optimized for hosting distributions in Docker containers. Provides the reliability of firmware with the ease-of-use of package managers. Uses the Buildroot cross-compilation tool for support for all Pine64 boards. Use configuration packages to configure the distribution: @@ -247,7 +249,7 @@ Resources: Downloads: -* [download](http://dl.fail.pp.ua/slackware/images/rockpro64/) (supports microSD card, look for slarm64-current-aarch64-xfce-rockpro64-x.xx.x-build-xxxxxxxx.img.zst) +* [download](https://dl.irradium.org//slackware/images/rockpro64/) (supports microSD card, look for slarm64-current-aarch64-xfce-rockpro64-x.xx.x-build-xxxxxxxx.img.zst) | Default credentials | | | -------- | ------- | @@ -377,26 +379,26 @@ Download: * Support Sony IMX214 camera module and works on both MiPi-CSI ports * This build supports PINE64 7" LCD panel with tablet UI (not Android TV) * DD image for 8GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-8GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-8GB.img.gz) ***** MD5 (GZip file): 7287fd0846616354615c8d3eff6a2a92 ***** File Size: 602MB * DD image for 16GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-16GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-16GB.img.gz) ***** MD5 (GZip file): 78352bbf21198d062af8bab2217ee691 ***** File Size: 611MB * DD image for 32GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-32GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-32GB.img.gz) ***** MD5 (GZip file): c5c8dce419478f75f85f893ee4808dbd ***** File Size: 624MB * DD image for 64GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-64GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-64GB.img.gz) ***** MD5 (GZip file): aab1cf4d30c4d16e6ce2672f3ecae935 ***** File Size: 666MB **Stock for RK Flash tool [eMMC Boot] [20200804]** * Please unzip first and then using Android tool to flash in * The OTG port located at USB type-C connector, needs USB type A to type C cable. -* [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20200708_stock_android_9.0_emmcboot.img.gz) +* [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20200708_stock_android_9.0_emmcboot.img.gz) ** MD5 (GZip file): 9ac830527814521e15b009fa2503c9e3 ** File Size: 589MB @@ -406,26 +408,26 @@ Download: * Supports new RockPro64 AP6256 Wifi/BT module * This build supports PINE64 7" LCD panel with tablet UI (not Android TV) * DD image for 8GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-8GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-8GB.img.gz) ***** MD5 (GZip file): ef5f5a890a9270734e0adee21f006837 ***** File Size: 597MB * DD image for 16GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-16GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-16GB.img.gz) ***** MD5 (GZip file): 179bd684a468f800a86f7c658a543bef ***** File Size: 606MB * DD image for 32GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-32GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-32GB.img.gz) ***** MD5 (GZip file): d930b757c4427be07b83c37a9c8494a1 ***** File Size: 630MB * DD image for 64GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-64GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-64GB.img.gz) ***** MD5 (GZip file): 09a970d68a10bdb3d6495d55860940e6 ***** File Size: 660MB **Stock for RK Flash tool [eMMC Boot] [20200708]** * Please unzip first and then using Android tool to flash in * The OTG port located at USB type-C connector, needs USB type A to type C cable. -* [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20200708_stock_android_9.0_emmcboot.img.gz) +* [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20200708_stock_android_9.0_emmcboot.img.gz) ** MD5 (GZip file): 6d060ddd47ebcfd5cfcdbf90ec042c97 ** File Size: 589MB @@ -435,15 +437,15 @@ Download: * Please ignore "internal problem with your device" popup message if appear on Android boot-up page. * This build supports PINE64 7" LCD panel with tablet UI (not Android TV) * DD image for 16GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz) ***** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7 ***** File Size: 609MB * DD image for 32GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz) ***** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C ***** File Size: 627MB * DD image for 64GB eMMC module -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz) ***** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF ***** File Size: 663MB @@ -454,19 +456,19 @@ Download: * Please ignore "internal problem with your device" popup message if appear on Android boot-up page. * This build supports PINE64 7" LCD panel with tablet UI (not Android TV) * DD image for 8GB microSD card -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz) ***** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A ***** File Size: 599MB * DD image for 16GB microSD card -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz) ***** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C ***** File Size: 609MB * DD image for 32GB microSD card -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz) ***** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B ***** File Size: 627MB * DD image for 64GB microSD card -** [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz) +** [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz) ***** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284 ***** File Size: 663MB @@ -475,7 +477,7 @@ Download: * The OTG port located at USB type-C connector, needs USB type A to type C cable. * Please allow 3-5 minutes boot up time on first time for initialization * This build supports PINE64 7" LCD panel with tablet UI (not Android TV) -* [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz) +* [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz) ** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341 ** File Size: 592MB @@ -485,7 +487,7 @@ Download: * Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [Etcher](https://www.balena.io/etcher/) or another specialized SD writing tool is preferred. * Please allow 3-5 minutes boot up time on first time for initialization * This build supports PINE64 7" LCD panel with tablet UI (not Android TV) -* [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz) +* [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz) ** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A ** File Size: 414MB @@ -494,7 +496,7 @@ Download: * Please allow 3-5 minutes boot up time on first time for initialization * This build supports PINE64 7" LCD panel with tablet UI (not Android TV) * DD image (for 8GB microSD card and above) -* [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz) +* [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz) ** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405 ** File Size: 616MB @@ -503,7 +505,7 @@ Download: * The OTG port located at USB type-C connector, needs USB type A to type C cable. * Please allow 3-5 minutes boot up time on first time for initialization * This build supports PINE64 7" LCD panel with tablet UI (not Android TV) -* [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz) +* [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz) ** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE ** File Size: 415MB @@ -513,7 +515,7 @@ Download: * Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [Etcher](https://www.balena.io/etcher/) or another specialized SD writing tool is preferred. * Please allow 3-5 minutes boot up time on first time for initialization * This build supports PINE64 7" LCD panel with tablet UI (not Android TV) -* [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz) +* [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz) ** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B ** File Size: 345MB @@ -522,14 +524,14 @@ Download: * The OTG port located at USB type-C connector, needs USB type A to type C cable. * Please allow 3-5 minutes boot up time on first time for initialization * This build supports PINE64 7" LCD panel with tablet UI (not Android TV) -* [Direct download from pine64.org](http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz) +* [Direct download from pine64.org](https://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz) ** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920 ** File Size: 342MB ### Android SDK **Android P SDK [v9.0]** -* [Direct Download from pine64.org](http://files.pine64.org/SDK/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz) +* [Direct Download from pine64.org](https://files.pine64.org/SDK/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz) ** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E ** File Size: 125.16GB @@ -547,19 +549,19 @@ The Ayufan github page Below are the LPDDR4 driver for RK3399 -* [rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build](http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin) -* [rk3399_ddr_666MHz_v1.11.bin, this is alpha version](http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin) -* [rk3399_ddr_933MHz_v1.11.bin, this is alpha version](http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin) +* [rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build](https://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin) +* [rk3399_ddr_666MHz_v1.11.bin, this is alpha version](https://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin) +* [rk3399_ddr_933MHz_v1.11.bin, this is alpha version](https://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin) ROCKPro64 related files -* [ROCKPro64 Kernel file](http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz) -* [trust.img](http://files.pine64.org/os/ROCKPro64/driver/trust.img) +* [ROCKPro64 Kernel file](https://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz) +* [trust.img](https://files.pine64.org/os/ROCKPro64/driver/trust.img) ## Miscellaneous tools -* [Windows ADB driver package](http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip) +* [Windows ADB driver package](https://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip) * [MAC address](/documentation/ROCK64/Software/MAC_address) -* [Guide to install stock Android build to eMMC module](http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf) -* [Tools to burn Android build into a bootable microSD card](http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip) -* [Tools that allows developer flash image into eMMC’s Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition](http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip) +* [Guide to install stock Android build to eMMC module](https://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf) +* [Tools to burn Android build into a bootable microSD card](https://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip) +* [Tools that allows developer flash image into eMMC’s Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition](https://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip) diff --git a/content/documentation/RockBox/External_resources.md b/content/documentation/RockBox/External_resources.md index daea6a50..cf1131b8 100644 --- a/content/documentation/RockBox/External_resources.md +++ b/content/documentation/RockBox/External_resources.md @@ -11,5 +11,4 @@ menu: * [Retro Center online store](https://www.retro-center.com/product/rockbox-r-cade/) * [R-Cade software detail](https://www.retro-center.com/about-r-cade/) -* [Networked Media Tank forum section](http://www.networkedmediatank.com/forumdisplay.php?fid=154) * [PINE64 forum](https://forum.pine64.org/forumdisplay.php?fid=85&page=1) diff --git a/content/documentation/SOEDGE/Further_information/Datasheets.md b/content/documentation/SOEDGE/Further_information/Datasheets.md index b8266dfd..61e271b2 100644 --- a/content/documentation/SOEDGE/Further_information/Datasheets.md +++ b/content/documentation/SOEDGE/Further_information/Datasheets.md @@ -11,7 +11,7 @@ menu: Rockchip RK1808 SoC information: -* [Rockchip RK1808 ver 1.2 datasheet](http://opensource.rock-chips.com/images/4/43/Rockchip_RK1808_Datasheet_V1.2_20190527.pdf) +* [Rockchip RK1808 ver 1.2 datasheet](https://opensource.rock-chips.com/images/4/43/Rockchip_RK1808_Datasheet_V1.2_20190527.pdf) * [Rockchip TK1808 Technical Reference Manual Part 1](https://files.pine64.org/doc/datasheet/SOEdge/Rockchip%20RK1808%20TRM%20Part1%20V1.2--20190826%20open%20source.pdf) Rockchip RK809 PMU (Power Management Unit) information: diff --git a/content/documentation/SOEDGE/Releases.md b/content/documentation/SOEDGE/Releases.md index fe736d67..56b378f9 100644 --- a/content/documentation/SOEDGE/Releases.md +++ b/content/documentation/SOEDGE/Releases.md @@ -39,7 +39,7 @@ Notes: Download: -* [SOEdge_linux_v1.1.img.gz](http://files.pine64.org/os/SOEdge/stock/SOEdge_linux_v1.1.img.gz) from _pine64.org_, MD5 (TAR-GZip file): a6629f997ae2cae7d9d5324c4e942deda9, size: 119MB +* [SOEdge_linux_v1.1.img.gz](https://files.pine64.org/os/SOEdge/stock/SOEdge_linux_v1.1.img.gz) from _pine64.org_, MD5 (TAR-GZip file): a6629f997ae2cae7d9d5324c4e942deda9, size: 119MB Notes: @@ -50,7 +50,7 @@ Notes: Download: -* [SOEdge_linux_usb_compute_stick.img.gz](http://files.pine64.org/os/SOEdge/stock/SOEdge_linux_usb_compute_stick.img.gz) from _pine64.org_, MD5 (GZip file): af6ac45995f7ddd9343a7052efffaf30, size: 47MB +* [SOEdge_linux_usb_compute_stick.img.gz](https://files.pine64.org/os/SOEdge/stock/SOEdge_linux_usb_compute_stick.img.gz) from _pine64.org_, MD5 (GZip file): af6ac45995f7ddd9343a7052efffaf30, size: 47MB Notes: @@ -61,7 +61,7 @@ Notes: Download: -* [SOEdge_linux_v1.1.img.gz](http://files.pine64.org/os/SOEdge/stock/SOEdge_linux_v1.1.img.gz) from _pine64.org_, MD5 (TAR-GZip file): a6629f997ae2cae7d9d5324c4e942deda9, size: 119MB +* [SOEdge_linux_v1.1.img.gz](https://files.pine64.org/os/SOEdge/stock/SOEdge_linux_v1.1.img.gz) from _pine64.org_, MD5 (TAR-GZip file): a6629f997ae2cae7d9d5324c4e942deda9, size: 119MB Notes: @@ -72,7 +72,7 @@ Notes: Download: -* [SOEdge_linux_usb_compute_stick.img.gz](http://files.pine64.org/os/SOEdge/stock/SOEdge_linux_usb_compute_stick.img.gz) from _pine64.org_, MD5 (GZip file): af6ac45995f7ddd9343a7052efffaf30, size: 47MB +* [SOEdge_linux_usb_compute_stick.img.gz](https://files.pine64.org/os/SOEdge/stock/SOEdge_linux_usb_compute_stick.img.gz) from _pine64.org_, MD5 (GZip file): af6ac45995f7ddd9343a7052efffaf30, size: 47MB Notes: @@ -81,6 +81,6 @@ Notes: ## Linux BSP SDK -* [Linux BSP Kernel ver 1.1.7](http://files.pine64.org/SDK/SOEdge/rk1808_v1.1.7.tar.gz) from _pine64.org_, MD5 (TAR-GZip file): 47a81a990a644539f3a0e84034654f78, size: 17.42GB +* [Linux BSP Kernel ver 1.1.7](https://files.pine64.org/SDK/SOEdge/rk1808_v1.1.7.tar.gz) from _pine64.org_, MD5 (TAR-GZip file): 47a81a990a644539f3a0e84034654f78, size: 17.42GB * [Full BSP SDK ver 1.1](https://files.pine64.org/SDK/SOEdge/SOEdge_RK-BSP_SDK_v1.1.tar.gz) from _pine64.org_, MD5 (TAR-GZip file): a66c92e52824762d7c0a63400d6342ea, size: 13.55GB * [Neural AI Stick BSP SDK ver 1.1](https://files.pine64.org/SDK/SOEdge/SOEdge_RK-BSP_USB_Dongle_SDK_v1.1.tar.gz) from _pine64.org_, MD5 (TAR-GZip file): 46f12441e8c35c06184681f355c89651, size: 9.65GB diff --git a/content/documentation/SOPINE/Further_information/Specification.md b/content/documentation/SOPINE/Further_information/Specification.md index c183e8d0..c441705c 100644 --- a/content/documentation/SOPINE/Further_information/Specification.md +++ b/content/documentation/SOPINE/Further_information/Specification.md @@ -13,7 +13,7 @@ Based on the Allwinner A64 ## CPU Architecture -* [Quad-core ARM Cortex-A53 Processor@1152Mhz](http://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php) +* [Quad-core ARM Cortex-A53 Processor@1152Mhz](https://developer.arm.com/Processors/Cortex-A53) * A power-efficient ARM v8 architecture * 64 and 32bit execution states for scalable high performance * Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function @@ -24,9 +24,9 @@ Based on the Allwinner A64 ## GPU Architecture -* [ARM Mali400MP2 Dual-core GPU](http://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php) +* [ARM Mali400MP2 Dual-core GPU](https://developer.arm.com/Processors/Mali-400) * Supports OpenGL ES 2.0 and OpenVG 1.1 standard Five megapixel CMOS camera module information: -* [PINE64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)](http://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf) +* [PINE64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)](https://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf) diff --git a/content/documentation/SOPINE/Pins_and_GPIOs.md b/content/documentation/SOPINE/Pins_and_GPIOs.md index 2ec1a816..2d87ab98 100644 --- a/content/documentation/SOPINE/Pins_and_GPIOs.md +++ b/content/documentation/SOPINE/Pins_and_GPIOs.md @@ -13,7 +13,7 @@ menu: This is table of all available GPIOs on SOPine with their alternate functions. -For more information about GPIOs, check the [Allwinner A64 Datasheet](http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf) section _4.2 GPIO Multiplexing Functions_ and section _4.3 Detailed Pin/Signal Description_ +For more information about GPIOs, check the [Allwinner A64 Datasheet](https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf) section _4.2 GPIO Multiplexing Functions_ and section _4.3 Detailed Pin/Signal Description_ | Pin name | Linux | SOPine Pin | Direction | Default Function | Default Pull | Function 2 | Function 3 | Function 4 | Function 5 | Function 6 | SOPine Name | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | diff --git a/content/documentation/SOPINE/Software/Releases.md b/content/documentation/SOPINE/Software/Releases.md index 270be3fd..e71b619f 100644 --- a/content/documentation/SOPINE/Software/Releases.md +++ b/content/documentation/SOPINE/Software/Releases.md @@ -38,7 +38,7 @@ Download: ### FreedomBox {{< figure src="/documentation/images/FreedomBox.jpg" >}} -FreedomBox is a private server for non-experts: it lets you install and configure server applications with only a few clicks. For more information about FreedomBox, please visit http://www.freedombox.org. +FreedomBox is a private server for non-experts: it lets you install and configure server applications with only a few clicks. For more information about FreedomBox, please visit https://www.freedombox.org. {{< admonition type="warning" >}} Outdated release @@ -51,7 +51,7 @@ Download: Notes: * This is a headless build, not HDMI output. -* Please plug-in Ethernet cable first before initial power up. After power up for 10 minutes, using browser and type in http://fredombox.local to setup. Browser may warms for unsecure site and please proceed with exception. +* Please plug-in Ethernet cable first before initial power up. After power up for 10 minutes, using browser and type in https://fredombox.local to setup. Browser may warms for unsecure site and please proceed with exception. * Freedom Manual: https://wiki.debian.org/FreedomBox/Manual ### LibreELEC @@ -78,7 +78,7 @@ NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-con Download: -* [Direct download from pine64.org](http://files.pine64.org/os/SOPINE/nems/NEMS_v1.5-SOPine-Build1.zip) (supports the microSD card, 16GB or more, MD5 of the xz file is _5ad0d684296d50b4c1fcbac6db205ae0_) +* [Direct download from pine64.org](https://files.pine64.org/os/SOPINE/nems/NEMS_v1.5-SOPine-Build1.zip) (supports the microSD card, 16GB or more, MD5 of the xz file is _5ad0d684296d50b4c1fcbac6db205ae0_) * [Download torrent seed from NEMS Linux](https://nemslinux.com/download/nagios-for-pine64.php) (supports the microSD card, 16GB or more, MD5 of the xz file is _6e2088922c5d197db8b8ba3057120389_) {{< admonition type="info" >}} @@ -130,7 +130,7 @@ NetBSD is a free, fast, secure, and highly portable Unix-like Open Source operat Download: -* [Direct download](http://www.armbsd.org/arm/) (select _PINE A64-LTS / SoPine with baseboard_) +* [Direct download](https://nycdn.netbsd.org/pub/arm/) (select _PINE A64-LTS / SoPine with baseboard_) | Default credentials | | | -------- | ------- | @@ -147,11 +147,11 @@ Linux BSP Kernel 4.9 Download: -* [Direct Download](http://files.pine64.org/SDK/PINE-A64/PINE-A64_lichee_BSP4.9.tar.xz) from _pine64.org_ (5.40GB, MD5 of the TAR-GZip _7736e3c4d50c021144d125cc4ee047a4_) +* [Direct Download](https://files.pine64.org/SDK/PINE-A64/PINE-A64_lichee_BSP4.9.tar.xz) from _pine64.org_ (5.40GB, MD5 of the TAR-GZip _7736e3c4d50c021144d125cc4ee047a4_) ## Android SDK Android Oreo (v8.1) Download: -* [Direct Download](http://files.pine64.org/SDK/PINE-A64/PINE-A64_SDK_android8.1.tar.xz) from _pine64.org_ (24.94GB, MD5 of the TAR-Gzip _b0394af324c70ce28067e52cd7bc0c87_) +* [Direct Download](https://files.pine64.org/SDK/PINE-A64/PINE-A64_SDK_android8.1.tar.xz) from _pine64.org_ (24.94GB, MD5 of the TAR-Gzip _b0394af324c70ce28067e52cd7bc0c87_) diff --git a/content/documentation/SOPINE/Troubleshooting.md b/content/documentation/SOPINE/Troubleshooting.md index 6549f9d2..5ef382da 100644 --- a/content/documentation/SOPINE/Troubleshooting.md +++ b/content/documentation/SOPINE/Troubleshooting.md @@ -20,7 +20,7 @@ There is a number of things that can prevent the board from booting up properly. Make sure to have the newest version of the operating system and the bootloader installed. {{< /admonition >}} -To find out more, visit the [PINE64 forum thread](http://forum.pine64.org/showthread.php?tid=514). +To find out more, visit the [PINE64 forum thread](https://forum.pine64.org/showthread.php?tid=514). ## Supported screen resolutions @@ -39,4 +39,4 @@ Follow these steps to determine the cause of your problem: ## Notes -If neither of the above mentioned scenarios fits the problem you are facing, please consult the [PINE64 forum thread from user _Ghost_](http://forum.pine64.org/showthread.php?tid=680). +If neither of the above mentioned scenarios fits the problem you are facing, please consult the [PINE64 forum thread from user _Ghost_](https://forum.pine64.org/showthread.php?tid=680). diff --git a/content/documentation/SOQuartz/Software/Android_SDK.md b/content/documentation/SOQuartz/Software/Android_SDK.md index 471bf1ed..4ca17800 100644 --- a/content/documentation/SOQuartz/Software/Android_SDK.md +++ b/content/documentation/SOQuartz/Software/Android_SDK.md @@ -13,7 +13,7 @@ menu: Download: -* [Direct Download from pine64.org](http://files.pine64.org/SDK/Quartz64/QUARTZ64_SDK_android11.tar.gz) +* [Direct Download from pine64.org](https://files.pine64.org/SDK/Quartz64/QUARTZ64_SDK_android11.tar.gz) Notes: diff --git a/content/documentation/SOQuartz/Software/BSP_Linux_SDK.md b/content/documentation/SOQuartz/Software/BSP_Linux_SDK.md index dc131141..7c0af3f0 100644 --- a/content/documentation/SOQuartz/Software/BSP_Linux_SDK.md +++ b/content/documentation/SOQuartz/Software/BSP_Linux_SDK.md @@ -13,7 +13,7 @@ menu: Download: -* [Direct Download from pine64.org](http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz) +* [Direct Download from pine64.org](https://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz) Notes: diff --git a/content/documentation/Unsorted/PhoenixCard.md b/content/documentation/Unsorted/PhoenixCard.md index 27d5e751..22b429f7 100644 --- a/content/documentation/Unsorted/PhoenixCard.md +++ b/content/documentation/Unsorted/PhoenixCard.md @@ -40,7 +40,5 @@ menu: ## Related Reference -* [Easily Create an Android Bootable SD Card for Allwinner A80 Devices with PhoenixCard Tool](http://www.cnx-software.com/2015/01/06/easily-create-an-androidlinux-bootable-sd-card-for-allwinner-a80-devices-with-phoenixcard-tool/) -* [Boot from SD-Card or flash a ROM with PhonixCard](http://www.ondaforum.com/topic/2022-boot-from-sd-card-or-flash-a-rom-with-phonixcard/) -* [How to upgrade tablet pc with Micro SD Card Tutorial](http://www.androidsoldier.com/2013/11/upgrading-method-android-tablet.html) +* [Easily Create an Android Bootable SD Card for Allwinner A80 Devices with PhoenixCard Tool](https://www.cnx-software.com/2015/01/06/easily-create-an-androidlinux-bootable-sd-card-for-allwinner-a80-devices-with-phoenixcard-tool/) * [PhoenixCard Tutorial YouTube Video](https://www.youtube.com/watch?v=eKo82AUgbFM) diff --git a/content/podcast/s01e09.md b/content/podcast/s01e09.md index 89f2f027..914c3bf5 100644 --- a/content/podcast/s01e09.md +++ b/content/podcast/s01e09.md @@ -106,7 +106,7 @@ Sadly no, but Ezra commits to reporting about his successes and failures in the _Have you guys thought about verified boot camp n pinephone? 🙂_ -Content to read on the topic: [Protecting Linux devices with verified boot, from ROM to Userspace](http://linuxgizmos.com/protecting-linux-devices-with-verified-boot-from-rom-to-userspace/). +Content to read on the topic: [Protecting Linux devices with verified boot, from ROM to Userspace](https://linuxgizmos.com/protecting-linux-devices-with-verified-boot-from-rom-to-userspace/). If you have experimented with this on the PinePhone, please get in touch! diff --git a/content/podcast/s01e10.md b/content/podcast/s01e10.md index d65efc1f..260c8a2f 100644 --- a/content/podcast/s01e10.md +++ b/content/podcast/s01e10.md @@ -42,7 +42,7 @@ Links about the things we talked about, in order of appearance: Getting started with Linux -* [Knoppix](http://www.knoppix.org/) +* Knoppix * Getting involved with postmarketOS * Oliver Smith’s blog: [postmarketOS: Aiming for a 10 year life-cycle for smartphones](https://ollieparanoid.github.io/post/postmarketOS/) * postmarketOS blog: [100 days of postmarketOS](https://postmarketos.org/blog/2017/09/03/100-days-of-postmarketos/) @@ -67,7 +67,7 @@ Follow Martijn’s work on: * [LBRY/Odysee](https://odysee.com/@martijn:b) * [Blog](https://blog.brixit.nl/) * [sourcehut](https://git.sr.ht/~martijnbraam/) -* and the [postmarketOS podcast](http://cast.postmarketos.org/)! +* and the [postmarketOS podcast](https://cast.postmarketos.org/)! ## Community News * PINE64: [FemtoStar: taking aim for the stars](https://www.pine64.org/2021/05/19/femtostar-taking-aim-for-the-stars/) @@ -112,7 +112,7 @@ So: * Sometimes implemented within the SoC (e.g. MediaTek MT6753) * Sometimes within the Wifi/BT chip (e.g. Samsung Galaxy SII) * Do we have support for FM radio? - * the Realtek RTL 8723CS chip used for WiFi and Bluetooth in the PinePhone [alledgedly supports receiving FM radio](https://www.realtek.com/en/press-room/news-releases/item/realtek-to-show-latest-wlan-iot-solutions-at-internet-of-things-world-2015) according to its announcement, but it’s nowhere to be found on the [spec sheet](http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf). + * the Realtek RTL 8723CS chip used for WiFi and Bluetooth in the PinePhone [alledgedly supports receiving FM radio](https://www.realtek.com/en/press-room/news-releases/item/realtek-to-show-latest-wlan-iot-solutions-at-internet-of-things-world-2015) according to its announcement, but it’s nowhere to be found on the [spec sheet](https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf). * but: We don’t have a driver that would support this, and we don’t have the hardware for it. * Would the Pogopin i2c (i-squared-c bus (inter-integrated-circuit interface) offer enough bandwith for fm-radio on the PinePhone? * bandwith is rather limited, but [actual "hard numbers" information seems to be scarce](https://en.wikipedia.org/wiki/I%C2%B2C#Design) diff --git a/content/podcast/s01e12.md b/content/podcast/s01e12.md index 26b51bed..02d3a7fa 100644 --- a/content/podcast/s01e12.md +++ b/content/podcast/s01e12.md @@ -56,7 +56,7 @@ See [pineroot](https://github.com/e59e4835/pineroot) * Follow the project on [Twitter](https://twitter.com/pineroot1/) ### Brian Daniels: Hardware Accelerated Video Decoding on the PinePhone -[Brian Daniels: Hardware Accelerated Video Decoding on the PinePhone](http://briandaniels.me/2021/06/27/hardware-accelerated-video-playback-on-the-pinephone.html) +[Brian Daniels: Hardware Accelerated Video Decoding on the PinePhone](https://briandaniels.me/2021/06/27/hardware-accelerated-video-playback-on-the-pinephone.html) ### InfiniTime [InfiniTime 1.2.0](https://github.com/JF002/InfiniTime/releases/tag/1.2.0) diff --git a/content/podcast/s01e13.md b/content/podcast/s01e13.md index 3a3108f0..d2aefe7a 100644 --- a/content/podcast/s01e13.md +++ b/content/podcast/s01e13.md @@ -51,7 +51,7 @@ Peter: #### PinePhone: Software -* Brian Daniels: [Hardware Accelerated Video Decoding on the PinePhone with Clapper](http://briandaniels.me/2021/07/06/hardware-accelerated-video-playback-on-the-pinephone-with-clapper.html) +* Brian Daniels: [Hardware Accelerated Video Decoding on the PinePhone with Clapper](https://briandaniels.me/2021/07/06/hardware-accelerated-video-playback-on-the-pinephone-with-clapper.html) * [Clapper](https://rafostar.github.io/clapper/) * [Peters Flatpak recipe](https://framagit.org/1peter10/flatpaks) * [Arch Linux ARM by Danct12](https://github.com/dreemurrs-embedded/Pine64-Arch/releases) @@ -123,11 +123,11 @@ FAANG’s minion played by Peter | Track | Artist | License | | --- | --- | --- | -| raising evil | Oleg Makarov | http://creativecommons.org/licenses/by-nc-nd/3.0/ | -| Cybernetic Rhythm | Michael-K | http://creativecommons.org/licenses/by-nc-nd/3.0/ | -| The Road Adventures | 83Crutch | http://creativecommons.org/licenses/by-nc-sa/3.0/ | -| In Dark Triller | soundside (royalty free music) | http://creativecommons.org/licenses/by-nc-nd/3.0/ | -| Rejuvenation - Full Length | pinegroove | http://creativecommons.org/licenses/by-nc-nd/3.0/ | +| raising evil | Oleg Makarov | https://creativecommons.org/licenses/by-nc-nd/3.0/ | +| Cybernetic Rhythm | Michael-K | https://creativecommons.org/licenses/by-nc-nd/3.0/ | +| The Road Adventures | 83Crutch | https://creativecommons.org/licenses/by-nc-sa/3.0/ | +| In Dark Triller | soundside (royalty free music) | https://creativecommons.org/licenses/by-nc-nd/3.0/ | +| Rejuvenation - Full Length | pinegroove | https://creativecommons.org/licenses/by-nc-nd/3.0/ | ### Audio Production diff --git a/themes/pinetheme/assets/css/style.css b/themes/pinetheme/assets/css/style.css index f2f01ca0..9bf7c2a3 100644 --- a/themes/pinetheme/assets/css/style.css +++ b/themes/pinetheme/assets/css/style.css @@ -1059,8 +1059,6 @@ button.podcast:hover { color: #9f7f00; } - - /* Youtube partial */ .video-container { position: relative; diff --git a/themes/pinetheme/static/podlove/README.md b/themes/pinetheme/static/podlove/README.md deleted file mode 100644 index 2e62b085..00000000 --- a/themes/pinetheme/static/podlove/README.md +++ /dev/null @@ -1,44 +0,0 @@ -# Podlove Web Player - -> Sandboxed Podlove Player Templates with the ability to embed and share episodes - -![Preview](screenshot.png) - -## About - -HTML5 Goodness for Podcasting - -**Podlove** Web Player is a Podcast-optimized, HTML5-based video and audio player. -It can be used as a WordPress plugin or within a static HTML/JavaScript context. - -The **Podlove** Web Player supports almost every modern browser (Edge, Firefox, Chrome, Safari) and also does captions, chapters, transcripts and much more. - -* [Web Player Documentation](http://docs.podlove.org/podlove-web-player/) -* [Official site on podlove.org](http://podlove.org/podlove-web-player/) - -## Features - -- Encapsulate Player in an iframe -- Provide a global function to bootstrap the embedded player -- Parse the provided configuration (resolving the root config, transcripts and chapters asynchroniously) -- Persist selected tabs and playtime to local storage -- Transform url parameters to player actions -- Forward the player api to the embedding page -- Provide additonal extensions for embedding page integration - -## Architecture - -![Architecture](architecture.svg) - -## Getting Started - -### Development - -1. Bootstrap the web-player package: `lerna bootstrap --hoist` -2. Run the development mode: `npm run dev` -3. Open your browser on `http://localhost:9000` to get started - -### Building - -1. Make sure that the dependencies are up to date: `lerna bootstrap --hoist` -2. Run the build step: `npm run build`