March Update: Introducing the QuartzPro64

Lukasz Erecinski Mar 15. 2022 27

This month we’re announcing the QuartzPro64 – a new single-board computer based on Rockchip’s powerful RK3588 SoC. This is our first Pro-grade SBC since the introduction of the ROCKPRo64, and I believe it to be a worthy successor to the much revered Pro lineup. I am also happy to let you know that the Quartz64 model-B will be arriving at the Pine Store in the coming weeks, with all of its features supported in the most recent Manjaro OS image. 

We’ve got much to discuss, let’s get into it.  

You can watch the synopsis of this month’s community update on YouTube (embedded below) as well as on Odysee and PeerTube. To stay up-to-date with PINE64 news make sure to subscribe to this blog (subscription widget at the bottom of the webpage), follow PINE64 Telegram News channel, the announcements channel on Matrix, the announcements channel in Discord as well as our Twitter and Mastodon.

I’d like to thank JF, Alex (clover), Brian (33YN2), Danct12 and PizzaLovingNerd for their contributions to this community update.

N.B. Comments on the blog post need to be in English and follow our Community Rules and Code of Conduct.

Synopsis of this month’s update in video format

TL;DR

  • Housekeeping
    • A new episode of PineTalk is out – listen to the hosts’ suggestions for future PINE64 devices
    • Improvements to the chats have been made over the last few weeks which should significantly reduce spam
    • PineTab and Pinebook Pro will sadly remain unavailable for a while longer
    • PINE64 EU is on track for May 1st launch
  • QuartzPro64
    • We’re introducing the QuartzPro64 based on RK3588 – available in the coming weeks to developers
    • It will cost North of $300 and will initially only be available to developers via a coupon system 
    • With development in mind, the QuartzPro64 exposes as much I/O as possible
    • Equipped with 16GB RAM and 64GB of expandable eMMC
    • Will only be available publicly when BSP releases are in good shape
  • PinePhone (Pro)
    • Shipment has resumed post-CNY and most if not all of the backlog has been cleared
    • Suspend now works on the PinePhone Pro – u-boot fix applied by pgwipeout
    • Keyboard case battery capacity reporting in UI is coming – already available in Manjaro’s OS images 
    • Tow-Boot 4th release adds official support for the PinePhone Pro adding mobile-specific elements 
    • SailfishOS and Nemo mobile get GPS support on the PinePhone and work began to start integrating the fingerprint reader back case
    • The original PinePhone can be used to run LibreELEC – and it runs well including 1080p@60 video playback
  • Quartz64
    • Quartz64 model-B is coming soon; 4GB version of the board is launching first 
    • Manjaro OS image for model-B if feature-complete, including full support for desktop and UI usage and all I/O present on the board
    • More improvements for the RK3566 and thus also the Quartz64 and derivative devices is coming soon
  • PineTime
    • Active development is ongoing with many merge requests awaiting
    • InfiniSim is an InfiniTime desktop simulator, which can be run on a PinePhone (Pro) that allows for easy InfiniTime development and testing
    • InfiniSim is now a part of InifiniTime organization on GitHub

Housekeeping 

I’m starting with a last-minute edit to this month’s update; Shenzhen, the city where PINE64 electronics are manufactured, has just imposed a strict COVID19 testing procedure and issued a ‘stay at home’ order until March 20th. This is due to an increase in COVID19 cases in the region. It remains to be seen how, if at all, this situation will impact our production schedule. However, for the time being, the shipping staff have been sent home, which means that only Hong Kong-based shipments (PinePhone, PinePhone Pro, and PineNote) will be sent out this and the coming week. Once I have an update on the situation I’ll make sure to relay it to the community via social media, on the forum, and in the chats.

Left: original text in Chinese // Right: auto-translation into English (‘deep training’ to be read as ‘thorough testing’)

A new episode of the PineTalk is out. In this most recent entry to our community podcast, Justin and Brian discuss current PinePhone and PinePhone Pro developments, including Tow-boot and improvements to Mexapixels post-processing, as well as their own open-hardware ideas. While I do not think we’ll embark on a journey to create an open Google Glass-type device, as suggested by Brian, an open speaker with a personal assistant is actually a compelling idea (and one we discussed internally all the way back in 2020). A solid idea Justin and one perhaps worth visiting. Have a listen and let us know what you think about the show-hosts ideas for future hardware. The most recent episode can be found on PineTalk’s page; I also encourage you to subscribe to the podcast’s RSS feed

