Live data from Hacker News

Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

cnx-software.com

61–70 of 105 posts

Re: Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

#61

Earlier quoted context omitted.

It's important to note that competitive x86 SBC do exist, and have the typical, full, x86 support. Of course, the downside is that the price is higher (around twice as much for a full system). A downside of ARM SBCs is that they pretty much all have an expiry date. Due to their closed nature, when the community pulls the plug, they're gone (SW-wise). x86 boards last virtually forever. While they're somewhat compatibl…

With pi's that last point is at least somewhat mitigated. The foundation has committed to supporting specific hardware for several years.

Heck, they still support the original Pis and A+; I just installed the latest version of Raspberry Pi OS on my A+ with 128 MB of RAM, and while it is slow, it works just the same.

Re: Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

#62
post #38

Earlier quoted context omitted.

It's important to note that competitive x86 SBC do exist, and have the typical, full, x86 support. Of course, the downside is that the price is higher (around twice as much for a full system). A downside of ARM SBCs is that they pretty much all have an expiry date. Due to their closed nature, when the community pulls the plug, they're gone (SW-wise). x86 boards last virtually forever. While they're somewhat compatibl…

There's quite a bit more to it than that, though. First, the "closed nature" thing is just as true about x86 as it is about ARM; you don't get full specs for any machine these days, Broadcom or not. Rather, from the perspective of "Linux developers who write code on and deploy to Linux" — or maybe "Linux Desktop Users" — the difference is in peripheral discovery and setup, of which x86 has ACPI and UEFI to dynamicall…

[deleted]

Re: Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

#63

Earlier quoted context omitted.

we're pretty much there. The new pi 4 compute module breaks out the pcie bus. The official pi4 compute base board routes that to a standard pcie x1 slot instead of USB 3.0 which is a massive win in my book (hello more ethernet/sata/fpga/nvme/etc). It's a baby Arm mobo with pci and I'm a little excited :-) I have a pi4 compute + base board on pre-order plus I just bought a pcie x1 m.2 M-key card off amazon. I plan to…

Almost! :) Not sure about the IO performance of this solution. > The official pi4 compute base board routes that to a standard pcie x1 slot instead of USB 3.0 Do you have more info on this? I am not sure how it works.

Also check out https://www.jeffgeerling.com/blog/2020/raspberry-pi-compute-...

Re: Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

#64

Earlier quoted context omitted.

No GPIOs there, though.

Sure, but the post I replied to specifically said > The vendor just doesn't want to acknowledge the real role of Raspberry Pi is not limited to being a cheap tinkerer board anymore To me, tinkering means GPIO. That's why I was asking why the want for a Raspberry Pi, why not get something else that already exist. I'm curious what they're looking for. Of course if they still want GPIO then that's a valid point.

> not limited to being a cheap tinkerer board anymore

being not limited to being a cheap tinkerer board doesn't mean not being a [slightly less cheap] tinkerer board among the rest of roles. I didn't mean I don't need GPIO. I actually want more GPIO so I could connect a "hat", an infrared port, a cooler and still have spare pins for actual tinkering.

Another cool thing available exclusively with Raspberry Pi is polished Raspbian OS coming with free Mathematica and other goodies.

Hardware codecs also feels nice and, AFAIK, you don't get them with x86.

At last but not at least (this arguably is the most valuable part actually) it is THE SBC. This means it's easy and efficient to target for a developer (incl hardware developers) and easy and efficient to share problems and solutions for the community.

Re: Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

#65

Earlier quoted context omitted.

With pi's that last point is at least somewhat mitigated. The foundation has committed to supporting specific hardware for several years.

Heck, they still support the original Pis and A+; I just installed the latest version of Raspberry Pi OS on my A+ with 128 MB of RAM, and while it is slow, it works just the same.

It helps that the pi zero hasn't been superseded yet, and probably won't be for a long time. (They've surprised me, heck, everybody, before though)

Re: Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

#66
post #48

Earlier quoted context omitted.

What would you recommend in the x86 space?

I haven't actually purchased it myself so can't recommend as such, but for example the Biostar A10N-8800E looks[2] interesting. Has a quad core AMD APU, 2x DDR4 DIM sockets, PCIe 3.0 x16 slot, one M key M.2 slot, 2x SATA, 2x USB 3.1 Gen 1. Board itself with integrated CPU costs just ~20% more than the Raspberry Pi 4 8GB, at least here in Norway. Add in 8GB of value memory and a small/spare PSU and you should be not f…

> 2x USB 3.1 Gen 1.

USB 3.1 Gen 1 means simple USB 3.0, right?

Re: Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

#67
post #36
post #27

Earlier quoted context omitted.

For first year(s?), Broadcom RPi components (GPU) were closed source (opaque binary blob) and need RE work. For a hardware supposed to be "open to hack", it was considered a non-sense. I suspect things have changed regarding RPi situation.

Is there an "open" SBC by your definition? Intel has ME/AMT, and requires an opaque, PK-signed-and-only-intel-and-NSA-have-the-key blob. AMD is the same with PSP. I'm not up to date, there might be a RISC-V core available today that is blob free, but in 2012 when RasPi was introduced I wasn't aware of anything blobless.

Freescale's i.MX SoCs are full open. No blobs at all. Check them out. They are sweet. Boards exist.

Re: Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

#68

Earlier quoted context omitted.

Sure, but the post I replied to specifically said > The vendor just doesn't want to acknowledge the real role of Raspberry Pi is not limited to being a cheap tinkerer board anymore To me, tinkering means GPIO. That's why I was asking why the want for a Raspberry Pi, why not get something else that already exist. I'm curious what they're looking for. Of course if they still want GPIO then that's a valid point.

> not limited to being a cheap tinkerer board anymore being not limited to being a cheap tinkerer board doesn't mean not being a [slightly less cheap] tinkerer board among the rest of roles. I didn't mean I don't need GPIO. I actually want more GPIO so I could connect a "hat", an infrared port, a cooler and still have spare pins for actual tinkering. Another cool thing available exclusively with Raspberry Pi is polis…

Ah, fair enough.

> At last but not at least (this arguably is the most valuable part actually) it is THE SBC.

I'm not sure a significantly more expensive, but more powerful, Raspberry Pi would have the same market appeal. Then again, what do I know :)

Re: Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

#70
post #2

This is what sets the raspberry pi apart from all other SBCs in my experience: software support. Kudos, this is fantastic stuff! Will love to see the ecosystem of stuff that springs up that takes advantage of this.

It's important to note that competitive x86 SBC do exist, and have the typical, full, x86 support. Of course, the downside is that the price is higher (around twice as much for a full system). A downside of ARM SBCs is that they pretty much all have an expiry date. Due to their closed nature, when the community pulls the plug, they're gone (SW-wise). x86 boards last virtually forever. While they're somewhat compatibl…

> While they're somewhat compatible with standard Linux distro, in order to have full support, one needs to use the adhoc ARM distros.

Maybe you mean something specific by "adhoc" or "full support" that isn't apparent to me, but Ubuntu has ARM distros today and I expect that ARM support is only going to get better as (1) ARM continues to make headway in the server space and (2) Apple Silicon pressures desktop/laptop OEMs to adopt ARM.

Post reply on HN