HNHacker News
TopNewBestAskShowJobs

LeFantome

2,162 karma · joined August 14, 2020

submissionscomments
LeFantome··on What is RISC-V and why it matters to Canonical
> platform fragmentation

RISC-V is addressing this issue quite directly. For things like desktops, laptops, SBCs and servers we have the RVA23 profile which defines quite specifically what features a chip must support to ensure code portability.

On top of this, there are platform specifications. For example, the server spec is about to finalize next month. It extends RVA23 which things like UEFI, SBI, and ACPI to ensure that your can take something like a Linux distro and easily install it on any RISC-V server, like you can in the world of x86-64.

> we have phones that are only good for landfill once their support lifetime is up

RISC-V will probably not solve that problem in general.

First, the ISA cannot really demand that your phone avoid a Broadcom wireless chip that requires proprietary firmware for example.

Also, the phone vendor can still lock down the devices to prevent running arbitrary code.

Thankfully, the RISC-V world is developing a culture of openness. If a company wants to create a fully “open” phone, they are quite likely to adopt RISC-V. And, because of RISC-V, even the SoC itself could be fully Open Source.

But your typical Android phone is not going to get more Open just because they contain a RISC-V CPU.

LeFantome··on What is RISC-V and why it matters to Canonical
Pinecil?
LeFantome··on What is RISC-V and why it matters to Canonical
SiFive, Tenstorrent, and other big RISC-V firms are not Chinese.
LeFantome··on What is RISC-V and why it matters to Canonical
ARM is RISC and dominates x86 in most markets.

In 2026, RISC-V is not what I would call “low end”. Look up the P870-D, or Ascalon, it C950.

Do you think Apple spends more money than Intel on chip design?

LeFantome··on What is RISC-V and why it matters to Canonical
There are many more RISC chips than not. Apple Silicon is RISC. All ARM is RISC (eg. Raspberry Pi).
LeFantome··on What is RISC-V and why it matters to Canonical
Yes, extensions are perfect for embedded. But not just there.

Extensions allow you to address specific customer needs, evolve specific use cases, and experiment. AI is another perfect fit. And the hyperscaler market is another one where the hardware and software may come from the same party and be designed to work together. Compatibility with the standard is great for toolchains and off-the-shelf software but there is no need for a hyperscaler or AI specific extension to be implemented by anybody else. If something more universally useful is discovered by one party, it can be added to a future standard profile.

LeFantome··on Why has the most influential RISC-V startup just cut 130 people? (2.5 yrs old)
> astonishingly poor investment

Very brave of you to put that on the Internet.

They claim to have customers using P870-D silicon today. That is about Neoverse N2 performance territory, except SiFive claims 25% smaller die area and lower power (at the same process size).

Now they have $400 million to push that further.

https://www.sifive.com/blog/investing-in-our-next-chapter-of...

If SiFive can grab even a fraction of a hyperscaler market, they are going to be worth a lot more than $3 billion.

LeFantome··on SiFive Raises $400M to Accelerate High-Perf RISC-V Data Center Solutions
Apologies, I responded in the wrong place so see my other comment. Here is the most relavent bit...

"Today, with over 500 design wins and our customers shipping more than 10 billion SiFive-based cores, SiFive has proven-in-silicon quality that customers can rely on."

LeFantome··on SiFive Raises $400M to Accelerate High-Perf RISC-V Data Center Solutions
"Today, with over 500 design wins and our customers shipping more than 10 billion SiFive-based cores, SiFive has proven-in-silicon quality that customers can rely on."

"SiFive’s 3rd Generation of Performance CPU IP, the P870-D, is up and running in customer silicon and is designed to be highly competitive with the ARM Neoverse N2 class in the data center."

https://www.sifive.com/blog/investing-in-our-next-chapter-of...

Sounds like just a bit more than CHISEL specs. Perhaps people are tripping over themselves to give SiFive $400 million for a reason.

LeFantome··on Top laptops to use with FreeBSD
Those barely work with Linux.

