OK, some progress has been made: The DAC DOES support DoP, as I can play one of my sample DSD64 dsf files from my android phone, using HibyMusic. I can toggle on the fly, between DoP, Native and PCM modes, barely hearing the very slightest interruption to the stream as the signal switches.
On the touch, I did briefly try a COAX connection, to see if that helped, but heard nothing at all, so switched back to USB. After switching back, I have accepted the default EDO Digital only kernel which uname lists as: 2.6.26.8-rt16-332-g5849bfa I have not tried other kernels for now, as last time I got mostly only noise resembling bird chatter, when I was playing around with the kernels. With this kernel, the file settings: -DFF DFF native DFF FLAC dsdplay DSF DSF native DSF FLAC dsdplay FLAC FLAC native FLAC PCM - flac- [The "DSD Audio file FLAC - dsdplay" line doesn't exist.] and DoP checked on the touch player settings: I DO hear a very faint playback of the DSD64 track, under quite a lot of white noise type hiss. The music is playing at the correct pitch and speed. I tried doing a lsusb on the touch, to see what it said about teh DAC, but it seems lsusb is not included. dmesg gives me: ... ... firmware: requesting ir_controller_21323.hex mxsdhci: MXC Secure Digital Host Controller Interface driver mxsdhci: MXC SDHCI Controller Driver. mmc0: SDHCI detect irq 0 irq 7 INTERNAL DMA mxsdhci: MXC SDHCI Controller Driver. mmc1: SDHCI detect irq 102 irq 8 INTERNAL DMA input: SMSL AUDIO Sanskrit PRO as /class/input/input2 mmc0: new SDIO card at address 0001 input: USB HID v1.00 Device [SMSL AUDIO Sanskrit PRO] on usb-fsl-ehci.0-1 usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.16. MXC spdif support initialized 3:1:4 : unsupported sample bitwidth 64 in 8 bytes usbcore: registered new interface driver snd-usb-audio AK4420 Audio Codec 0.1<6>DMA Sound Buffers Allocated:UseIram=0 buf->addr=87ed0000 buf->area=fe004000 size=65536 asoc: ak4420-dai <-> imx-ssi-1 mapping ok WM8974 Audio Codec 0.1 DMA Sound Buffers Allocated:UseIram=0 buf->addr=87ef0000 buf->area=fe014000 size=65536 DMA Sound Buffers Allocated:UseIram=0 buf->addr=87f00000 buf->area=fe024000 size=65536 asoc: wm8974-hifi-dai <-> imx-ssi-3 mapping ok fab4 WM8974 Audio Driver ALSA device list: #0: MXC Freescale with SPDIF #1: SMSL AUDIO Sanskrit PRO at usb-fsl-ehci.0-1, high speed #2: fab4 (ak4420) #3: fab4 (wm8974) oprofile: using arm/armv6 TCP cubic registered NET: Registered protocol family 17 RPC: Registered udp transport module. RPC: Registered tcp transport module. ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation <[email protected]> ieee80211_crypt: registered algorithm 'NULL' mxc_rtc mxc_rtc.0: rtc core: registered mxc_rtc as rtc0 No external RTC clock Real TIme clock Driver v1.0 mxc_rtc: probe of mxc_rtc.0 failed with error -2 Static Power Management for Freescale i.MX35 VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 3 MXC Backlight Device mxc_ipu_bl.0 Initialized. platform mxc_rtc.0: setting system clock to 1970-01-05 20:19:21 UTC (418761) VFS: Mounted root (cramfs filesystem) readonly. Freeing init memory: 152K UBIFS: recovery needed UBIFS: recovery completed UBIFS: mounted UBI device 0, volume 2, name "ubifs" UBIFS: file system size: 19869696 bytes (19404 KiB, 18 MiB, 154 LEBs) UBIFS: journal size: 1032193 bytes (1008 KiB, 0 MiB, 8 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: lzo UBIFS: reserved for root: 938494 bytes (916 KiB) FAB4 IR: fw checksum ok aa3 ... ... I don't understand why the DAC is being picked up as a HID device?? On the touch, I can see some info about the DAC, which is listed correctly as a Sanskrit PRO: Status: Running Speed: High Connection: Direct Type: Async Frequency: depends on the last source being played, but my DSD64 file gives me something like 1760** (can't remember the last two digits and didn't take a picture - it looked about right). Format: S32_LE Rates: 44100, 48000, 88200, 96000, 176400, .. .. Feedback Format: High (16.16) Interval: 125 us I notice that it is the ak4490 chip that is being recognised (as an ak4420-dai) and not the CM6632A. Dioes anyone have any clues about what I could try next? I have managed to get hold of the 2.6.26 kernel source for the fab4, including Triode's patches. As most of Triode's test kernels are still missing (only his default USB kernel and test kernels #11 and #12 are available at the moment) , it may well be that one of the other test kernels would have resolved the issue. Does anyone have any idea where in te kernel source I might try looking for tweaks and patches to apply? ------------------------------------------------------------------------ Learnincurve's Profile: http://forums.slimdevices.com/member.php?userid=64807 View this thread: http://forums.slimdevices.com/showthread.php?t=94512
_______________________________________________ Touch mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/touch
