News for hackers. Stuff that matters.
Re:Sipeed Longan Nano – RISC-V Development Board by tyingq on Friday August 30, 2019 @08:57AM (#20838088)
No ARM-like revenue based royalties, and broadly supported, including mainline Linux kernel support. So, companies like Western Digital are all in. And, if someone makes an "open source" CPU with it, to match the open source ISA, it's a win for trusted computing.

Also popular here because some folks imagine a new ecosystem of cheap Rpi type boards with no magical binary blobs. See, for example, lowrisc.org (though they seem far from shipping)

Re:Sipeed Longan Nano – RISC-V Development Board by slezyr on Friday August 30, 2019 @09:13AM (#20838206)
> Also popular here because some folks imagine a new ecosystem of cheap Rpi type boards with no magical binary blobs. See, for example, lowrisc.org (though they seem far from shipping)

I thought that the biggest blob in most linux systems is GPU driver and RISC-V doesn't solves this.

Re:Sipeed Longan Nano – RISC-V Development Board by ben-schaaf on Friday August 30, 2019 @09:53AM (#20838588)
The AMD graphics drivers are completely open source.
Re:Sipeed Longan Nano – RISC-V Development Board by pb82 on Friday August 30, 2019 @12:06PM (#20839878)
The drivers are, but not the firmware running on the GPU (i think it's called Video BIOS). I'm not sure if a completely free GPU exists. But this is not something that RISCV is concerned with.
Re:Sipeed Longan Nano – RISC-V Development Board by ansible on Friday August 30, 2019 @03:53PM (#20842007)
There are actually RISC-V extensions designed for numerical computation, though I don't recall if you could actually do a shader core or something like that based on RISC-V.

At any rate, I hadn't heard about anyone trying to make a completely open GPU. That would be cool though.

Re:Sipeed Longan Nano – RISC-V Development Board by floatboth on Friday August 30, 2019 @12:50PM (#20840260)
"Video BIOS" (these days, more likely an EFI GOP driver) runs on the CPU and provides display output before the OS is booted.

On-GPU firmware is not that interesting or concerning, you can consider it part of the hardware.

Re:Sipeed Longan Nano – RISC-V Development Board by squarefoot on Friday August 30, 2019 @03:48PM (#20841957)
"On-GPU firmware is not that interesting or concerning, you can consider it part of the hardware. "

It depends on how it can communicate with the external world. If it only eats numbers and draws pixels, then no problems, but if its driver nature (ie, running at higher privileges than anything including root/administrator) allows it to create a covert channel with other hardware (say a network chip) and send vital information to the outside world, then it becomes a huge potential vulnerability. In open source systems, CPU/GPU/system chipsets firmware and closed device drivers are the places where malware can hide unnoticed for ages, and incidentally the one where it can do the most damage due to the aforementioned privileges, therefore those should be the first parts of a system in which we should demand for total openness.

A simple program with no access to files (therefore considered safe) reading the CPU load and populating a remote graph with numbers can become an effective spying tool if paired with another seemingly innocuous program which has no network access (considered safe as well) but reads files and busy loads one CPU core with values resulting from some encoding of the data it reads. They're 100% safe by themselves, but once paired (say because they're written by the same entity, or different entities obeying to the same government/s) they can exfiltrate information pretty easily. Back on the firmware topic, we can't know if there any seemingly unrelated device drivers talking each other unbeknownst of the system administrator, but should they do, that would be the most dangerous backdooring toolkit ever conceived. Until they stay closed, there's no way to know if they do other things.

Re:Sipeed Longan Nano – RISC-V Development Board by rrss on Friday August 30, 2019 @02:27PM (#20841161)
> On-GPU firmware is not that interesting or concerning

So people don't like it if kernel drivers are closed source, but if all the functionality is moved to firmware and the open kernel driver just pokes the closed firmware that does all the work it's fine? What? How does that logic work?

Re:Sipeed Longan Nano – RISC-V Development Board by jtl999 on Friday August 30, 2019 @05:11PM (#20842748)
Go ask the FSF with their questionable RYF certification. TLDR: As long as the firmware blobs are in ROM, who cares?
Re:Sipeed Longan Nano – RISC-V Development Board by debatem1 on Friday August 30, 2019 @02:52PM (#20841449)
Why is it neither interesting nor concerning? From a security perspective it would seem to be both-- hostile firmware could at the least read secrets from your screen, and I'd be shocked if it couldn't convince the corresponding kernel driver to misbehave in interesting ways. Not knowing what is actually in the blob, you have to assume it is at least potentially that malicious.
Re:Sipeed Longan Nano – RISC-V Development Board by mcbits on Friday August 30, 2019 @07:24PM (#20843623)
Correct me if I'm wrong (and I really hope I am), but it doesn't appear to be possible to use "pro" features like OpenCL with the open source AMD drivers, at least not with my 2400G APU. The last two times I tried, I had to install some blob that failed part-way through the installation and rendered my system unbootable.
Re:Sipeed Longan Nano – RISC-V Development Board by tyingq on Friday August 30, 2019 @09:21AM (#20838285)
There's a mystery boot blob in the RPi that's pretty famous.
Re:Sipeed Longan Nano – RISC-V Development Board by imtringued on Friday August 30, 2019 @10:21AM (#20838850)
I'm not sure what you are talking about. There is no such thing as a mystery boot blob in the Raspberry Pi. It is well known that the video core chip is the main processor of the Raspberry Pi. It runs a proprietary RTOS called ThreadX. As an afterthought someone added a bunch of ARM cores to the Video Core chip which obviously has to cooperate with the main processor to do anything at all.

https://www.heise.de/select/ct/2016/8/1460193213013079/conte...

Re:Sipeed Longan Nano – RISC-V Development Board by tyingq on Friday August 30, 2019 @10:32AM (#20838980)
So you're saying there's source available for the boot binary?
Re:Sipeed Longan Nano – RISC-V Development Board by wolfgke on Friday August 30, 2019 @09:38AM (#20838467)
This is because of the specific architecture of BCM2836, BCM2837, and BCM2711B0, which are rather VideoCore chips with appended ARM cores.
Re:Sipeed Longan Nano – RISC-V Development Board by wolfgke on Friday August 30, 2019 @09:39AM (#20838472)
> I thought that the biggest blob in most linux systems is GPU driver and RISC-V doesn't solves this.

It makes no sense to counter a hypetrain with intelligent arguments. :-)

Of course, you are right.

Re:Sipeed Longan Nano – RISC-V Development Board by makomk on Friday August 30, 2019 @10:00AM (#20838651)
There's already a lot of Allwinner-based Pi clones with no magical binary blobs, though - depending on the board the only blob may be the non-modifiable boot ROM, which is actually quite convenient for low-level hackers since it just loads your own bootloader from one of several devices and gets out of its way. This includes support for raw NAND flash so in theory you can avoid even having a binary blob in your storage device if you get one of the few boards with raw NAND onboard.
Re:Sipeed Longan Nano – RISC-V Development Board by panpanna on Friday August 30, 2019 @09:01AM (#20838112)
Arm license cost is nothing compared to what they have invested in testing and QA. One round of asic that fails is significantly more expensive.

If you are jumping on risc-v to save money you have your priorities very wrong. On the other hand if you are Huawei and can't do business with arm...

Re:Sipeed Longan Nano – RISC-V Development Board by abainbridge on Friday August 30, 2019 @09:53AM (#20838589)
This argument used to come up when I worked at Cambridge Silicon Radio, where we made ASICs. We made our own CPU designs for those ASICs.

Some of the engineers thought making our own CPU designs was a stupid idea and some thought that switching to ARM designs was a stupid idea. The only fact I have is that our CPU designs were not the main cause of bugs in our chips. If you asked the digital designers, they'd say things like, "Why are software engineers so interested in CPU designs. The kinds of embedded CPUs we need are easy to design. Implementing a correct power management state machine is hard. Implementing an efficient WiFi PHY is hard. Get off my lawn..."

Some problems with putting ARM CPUs in our chips were: a) integration engineering costs (ie find a way to multiplex some existing pins on the package with the jtag debug port), b) having to do price and contract negotiation with ARM (that part of the company was less efficient than the digital engineering team), c) finding that the change you wanted to make to the chip was incompatible with the ARM contract you'd just spent 6 months negotiating.

Re:Sipeed Longan Nano – RISC-V Development Board by btashton on Friday August 30, 2019 @10:13AM (#20838775)
But you also left developers with really hard to use dev tools based on a fork of gcc. The arch also left you having to do all kinds of mental gymnastics when writing code to make sure you were keeping the size down.

That said the chips certainly did there job at a good price point once you got everything stable and fixes made to the binary blobs that you had no way to debug.

Re:Sipeed Longan Nano – RISC-V Development Board by abainbridge on Friday August 30, 2019 @10:39AM (#20839046)
> But you also left developers with really hard to use dev tools based on a fork of gcc

Yep. Sorry about that. Not that it was my fault. Anyhow, I guess my belief is that a similar company to CSR could put RISCV cores in their chips now, which would avoid the problem you describe and some of the problems I described with using ARM.

Re:Sipeed Longan Nano – RISC-V Development Board by ansible on Friday August 30, 2019 @03:57PM (#20842041)
Ah, the good old XAP processor. For a while you guys were marketing a BC03 or BC04 era chip as a general-purpose microcontroller with digital audio functions.
Re:Sipeed Longan Nano – RISC-V Development Board by panpanna on Friday August 30, 2019 @10:02AM (#20838673)
I believe CSR went out of business after burning an investment of $1bn with nothing to show for.

Not trying to be hostile, just pointing out how costly "let's design our own soc, how hard can it be?" is.

Re:Sipeed Longan Nano – RISC-V Development Board by lnsru on Friday August 30, 2019 @10:26AM (#20838914)
Are we talking about same CSR? It’s still in business. It’s now part of Qualcomm: https://en.m.wikipedia.org/wiki/CSR_(company)
Re:Sipeed Longan Nano – RISC-V Development Board by panpanna on Friday August 30, 2019 @10:32AM (#20838976)
Hmmm.. I stand corrected.

I know a few people who joined ARM after CSR closed down but that could be just some offices shutting down.

(not an arm employee, btw)

Re:Sipeed Longan Nano – RISC-V Development Board by abainbridge on Friday August 30, 2019 @10:44AM (#20839097)
The offices in Cambridge didn't shutdown. Approximately Samsung bought one building (WiFi), and a year later Qualcomm bought the other (BT + audio). Both Samsung and Qualcomm had rounds of redundancies but have also both hired lots of people. My guess is both offices are about the same fullness as they were ten years ago.
Re:Sipeed Longan Nano – RISC-V Development Board by tyingq on Friday August 30, 2019 @09:03AM (#20838136)
1.5% of your per unit revenue for a hard drive seems significant. WD seems to agree, and they don't seem like a risk prone company.
Re:Sipeed Longan Nano – RISC-V Development Board by panpanna on Friday August 30, 2019 @09:19AM (#20838263)
1.5% does sound significant, but does WD save 100% of those 1.5% by doing it in-house?

Furthermore, those 1.5% covered more than just the CPU (peripherals, buss technologies, patents, manufacturing know-how).

I'm not saying WD is wrong, but I think they are overestimating how much they can save. This is probably just to get a better deal from arm.

Re:Sipeed Longan Nano – RISC-V Development Board by hajile on Friday August 30, 2019 @11:22AM (#20839475)
1.5% of a big number is still a big number. Western Digital's revenue in 2018 was 18 billion. Even if only 0.15% of their revenue went to ARM, that would be 27M or enough to hire 100 chip designers at 270K each.

That would be enough people for a very advanced chip, but WD doesn't need to build the next supercomputer. Instead, they want a chip customized to handle their specific workload with high throughput and probably some specialized instructions to put some algorithms in hardware. Moreover, their RISCV chip design expense should reduce over time both because they don't need to change chip micro-architectures very often and because as more companies switch to shared, open hardware, the costs are reduced

Another example is Nvidia. They continue to hold an ARM license for several ARM designs and another license for their own custom Denver/Carmel designs. Despite this, they still opted to use RISCV in their GPUs.

These companies manufacture chip designs for a living. They certainly understand the costs involved and have determined the immediate and long-term costs are lower vs the provided benefits.

Re:Sipeed Longan Nano – RISC-V Development Board by phkahler on Friday August 30, 2019 @11:25AM (#20839489)
From their public statements, this is not to get a better deal from ARM. they are all-in with risc-v and have already made public their first core (among other things), which is better than an equivalent from ARM. At this point I dont think ARM could bring much to the table for WD. They've invested way beyond what makes sense for getting better pricing.
Re:Sipeed Longan Nano – RISC-V Development Board by pjc50 on Friday August 30, 2019 @10:30AM (#20838956)
It's not for the whole unit, just the chip? Isn't it Qualcomm with the whole-device royalties?
Re:Sipeed Longan Nano – RISC-V Development Board by tyingq on Friday August 30, 2019 @10:34AM (#20839006)
Seems you may be right, but how would you calculate the "chip selling price" for a chip inside a hard drive? It's not clear to me what the royalty charge is for a company like WD.
Re:Sipeed Longan Nano – RISC-V Development Board by pjc50 on Friday August 30, 2019 @10:44AM (#20839102)
Probably they've negotiated a nominal value with their ARM rep based on whatever they're currently using.
Re:Sipeed Longan Nano – RISC-V Development Board by jimktrains2 on Friday August 30, 2019 @09:21AM (#20838283)
> One round of asic that fails is significantly more expensive.

Does that change with ARM? If you're licensing the ISA, or even bits of HDL, you're still fabbing your own stuff, right?

If it was the choice between pre-made RISCV and pre-made ARM, then the licensing could play into a cost difference between models, but otherwise they'd both be pre-fabbed, ready-to-use-products?

Re:Sipeed Longan Nano – RISC-V Development Board by panpanna on Friday August 30, 2019 @09:31AM (#20838385)
But then why bother if you are just using someone elses pre-made macros with a fixed architecture (cpu + memories + peripherals + power & clock distribution)? At this stage, would it even be cheaper?

I think there is some merit to risc-v but people pushing hard for it's use RIGHT NOW don't seem to understand the challenges of SoC design and manufacturing.