Fosstodon

Detlev ZundelDas einzig gute an der Zeit, die ich da investiert habe, ist die zusätzliche Unterstützung von <a href="https://hostsharing.coop/tags/DeviceTree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeviceTree</a> File Syntax Coloring aus orgmode Posts, was jetzt auch funktioniert!Ok, bei 8 Zeilen dts File ist das jetzt noch nicht sooo wichtig, aber cool ist es schon 😂 <a href="https://hostsharing.coop/tags/orgmode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#orgmode</a> rules!

Stefan Römer<a href="https://mastodon.giftedmc.com/@haui" class="u-url mention">@haui</a> I couldn't resist to have a quick look into the device tree file(s) in the kernel sources of Bianbu Linux:see here: <a href="https://gitee.com/bianbu-linux/linux-6.6/blob/bl-v2.0.y/arch/riscv/boot/dts/spacemit/k1-x.dtsi" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://gitee.com/bianbu-linux/linux-6.6/blob/bl-v2.0.y/arch/riscv/boot/dts/spacemit/k1-x.dtsi</a>On a quick look (didn't check entry by entry) the 'riscv,isa-extensions' entries per cpu seems to match your table. Anyway as I said before, I think this does not need to reflect the real capabilities of the SOC too.<a href="https://fosstodon.org/tags/riscv" class="mention hashtag" rel="tag">#riscv</a> <a href="https://fosstodon.org/tags/spacemit" class="mention hashtag" rel="tag">#spacemit</a> <a href="https://fosstodon.org/tags/spacemitk1" class="mention hashtag" rel="tag">#spacemitk1</a> <a href="https://fosstodon.org/tags/spacemitx60" class="mention hashtag" rel="tag">#spacemitx60</a> <a href="https://fosstodon.org/tags/devicetree" class="mention hashtag" rel="tag">#devicetree</a> <a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="tag">#linux</a> <a href="https://fosstodon.org/tags/bananapif3" class="mention hashtag" rel="tag">#bananapif3</a> <a href="https://fosstodon.org/tags/bpif3" class="mention hashtag" rel="tag">#bpif3</a>

Stefan Römer<a href="https://mastodon.giftedmc.com/@haui" class="u-url mention">@haui</a> Regarding this I found an article from RedHat:see <a href="https://research.redhat.com/blog/article/risc-v-extensions-whats-available-and-how-to-find-it/" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://research.redhat.com/blog/article/risc-v-extensions-whats-available-and-how-to-find-it/</a>According to the article the DeviceTree can be used to get that information, but since that's just a configuration describing the hardware it could be incomplete too.<a href="https://fosstodon.org/tags/riscv" class="mention hashtag" rel="tag">#riscv</a> <a href="https://fosstodon.org/tags/spacemit" class="mention hashtag" rel="tag">#spacemit</a> <a href="https://fosstodon.org/tags/spacemitk1" class="mention hashtag" rel="tag">#spacemitk1</a> <a href="https://fosstodon.org/tags/bananapif3" class="mention hashtag" rel="tag">#bananapif3</a> <a href="https://fosstodon.org/tags/bpif3" class="mention hashtag" rel="tag">#bpif3</a> <a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="tag">#linux</a> <a href="https://fosstodon.org/tags/devicetree" class="mention hashtag" rel="tag">#devicetree</a>

Anisse"Operating system provided device-trees" by Heinrich SchuchardtWhile it was not the initial goal, in practice, when booting Linux, device trees need to be coupled with a given kernel version.This brings its own sets of challenge, because the bootloader needs to patch the device tree to provide information to the OS.When using EFI, there is now the EFI_DT_FIXUP_PROTOCOL.Outside of EFI, the flash-kernel tool helps picking the correct device tree depending on the board model.The way forward would be to use Unified Kernel Images, which would contain all device trees for supported platform, with the efistub used to select the correct one.<a href="https://social.treehouse.systems/tags/OSFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSFC</a> <a href="https://social.treehouse.systems/tags/OSFC2024" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSFC2024</a> <a href="https://social.treehouse.systems/tags/DeviceTree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeviceTree</a>

Marcin JuszkiewiczWrote some words about my experiences with FriendlyELEC NanoPC-T6 SBC.<a href="https://marcin.juszkiewicz.com.pl/2024/08/09/i-had-some-fun-with-friendlyelec-nanopc-t6/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://marcin.juszkiewicz.com.pl/2024/08/09/i-had-some-fun-with-friendlyelec-nanopc-t6/</a><a href="https://society.oftrolls.com/tags/UEFI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UEFI</a> <a href="https://society.oftrolls.com/tags/ACPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ACPI</a> <a href="https://society.oftrolls.com/tags/DeviceTree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeviceTree</a> <a href="https://society.oftrolls.com/tags/FriendlyELEC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FriendlyELEC</a> <a href="https://society.oftrolls.com/tags/NanoPCT6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NanoPCT6</a>