During my absence (more on this a bit later), Fire219 and Gamiee have done some solid improvements to our chat infrastructure. As I’ve reported late last year, and as many of you know from first-hand experience, spam in the chat has been an issue in recent months. A part of the problem is our cross-platform bridge: not all moderators have moderation privileges on all platforms, and those that do aren’t always there to react. Moreover, it is easier to get the moderators’ attention on some platforms than others. Earlier this year Fire219 and Gamiee laid the foundations for automatically removing spam and flagging potential malware. This reduced the number of incidents but hasn’t fully eliminated the issue. Now, however, we’ve got two new weapons at our disposal: cross-platform deletion and a sophisticated and trained AI bot with cross-platform deletion permissions. This means that even if the, rather sophisticated, bot fails to catch the spam any moderator can delete any spam message on any platform. Long story short, the spam problem should be less intrusive moving forward. 

I also promised you an update regarding PineTab and Pinebook Pro’s availability; as may recall, the product team has been scavenging around for a vendor who’d be willing to sell us a batch of LCD panels that are reasonably priced and come with a warranty (so that if they are faulty, do not meet the grading or fail during usage we can RMA them at the source). Unfortunately, as of today, the team has not found a vendor who would be willing to sell such a batch of panels. We’re well aware that it has been a long wait and that many of you are eager to see the production of these devices resumed, but I’m afraid we’ll all have to wait a little longer for the next production run. I’ll make sure to keep you updated if anything changes.

PINE64 EU website is coming along

Lastly, I’ve been away these past few weeks laying the foundations for the PINE64 EU store. The last paperwork to get the EU store off the ground has now been filed, and I even have an office with (mostly) assembled IKEA office furniture. If all goes to plan, and the Polish state’s bureaucracy doesn’t take an eternity to process the application, then I hope to receive the first shipment of hardware sometime in late April. I don’t want to commit to a firm launch date at this stage, but I am currently aiming to have everything ready to go on May 1st. For those who want to learn more about the plans for the EU store, I invite you to read last month’s community update.  I’ll be posting progress updates on PINE64 EU’s Twitter as we get closer to launch.

QuartzPro64

In January I outlined our plans for the Rockchip RK3588 platform – a powerful Arm SoC with an impressive array of I/O options. Today I am pleased to introduce the QuartzPro64, our single board computer based on the RK3588. Let’s start with a quick recap: the RK3588 is an 8-core SoC, featuring 4x A55 and 4x A76 cores clocked at 1.8GHz and 2.4GHz respectively. This new SoC features the recently introduced Mali G610MC4 GPU with 4 cores, based on the Valhalla architecture. The SoC is capable of driving an 8K display and multiple 4K displays (4 total), has a 6TOPS NPU, an 8K 10-bit decoder as well as an 8K encoder. In our single board computer lineup, the RK3588 SoC is the successor to the very successful RK3399 used in the ROCKPro64. However, while this SoC is the successor to the RK3399, I want to make it clear that it will not be replacing it anytime soon. Thus, the QuartzPro64 will also not be replacing the ROCKPro64 for a very long time either. 

No picture due to the ‘stay at home’ order affecting the product team, so this will have to suffice for now

Before I get into discussing the details of the QuartzPro64 I feel that I first need to make two things clear. Firstly, to purchase the board you will need to be a developer – at least initially. We’ll use the same coupon system we used for the first production runs of the PineNote and the PinePhone Pro once these devices launch. The software for the QuartzPro64 is yet to be developed and to say that the device is ‘not end-user ready’ would be an understatement; we both hope and expect to see BSP-based support in the initial months, with mainlining efforts running in parallel to the BSP development. Secondly, this will not be an inexpensive single-board computer. While we haven’t settled on a price-point yet, we expect it to cost North of $300. It will be sold either at cost or we will subsidize it. I think that it is necessary for me to mention the above up-front to align everyone’s expectations and tamper with unnecessary hype. Here’s the take-away: this is an amazing platform, but it will take time for it to mature.

QuartzPro64 block diagram

Now, with that out of the way, the QuartzPro64 will ship with 16GB of LPDDR4X RAM and 64GB of eMMC storage, which ought to be plenty for development and future implementation. With development in mind, we chose to expose as much of the available I/O as possible.

