Live now! Join @crowdsupply @helenleigh for a conversation with Tim Ansell (@mithro) about wafer.space, a new way for chip designers to easily turn a design into real, working chips: https://www.youtube.com/watch?v=tEOmnN8IAjs
#OpenHardware #OSHW #OpenSilicon #OpenPDK
#kr2025 is already over! A huge thank you…
... to all the speakers who made this edition such a success,
to our godfather @paulmckrcu who did an incredible job putting together and keeping track of the agenda,
to Jean-Christophe for making the livestream possible and running the sound and video so flawlessly,
to @Aissen for the amazing live blog,
to Erwan for his spot-on mic throws,
to Frank for joining us on this third day and adding that little touch of craziness to the conference,
""WE ARE NOT PREEMPTIVELY SUPPORTING BIG-ENDIAN ON RISC-V""
Linus send that to #LKML a few hours ago, after somebody asked if some of the big-endian work will make it into #Linux 6.18.
For the full thread, see: https://lore.kernel.org/lkml/CAHk-%3DwgYcOiFvsJzFb%2BHfB4n6Wj6zM5H5EghUMfpXSCzyQVSfA@mail.gmail.com/t/#mce138059dc56014643bbda330810183031ef5c06
There he calls the reasons documented on riscv.org as "craziness" and insane:
""In other words, it is suggesting that RISC-V add a big-endian mode due to
(a) internet protocols - where byte swapping is not an issue
(b) using "some RISC-V implementations don't do the existing Zbb extension" as an excuse
This is plain insanity. First off, even if byte swapping was a real cost for networking - it's not, the real costs tend to be all in memory subsystems - just implement the damn Zbb extension.""
@mithro spoke about his new company wafer.space on the Amp Hour podcast. wafer.space will fab designs on Global Foundries 180nm (GF180MCU)
https://theamphour.com/703-building-wafer-space-with-tim-ansell
The photo/artwork is amazing
It's almost October which means it's almost Open Hardware Month! We are so excited for another OHM with all kinds of exciting events all over the world. We'll be running another membership livestream event running 12 hours and featuring OSHW creators who do incredible work. Mark your calendars and get excited because there's going to be really amazing speakers and perhaps even some sloths! How are you celebrating Open Hardware Month?
When a vendor wants to control upstreaming process and objects to community-led patches, I’ll just point to this brilliant response from @conor:
It’s only better if <vendor name> submits better quality patches (no evidence for that yet) or submits the patches more promptly than others (which clearly has not happened here), and offers review commentary etc at a higher standard and more frequently than a non-employee maintainer would be able to do (there’s no evidence for that so far either, given you’re trying to stall this patchset). Your claim seems to have no merit as there is no proof that you’d do a better job.
https://lore.kernel.org/all/20250925-jaundice-uneasy-ff8b3b595879@spud/
My talk at @KernelRecipes timestamped in the live feed for those that didn't catch it
Talking about where memory comes from... :)
https://www.youtube.com/watch?v=LcWIJhcDooM&t=19925s
Live blog for the last afterrnoon is available: https://kernel-recipes.org/en/2025/live-blog-day-3-afternoon/
#kr2025
Frank is back (and we are very happy of that). Beware!
@vbabka now: Observing the memory mills running
After last year talk about /proc/meminfo exploration, we will go deeper in what to do with memory usage information
https://kernel-recipes.org/en/2025/schedule/observing-the-memory-mills-running/
Starting soon 3rd day of #kr2025. Check the live stream
https://youtube.com/live/ko8Ap3PrYnQ
Live blog of this second afternoon https://kernel-recipes.org/en/2025/live-blog-day-2-afternoon/