#eoss — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #eoss, aggregated by home.social.
-
I’m happy to announce the Amlogic ARM64 Device Tree is now fully documented in linux-next, ready for v6.12!
Since the beginning of Device Tree on Linux, we documented how it should be written so drivers could know what to expect, it’s called “bindings”, it’s a sort of “contract” between Device Tree and drivers.
But those were written in human readable open text format, without any automated way to verify Device Tree files. There were numerous attempts, but ultimately Rob Herring leveraged JSON Schema [1] into “dtschema” [2] leading to this patch serie https://lore.kernel.org/all/2018100516[email protected]/.
Thus “dtschema” made it possible to write bindings in YAML and the developed scripts would convert Device Tree in YAML and run a validation with JSON Schema validation. This was merged in end of 2018 then conversion of the text files in YAML files started.
For reference, there were 3278 text bindings in Linux 4.20 git tree, in today’s Linux next for v6.12 only 1250 text files remains but there’s 4345 yaml files now! In addition to the transition to yaml bindings, new platforms were introduced using the new format.
Around one year ago, I upstreamed support for the Snapdragon 8 Gen 3, and it was fully documented from day 1, and most of the changes was yaml bindings change since the SoC was mainly an upgrade from the Snapdragon 8 Gen 2 I helped upstream 2 years ago.
Let’s go back to Amlogic, were I started converting the text file to yaml bindings in August 2019 (see [3]), and finally ended the transition early this month with the patch [4]. This makes the Amlogic ARM64 Device Trees join fully documented along other platforms like Samsung Exynos
If you want to know more about Device Tree validation, you can look at my @LinaroLtd colleague @krzk talk he did in this year's #EOSS in Seattle https://sched.co/1aBEf!
Now the links:
[1] https://json-schema.org/
[2] https://github.com/devicetree-org/dt-schema
[3] https://lore.kernel.org/all/2019080113[email protected]/
[4] https://lore.kernel.org/all/20240905-topic-amlogic-upstream-gxlx-drop-iio-compat-v2-1-7a690eb95bc2@linaro.org/
Thanks for reading ! -
I’m happy to announce the Amlogic ARM64 Device Tree is now fully documented in linux-next, ready for v6.12!
Since the beginning of Device Tree on Linux, we documented how it should be written so drivers could know what to expect, it’s called “bindings”, it’s a sort of “contract” between Device Tree and drivers.
But those were written in human readable open text format, without any automated way to verify Device Tree files. There were numerous attempts, but ultimately Rob Herring leveraged JSON Schema [1] into “dtschema” [2] leading to this patch serie https://lore.kernel.org/all/2018100516[email protected]/.
Thus “dtschema” made it possible to write bindings in YAML and the developed scripts would convert Device Tree in YAML and run a validation with JSON Schema validation. This was merged in end of 2018 then conversion of the text files in YAML files started.
For reference, there were 3278 text bindings in Linux 4.20 git tree, in today’s Linux next for v6.12 only 1250 text files remains but there’s 4345 yaml files now! In addition to the transition to yaml bindings, new platforms were introduced using the new format.
Around one year ago, I upstreamed support for the Snapdragon 8 Gen 3, and it was fully documented from day 1, and most of the changes was yaml bindings change since the SoC was mainly an upgrade from the Snapdragon 8 Gen 2 I helped upstream 2 years ago.
Let’s go back to Amlogic, were I started converting the text file to yaml bindings in August 2019 (see [3]), and finally ended the transition early this month with the patch [4]. This makes the Amlogic ARM64 Device Trees join fully documented along other platforms like Samsung Exynos
If you want to know more about Device Tree validation, you can look at my @LinaroLtd colleague @krzk talk he did in this year's #EOSS in Seattle https://sched.co/1aBEf!
Now the links:
[1] https://json-schema.org/
[2] https://github.com/devicetree-org/dt-schema
[3] https://lore.kernel.org/all/2019080113[email protected]/
[4] https://lore.kernel.org/all/20240905-topic-amlogic-upstream-gxlx-drop-iio-compat-v2-1-7a690eb95bc2@linaro.org/
Thanks for reading ! -
I’m happy to announce the Amlogic ARM64 Device Tree is now fully documented in linux-next, ready for v6.12!
Since the beginning of Device Tree on Linux, we documented how it should be written so drivers could know what to expect, it’s called “bindings”, it’s a sort of “contract” between Device Tree and drivers.
But those were written in human readable open text format, without any automated way to verify Device Tree files. There were numerous attempts, but ultimately Rob Herring leveraged JSON Schema [1] into “dtschema” [2] leading to this patch serie https://lore.kernel.org/all/2018100516[email protected]/.
Thus “dtschema” made it possible to write bindings in YAML and the developed scripts would convert Device Tree in YAML and run a validation with JSON Schema validation. This was merged in end of 2018 then conversion of the text files in YAML files started.
For reference, there were 3278 text bindings in Linux 4.20 git tree, in today’s Linux next for v6.12 only 1250 text files remains but there’s 4345 yaml files now! In addition to the transition to yaml bindings, new platforms were introduced using the new format.
Around one year ago, I upstreamed support for the Snapdragon 8 Gen 3, and it was fully documented from day 1, and most of the changes was yaml bindings change since the SoC was mainly an upgrade from the Snapdragon 8 Gen 2 I helped upstream 2 years ago.
Let’s go back to Amlogic, were I started converting the text file to yaml bindings in August 2019 (see [3]), and finally ended the transition early this month with the patch [4]. This makes the Amlogic ARM64 Device Trees join fully documented along other platforms like Samsung Exynos
If you want to know more about Device Tree validation, you can look at my @LinaroLtd colleague @krzk talk he did in this year's #EOSS in Seattle https://sched.co/1aBEf!
Now the links:
[1] https://json-schema.org/
[2] https://github.com/devicetree-org/dt-schema
[3] https://lore.kernel.org/all/2019080113[email protected]/
[4] https://lore.kernel.org/all/20240905-topic-amlogic-upstream-gxlx-drop-iio-compat-v2-1-7a690eb95bc2@linaro.org/
Thanks for reading ! -
I’m happy to announce the Amlogic ARM64 Device Tree is now fully documented in linux-next, ready for v6.12!
Since the beginning of Device Tree on Linux, we documented how it should be written so drivers could know what to expect, it’s called “bindings”, it’s a sort of “contract” between Device Tree and drivers.
But those were written in human readable open text format, without any automated way to verify Device Tree files. There were numerous attempts, but ultimately Rob Herring leveraged JSON Schema [1] into “dtschema” [2] leading to this patch serie https://lore.kernel.org/all/2018100516[email protected]/.
Thus “dtschema” made it possible to write bindings in YAML and the developed scripts would convert Device Tree in YAML and run a validation with JSON Schema validation. This was merged in end of 2018 then conversion of the text files in YAML files started.
For reference, there were 3278 text bindings in Linux 4.20 git tree, in today’s Linux next for v6.12 only 1250 text files remains but there’s 4345 yaml files now! In addition to the transition to yaml bindings, new platforms were introduced using the new format.
Around one year ago, I upstreamed support for the Snapdragon 8 Gen 3, and it was fully documented from day 1, and most of the changes was yaml bindings change since the SoC was mainly an upgrade from the Snapdragon 8 Gen 2 I helped upstream 2 years ago.
Let’s go back to Amlogic, were I started converting the text file to yaml bindings in August 2019 (see [3]), and finally ended the transition early this month with the patch [4]. This makes the Amlogic ARM64 Device Trees join fully documented along other platforms like Samsung Exynos
If you want to know more about Device Tree validation, you can look at my @LinaroLtd colleague @krzk talk he did in this year's #EOSS in Seattle https://sched.co/1aBEf!
Now the links:
[1] https://json-schema.org/
[2] https://github.com/devicetree-org/dt-schema
[3] https://lore.kernel.org/all/2019080113[email protected]/
[4] https://lore.kernel.org/all/20240905-topic-amlogic-upstream-gxlx-drop-iio-compat-v2-1-7a690eb95bc2@linaro.org/
Thanks for reading ! -
I’m happy to announce the Amlogic ARM64 Device Tree is now fully documented in linux-next, ready for v6.12!
Since the beginning of Device Tree on Linux, we documented how it should be written so drivers could know what to expect, it’s called “bindings”, it’s a sort of “contract” between Device Tree and drivers.
But those were written in human readable open text format, without any automated way to verify Device Tree files. There were numerous attempts, but ultimately Rob Herring leveraged JSON Schema [1] into “dtschema” [2] leading to this patch serie https://lore.kernel.org/all/2018100516[email protected]/.
Thus “dtschema” made it possible to write bindings in YAML and the developed scripts would convert Device Tree in YAML and run a validation with JSON Schema validation. This was merged in end of 2018 then conversion of the text files in YAML files started.
For reference, there were 3278 text bindings in Linux 4.20 git tree, in today’s Linux next for v6.12 only 1250 text files remains but there’s 4345 yaml files now! In addition to the transition to yaml bindings, new platforms were introduced using the new format.
Around one year ago, I upstreamed support for the Snapdragon 8 Gen 3, and it was fully documented from day 1, and most of the changes was yaml bindings change since the SoC was mainly an upgrade from the Snapdragon 8 Gen 2 I helped upstream 2 years ago.
Let’s go back to Amlogic, were I started converting the text file to yaml bindings in August 2019 (see [3]), and finally ended the transition early this month with the patch [4]. This makes the Amlogic ARM64 Device Trees join fully documented along other platforms like Samsung Exynos
If you want to know more about Device Tree validation, you can look at my @LinaroLtd colleague @krzk talk he did in this year's #EOSS in Seattle https://sched.co/1aBEf!
Now the links:
[1] https://json-schema.org/
[2] https://github.com/devicetree-org/dt-schema
[3] https://lore.kernel.org/all/2019080113[email protected]/
[4] https://lore.kernel.org/all/20240905-topic-amlogic-upstream-gxlx-drop-iio-compat-v2-1-7a690eb95bc2@linaro.org/
Thanks for reading ! -
Back from #EOSS. Physically tired, mentally drained, it was awesome. Hopefully see you all again next year!
-
Back from #EOSS. Physically tired, mentally drained, it was awesome. Hopefully see you all again next year!
-
Back from #EOSS. Physically tired, mentally drained, it was awesome. Hopefully see you all again next year!
-
Back from #EOSS. Physically tired, mentally drained, it was awesome. Hopefully see you all again next year!
-
Day 2 at the #EOSS summit in Prague! Come and say hello and don’t miss Ashok’s presentation about the upcoming #wireplumber 0.5 changes at 15:05 in south hall 3B!
-
Punk ist nicht tot, Punk bereitet jetzt Slides für seinen #EOSS Talk vor.
-
Punk ist nicht tot, Punk bereitet jetzt Slides für seinen #EOSS Talk vor.
-
Happy to be back at #embeddedossummit #eoss, this year for the first time as a speaker!
Join my talk on Embedded Android on Friday, 9 am sched.co/1LcQE -
Happy to be back at #embeddedossummit #eoss, this year for the first time as a speaker!
Join my talk on Embedded Android on Friday, 9 am sched.co/1LcQE -
Happy to be back at #embeddedossummit #eoss, this year for the first time as a speaker!
Join my talk on Embedded Android on Friday, 9 am sched.co/1LcQE -
Happy to be back at #embeddedossummit #eoss, this year for the first time as a speaker!
Join my talk on Embedded Android on Friday, 9 am sched.co/1LcQE -
Happy to be back at #embeddedossummit #eoss, this year for the first time as a speaker!
Join my talk on Embedded Android on Friday, 9 am sched.co/1LcQE -
-
-
Team Mender.io preparing for #EOSS in Prague. Make sure to catch up with me or Fabio Tranchitella for the newest, latest and greatest, and your share of this.
https://sched.co/1LaQh - Fabio presenting on Secure Boot
https://sched.co/1LcNZ - Me on OTA updates for Zephyr
-
Team Mender.io preparing for #EOSS in Prague. Make sure to catch up with me or Fabio Tranchitella for the newest, latest and greatest, and your share of this.
https://sched.co/1LaQh - Fabio presenting on Secure Boot
https://sched.co/1LcNZ - Me on OTA updates for Zephyr
-
Team Mender.io preparing for #EOSS in Prague. Make sure to catch up with me or Fabio Tranchitella for the newest, latest and greatest, and your share of this.
https://sched.co/1LaQh - Fabio presenting on Secure Boot
https://sched.co/1LcNZ - Me on OTA updates for Zephyr
-
<Konferenz-Vorbereitungsgeräusche/>
Und dank #inkscape Nachhilfe von @fiurin klappt das mit dem Grafiken-malen auch alles schon viiiiiiiel besser...
#eoss-leaks #pengutronix
-
<Konferenz-Vorbereitungsgeräusche/>
Und dank #inkscape Nachhilfe von @fiurin klappt das mit dem Grafiken-malen auch alles schon viiiiiiiel besser...
#eoss-leaks #pengutronix
-
Preparing for @linuxfoundation #EOSS in Prague - right at the intersection of @yoctoproject, BeagleBoard and Mender. Stay tuned!
-
Preparing for @linuxfoundation #EOSS in Prague - right at the intersection of @yoctoproject, BeagleBoard and Mender. Stay tuned!
-
Preparing for @linuxfoundation #EOSS in Prague - right at the intersection of @yoctoproject, BeagleBoard and Mender. Stay tuned!
-
@linuxfoundation Lots and lots of excellent submissions for #EOSS made ranking really hard! Really looking forward to this conference. See you all in Prague!
-
@linuxfoundation Lots and lots of excellent submissions for #EOSS made ranking really hard! Really looking forward to this conference. See you all in Prague!
-
@linuxfoundation Lots and lots of excellent submissions for #EOSS made ranking really hard! Really looking forward to this conference. See you all in Prague!
-
@linuxfoundation Lots and lots of excellent submissions for #EOSS made ranking really hard! Really looking forward to this conference. See you all in Prague!
-
@linuxfoundation Lots and lots of excellent submissions for #EOSS made ranking really hard! Really looking forward to this conference. See you all in Prague!
-
Hear business perspectives on #opensouce from industry leaders! 🔊
November 10, together with our friends at @[email protected], @[email protected], @[email protected] will be present at the Enterprise Open Source Day. 💪 #EOSS #FOSS
See the schedule! Secure your seat! 🎫 http://hopin.com/events/enterprise-open-source-event
-
Hear business perspectives on #opensouce from industry leaders! 🔊
November 10, together with our friends at @[email protected], @[email protected], @[email protected] will be present at the Enterprise Open Source Day. 💪 #EOSS #FOSS
See the schedule! Secure your seat! 🎫 http://hopin.com/events/enterprise-open-source-event
-
The future is open! ✌️
Together with our friends at @[email protected], @[email protected], @[email protected] we will be highlighting business perspectives on the use of #opensource. 💪
November 10 🗓️ meet us at the Enterprise Open Source Day #EOSS 👉 http://collaboraoffice.com/company-news/a-business-perspective-on-open-source-the-enterprise-open-source-day/
-
The future is open! ✌️
Together with our friends at @[email protected], @[email protected], @[email protected] we will be highlighting business perspectives on the use of #opensource. 💪
November 10 🗓️ meet us at the Enterprise Open Source Day #EOSS 👉 http://collaboraoffice.com/company-news/a-business-perspective-on-open-source-the-enterprise-open-source-day/