Live data from Hacker News

Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

liliputing.com

31–40 of 48 posts

Re: Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

#31
post #19

Earlier quoted context omitted.

All my (ARM) Orange Pi boards run Armbian just fine. This one, of course, is unlikely to, but I'm curious to see what it ships with.

I know Armbian for the Orange Pi 4 had broken video out for at least a year: https://forum.armbian.com/topic/26818-opi-4-lts-no-hdmi-outp... Haven't tried it on mine recently so no clue if it's better now.

Depends on whether things are officially supported or just community contributes, in my experience. I tend to stick to officially supported devices.

Re: Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

#32
post #27

Earlier quoted context omitted.

The CV1800B on the original 64 MB Milk-V Duo does not have an Arm core. It is otherwise very similar to the 256 MB and 512 MB SG2000 chips (Sophgo bought CVITECH, so the CV -> SG is just a rename)

Well, we can all expect sophgo will refrain putting ARM cores in their SOC in the future :( (... and I would not mind displayport instead of hdmi and av1/opus codec block instead of a mpeg one neither... 0 royalties...)

All MP3, MP4, and H.264 patents have expired, so you don't have to worry there. I don't get why more hardware doesn't adopt DisplayPort, though. At least HDMI ports accept DVI signals, and DVI is also in the public domain.

Re: Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

#33
post #14

Will this run off the mainline kernel? Or will require strange patches from somewhere? Half the problem with orange pi is lack of main Linux distribution support.

I have a similar issue with the MangoPi MQ Pro. Its great to have a RISC-V processor now but not having HDMI available on my SBC kinda massively sucks.

Re: Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

#34
post #27

Earlier quoted context omitted.

Well, we can all expect sophgo will refrain putting ARM cores in their SOC in the future :( (... and I would not mind displayport instead of hdmi and av1/opus codec block instead of a mpeg one neither... 0 royalties...)

All MP3, MP4, and H.264 patents have expired, so you don't have to worry there. I don't get why more hardware doesn't adopt DisplayPort, though. At least HDMI ports accept DVI signals, and DVI is also in the public domain.

I mostly agree with you, but nowadays codec blocks are mostly h.265 and ac3 :( They are smart as they will just do a little bit more things in a new codec and renew their patents. The thing is displayport, yep, something is off here, hardware ppl don't need a expensive hdmi connector, just another USB-C... I wonder if the HDMI people are not doing things in the shadow to end up favored...

That said, I have to point the fact, those patents are only valid in some countries, namely subject to royalties (USA, UK, Japan... but not EU for instance).

I don't know why raspberry is not selling some of their SOCs with the ARM blocks hard disabled at sell time, namely they did not pay for the ARM royalties.

In the end, it is near impossible to buy all those RISC-V boards in my country with a noscript/basic (x)html browser, and if possible with wallet codes (or bank swift) instead of a credit card.

Re: Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

#35
post #17

I was excited about Orange Pi ARM but they made an idiotic boot loader that always uses the SD when any SD is present. I think that's unacceptable for an "embedded" thing. This board also has a USB port where plugging in something it doesn't like takes down that entire bus until a reboot. It's cool to see RISC-V, but I'd go with a different company.

Why is that unacceptable?

If I have an SD card for extra storage and tuck it away somewhere, any interruption in power would mean it needs to be manually reset. I actually wanted something with SD storage that I could turn on and off remotely.

Re: Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

#36
Hmm. As a fairly non-experienced person with a strong interest in experimenting with RISC-V, I read the comments here, and the article, and still feel, maybe this isn't the thing to get me started. Maybe the ecosystem still isn't there for a beginner to jump in.

Is there such a thing as a (cheap) SBC that runs RISC-V, which has good documentation (books, forums, whatever) on getting started programming on it? I'd like to get into assembly more, and hardware, and I'm interested in RISC-V for its open nature, but it can feel overwhelming getting the foot in the door.

Or is this it, and I'm just being overwhelmed by all the talk? Where would I go to get clear documentation on programming and experimenting with an Orange Pi RV2, if I went that route?

Re: Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

#37
post #30
post #29

Earlier quoted context omitted.

Armbian adds all sorts of non-mainline Linux kernels and other stuff in order to achieve the hardware support it does have. Other more standard distros like Debian or Fedora don't do this.

Well, do you want things to work or are you willing to wait years until things are mainlined?

That's the thing, it forces me into a specific distro/kernel where the stuff that I actually want to run isn't available.

I have a pair of Orange Pi 5Bs and they didn't really replaced my old Raspberries after spending more time on it than what I was initially willing to spend on my upgrade.

Re: Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

#38
post #30
post #29

Earlier quoted context omitted.

Armbian adds all sorts of non-mainline Linux kernels and other stuff in order to achieve the hardware support it does have. Other more standard distros like Debian or Fedora don't do this.

Well, do you want things to work or are you willing to wait years until things are mainlined?

My definition of "work" is a Linux kernel that can be upgraded as CVEs are discovered and new features added. Modified versions of Linux usually aren't that, much of the time they are stuck on the same kernel version, which eventually leaves security support periods.

Re: Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

#39
post #30
post #29

Earlier quoted context omitted.

Armbian adds all sorts of non-mainline Linux kernels and other stuff in order to achieve the hardware support it does have. Other more standard distros like Debian or Fedora don't do this.

Well, do you want things to work or are you willing to wait years until things are mainlined?

> Well, do you want things to work or are you willing to wait years until things are mainlined?

What I want is for the SoC vendors to actually learn how to participate in the kernel process. Design their drivers from the ground up to be maintainable and mainlineable.

The problem with "wanting things to work now" that we've seen over and over and over in the ARM SoC world is that each family of chips ends up with its own fork of the kernel which never gets mainlined because of one or more of the following:

* It can't actually be compiled as provided

* Successful compilation depends heavily on the build environment which is undocumented

* It depends on binary drivers

* It is written in ways that do not meet the standards of the kernel

* It modifies kernel interfaces in ways that break other drivers

* It's just bad code in general.

When this happens the vendor might update it a couple of times over the product's profitable life but inevitably they will stop doing so. If there's enough of a community around the platform and they're lucky enough to have complete source it's sometimes possible for the community to take over development of the fork and try to port the vendor code to newer kernels while slowly cleaning it up. Most of the time though there's a binary driver somewhere critical to many if not all users which will only work with a certain range of kernel versions, at which point the community is left supporting an obsolete kernel and mostly just backporting relevant fixes rather than gaining anything new. Sometimes there's a way to shim an old driver to work with a new kernel, and sometimes a driver for a newer piece of hardware from the same vendor can be made to work on the older versions, but in neither case can it be counted on.

The worst part IMO is that it's usually not even a LTS kernel that these vendors decide to settle on, it's all too often one that was obsolete and unsupported before the SoC was ever in the public's hands. If you're going to launch a Linux-based product with no intent of mainlining the kernel code at least make it run either the latest LTS or SLTS kernel.

It doesn't take years to get code mainlined, lots of vendors are doing it every day for hardware that hasn't even been released yet. A lot of SoC vendors either just don't care or actively don't want to.

Re: Orange Pi RV2 is a single-board PC with an 8-core RISC-V processor

#40

Hmm. As a fairly non-experienced person with a strong interest in experimenting with RISC-V, I read the comments here, and the article, and still feel, maybe this isn't the thing to get me started. Maybe the ecosystem still isn't there for a beginner to jump in. Is there such a thing as a (cheap) SBC that runs RISC-V, which has good documentation (books, forums, whatever) on getting started programming on it? I'd lik…

You don't need new hardware for that, you can just use qemu.
Post reply on HN