this post was submitted on 18 Jun 2024
0 points (NaN% liked)
Technology
59099 readers
3181 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So if I'm developing a garage door opener using ESP32 RISC-V module, I'm not a RISC-V developer? The dev tools and the cross-compiler only come in x86_64 variant, they simply won't work on RISC-V laptop. But at least they provide a Linux installer.
The only use case I can think of is to build Debian packages on a target architecture without cross-compilation, because many packages do not support cross-compilation, but it's more an issue of poor build scripts.
RIEC-V is as far as I know very new as a processor.
This means most of your software that works on Linux, Windows, Mac, Android or anything similar doesn't do so on the new processor.
This means you need developer who will port it or write new software for it. While crosscompiling is possible it is usually easier to have real hardware to test on. Not even to write the software on that device. You still can write it on your x86-64 pc and then either compile it on the RISC-V pc or crosscompile and test it only on the RISC-V pc.
For people who want to do this,it is targeted I think.
Tech enthusiasts who like new stuff.