(10-14-2019, 08:17 AM)starbender Wrote: Hi Kent,
It does run 64bit, but you have to modify config.txt for it.
Ah, I missed that (...minor grumbling 'bout not being able to find documentation while editing config.txt...). Yup, both the kernel and root file system appear to be 64bit.
Quote:I know two distro is different to the bone. One of them is using buster and mpd, other is using tinycore and sqlite and lms.
But I always thought drivers/overlay files is same but compiled in a different way..
I was making the same assumption. It appears the digi and digi-pro overlays are the same in both distros. They are nearly the same lengths and when i reverse-compiled them they read the same, so I attributed the different lengths to the build environments. The wm8804 driver file itself is also similar length but my interest flagged at digging through sources. I didn't see any recent (e.g., post-RPi4B release date) commits. I gave up at that point. There's a lot of futzing with filenames and directory structures between the two distros and scrolling through git commit comments can be a bore.
I just tried searching the HiFiBerry forum for posts about RPi4B and Digi but didn't get any hits. I still think that's the place to ask to get answers right from the horse's mouth so to speak.
Just out of curiosity, have you tried your Digi and RPi4 with Volumio?
Quote:There is zillions of different digi hats, all of them using wm8804 and i2c with very simple implementations. All was working with pi3 and strech based distros.
Regards,
Sb.
Occasionally I've bought a piece of kit just to figure out why it isn't working with moOde (like I did the Khadas Tone Board) 'cuz I know I can invent a use for it after, but I haven't had any S/PDIF gear in decades so picking up a WM8804 board isn't in the cards. Sorry.
Good luck.
Regards,
Kent
PS: If you're game for what my dad used to call the brute force and ignorance approach, you could just copy over the subject 32bit piCorePlayer drivers with appropriate name changes to the appropriate places in moOde and see what happens. (It's unlikely this qualifies as a smoke test but I make no guarantees!)