<!doctype html><html><head>
<meta charset="UTF-8">
</head>
<body>I think the "made for Linux" is a reference to the board and not the chip.<br><br><div class="gmail_quote">On January 18, 2021 11:34:12 PM EST, jonhall80@comcast.net wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="font-size: 12pt; font-family: helvetica,arial,sans-serif; color: #333333;">
<span style="font-family: helvetica; font-size: 12pt;">All,<br><br></span>I have not really inspected the ISA for RISC-V to see if there were any instructions that were "designed for Linux" other than the normal instructions that would be there for almost any modern operating system for things like atomic operations, etc.
<br>
<br>Since RISC-V is a RISC computer, I would expect the instructions to be as simple as possible and allow the compilers to do optimization to make the chip run very fast.
<br>
<br>On the other hand, as you to up the stack of things necessary for speed, such as good design for cache, data transfer, etc. I would hope that the architects were able to jettison lots of legacy features that are not necessary in a completely new architecture that would not be needed for backward compatibility, and instead build in compatibility with 16-bit, 32-bit, 64-bit and 128-bit instructions.
<br>
<br>On the other hand, to talk about a BOARD that is "Linux compatible" I could see lots of things that would make it "Linux friendly", such as hardware interfaces for I/O that would be published and available to software developers, boot code that would have the sources published, having the ability for the kernel to interact with hardware interfaces built into the system, and the ability for hypervisors to work well with the board, again leaving behind some trade-offs done for previous operating systems.
<br>
<br>This is not to say that these other operating systems will not change over time to take advantage of this new hardware, it is just that some of the legacy stuff will be left behind.
<br>
<br>Just my thoughts on this.
<br>
<br>md
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div>
<blockquote type="cite">
<div>
On 01/18/2021 10:05 PM Michael Potter via Ale <ale@ale.org> wrote:
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
I skimmed the article.
<br>
<br>I did not see anywhere where it said what made it made for Linux.
<div>
</div>
<div>
Any clue?
</div>
<div>
</div>
<div>
I would expect two things....
</div>
<div>
</div>
<div>
Some kind of instructions specific for networking.
</div>
<div>
</div>
<div>
Instructions specific for fork().
</div>
<div>
</div>
<div>
</div>
<div>
</div>
</div>
<br>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">
On Sun, Jan 17, 2021 at 11:50 AM Jim Kinney via Ale <
<a href="mailto:ale@ale.org">ale@ale.org</a>> wrote:
</div>
<blockquote>
<div>
All true. Spark and Power are (mostly,?)dead and no longer produced outside of industrial gear.
<br>
<br>I guess my real enthusiasm is for the "designed for Linux" aspect.
<br>
<br>I don't play games so I'm not sure what runs all the consoles now. I also don't have any beagle toys yet. My electronic skills are really rusty and never were design oriented. I designed and built only one power supply and it was strange, variable current 0-5A at one pin pair, variable voltage 0-1000V on another pin pair, one pin common between the two. Basically a variac driven tube. The 0.5 F capacitor was fun.
<br>
<br>
<div class="gmail_quote">
On January 17, 2021 11:12:55 AM EST, Solomon Peachy <
<a href="mailto:pizza@shaftnet.org" target="_blank" rel="noopener">pizza@shaftnet.org</a>> wrote:
<blockquote>
<pre>On Sun, Jan 17, 2021 at 08:26:18AM -0500, Jim Kinney via Ale wrote:</pre>
<blockquote>
A fully open source cpu design is a game changer.
</blockquote>
<pre><br>Is it really? SPARC, and POWER have all had fully open ISAs and core <br>designs since 2005 and 2013, respectively.<br><br>As someone who has done low-level hacking on various architectures over <br>the years, the actual CPU core/ISA makes very little difference; most of <br>the headaches are in the rest of the system[-on-chip].<br><br>RISC-V might be fully open from an ISA perspective, but that doesn't <br>mean that any given SoC built on it has an open source CPU core, or that <br>any of the various controllers (DMA, display, audio, I2S/I2C/SPI, etc) <br>or accelerators (video codecs, crypto engines) are open source or even <br>have documentation available without three-deep NDAs.<br><br>Meanwhile, from the perspective of someone writing software, the <br>underlying CPU architecture rarely matters if you're not doing low-level <br>OS/compiler hackery or trying to hand-optimize performance-critical code <br>that can't be run on a GPU or more specialized accelerator.<br><br></pre>
<blockquote>
I was quite surprised to see fedora is ready to go on riscV. It's
<br>usually Debian or Ubuntu that's first on the ground for new gear.
</blockquote>
<pre><br><a href="https://sifivetechsymposium.com/wp-content/uploads/2020/01/Fedora_on_RISC-V_SiFive_BJ_2019.pdf" target="_blank" rel="noopener">https://sifivetechsymposium.com/wp-content/uploads/2020/01/Fedora_on_RISC-V_SiFive_BJ_2019.pdf</a><br><br>TL;DR: Fedora has a very strong "upstream first" mentality, and Red <br>Hatters contribute heavily to all of the upstream projects that needed <br>work to enable RISC-V and used Fedora's tooling to work out the kinks.<br><br>...meanwhile, has Ubuntu _ever_ preceeded Debian when it comes to <br>architecture/platform support?<br><br>(I don't mean "here's a pre-built image you can put on an SD card to <br> boot board X and you have to use our special snowflake kernel and <br> bootloader with binary blobs which preclude getting security updates <br> from the distribution")<br><br> - Solomon</pre>
</blockquote>
</div>
<br>--
<br>Computers amplify human error
<br>Super computers are really cool
</div> _______________________________________________
<br>Ale mailing list
<br>
<a href="mailto:Ale@ale.org" target="_blank" rel="noopener">Ale@ale.org</a>
<br>
<a href="https://mail.ale.org/mailman/listinfo/ale" target="_blank" rel="noopener">https://mail.ale.org/mailman/listinfo/ale</a>
<br>See JOBS, ANNOUNCE and SCHOOLS lists at
<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank" rel="noopener">http://mail.ale.org/mailman/listinfo</a>
</blockquote>
</div>
<br clear="all">
<div>
</div> --
<br>
<div class="gmail_signature" dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
Michael Potter
<br> Tapp Solutions, LLC
</div>
<div>
<a href="http://www.tappsolutions.com" target="_blank" rel="noopener">www.tappsolutions.com</a>
<br>+1 770 815 6142 ** Atlanta **
<a href="mailto:michael@potter.name" target="_blank" rel="noopener">michael@potter.name</a> **
<a href="http://www.linkedin.com/in/michaelpotter" target="_blank" rel="noopener">www.linkedin.com/in/michaelpotter</a>
</div>
<div>
Schedule a meeting with me:
<a href="https://calendly.com/michael-potter" target="_blank" rel="noopener">https://calendly.com/michael-potter</a>
</div>
</div>
</div>
</div>
</div>
</div>
</div> _______________________________________________
<br>Ale mailing list
<br>Ale@ale.org
<br>https://mail.ale.org/mailman/listinfo/ale
<br>See JOBS, ANNOUNCE and SCHOOLS lists at
<br>http://mail.ale.org/mailman/listinfo
</blockquote>
</blockquote></div><br>-- <br>Computers amplify human error<br>Super computers are really cool</body></html>