“Allo Katana” on the way->.dts accepted for rpi-mainline-kernel; Diyaudio.com forum

so, 😉
the long promised “Allo Katana“, a “monster triple-dac” hat->controller+psu/dac/output and with 6 Op-Amps from Allo is appearantly in the last stage..
(picture is from here-> http://www.forum-hifi.fr/thread-7848.html and relatively “fresh” and/but i don´t know if this is exactly the promised Katana-DAC/HAT, but looks so..(95%))

by that if u really want some fresh/new audio-(dac-hat) info 😉 go to the phenomenal board diyaudio.com/forums..
absolutely superb there; there are sooo much super interesting threads->for example this http://www.diyaudio.com/forums/vendor-s-bazaar/310338-dac-allo-ess9028q2m-rpi-35.html or http://www.diyaudio.com/forums/digital-line-level/317577-allo-boss-dac-1-2-performance-4.html and so on and on..(some Link is also in the sidebar on the right->links)
this site is absolutely “low-mo” 😉 in regarding/comparison to the super interesting infos there..

by that, as said, the “allo-katana”-.dts was accepted by the rpi-mainline-kernel maintainer->(link maybe later) and i first thought:”yeah, then we finally have our es9038q2m.kos for the chip”, but they said, this .dts adresses the special mcu by Allo which adresses then the ess9038q2m-chip..

anyway, here is (imho) a super interesting excerpt of the code for the .dts file: (sound/soc/codecs/sabre-ess.c and sound/soc/codecs/sabre-ess.h) from here:->https://github.com/raspberrypi/linux/pull/2519/commits/e67122b366f539713cf6ef91c63ab00cb269113d
it shows the different register of the es9038q2m (or in this case the allo-mcu but the basics are the same i think) + the adressing->

some user over there is also a few steps before reading out the mcus on our chinese-9038q2m-boards (i tried something similar a few months ago in trying to read out the mcu on a ES9028Q2M via the onboard SWIM-interface and with a ST-Link V2 but with no success)..
so, as said, very interesting, but go and visit these phenomenal diyaudio.com forums !! 😉

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.