Live data from Hacker News

Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance

cnx-software.com

91–100 of 105 posts

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

#91
post #89

Earlier quoted context omitted.

> don't want them dealing with non-profitable sales to hobbyists Have said hobbyists pay an appropriate amount of money. If an expert of TI can help me get started I'd find something like 100-200€/h reasonable. > or buying small quantities to poke around and copy IP Anyone wanting to steal IP for profit can already do so, most datasheets are available on pirate sites.

It would cost more than that.

200€/h results in a gross yearly income of ~380k €. That should be way more than enough, even accounting for overhead costs.

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

#92
post #89

Earlier quoted context omitted.

It would cost more than that.

200€/h results in a gross yearly income of ~380k €. That should be way more than enough, even accounting for overhead costs.

Overhead is typically 40-50% for this kind of corporation. So not really enough.

However the calculation has nothing to do with what guessing a reasonable hourly rate.

The issue is whether someone with the expertise to do this would benefit the company and their own career more doing something other than a tech support role.

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

#93
post #31

Earlier quoted context omitted.

"The vendor" is a foundation that has education at the center of its charter. https://en.wikipedia.org/wiki/Raspberry_Pi_Foundation They are not doing this for profit, although they are self-financing at this point (from what I've read).

Ostensibly, yes. But consider that Eben Upton is an ex-Broadcom guy that helped build videocore and that they get everything at cost, and it looks like an incredibly powerful PR move for Broadcom with side benefits.

Well, I like to think the better of people. I don't know Eben, but he comes across (in what he wrote and I've seen him speak) as honest, unassuming and set on the mission (even if he is now running the commercial side).

I'd give some minor portion of my anatomy to be part of something like the Raspberry Pi project and make some sort of difference (even if it might be seen as pandering to geeky tinkerers rather than helping schoolchildren, it's still one of the most fun and rewarding things I can envision as an engineer).

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

#94

Earlier quoted context omitted.

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

i.MX8 requires blobs for HDMI. The controller will only load an NXP signed blob. No blob, no HDMI (or displayport). https://forums.puri.sm/t/the-i-mx8-cannot-be-deblobbed-nxp-s...

But it will boot and run. It has other display outputs you may use.

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

#95
post #83

Does anyone have a good solid modern guide or pointers on making easy 3D stuff in text/CLI mode (not x-windows, etc), and hopefully using a convenient library? I'm trying to make a simple fast-booting instrumentation display. I picked up a Pi zero and muddled my way through what I could in C/C++ from piecemeal guides, and from text boot mode managed to initiate a graphics mode and draw a spinning triangle. Think I th…

ImGui [0] Immediate-mode UIs are by far the easiest for quick and dirty work. Near trivial to get stuff up on screen you can interact with. [0] https://github.com/ocornut/imgui

Thanks for the pointer, will check it out.

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

#96
post #83

Does anyone have a good solid modern guide or pointers on making easy 3D stuff in text/CLI mode (not x-windows, etc), and hopefully using a convenient library? I'm trying to make a simple fast-booting instrumentation display. I picked up a Pi zero and muddled my way through what I could in C/C++ from piecemeal guides, and from text boot mode managed to initiate a graphics mode and draw a spinning triangle. Think I th…

If you’re OK with .NET, you can try my library: https://github.com/Const-me/Vrmac/ The library supports both X windows, and bare OS kernel DRM/KMS. Spinning textured cube: https://github.com/Const-me/Vrmac/tree/master/RenderSamples/... Spinning teapot with lightning, inertia, mouse and keyboard input, etc: https://github.com/Const-me/Vrmac/tree/master/RenderSamples/... Dependencies: https://github.com/Const-me/Vrmac/…

Thanks kindly, will take a look.

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

#97
post #3

Dumb question - if I want to do simple image processing on a pi4 (2d ffts, small kernels, summing 2d arrays in one dimension, finding Maxima), and I care about performance, is this a reasonable stack to use,with decent prospects or is it faster/safer to stick on the Arm, despite the GPU. 1k x1k monochrome images, at 3-10 fps ( or more)? Jetson nano seems to be the obvious commodity but pricier alternative with GPU ac…

An extremely rough estimate, FFT (prolly the most expensive one of what you mentioned) needs 5N*Log2(N) operations. If you have 1M source floats and want 60 FPS, translates to only 6 GFlops. On Pi4, on paper the GPU can do 32 GFlops. Again on paper, the CPU can do 8 FLOPs/cycle which translates (4 cores at 1.5 GHz) to 48 GFlops. That’s assuming you know what you’re doing, writing manually-vectorized C++ http://const.…

It still gives me a giggle that the flops numbers you're talking about were supercomputer-level when I was a kid, and now I can buy that kind of power with beer money and lose it in the back of a drawer.

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

#98
post #92

Earlier quoted context omitted.

200€/h results in a gross yearly income of ~380k €. That should be way more than enough, even accounting for overhead costs.

Overhead is typically 40-50% for this kind of corporation. So not really enough. However the calculation has nothing to do with what guessing a reasonable hourly rate. The issue is whether someone with the expertise to do this would benefit the company and their own career more doing something other than a tech support role.

> Overhead is typically 40-50% for this kind of corporation. So not really enough.

Even assuming 50% overhead something just short of 200k remains. I agree, for the US it may be on the lower end of the scale (given the ridiculous costs of housing and healthcare), but Europe or Asia? Way more than enough.

> The issue is whether someone with the expertise to do this would benefit the company and their own career more doing something other than a tech support role.

At least in my experience it is definitely good for people to spend time directly with customers. I agree it may not be worthwile for a chip developer or a documentation writer to spend their full time on doing support - but a set amount of time, say four or eight hours a week? That's direct, unfiltered input from the customers where the documentation is either missing, unclear or buggy.

Generic questions ("which combination of chips to choose if I have an USB-C female receptacle and want to provide bidirectional PD, bidirectional DisplayPort and USB3.2 over it") / 1:1 tutoring like "how do I best route a PCI-E differential lane pair", "how to properly calculate trace widths for said lanes given fab house X's stack specifications" can be directed to less specialist / sales staff or to a partner PCB design house.

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

#99
post #79

Earlier quoted context omitted.

Often it has been that Vulkan is closer to how GPUs work simply due to GPU manufacturers having to change their GPUs to work well with Vulkan. To for example add a co-processor to the GPU so that it can do job scheduling in a more Vulkanish way. Vulkan was after all a spec from one GPU manufacturer (AMD), there are a handfull others with their own archs developed with their own assumptions.

Mantle was the single GPU manufacturer API, Vulkan was based on Mantle, but its creation had input from all the major vendors including Nvidia.

'had input' = can be accepted, not 'is also based on'

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

#100

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…

> 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…

Just because Ubuntu has "ARM distros" doesn't mean those "ARM distros" have the necessary drivers needed to actually use all features of your SBC. The fact that Vulkan support in raspberry pi landed in 2020 should tell you something.

Even the most well known SBC series is getting driver support at a glacial pace. When was the last time you waited for your x86 iGPU to get vulkan drivers?

Post reply on HN