40 ms·
My Unholy Battle with a Rock64
- rjsw 5y agoIf the author likes NetBSD then they are probably familiar with pkgsrc, there is a package for u-boot for the Rock64 that will take care of combining it with the ARM Trusted Firmware. I'm currently debugging the lima DRM driver for NetBSD.
- matrix12 5y agoNetBSD works fantastically on my army of Rock64Pro systems. Thanks for the contributions. It is much simpler due to folks like you putting in the hard work.
- fargle 5y agoWell written! That sounds about right, normal process for bringing up Linux on a new ARM single board computer. Actually sounds like everything worked fairly clean. Doing it yourself is a lot of "fun" and a good learning experience.
- marktangotango 5y agoNice write up, very informative, thanks for taking the time and sharing. There are a lot of these sbc's around nowadays, I've always been hesitant to explore them, for exactly the reasons here (huge learning curve).
- adultSwim 5y agoI appreciate making a post that ends in failure. Worthwhile to document your progress for others, as well as acknowledge that we don't always figure it out.
- orangepurple 5y agoThat ARM requires "trusted" (LOL) firmware to boot at all makes me cringe. I'm not sure I "trust" that firmware.
- matrix12 5y agoCompared to the undocumented blobs RPI gear makes you load, the documentation of the Rock64 stuff is all open.
- CameronNemo 5y agoIt is just the name of the project. The TF-A project is 100% open source.
- ranma42 5y agoIts just the reference implementation of the EL3 "Secure world" monitor, and this is where some of the power management stuff is implemented according to ARM standards (e.g. PSCI). Technically I'm pretty sure you could do without it, but then you'd need to amend the devicetree and drivers to handle power state transitions. On the Rockchip SoC in question, boot security is disabled by default, so you can compile it yourself from source and run your own modified version if you want to.
- taffronaut 5y agoTrusted Firmware is an open governance project[1] and you build it from source. It's not 'required' by Arm. It's perfectly possible to boot without it, as demonstrated by most if not all Qualcomm CPUs. [1] www.trustedfirmware.org
- c0l0 5y agoThis post nicely sums up why I just cannot get excited about anyone's announcement of some new and (on paper) awesome SBC with specs much better than those of a contemporary Raspberry Pi. Software ecosystem support is THE killer feature for this class of device. And the RPI has, despite its fundamental shortcomings (needing the proprietary GPU to manage bootup, etc.), the best story in that particular department by so much that it's not even a contest.
- jancsika 5y ago> And the RPI has, despite its fundamental shortcomings (needing the proprietary GPU to manage bootup, etc.), the best story in that particular department by so much that it's not even a contest. Exactly! On the RPI if I want to watch HBO Max without stuttering, all I do is apt install Chromium in Raspbian Buster, fuck around with a dozen or so startup flags, give up, try Kodi, notice that there's no official plugin, install a conceivably legal plugin from "http://k.slyguy.xyz http://k.slyguy.xyz", unzip it, twiddle some quality settings, and put up with intermittent stuttering that's slightly better than when I started the whole process. I'm just guessing at the Kodi part[1] since I've only made it to the "give up on Chromium" part so far. Anyway, it's probably less work than what the author describes. Probably. 1: https://www.firesticktricks.com/hbo-max-kodi-addon.html https://www.firesticktricks.com/hbo-max-kodi-addon.html
- RealStickman_ 5y agoI have a Pi 4 and a Rock64Pro, both with LibreElec (basically Kodi) installed. The video playback performance and stability of the Pi 4 beat the Rock64 handily.
- arinlen 5y agoWhat an outstanding read. It even had an element of suspense. In the very least, it makes us appreciate those cheap raspberry pi alternatives that work out of the box.
- StillBored 5y agoThis is what you get with 99% of the arm SBC trash. They will generally boot the one hacked up kernel the vendor ships, which are overwhelmingly about 5 years out of date because its the kernel they hacked up for the original high margin customer, and by the time the SoC is publicly available its basically abandonware. Outside of rpi's which have boatloads of community support, about the only boards that aren't this way are the systemready ES/SR certified ones. There is a IR level too, but its still using DT, meaning that the linux kernel devs will break the machine at random times requiring firmware/DT updates when newer kernels are loaded. The ES/SR bands use UEFI+ACPI and provide a standardized platform that is the same as what one expects of a random pc.
- unregistereddev 5y agoAgreed. In this case, the vendor doesn't ship a working kernel at all. Their view is that the community will handle that. Massive props to ayufan, without whom most of the Pine SBC's would likely have no bootable image. I experimented with a RockPro64 a few years ago before learning this lesson. The hardware sounded wonderful. Unfortunately, there was some kind of conflict between the PCIe slot and the GPU. It was possible to get hardware-accelerated video, or use the PCIe slot for additional SATA slots, but not both at the same time. I spent a fair amount of time trying to dig into it, but never did establish whether the problem was in hardware, the device tree, or the drivers.
- CameronNemo 5y agoThe SoC vendor ships a functional kernel for the rk3328 (which is in the Rock64), but it is indeed hacked up. The Rock64 runs mainline Linux these days with pretty much everything working except the video decoder. Even the successor Rockchip SoC, the rk3566, has great mainline support despite only being released last year.
- frostwarrior 5y agoIt's sad to see that. Looks like my only option for a fast ARM workstation are the M1 macs
- HidyBush 5y agoDevelopers should just stop putting up with this nonsense and start migrating to non proprietary RISC-V boards. We already have low cost options for developers who want to get their feet wet, the moment we start having a decent community around a RISC-V microcontroller, a RISC-V router and a RISC-V dev board then the ecosystem will be very desireable.
- rjsw 5y agoMost of the blog post described trying to use hardware features that are missing from RISC-V dev boards.
- repiret 5y agoHelp me understand how RISC-V solves these problems? It doesn’t offer a standard way to enumerate hardware in the SoC, so you still need device trees; it’d not a GPU, so you still need to deal with proprietary GPU drivers; it doesn’t standardize clocking or DRAM controllers, so you still need uboot or some other first stage boot loader; AFAIK, it doesn’t standardize power management, so you still need secure firmware or equivalent. The need to PXE boot comes from only having one boot device supported by the board, which isn’t solved by RISC-V PCs (partially) solve these problems because the BIOS plays the role of secure firmware and first stage boot loader. Hardware enumeration is solved by having most things be PCI-attached and the bios providing ACPI to enumerate the rest.
- HidyBush 5y agoI was talking about non proprietary boards on the whole, not just the CPU. Also if everything is documented it's not a big deal to customize your bootloader to do all the needed stuff. Of course standards would be very welcome, but at least you wouldn't need some arcane knowledge to get things running
- repiret 5y agoI don't think access to SoC documentation would have solved very many of the problems described in the article. The author still would have had to fiddle with device trees, secure firmware, u-boot, pxeboot, and getting a kernel with the right drivers built in. RISC-V also doesn't solve SoC documentation access. Most of Arm's CPU documentation is freely available, its all the other stuff SoC vendors bolt on that's hard to get access to. I don't see RISC-V changing that.
- hatware 5y agoI went deep on the Pine64 ecosystem, the RockPro64s are pretty nifty with all their inputs, but all (5) of my Rock devices are collecting dust because, like OP, I discovered the ecosystem is still embryonic. I think progress will continue to be made, just at a snails pace.
- megous 5y agoActually RockPro64's SoC RK3399 SW support is fully open and mainlined... from DRAM code, to low level suspend to RAM code, to bootloader and platform firmware with development originally mostly supported by Google. So if you think that SoC's support is in embryonic state, I don't think your standards are reasonable. :) You can pretty much just do a common builds of unmodified TF-A, U-Boot and Linux and get a working system. I can count platforms with lacking SW support on all my fingers, easily, but RK3399 is not it.
- hatware 5y agoNot sure you read my comment thoroughly. I called the RockPro64 nifty, followed by mentioning all 5 of my Pine64 devices are collecting dust. It's embryonic across all 5 devices and that's pretty clear once you get to the camera, or phones.
- megous 5y agoI don't think you wrote your comment thoroughly. ;) You mentioned RockPro64 and then that you have 5 Rock devices, and Pine64 doesn't have many Rock boards, just RockPro64 and Rock64. Pro one is maybe supported better.
- candiddevmike 5y agoHad the same battle with Rock64 and a Pinebook Pro. RPI has UEFI support (https://github.com/pftf/RPi4 https://github.com/pftf/RPi4) that makes the entire bootloader process so, so much simpler. I wish Pine would provide something similar for every chipset they produce. U-boot is too hard to understand/script, give me a standard UEFI interface that I can use with native linux tools like efibootmgr and systemd-boot.
- NoahKAndrews 5y agoLook into the Tow-Boot project. They're trying to replace the paradigm of distributions shipping their own hardware specific u-boot implementations with a u-boot platform firmware that gets saved to dedicated storage and presents a UEFI interface for distributions to use. A bunch of Pine64 devices are supported!
- yepguy 5y agoThere's Tow-Boot[1] for UEFI support. It looks like they support the Pinebook Pro but not the Rock64. I'm happily using it on my RockPro64, although I did need to disable USB initialization to get it to boot on mine[2]. [1]: https://tow-boot.org/devices/index.html https://tow-boot.org/devices/index.html [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973323 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973323
- candiddevmike 5y agoWow! I'm glad I made some noise then, I even see odroid-n2 on there. This will help a lot, thank you for sharing.
- rjsw 5y agoThere is the Tianocore EDK II [1] for the Quartz64 [1] https://github.com/jaredmcneill/quartz64_uefi https://github.com/jaredmcneill/quartz64_uefi
- mike_hock 5y agoWhy TF is the device tree in some patch from John Doe on IRC and not in an official download on the manufacturer's website?
- auxym 5y agoPine's whole schtick is "cheap hardware with nice specs but zero software support". You can like it or not but they're pretty open about the business model.
- deleted 5y ago[deleted]
- tadfisher 5y agoThe device tree is in mainline. The patch is for enabling the HW video decoder, which is currently being reviewed for 5.19. The person on IRC just pointed to the patch.
- CounterPillow 5y agoHi, John Doe from IRC here. I made this account just to reply to you. The patch to the (already mainlined ages ago) device tree is not "on the manufacturer's website" because it is already on the Linux kernel's website. To which I linked. And it will be in Linux kernel 5.19. Unlike Broadcom's fruit-themed tax evasion scheme, we strive to mainline support for the devices, so that you do not need manufacturer specific patches and mainline Linux just works out of the box. The berries wrinkle their nose at this approach, as they'd rather use a proprietary boot chain with their own kernel fork and pre-made SD card images containing forks of Debian for maximum handholding. Meanwhile, I'll be content booting fully open and auditable firmware with mainline bootloaders, kernels and userlands. We all have our own priorities.
- mike_hock 5y agoFair enough, thanks for the clarification.
- tedunangst 5y agoExperts predict year of the arm desktop to arrive not long after year of the linux desktop. People were saying "it's only this first generation, things are getting better fast" since before arm64.
- zokier 5y agoYear of ARM desktop arrived pretty much with M1 Macs
- candiodari 5y agoJust as it did with Alpha's. Just as it did with Itanium. Just as it did with PowerPC. Just as it did with MIPS. Just as it did with Transmeta. Just as it did with ARM last time ( https://en.wikipedia.org/wiki/Acorn_Archimedes https://en.wikipedia.org/wiki/Acorn_Archimedes ) The year of replacing the x86 architecture never arrives ... Frankly, I would probably give Itanium the best odds (Intel + Microsoft behind it), then Alpha (Microsoft behind it).
- nebula8804 5y agoHave you actually tried M1 Macs? They are truly a wonder to behold. Not comparable in any way to the garbage you listed.
- phendrenad2 5y agoThe PowerPC G3 "eats Pentiums for breakfast"...
- klelatti 5y agoI’m completely baffled by this comment. Itanium is dead, never made it to the desktop and so has zero chance and we have an actual mass market Arm desktop available - and apparently selling very well.
- _vdpp 5y ago
- MisterTea 5y agoArm really messed up by not standardizing a sane firmware standard around their arch similar to (minus the wintel brain damage) what Intel did with the PC and provide a simple OS interface to query and configure hardware. Instead we have this device tree madness.
- _vdpp 5y agoThere’s a lot more to a computer than just a CPU or instruction set, and it’s borderline negligent for these companies to avoid developing standards for the surrounding ecosystem. RISC-V was initially guilty of this too, but I think they’re finally coming around and publishing some guidelines for what the rest of a RISC-V computer should look like. I miss the days of standardized I/O ports, BIOS interrupts and memory-mapped devices at published addresses. Now, with ACPI, you practically need to run an entire VM in kernel to figure out what’s connected, and the complexity of drivers makes it very difficult for the hobbyist to interact directly with hardware.
- phendrenad2 5y agoIt made sense when ARM was only selling cores for android phones and embedded devices. Maybe they're just stuck in a comfortable groove.
- madduci 5y agoThis story reminds me of the Adventures I've experienced while getting a Wandboard with a FreeScale I.MX6Q to a latest version rather then the official Image offering Xubuntu 11.10. No binary blobs available for the graphic card (actually there was a triple graphic chip boosted from Vivante) and Xorg in newer versions couldn't detect it. If you were running an apt-get upgrade on the official image, the very next boot could made the UI experience broken. I still have the board but I use it headless for pihole and wireguard, but the whole ARM experience becomes awful when it comes to graphic acceleration and the drivers aren't open source and not maintained anymore.
- zokier 5y agoThat sounds unfortunate, I was under the impression that imx series socs were relatively foss friendly and in particular the vivante gpu would be well-supported by free etnaviv driver. Quick googling found that Debian Buster (i.e. oldstable at this point) should work relatively smoothly? > On 2017-12-14 Debian Buster (currently 'testing') was tested and running GNOME on Wandboard almost worked right out of the box. (In Buster the GNOME session uses Wayland by default instead of Xorg.) The only change needed was reserving contiguous memory, see the 'cma' section above. https://wiki.debian.org/InstallingDebianOn/Wandboard https://wiki.debian.org/InstallingDebianOn/Wandboard
- discardedrefuse 5y agoExcellent write up. The world of cheap SBC's is a hot mess right now. I recently researched and bought one for my own project, and I feel like I've commented about it on HN several times already, but here we go again. A Raspberry Pi's is by far the easiest way to go, but I've found they have become way too expensive. If anyone is looking at cheap SBC's I suggest you pick one with Linux kernel mainline support. Here is a good place to start: https://linux-sunxi.org/Linux_mainlining_effort https://linux-sunxi.org/Linux_mainlining_effort A lot of the newer SBC's aren't supported yet. This means that you will be stuck using the vendor's Linux distribution until support lands in the mainline kernel (which could be never). If you get an older SBC with mainline support, you can run 3rd party distros like Armbian. https://www.armbian.com/ https://www.armbian.com/
- throwaway894345 5y agoI’m really surprised that the only way to get a consumer ARM chip is to buy an SBC or else a fully assembled computer (e.g., Mac Mini). I really want to build my own low-power server, but it seems like the only way to go is to buy a Raspberry Pi compute module and a carrier board (I’m not even sure where to find one of decent quality), and even then I’m either stuck with the SBC memory/gpu or maybe I can supplement with some PCIe stuff (although it seems like a complete gamble as to whether or not the Pi will support a given device). Why isn’t there a market for standalone ARM chips and motherboards like there is for x86?
- pm215 5y agoThe answer to this is essentially that CPUs are only cheap if you make them in huge volume, and "I want something that's like a PC but not actually PC compatible" is a pretty small market, so an SoC designed and manufactured for that niche would just be too expensive for anybody to buy. So if you try to target that niche you are going to be doing it with an SoC designed for some other market, and accepting the tradeoffs that come with it. The traditional high-volume Arm CPU market is mobile, which is what almost all these SBCs are borrowing parts from, and you don't have PCIe on a mobile phone, so no PCIe on an SBC using a mobile part. Possibly as more Arm server chips appear something usable in a desktop form factor will appear, but I suspect that you'll end up just seeing a different set of tradeoffs instead (e.g. much higher price per part).
- NelsonMinar 5y agoCan anyone explain why the ARM ecosystem is like this? So many comments in this discussion about how all SBCs other than the RPi are terrible to get booted. Why is it like that? Why hasn't the market settled on one bootchain? (Asking for my next home server!)
- bri3d 5y agoBecause the way most ARM SoCs work is this: * Vendor integrates a bunch of IP (Cortex, codecs, GPU), tapes out SoC design. * Vendor has challenges hiring or retaining excellent software engineering team, because VLSI and hardware are the core competencies that make money, not software. * Vendor's struggling software engineering team hacks copy-pasted code together until they can produce a board support package against a single Linux kernel version, with no care to upstream. Once the device boots in a single configuration, they ship it. * Vendor's also struggling documentation team attempt to use sketchy descriptions from engineers to produce documentation. Often, internal interfaces are ignored or not documented since "it works" - only the external interfaces needed to make the chip run are documented. Now, an OEM buys the SoC and BSP. Sometimes they do some extra work to get the BSP to work with a newer kernel, and sometimes they don't. And if they do, they hack on top of the hacks, so the divergence increases and now there are multiple devicetree versions floating around (as happened with this Rock64 board).
- DCKing 5y agoI wonder at what point, if ever, the economics of ARM chip makers [1] starts to work in favor of ARM chips supporting full UEFI and ACPI for hardware initialization like x86 boxes do. I may be mistaken, but I thought some more "enterprise grade" ARM hardware already does UEFI+ACPI, as well as perhaps the Surface Pro X Windows 10 ARM device with a Qualcomm ARM SoC? You'd imagine at some point the maintenance costs for the chipmakers themselves as well as the increased interest / adoption rates from customers would tip the economics of all of this firmly towards standardization of this mess. Then again, I may not fully understand the economics here, or how much cheaper the current hacky approach is. [1]: Looking at you, Rockchip, Amlogic, Mediatek, Unisoc, Allwinner, Broadcom and the list goes on. I hope the Raspberry Pi Foundation + Broadcom can take the opportunity with the Raspberry Pi 5 or something to lead the way, but I'm not optimistic at all.
- zxcvgm 5y agoI have a Rock64 and I don't remember it being that difficult to setup. Maybe I was just using it as a headless machine, but to get a working Linux install shouldn't have been this hard. I typically use Arch Linux because it's very barebones, and Arch Linux ARM has a working setup [0] for the Rock64. You do need to write various parts like U-Boot bootloader onto the SD card manually, but everything has been pre-compiled. If you prefer an image that you can directly flash onto an SD card like Raspbian, then maybe you can try Armbian [1]. These should get you a working Linux install rather quickly, bringing you to up to the "sixth circle" as written by the author. [0] https://archlinuxarm.org/platforms/armv8/rockchip/rock64#installation https://archlinuxarm.org/platforms/armv8/rockchip/rock64#ins... [1] https://www.armbian.com/rock64/ https://www.armbian.com/rock64/
- oynqr 5y agoI can second this, I have a Rock64 and have had zero problems with it, even when tinkering with custom u-boot builds.
- carlsborg 5y agoAny opinions on peripheral support and software, especially the camera module?
- JeremyNT 5y agoYes indeed, OP specifically chose "hard mode" here by not using a distribution that supports it with a prebaked image. That's fine for the OP! They probably wanted to experiment and tinker, no problems there. But it seems to have given a lot of people in this thread the wrong idea about how well supported these devices are for normal users.
- stuaxo 5y agoPeople like op are how progress is made. A lot of this will be upstreamed and people will use the info from ops article then fill in a bunch of the gaps.
- Teknoman117 5y agoDid anyone ever figure out the hardware video acceleration on the Rock64Pro / Pinebook Pro? Bought one two years ago and it still doesn't seem to work with the official Linux image (Manjaro ARM?).
- megous 5y agoIt's supported since late 2018 in the kernel, based on generic v4l2-requests interface. So anything that uses v4l2-requests should have video acceleration working. That should be all gstreamer based apps at the very least. Various codecs were gradually stabilized and moved to public API over the last few years. There's no support in ffmpeg for v4l2-requests API, and nobody forward ported old Bootlin vaapi wrapper driver around v4l2-requests API to the stabilized public version of the API, yet. So app relying on these programs/interfaces don't get the acceleration, atm.
- tuckerpo 5y agoPCIe training and enumeration just doesn't work most of the time on RK SoC. Painful stuff. Mediocre platform that's impressive on paper only.
- megous 5y agoRK356x has a different PCIe controller, which works better.
- confident_inept 5y agoAll of the Pine64 stuff is like this and it's detestable. I had a RockPro64 for a while that I had tons of trouble getting to work for almost these exact reasons (largely thanks to uboot). Got rid of my Pinebook Pro for similar reasons. Pine64 makes tons of interesting devices then relies almost 100% on unpaid post-consumer-hobbyist interest for any usability outside of a hacked together barebones ecosystem. Even their unique PineTime, which has been out for some time, is at a barely functioning level and I have zero hope for the PineNote at this point. I really wish they cared about more than spinning out flashy hardware and patting themselves on the back.
- stryan 5y agoIsn't that the point of the org though? They spin out cheap hacker-friendly ARM hardware at cost for interested hobbyists and that's about it. They're very clear[0] that they don't necessarily provide software outside of the bare basics for it. [0]https://www.pine64.org/philosophy/ https://www.pine64.org/philosophy/
- tmountain 5y agoI went through hell trying to get a NanoPC-T4 (RK3399) board to work with NixOS. Getting everything working took up roughly a month of my free time and required engagement with multiple communities (including Armbian) and a bunch of digging to cobble together bits of information into a coherent build process (reading shell scripts from distros, etc). I did finally get everything working, and I wrote some documentation to capture it. https://nixos.wiki/wiki/NixOS_on_ARM/NanoPC-T4 https://nixos.wiki/wiki/NixOS_on_ARM/NanoPC-T4 What I learned in the process is that Nix is a great resource to see how to get lots of Arm chipsets to bootstrap with Linux. Specifically, the uboot config file. https://github.com/NixOS/nixpkgs/blob/master/pkgs/misc/uboot/default.nix https://github.com/NixOS/nixpkgs/blob/master/pkgs/misc/uboot... By reading that, you can get a good view into what proprietary blobs and tools are necessary to get various boards working. As an added bonus, since Nix is declarative and versioned, weird boards should continue to work for the long haul. Ironically, once I got the board up and running, I completely lost interest. Turns out the challenge of getting it to work was scratching a particular itch, not actually using it in practice.
- phendrenad2 5y agoIt's too bad the ARM world seems vehemently opposed to UEFI/ACPI. On x86 platforms, you can rely on a standard interface for everything... Loading the kernel from the UEFI partition, enumerating PCIe and USB devices, console input/output, even drawing simple 2D graphics to the framebuffer. DeviceTree is just a file format, it's not really an alternative to the guarantees that UEFI/ACPI provide.
- megous 5y agoU-Boot is the defacto standard in the cheap ARM SBC land, which is mosty based on SoCs meant for something else, like TV boxes, etc..
- phendrenad2 5y agoYes, U-Boot seems to be designed to load kernel images from flash ROM. I doubt it can handle, for instance, loading a kernel image from a hard drive connected via USB.
- megous 5y agoWhy would it not? It has a generic block layer, generic USB host mode support and mass storage class support: https://github.com/ARM-software/u-boot/blob/master/doc/README.usb https://github.com/ARM-software/u-boot/blob/master/doc/READM...
- phendrenad2 5y agoAh I see. So uboot is roughly equivalent to PC UEFI BIOS, but configuration is more open to the user.
- CounterPillow 5y agoWhether or not a particular strain of u-boot supports booting from a certain medium or interacting with a certain thing in general is often more a function of whether said strain of u-boot is new enough (measured through mainline) and whether the particular PHY and controller has a driver in u-boot. For example, the vendor u-boot on my RK3588 dev board can even PXE boot, because u-boot has that functionality and the vendor u-boot has GMAC and Ethernet PHY drivers. Rockchip SoCs builtin "maskrom" can read u-boot (or whatever other bootloader you use, Quartz64 with its RK3566 actually has a Tianocore EDKII port for full UEFI) from either SPI flash, eMMC or SD. The boot mediums after that are entirely up to said bootloader. This is not somehow special to ARM, your x86_64 PC motherboard just comes with an SPI flash chip that has firmware like this flashed to it from the factory. Some SBC vendors are doing this as well now, e.g. ODROID is shipping u-boot+Petitboot (which seems like a bad idea, kexec is fragile from what I know) right on a flash chip included on the board. The difference with RK3328 as found on the ROCK64 and RK3399 as found on the ROCKPro64 or Pinebook Pro is that you are not at the mercy of your vendor to provide you with firmware updates. Everything (TF-A, u-boot, and kernel) is included in the main repository for those particular projects and will be maintained going forward, and you can build it from source and hack on it at any time. It's not a u-boot fork from 2017 languishing in some dumping ground of a GitHub repository.
- Sophistifunk 5y agoAn old fish swims past a couple of young fish, and says, "morning lads, how's the water?" the young fish look at each other briefly, and one asks, "what's water?" The water in this case is Linux. All I want is a handful of risc CPU cores, a few gb of ram, and a framebuffer device with a good blitter. Something well-documented so I can play with the metal.
- ankurdhama 5y ago> That’s important because the boot process for ARM SoCs is almost entirely non-standard, and any similarities between chips is largely incidental. This is exactly why I am not on the hype of ARM for personal computing. It's like every computer with ARM SoC is completely different beast.
- ulzeraj 5y agoI’ve tried using á RockPro64 with FreeBSD 13.0-CURRENT and although it runs just fine without hacks I’ve noticed the performance is not that good. FreeBSD is not big.little aware so it doesn’t distinct between the A53 and A72 cores. Cryptographic hardware acceleration is not very good. On the other hand most Linux distros work quite well. Then there is the piece of flaming crap that is the ASMedia PCI-E SATA card that they sell along with the board on their store. That thing cannot handle 2 SSDs and its not a problem with power delivery. Replacing it with some marvel based cards.