On 10/30/2013 09:17 AM, jml@xxxxxxxxxx wrote: > Hello, > > I'd like to use my Tascam US-122 with my Raspberry Pi. In the stock > raspberry pi kernel snd-usb-usx2y is not included. So I took the > kernel source (3.6.11) from https://github.com/raspberrypi/linux and > compiled it. > > In sound/usb/Kconfig, section "config SND_USB_USX2Y", I had to remove > the line "depends on X86 || PPC || ALPHA". > > Now I can * load the module snd-usb-usx2y with nrpacks=1 * load the > firmware with fxload * run usx2yloader > > aplay -l now show the device: > > # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: USX2Y > [TASCAM US-X2Y], device 0: US-X2Y Audio [US-X2Y Audio #0] Subdevices: > 1/1 Subdevice #0: subdevice #0 card 0: USX2Y [TASCAM US-X2Y], device > 2: US-X2Y hwdep Audio [US-X2Y hwdep Audio] Subdevices: 1/1 Subdevice > #0: subdevice #0 > > If I try to play a wav file I get the output: > > # aplay -D hw:0,0 test.wav Playing WAVE 'test.wav' : Signed 16 bit > Little Endian, Rate 48000 Hz, Stereo aplay: pcm_write:1710: write > error: Input/output error Does the kernel log show anything after that? (dmesg) > I > can imagine the Line "depends on X86 || PPC || ALPHA" was there for a > reason... I actually don't think so, but I haven't looked at the sources yet. It's just a USB module, which should work on any platform. Daniel ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user