Marcin JuszkiewiczI thought that booting Seriously Bad Computers in ACPI mode is crippled compared to booting in DeviceTree mode.NanoPC-T6 is otherwise. Same 6.11-rc2 kernel gives working system in ACPI mode and fail-to-boot one in DT.DT = no USB, no PCIe while rootfs is on NVME cause it worked fine in ACPI mode.And DT is from 6.11-rc2 kernel.<a href="https://society.oftrolls.com/tags/SystemNotReady" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SystemNotReady</a> <a href="https://society.oftrolls.com/tags/ACPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ACPI</a> <a href="https://society.oftrolls.com/tags/DeviceTree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeviceTree</a> <a href="https://society.oftrolls.com/tags/SBC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SBC</a> <a href="https://society.oftrolls.com/tags/RK3588" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RK3588</a> <a href="https://society.oftrolls.com/tags/FriendlyELEC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FriendlyELEC</a> <a href="https://society.oftrolls.com/tags/NanoPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NanoPC</a>-T6

mortHey fellow <a href="https://fosstodon.org/tags/embeddedlinux" class="mention hashtag" rel="tag">#embeddedlinux</a> people! Have you ever wanted to generate a canonical representation of your devicetrees? Or diff two devicetrees? How about adding back labels to a decompiled devicetree? I've polished up and released a little tool I made for these things called DTCanon: <a href="https://github.com/mortie/dtcanon" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://github.com/mortie/dtcanon</a>This has been useful for me in some situations. Maybe it'll be useful for you too. It's <a href="https://fosstodon.org/tags/FOSS" class="mention hashtag" rel="tag">#FOSS</a> of course.<a href="https://fosstodon.org/tags/yocto" class="mention hashtag" rel="tag">#yocto</a> <a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="tag">#linux</a> <a href="https://fosstodon.org/tags/devicetree" class="mention hashtag" rel="tag">#devicetree</a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="tag">#opensource</a> <a href="https://fosstodon.org/tags/programming" class="mention hashtag" rel="tag">#programming</a>

GeekProjects NewsAt Last, Chumby is Ready <a href="https://hackaday.com/2024/08/05/at-last-chumby-is-ready/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hackaday.com/2024/08/05/at-last-chumby-is-ready/</a> <a href="https://geekprojects.com/tags/Retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Retrocomputing</a> <a href="https://geekprojects.com/tags/LinuxHacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxHacks</a> <a href="https://geekprojects.com/tags/devicetree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devicetree</a> <a href="https://geekprojects.com/tags/chumby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chumby</a> <a href="https://geekprojects.com/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

Pyrzout :vm:At Last, Chumby is Ready <a href="https://hackaday.com/2024/08/05/at-last-chumby-is-ready/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hackaday.com/2024/08/05/at-last-chumby-is-ready/</a> <a href="https://social.skynetcloud.site/tags/Retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Retrocomputing</a> <a href="https://social.skynetcloud.site/tags/LinuxHacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxHacks</a> <a href="https://social.skynetcloud.site/tags/devicetree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devicetree</a> <a href="https://social.skynetcloud.site/tags/chumby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chumby</a> <a href="https://social.skynetcloud.site/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

IT NewsAt Last, Chumby is Ready - It has been two years, but the slow and steady progress that [Doug Brown] has been... - <a href="https://hackaday.com/2024/08/05/at-last-chumby-is-ready/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hackaday.com/2024/08/05/at-last-chumby-is-ready/</a> <a href="https://schleuss.online/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> <a href="https://schleuss.online/tags/linuxhacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linuxhacks</a> <a href="https://schleuss.online/tags/devicetree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devicetree</a> <a href="https://schleuss.online/tags/chumby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chumby</a> <a href="https://schleuss.online/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

MusnedHow do I make <a href="https://mastodon.online/tags/deviceTree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#deviceTree</a> for an <a href="https://mastodon.online/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> device to custom ROM it.<a href="https://mastodon.online/tags/customROM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#customROM</a>

HabrДрайвер Ethernet для xv6Xv6 - учебная ОС - рассказывает об идеях, что лежат в основе операционных систем. Научим xv6 работать в сети, познакомимся со стандартом виртуальных устройств VirtIO, деревом устройств DeviceTree, технологией Ethernet, сетевыми протоколами, возведем сетевой мост между виртуальными машинами.<a href="https://habr.com/ru/articles/826500/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://habr.com/ru/articles/826500/</a><a href="https://zhub.link/tags/xv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xv6</a> <a href="https://zhub.link/tags/ethernet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ethernet</a> <a href="https://zhub.link/tags/virtio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#virtio</a> <a href="https://zhub.link/tags/devicetree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devicetree</a> <a href="https://zhub.link/tags/qemu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qemu</a> <a href="https://zhub.link/tags/dhcp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dhcp</a> <a href="https://zhub.link/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv4</a> <a href="https://zhub.link/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://zhub.link/tags/arp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#arp</a> <a href="https://zhub.link/tags/icmp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#icmp</a>

