Okay this is super cool to see ^^ https://www.youtube.com/watch?v=HRfbQJ6FdF0
Okay this is super cool to see ^^ https://www.youtube.com/watch?v=HRfbQJ6FdF0
I mamy kolejny komplet jąder #Gentoo #Linux Distribution Kernel (6.1.143, 6.6.96, 6.12.36, 6.15.5). A z nim kilka istotnych zmian:
• Przekopiowałem brakujące zmiany z sys-kernel/gentoo-kernel na sys-kernel/vanilla-kernel — przede wszystkim szersze wsparcie architektur.
• Dodałem domyślną konfigurację dla #RISCV w 6.12 (mieliśmy już ją w 6.15) — ta wersja również jest wspierana przez Fedorę.
• Wszystkie trzy paczki wykorzystują teraz archiwum z oryginalnym wydaniem jądra + połączoną łatkę aktualizacji (przedtem w vanilla-kernel używaliśmy osobnego archiwum dla każdego wydania, a w gentoo-kernel* używaliśmy łatek z genpatches). Dzięki temu będzie mniejsze zużycie przestrzeni dyskowej i łącza.
• Wszystkie trzy paczki wspierają verify-sig. NIe weryfikujemy już zdekompresowanego archiwum, lecz używamy pliku `sha256sums.asc`, który pozwala weryfikować skompresowane archiwum i łatkę.
• sys-kernel/gentoo-kernel* używa teraz własnego archiwum z genpatches. Dzięki temu jest dużo lżejsze i szybciej się nakłada (jak już wspomniałem, używamy teraz oryginalnej łatki z jądra zamiast pojedynczych łatek z genpatches). Możemy też teraz wydawać nasze jądra zanim gentoo-sources będą gotowe.
Nadal muszę nanieść zmiany na gałęzie 5.15 i 5.10 — zrobię to przy kolejnych wydaniach dla tych wersji.
New set of #Gentoo #Linux Distribution Kernels (6.1.143, 6.6.96, 6.12.36, 6.15.5) is out. This set brings some major changes:
• I've backported a bunch of changes from sys-kernel/gentoo-kernel to sys-kernel/vanilla-kernel that were missing — notably wider architecture support.
• I've added default #RISCV configs to 6.12 (in addition to 6.15), since Fedora had them.
• All three packages are based off the baseline kernel tarball + upstream patch (vanilla-kernel used to fetch patch-level tarball every time, and gentoo-kernel* used genpatches for patch versions). This should reduce disk space and bandwidth use.
• All three packages now support verify-sig. Rather than verifying the uncompressed tarball signature, we now use upstream `sha256sums.asc` file to verify the compressed tarball and patch.
• sys-kernel/gentoo-kernel* now repackages genpatches. This means patchset that's much leaner and faster to apply (since we just fetch and use the combined upstream patch rather than including point patches). This also means that we are able to release Distribution Kernels before gentoo-sources are done.
The changes still need to be done to 5.15 and 5.10 branches — we're going to do for the next upstream releases of these.
nanocray ? craycray ? crayola ?
Banana Pi BPI-F3 board schematics and TRM
https://forum.banana-pi.org/t/banana-pi-bpi-f3-board-schematics-and-trm/23766
#riscv #SBC #opensource #Linux #AIoT #AI
RISC-V is on the rise, challenging ARM and x86 with its open-source simplicity and modularity. Discover the future of computing architecture! #RISCV #Tech #OpenSource
https://dub.sh/7zJZaur
First step for non-x86_64 contributions
Ubuntu is raising its RISC-V profile requirements to RVA23, requiring vector and hypervisor extensions to be included. Most existing RISC-V SBCs on sale lack them.
https://www.omgubuntu.co.uk/2025/06/ubuntu-riscv-rva23-support
The jump to the RV23 stanrdard on Risc-V by #Ubuntu -- while no such board exists -- makes me think that #Canonical might be jumping into hardware. Basically, trying to pull a #RaspberryPi, but out of a Risc-V architecture.That would explain both their move to RV23, and their subsequent radio silence about it. In fact, for them, it even makes server-market sense. If that's true, it's definitely an exciting development for open hardware. Let's hope!
I suppose the #Nvidia #Jetson form factor is a kind of standard interface for #systemOnModule #SBC
There's already a #RiscV #SoM called the #MilkV Jupiter that's supposedly compatible with a #NvidiaJetson #carrierBoard, and now the #radxaN150 with an #x86 chip.
I'd be interested in seeing someone try various Jetson boards with the available modules.
@lajuste @fluffery @maumau @BryanGreyson @fairphone personally, I wished @GrapheneOS would support some #RISCv board becaise then they could do #FLOSS & #FLOSH thus.combining #transparency with #security.
Moving away from the constant upgrade cycle & moving closer to the ideals of #PermaComputing #MalleableSoftware
Design and setup a redundant system of old/used, cheap, low-power devices running ia: #Guix, #Linux, #FreeBSD, #macOS, #HaikuOS, #Plan9Front, #X11, #P9, #NFS, all working together
Become an expert on #MicroControllers #ESP32 #STM32 #RP2040 #MIPS #RiscV
DIY sensors which sing like birds to communicate their status
DIY robots "drones"
Move as much as possible of my computing needs to the #Terminal, #Emacs, #Rio #CLI #TUI #P9
Get an #3DPrinter and learn to use it
Design and build my own portable 8dot #braille terminal & try out if 3x3 or 3x4 dots is also workable.
Design and build my own low-power computers, their OS, and tools
Writing more of my own tools #DIY
#SmallTalk #ObjectPascal #Prolog #Scheme #Racket #CommonLisp #Haskell #Rust #Go #ObjectiveC #Swift
Deploy #LoRa #ReticullumNetwork #RNodes #MeshCore #Meshtastic
Start an #InternetResiliencyClub
Add #Tor, #I2P support by #WebProxy
#SolarPowered #SelfHost over #I2P, #OnionService #Blog #Wiki #Repositories #GopherHole #Darcs #Mercurial
#SelfHost my own #EmailServer, which will only accept email from #KnownServers #CommunityEmail #MutualEmailAcceptance
Share files via #BitTorrent over #I2P
DIY #HomeAutomation
DIY #GardeningAutomation
DIY #GreenHouse
Get a house cat, train the cat, use voice and gestures
Start asking money for advice & technology support
Build/program my own opportunistic and strange cryptocurrency miners #BTC, #XMR, #ZEC, etc #Art
#MakeMoreArt #LearnToDraw #Learn3DModeling #LearnGenerativeArt #LearnToComposeAmbientMusic
#ReCreateJottit #ReCreateInstikiWiki
#WriteMore #PublishMore #Letters, #Essays, #Missives, #Reports, #Treatise
…
In my little world of #RetroComputing, I have stumbled across minor issues in some of the tools that I use.
I've had two cases so far where maintainers very quickly took my suggestion and made it available in their main branch. I've also had one where I haven't heard back from the maintainer, i.e. where I'm going to need to maintain my own fork (for #RiscV compatibility). And that's OK. Beyond being glad that I got help, I'm glad that the original authors allow me also to do the work myself.
Just released version 0.1 of TinyGo-TKey to develop apps for the Tillitis TKey-1 using TinyGo!
https://github.com/hybridgroup/tinygo-tkey
TKey-1 is an open source, open hardware FPGA-based USB security token from the awesome team at Tillitis:
https://tillitis.se/
Linux 6.16-rc1, verso un kernel più moderno e robusto
https://gomoot.com/linux-6-16-rc1-verso-un-kernel-piu-moderno-e-robusto
I tried to boot debian 13 rc1 image #riscv on #visionfive2. Fiddling around (load fdt and kernel) in u-boot gives you the installer. Then installed it on nvme. But as expected no hdmi. Same with alpine-linux. I didn't manage to build a custom kernel yet and using HDMI output.
Hints are very welcome.