And I have found the WiFi to be incompatible with some networks.

LeFantome··on LibreOffice – Let's put an end to the speculation
Are you thinking of Code Weavers?
LeFantome··on Iran's IRGC Publishes Satellite Imagery of OpenAI's $30B Stargate Datacenter
Do it
LeFantome··on Japanese, French and Omani vessels cross Strait of Hormuz
One third of Americans voted Democrat.

One third voted Republican.

One third did not vote.

I hold the last group most responsible.

LeFantome··on Japanese, French and Omani vessels cross Strait of Hormuz
What “checks and balances”?

The SCOTUS ruled that presidents cannot be held accountable.

The constitution is pretty clear. Trump does not have the authority to invade Iran. Yet he did. What are you planning to patch?

Despite everything, Trump has 35-40 percent approval right now. You cannot patch that out.

LeFantome··on Japanese, French and Omani vessels cross Strait of Hormuz
Your point seems to be that the US has not changed. Regardless, the world thinks it has.

The “coalition of the willing” is not behind the US this time.

LeFantome··on Claude Code Found a Linux Vulnerability Hidden for 23 Years
The fact that most AI bug reports are low-quality noise says as much or more about the humans submitting them than it does about the state of AI.

As others have said, there are multiple stages to bug reports and CVEs.

1. Discover the bug

2. Verify the bug

You get the most false positives at step one. Most of these will be eliminated at step 2.

3. Isolate the bug

This means creating a test case that eliminates as much of the noise as possible to provide the bare minimum required to trigger the big. This will greatly aid in debugging. Doing step 2 again is implied.

4. Report the bug

Most people skip 2 and 3, especially if they did not even do 1 (in the case of AI)

But you can have AI provide all 4 to achieve high quality bug reports.

In the case of a CVE, you have a step 5.

5 - Exploit the bug

But you do not have to do step 5 to get to step 2. And that is the step that eliminates most of the noise.

LeFantome··on Claude Code Found a Linux Vulnerability Hidden for 23 Years
Sure he wrote a port scanner that obscures the IP address of the scanner, but does he know anything about security? /s

Oh, and he wrote Redis. No biggie.

LeFantome··on RISC-V is the Future – Jiachen Project
RISC-V is not a "CPU technology". It is an ISA.

I assume the primary "regime" you refer to here is China. What they have shown is that, if forced to, they are perfectly capable of producing their own domestic technologies and industries. Given that, I would vastly prefer them to use an open and sharable standard like RISC-V rather than to create a fully incompatible ecosystem that forces global supply chains to schism completely.

But of course the other "regimes" that are looking to RISC-V for independence are places like Europe and Canada. Were those the places you meant?

LeFantome··on Alibaba revealed the XuanTie C950, a 5-nanometer RISC-V Chip for agentic AI
As nice as this is, it is one of two years out. Hopefully Tenstorrent will have gotten to this performance level first.

What I really want to see is a C930 that I can buy today.

LeFantome··on Samsung's BM9K1 PCIe drive's controller is based on RISC-V delivering 11.4 GB/s
“The company said the RISC-V design enables more granular firmware optimization for QLC NAND management and AI-specific I/O patterns, resulting in a 23% improvement in energy efficiency over the BM9C1.”

A 23 percent power reduction is pretty nice. These kinds of custom instructions are why RISC-V is going to continue killing it in microcontrollers.

LeFantome··on The RISE RISC-V Runners: free, native RISC-V CI on GitHub
I should have replied differently.

“Good enough” here was meant to mean good enough to sell more, and therefore to drop prices.

That is already happening. It just needs to happen more. And I think it will. If you don’t find the RISC-V boards of 24 months from now “good enough”, that is ok with me. I just want them to get cheaper.

The other thing that is happening on that front is that microcontrollers are getting more powerful and staying inexpensive. You can get RISC-V microcontrollers today with similar performance to the original Raspberry Pi and with things like WiFi, Bluetooth, and USB. They are crazy cheap and there are many projects for which they are now “good enough”. And, of course, they keep getting better.