Here’s the core I/O run-down:

  • USB-C (with video-alt mode)
  • USB0-C (with debug mode)
  • USB- 3.0
  • 2x USB 2.0 
  • HDMI in
  • 2x HDMI out 
  • PCIe 3.0 
  • 2 SATA ports 
  • 2x Gigabit ethernet
  • 2x SMA Antenna 
  • 2x MIPI DPHY
  • 2x MPI DPCHY
  • Fan header
  • RTC battery holder
  • An array of switches, including power on/off maskrom and system KEY
  • eMMC socket
  • SD card slot
  • Power in via DC 12V 

The board is 180mm x 180mm in size, features heatsink mounting holes and system KEY buttons on the PCB. We hope this feature set will make QuartzPro64 interesting to its target audience – the development community. In anticipation of people asking about the general availability of the board; at present time it is unclear when the QuartzPro64 will be made available more broadly. This will depend on BSP and Mainline development. As most members of the community I too have high hopes for the QuartzPro64, and more broadly for the RK3588 platform, and I hope to see the SoC implemented in PINE64 devices in the far-off future. For the time being, we’ll be announcing QuartzPro64’s availability on our Telegram, Matrix and Discord announcement / news channels and on social media in the coming weeks. Stay tuned. 

PinePhone (Pro)

Shipments of the PinePhone and PinePhone Pro have resumed following Chinese New Year’s end, with the first batches of both dispatched earlier this month. I haven’t followed the dispatch process in recent weeks, but I believe that much of the CNY backlog has now already been shipped (and in many cases delivered). On the subject of PinePhone and PinePhone Pro shipments – we’re working on improving the dispatch and delivery logistics. The end goal is to ship smaller batches but more frequently. For the majority of you, this means that your PinePhone and PinePhone Pro order will be delivered much quicker. We are currently trialing a service that would cut down the delivery time significantly – depending on how the trial period goes we may implement this shipping mode permanently, and even expand it to other devices. I’ll return to this topic once the trial period is over and a decision has been reached later in the year.

PinePhone and PinePhone Pro most recent dispatch (I am intrigued by the red broom, you too?)

On the subject of software, there is much progress to report. Perhaps most importantly of all, suspend now works properly on the PinePhone Pro using u-boot. This enablement, or “fix” to be more accurate, comes courtesy of pgwipeout, who found a solution to this problem. I asked pgwipeout what the solution was, here is his response: “DMA transfers to SRAM always fail, no matter the source. The original fix handled disabling DMA on the SDMMC controller in SPL, but the SDHCI (eMMC) controller still was attempting DMA. I simply created a toggle for DMA in SPL for the SDHCI controller. Thus U-Boot on the eMMC now can load the SRAM bits without corrupting the data in-flight”. This fix has now found its way into Manjaro’s most recent OS image, which means you’ll be able to suspend/resume from suspend on the PinePhone Pro just like on the original PinePhone. While similar functionality can be achieved via Tow-boot (33YN2 writes more about this further down in this section), for those of you who specifically wish to use u-boot on their device I am glad to let you know that it is now a viable option.    

Battery capacity reporting for the keyboard case now works in the UI on the PinePhone and PinePhone Pro thanks to Megi. This means keyboard case battery levels can be read in Plasma Mobile, Phosh, and SXMO in the same way as the smartphone’s main battery. Prior to this, you needed to read the battery status from the command line, which obviously wasn’t the ideal way to keep track of battery usage. This enhancement has now made its way to Manjaro; if you’re on Arch then you can wait for kernel 5.17 or switch to linux-megi-rc package. I am confident that more distro will follow suit and implement this enablement in their OSes.

Keyboard case’s battery charge displayed in Phosh – picture by Martijn Braam

Tow-Boot, a user-friendly version of U-Boot, has seen a release for the PinePhone and PinePhone Pro. The project page states that Tow-Boot aims to make the process of booting your device “boringly” normal and simple. The goal is to have a standardized booting experience across a variety of Arm-based devices, with no need for board or OS-specific differences in the builds. The most recent version of Tow-Boot introduced a smartphone UI, supporting both touch-input and small screens. In line with the project’s mantra, the project explains on their GitHub that this build of Tow-Boot should “(…) enable users to live the dream of EBBR but on their phones.” Tow-boot also allows for a variety of additional functionality, similar to Jump Drive, exposing the smartphone’s internal eMMC memory in a way that it can be mounted and flashed from a PC. It also allows the user to select the bootable device (SD / eMMC) via a combination of button presses. To learn more, check out the project’s website.

Video showcasing Tow-Boot installation to PinePhone Pro’s SPI flash – via Martijn Braam