mortThings I would change in the <a href="https://fosstodon.org/tags/devicetree" class="mention hashtag" rel="tag">#devicetree</a> syntax if I was god emperor of the world (or at least the embedded Linux part of it):* Make semicolons after closing curly braces optional (ideally they'd be prohibited but that'd be a breaking change and I'd be a benevolent god emperor) * Make status = "enabled" a synonym to "ok" or "okay", to match status = "disabled"These two small changes would remove 99% of the mistakes I make when doing devicetree stuff<a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="tag">#linux</a> <a href="https://fosstodon.org/tags/embedded" class="mention hashtag" rel="tag">#embedded</a> <a href="https://fosstodon.org/tags/embeddedlinux" class="mention hashtag" rel="tag">#embeddedlinux</a> <a href="https://fosstodon.org/tags/yocto" class="mention hashtag" rel="tag">#yocto</a>

onion<a href="https://geekdom.social/@DesRoin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@DesRoin</a> there are devices / sensors, for example the <a href="https://mastodon.tal.org/tags/sps30" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sps30</a> PM sensors, that supports both <a href="https://mastodon.tal.org/tags/i2c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#i2c</a> and <a href="https://mastodon.tal.org/tags/uart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#uart</a> connections. There are two drivers, one for i2c and one for uart. i2c can be attached in various ways. But I have no idea how you are supposed to tell linux that behind this USB UART dongle, say /dev/ttyUSB0, is a sps30 that you should talk too with this driver. There is a very simple <a href="https://mastodon.tal.org/tags/devicetree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devicetree</a> example that does not help at all.

onionHow are you supposed to "attach" <a href="https://mastodon.tal.org/tags/uart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#uart</a> based sensor driver to a serial port in <a href="https://mastodon.tal.org/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> when NOT using a <a href="https://mastodon.tal.org/tags/devicetree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devicetree</a> ? <a href="https://mastodon.tal.org/tags/iio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iio</a>

m0veax<a href="https://mastodon.social/@CyReVolt" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@CyReVolt</a> gave a talk about "dtvis", a tool to visualize device trees.<a href="https://www.youtube.com/watch?v=Vlz_Jx7eeUc" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=Vlz_Jx7eeUc</a><a href="https://det.social/tags/devicetree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devicetree</a> <a href="https://det.social/tags/c3e" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#c3e</a>

Cloud ManulSo there is this thing that has bothered me since the dawn of time (ok, not that long, but at least since XML schemas): Why would you create a friendly, sensible URI for your schema like "<a href="http://devicetree.org/schemas/gpio/gpio-consumer.yaml#" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://devicetree.org/schemas/gpio/gpio-consumer.yaml#</a>", that is practically begging to be clicked, only to have your web server return 404? (same result for https) I am perfectly aware that schema IDs and web links are not the same, but would it kill somebody if they worked like that, just for once? <a href="https://nrw.social/tags/devicetree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devicetree</a>

CLion BlogCLion 2024.1 Is Available! CMake Writing Assistance, Debugger Enhancements, and Improvements for Embedded Development <a href="https://techhub.social/tags/Clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Clang</a> <a href="https://techhub.social/tags/CLion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CLion</a> <a href="https://techhub.social/tags/News" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#News</a> <a href="https://techhub.social/tags/Releases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Releases</a> #20241 <a href="https://techhub.social/tags/Bazel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bazel</a> <a href="https://techhub.social/tags/Cmake" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cmake</a> <a href="https://techhub.social/tags/Debug" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debug</a> <a href="https://techhub.social/tags/Devicetree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Devicetree</a> <a href="https://techhub.social/tags/Embedded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Embedded</a> <a href="https://techhub.social/tags/Meson" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Meson</a><a href="https://blog.jetbrains.com/clion/2024/04/clion-2024-1-available/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.jetbrains.com/clion/2024/04/clion-2024-1-available/</a>

Multi Purr Puss :verified:<a href="https://mastodon.social/@popey" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@popey</a> 🤣 i've noticed!Friggen Copilot sent me down a rabbit hole, suggesting writing&compiling device tree code, in order to define the PPS(Pulse Per Second) pin of my GNSS/GPS NTP server, using a BananaPi SBC - it turned out to be a one-liner, instead …i've wasted a whole day, watching a tech talk and reading <a href="https://layer8.space/tags/DeviceTree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeviceTree</a> specs …then, a rando from YouTube pointed me in the right direction …at one point copilot even served me my own forum post as a solution! 🤣 😅 (i've figure it out, eventually)

mortDoes anyone here know how to do I2S audio output in <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="tag">#Linux</a> ..? I've enabled an I2S device in <a href="https://fosstodon.org/tags/devicetree" class="mention hashtag" rel="tag">#devicetree</a> and and it shows up as /sys/devices/platform/fe480000.i2s, and shows up as using the rockchip-i2s-tdm driver. However, it doesn't show up as an alsa sound card...<a href="https://fosstodon.org/tags/embeddedlinux" class="mention hashtag" rel="tag">#embeddedlinux</a> <a href="https://fosstodon.org/tags/alsa" class="mention hashtag" rel="tag">#alsa</a> <a href="https://fosstodon.org/tags/rockchip" class="mention hashtag" rel="tag">#rockchip</a>

Recent searches

Search options

Administered by:

Server stats:

#devicetree