LeFantome··on From Proxmox to FreeBSD and Sylve in Our Office Lab
I agree with you and do not understand the “I read every manual” and “I test all software” crowd. I play around with A LOT of software but I cannot test it all.

Speculation is not useless if you are saying “the answer I got makes it 99% likely that this solution will not work for me”. Curation has immense value in the world today. I investigate only the options most likely to be useful. And that still takes all my time.

LeFantome··on The RISE RISC-V Runners: free, native RISC-V CI on GitHub
Well, part of “good enough” is features. The RVA23 profile was ratified a few months ago and the first chips are appearing now. That brings RISC-V to feature parity with X86-64 and ARM, including things like vector instructions and virtualization. QUbuntu 26.04 is compiled to require RVA23. So, the RISC-V advocates got that part right. Of course, the other side of “good enough” is performance.

The SpacemiT K3 has the multi-core performance of a 2019 MacBook Air and higher AI performance than an M4. That is better multi-core than an RK3588. If it were less expensive, the K3 would already be good enough for many people.

Alibaba has the C930 which is faster than the K3. We will see if it gets released to the rest of us.

Tenstorrent will release a chip in a few months that is twice as fast as the K3.

The recently announced C950 is supposed to be even faster but will be a year or more.

Of course, “good enough” is subjective but my statement was based on the above.

But you are right that there have been some false starts.

The SG2380 was just as fast as K3 and was ready to go two years ago. TSMC refused to manufacture it over US sanctions.

Ventana was about to release a very fast RISC-V chip but Qualcomm bought them.

Rivos was very close to releasing a RISC-V GPU but Meta bought them.

But even without these high-end chips, RISC-V is enjoying great success. It is taking over the microcontroller space. And billions of RISC-V cores are shipping.

LeFantome··on The RISE RISC-V Runners: free, native RISC-V CI on GitHub
RISC-V microcontrollers are inexpensive but “application” processors will be expensive until volumes increase.

Performance will get “good enough” over the next 2 years. Prices will drop after that.

LeFantome··on The RISE RISC-V Runners: free, native RISC-V CI on GitHub
The RISC-V ISA can be fast.

Tenstorrent Ascalon, expected later this year, is expected to be AMD Ryzen 5 speeds. Tenstorrent hopes to achieve Apple Silicon speeds in a few years.

The SpacemiT K3 is about half as fast as Ascalon and available in April. K3 is 3-4 times faster than the K1 (previous generation).

This should give you an idea about how fast RISC-V is improving.

LeFantome··on Key E-3 AWACS Damaged in Iranian Attack
It is looking more and more like Iran is the Ukraine to the US being Russia.
LeFantome··on The RISE RISC-V Runners: free, native RISC-V CI on GitHub
You can get RVV instances from Saleway.
LeFantome··on The RISE RISC-V Runners: free, native RISC-V CI on GitHub
Not yet

RV64GC (C910 cores)

LeFantome··on The RISE RISC-V Runners: free, native RISC-V CI on GitHub
That has been the case so far but is changing this year.

The SpacemiT K3 is faster than QEMU. Much faster chips are expected to release over the next few months.

I mean things like the Milk-V Pioneer were already faster but expensive.

One thing that has been frustrating about RISC-V is that many companies close to releasing decent chips have been bought and then those chips never appear (Ventana, Rivos, etc). That and US sanctions (eg. Sophgo SG2380).

LeFantome··on The RISE RISC-V Runners: free, native RISC-V CI on GitHub
RISE is supported by many legit companies. Stealing is for sure not the intent.

The idea is to promote testing on RISC-V and to eliminate lack of hardware for being the reason not to. Obviously, low budget projects and Open Source are the primary targets. Commercial products can afford real RISC-V hardware.

This is who you are trusting: https://riseproject.dev/members/

← PreviousPage 6 of 32Next →