Megi has demoed LibreELEC running on the original PinePhone and outputting video to an external display (TV). The KODI UI is accelerated and runs smoothly as does the video playback, which appears to be rock solid. I’m told that 1080p video, including 50fps (and likely also 60fps), plays back really well on the original PinePhone running LibreELEC. There isn’t a dedicated PinePhone OS image but thankfully Megi has put together comprehensive instructions on how to make one yourself. He also included a guide detailing how to add a LibreELEC entry into his multi-OS p-boot image. I really enjoy the PinePhone being used in non-phone specific ways, and this is certainly a great showcase of the versatility that the device offers. Being a retro-gamer I already asked Megi for a guide on how to port LAKKA to the PinePhone.    

LibeELEC on the original PinePhone – original video by Megi

Lastly, an alternative X86/X86-64 emulator for ARM64 called Fex-EMU (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!

Quartz64

Given QuartzPro64 introduction this month, I would be remiss not to mention all the development that Quartz64 has seen in recent months. I am also happy to announce that the Quartz64 model-B has now entered production and should become available in April (or earlier). Just to recap, the Quartz64 model-B features the same RK3566 SoC that is found on the model-A and on the PineNote. The SoC features 4x A55 cores and the Mali G52-2EE GPU. The model-B will be available in 2 configurations – with 4GB LPDDR4 and 8GBLPDDR4 RAM for $59.99 and $79.99 respectively. Unlike the model-A, model-B follows in the ROCK64’s steps and offers a small footprint. The small footprint means that some of the model-A I/O has been removed, but it retains the USB 3.0 alongside 2x USB 2.0 ports as well as DSI, CSI and RTC. This I/O selection is coupled with a full 40 GPIO pin connector and onboard Bluetooth and WiFi module. You can also outfit it with an eMMC module or a NVMe SSD (via PCIe 1x) located on the bottom of the PCB. It is a versatile little board, geared more towards end-users and industry than the bigger model-A.

The form factor of the Quartz64 model-B is, in all likelihood, very familiar to most of you

The model-B arrives at a good time; the software for the platform has matured to a point that distros and projects can develop fully fledged, functional OS images for the Quartz64. As per usual, Manjaro is the first to deliver an OS image with all core functionality enabled. The OS is built upon mainline-based kernel (5.17) and comes in five variations: minimal, with XFCE desktop, Plasma Desktop, GNOME and MATE desktops as well as Sway. The desktops (which support acceleration) are fully accelerated via the open source Panfrost GPU driver and I can attest that the desktop experience on the Quartz64 is excellent as far as SBCs are concerned. Latest pre-release Manjaro OS builds for the Quartz64 can be downloaded from here.

Quartz64 model-A with 2x SATA SSDs attached and powered directly from the SBC – picture by JF via Twitter

But that’s not all. I’ve spoken to pgwipeout and he’s told me that many improvements to end-users’ experience are in the works. He also updated me on the mainlining status of the various components: “Dwc3 support is pretty much ready to land in mainline, with the combophy queued up for 5.18. That also means pcie and sata are coming soon too. I’ve gotten DSI to work partially with the vop2 driver, but it still needs more work”. Moreover, the SPI controller has been confirmed to work and that SPL handling of recovery is now supported in mainline u-boot. While some I/O found on the model-A, such as the DSI, still needs some work all I/O on the model-B is already fully functional – “If you are including anything about model b, it’s pretty much good to go out of the box” pgwipeout told me. I believe that the release of the model-B will lead to a much broader adoption of the RK3566 and, in turn, a much wider range of OS choice. Indeed, I know this to be true, since we’ve already shipped a handful of dev kits to projects interested in supporting the Quartz-line of devices. 

PineTime [JF]

Since last month, the InfiniTime community kept working on the features I wrote about in last month’s update, and some of the features being work on have already been merged in the *develop* branch of the project. These new features will be available in the next release of InfiniTime. Just to recap, the new features will include, among others, an airplane mode, the terminal watchface and improvements to the heart rate sensor management.

The community is very active and is creating pull-requests faster than we can possibly review, test and merge them. This is also true for the feature requests – there are currently 91 pending features requests. I’m really grateful to be surrounded by such an enthusiastic and understanding community whose people understand that we are working on the project in our spare time, and that the features will be done when someone will find the time to work on it.

This month, I’m happy to announce that InfiniSim, the InfiniTime simulator, is now its own dedicated project. NeroBurner, the author of InfiniSim, joined the team to develop and maintain the project under the InfiniTime organization on GitHub. We worked together to create the project and to ensure that all the InfiniTime code modifications needed were applied to support the simulator. InfiniSim allows everyone and anyone to run the whole InfiniTime UI on their computer. It even runs on the PinePhone Pro!

InfiniSim running on the PinePhone Pro

You can use InfiniSim to easily design and debug new apps for InfiniTime from the confort of your powerful computer without even needing to flash it over (and over again) to the PineTime. I am also planning on using InfiniSim to take screenshots of the menus and apps of InfiniTime and add them to the project’s documentation. Take a look at this impressive mosaic!

If you are interested in using or contributing to InfiniSim, please check out the project page. It also provides useful information on how to build and run it.

 

That’s all for now, catch you next month! 

27 responses to “March Update: Introducing the QuartzPro64”

Leave a Reply to Tristan Cancel reply

Your email address will not be published.

I accept the Privacy Policy

    Please for the love of all that we hold dear do NOT create a Google Glass type device. We only just managed to avoid the privacy nightmare that gg would have made, normalizing the surveillance of not just the user, but also all of the unconsenting people around them, all the time.

    Even if it were made by privacy conscious devs, this project being successful would only encourage Google to pick it up again in a way that would be a huge step backwards for privacy and security.

    Google Glass is dead. Let’s keep it that way.

    On the other hand, personal assistants are actively out in the wild and rapidly growing already. That will continue regardless of what Pine does. We need an alternative here. Most FOSS people are looking to Mycroft without realizing their funding model or reading their horrific “privacy” policy that would make even Google blush.

    Meanwhile Stanford University has released Genie which is FOSS, private and in some ways more advanced than Siri/Aleca/Google Assistant. Unlike the proprietary assistants, it doesn’t just search for a limited set of keyphrases. It aims to understand the intent of what you say. What they are desperately missing though (with multipage discussions on their forum) is decent hardware.

    Pine64 + Stanford Genie (+Home Assistant?) would make a powerful partnership that imprives the world. It would go a long way to creating something devs, tinkeres and users would love while reclaiming a massive amount of privacy.

    Please, give the community the open smart speaker they’re already clamouring for rather than reviving Google’s personal surveillance device.

    “Please for the love of all that we hold dear do NOT create a Google Glass type device. We only just managed to avoid the privacy nightmare that gg would have made, normalizing the surveillance of not just the user, but also all of the unconsenting people around them, all the time.

    Even if it were made by privacy conscious devs, this project being successful would only encourage Google to pick it up again in a way that would be a huge step backwards for privacy and security.”

    That’s like saying the US shouldn’t build a new missile system, because it might confirm to it’s enemies that it would actually work, and then they’d go build one too to use against the US. That’s ridiculous.

    Anywhere you go you will find cases of companies abusing technology, it is not specific to wearable technology. Regardless, I highly doubt it would ever reach a mass market, as it is a niche device (PINE64 isn’t moving more than a few thousand of any of their products, as they have a niche segment of the market).

    I’m not agreeing what those companies do is good, but whether you like it or not it’s already far too invasive to avoid. Cars have built-in internet connections that they send telemetry with and track your vehicle… Phone location is tracked by cell towers… Smart speakers with cameras and microphones that listen to you are in millions of people’s houses already (Alexa)… And there’s already cameras everywhere.

    Just because such devices exist doesn’t mean they are ethical. Software that spies on users is bad no matter how popular it is. And just because there are already cameras on the streets doesn’t mean we should give up on privacy. We should be trying to make things better, not worse.

    Maybe such device would be so useful that it would be worth giving up our privacy, but then you would need to give us reasons why. Just saying the we are already being watched isn’t a good argument.

    shinkamui says:

    Not sure where you’ve been, but the dystopia has been around us for a long time. Everyone has a cellphone with a camera on it, and every one has their face buried in it all the time now. You can’t tell who’s recording you, whos just recording, and who’s playing candy crush. HMDs are really cool, and so is augmented reality. The Fudd surrounding glass was unfounded and silly. People abuse stuff, thats the nature of the beast. Sorry, but I don’t think living in crippling fear of a possibility is rational.

    In that case there is no reason for Pine64 to exist and to make privacy oriented devices. Because as you said we are already being spied on everywhere, so we should just accept it and give up. There is no reason to make Free Software either, because there will always be proprietary software that restricts us and spies on us anyway. We should replace our PinePhones with Android phones and use Windows on desktop. Companies abuse their users, that’s the nature of the beast. We will fail anyway, so fighting for privacy is irrational.

    Having privacy and control with the data and hardware in your own device, and having privacy _in public spaces,_ are two separate issues in my book. Not to say that one is more important than the other, but losing privacy (if we ever had any) in public doesn’t mean that we can’t still take measures to protect the parts of our life that can still be kept private, like your own home and your data.

    Awesome ideas! I was interested in Mycroft myself, but what you said might be a huge problem for me. Could you give me some examples from their privacy policy so that I don’t have to read the whole thing? Also what is their funding model?

    I’m worried that privacy will always be an issue with those devices, because our data will always go to somebody else’s server. How hard would be it to self host such server at home? Only then we could truly own our data.

    Nicholas Ipsen says:

    It seems that the QuartzPro64 is almost the size of a mini-ITX boards; will it have ATX-compatible mountpoints?

    Lukasz Erecinski says:

    Why is it (permanently?) mounted inside a container? Why is it all red? … I’ve got so many questions

    Dave Harper says:

    Regarding the PineTab, it’s been years since the original design – that’s a generation in “tablet time”. If it is ever resurrected will it be a newer design to take advantage of the advances that have been made since the original? This was the product that first attracted me to Pine64 and I had created a project targeted to this device. That project currently runs on a Raspberry Pi with an external touchscreen which was used for the original development. It is a poor substitute for a tablet and I’m still hoping the PineTab will eventually happen.

    Geoffrey Stokes says:

    I really like the idea of a open hardware speaker and assistant!

    I’d love a pair of open hardware TWS earbuds or wireless ANC headphones with an open foss assistant. (Or wireless open ack headphones with an LDAC)

    Speaker is absolutely the right device. I’d probably get at least three Amazon echo equivalents if they were Foss. Family would get more.
    A foss assistant would be a viable angle to get foss into many homes. Lots of people would value it.

    Lukasz Erecinski says:

    I too like the idea. If developers could somehow marry Volumio with Mycroft, and have it run on a device that would match (or just exceed) Echo’s price-point, then that would be worth considering. Designing a speaker chassis which could host a SOPine would likely be the best way to go, especially since there is a build of Volumio for the LTS (compatible with SOPine).

    Lukasz Erecinski says:

    It would have a speaker or two as well as microphones. What do you need the screen for? Volumio has a web-UI available.

    pabloyoyoista says:

    Hey, work about integrating the fingerprint backcase was mentioned in the TL;DR but I couldn’t find it in the post. Did it maybe slip?

    Piotr Masłowski says:

    Why not pine64.eu though? It even seems like you do own that domain. Or is that one actually fake?

    Lukasz Erecinski says:

    Fake and rather dodgy. I MAY try to take pine64.eu from them in the future, but it would likely mean going to court, which means: time, money and effort …

    Will there be an upgrade path for the PineBook Pro so that the existing board can be replaced with one that’s equivalent to the QuartzPro64?

    This would be even more important as it could reduce future pressure to source LCD pannels (only first time buyers of “Pine Book Quartz” or whatever it will be called would need LCD pannels ; previous owners of Pinebook Pro would “just” need a replacement board).

    I hope it will not have the same short-coming as the Pinebook upgrade board (Pro’s RK3399 had hotter thermals than PB’s A64 and couldn’t work in the plastic case).

    Bonus point if such future successor of the Pinebook Pro could have charging circuit that takes a wider range of voltage and amperage inputs (USB-C PD and QC3.0 – just like the Pinecil) to charge faster while simultaneously in use.

    QuartzPro64 – there are really NO GPIO or similar??

    Ok, given the price, you’d want to be careful if it had GPIO, but complete lack thereof turn this from the sbc deluxe I wished for into a (mere) PC mainboard…

    (still, good news:))

    Are there any updates regarding DevZone and bounties for development tasks?

    I’d be interested in being able to donate money towards for some of the tasks to “sweeten the pot” on tasks that I personally think are valuable. Are community donations something being considered in DevZone when it’s live?

    Could you use name/id HTML properties so that individual sections can be linked to directly? (at least for the main sections)

    Chris Rapier says:

    When you are building out the kernel for the QuartzPRO64 would it be possible to include support for common 10G NICs? I know the PCI 3.0 won’t support full line rate but it’s still a good 4Gb+ of throughput.

Subscribe to the PINE64 blog