patch, and other via82xx (VT8235) capture problems
I've attached a patch to fix a bug in the via82xx driver, but I suspect the register is wrong for the VT8235 because when I set the Input Source to 'Mic', no interrupts seem to be getting triggered:
arecord: pcm_read:1110: read error: Input/output error
But as 'Line', it works (albeit with significantly reduced voltage and volume)
Are the specs for the VT8235 available anywhere?
Useful info:
Kernel: Linux 2.6.0-test7 (patched bug exists in CVS tree, too) On-board sound card: 00:11.5 Class 0401: 1106:3059 (rev 50)
Motherboard: A7V333-X
Signature · 1 line
Zinx Verituse
sound/pci/via82xx.c renamed from sound/pci/via82xx.c.orig +2 -2
@@ -1382,7 +1382,7 @@static int snd_via8233_capture_source_get (snd_kcontrol_t *kcontrol,snd_ctl_elem_value_t *ucontrol) {via82xx_t *chip =snd_kcontrol_chip (kcontrol); -unsigned long port = chip->port + kcontrol->id.index ? (VIA_REG_CAPTURE_CHANNEL +0x10 ) :VIA_REG_CAPTURE_CHANNEL ; +unsigned long port = chip->port + (kcontrol->id.index ? (VIA_REG_CAPTURE_CHANNEL +0x10 ) :VIA_REG_CAPTURE_CHANNEL ); ucontrol->value.enumerated.item[0 ] =inb (port) &VIA_REG_CAPTURE_CHANNEL_MIC ?1 :0 ;return 0 ; }
@@ -1390,7 +1390,7 @@static int snd_via8233_capture_source_put (snd_kcontrol_t *kcontrol,snd_ctl_elem_value_t *ucontrol) {via82xx_t *chip =snd_kcontrol_chip (kcontrol); -unsigned long port = chip->port + kcontrol->id.index ? (VIA_REG_CAPTURE_CHANNEL +0x10 ) :VIA_REG_CAPTURE_CHANNEL ; +unsigned long port = chip->port + (kcontrol->id.index ? (VIA_REG_CAPTURE_CHANNEL +0x10 ) :VIA_REG_CAPTURE_CHANNEL );unsigned long flags;u8 val, oval;
At Wed, 22 Oct 2003 23:48:43 -0500,
Quoted 10 lines · Zinx Verituse
[1 <text/plain; us-ascii (7bit)>]
I've attached a patch to fix a bug in the via82xx driver, but I suspect the register is wrong for the VT8235 because when I set the Input Source to 'Mic', no interrupts seem to be getting triggered:arecord: pcm_read:1110: read error: Input/output error
But as 'Line', it works (albeit with significantly reduced voltage and volume)
thanks for the patch. now applied to cvs.
Quoted 1 line
Are the specs for the VT8235 available anywhere?
not in public i know of...
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/
Quoted 7 lines · Takashi Iwai
thanks for the patch. now applied to cvs.
Quoted 1 line
Are the specs for the VT8235 available anywhere?
not in public i know of...
Ah, too bad.
Quoted 1 line
Takashi
Any ideas on the problem with me not being able to record if the Input Source is set to Mic?
arecord records when it's set to Line (as it was forced, before), and does playback as well..
When it's set to Mic, I get no playback from a Mic (and I'm not wanting to hook up powered output in to the jack when it's set to Mic), but I suspect it's still Line-in, and the register being twiddled isn't right, or needs some more setup.
arecord waits a bit, then gives the error I mentioned:
arecord: pcm_read:1110: read error: Input/output error
dmesg says nothing :/
If nothing else, the settings do have to do with the actual capture sources (idx 0 vs. idx 1), because when I set idx 0 to mic, it can't record, but idx 1 can, and when I set idx 1 to mic, it can't record, but idx 0 can. When both are set to mic, neither can record.
Any recommendations for stuff to try would be apreciated, as I really would like to be able to record without getting another sound card :/
Signature · 8 lines
Zinx Verituse ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/
At Thu, 23 Oct 2003 20:05:02 -0500,
Quoted 28 lines · Zinx Verituse
Quoted 7 lines · Takashi Iwai
thanks for the patch. now applied to cvs.
Quoted 1 line
Are the specs for the VT8235 available anywhere?
not in public i know of...
Ah, too bad.
Quoted 1 line
Takashi
Any ideas on the problem with me not being able to record if the Input Source is set to Mic?
arecord records when it's set to Line (as it was forced, before), and does playback as well..
When it's set to Mic, I get no playback from a Mic (and I'm not wanting to hook up powered output in to the jack when it's set to Mic), but I suspect it's still Line-in, and the register being twiddled isn't right, or needs some more setup.
arecord waits a bit, then gives the error I mentioned:
arecord: pcm_read:1110: read error: Input/output error
Quoted 7 lines
dmesg says nothing :/
If nothing else, the settings do have to do with the actual capture sources (idx 0 vs. idx 1), because when I set idx 0 to mic, it can't record, but idx 1 can, and when I set idx 1 to mic, it can't record, but idx 0 can. When both are set to mic, neither can record.
sorry, could you elaborate this? i'm confused.
did you try hw:0,0 and hw:0,1, right?
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/
Quoted 19 lines · Takashi Iwai
At Thu, 23 Oct 2003 20:05:02 -0500,
Quoted 17 lines · Zinx Verituse
Any ideas on the problem with me not being able to record if the Input Source is set to Mic?
arecord records when it's set to Line (as it was forced, before), and does playback as well..
When it's set to Mic, I get no playback from a Mic (and I'm not wanting to hook up powered output in to the jack when it's set to Mic), but I suspect it's still Line-in, and the register being twiddled isn't right, or needs some more setup.
arecord waits a bit, then gives the error I mentioned:
arecord: pcm_read:1110: read error: Input/output errordmesg says nothing :/
Quoted 9 lines
Quoted 5 lines
If nothing else, the settings do have to do with the actual capture sources (idx 0 vs. idx 1), because when I set idx 0 to mic, it can't record, but idx 1 can, and when I set idx 1 to mic, it can't record, but idx 0 can. When both are set to mic, neither can record.
sorry, could you elaborate this? i'm confused.
did you try hw:0,0 and hw:0,1, right?
Yeah, hw:0,0 fails when Input Source idx 0 is set to Mic, and hw:0,1 fails when Input Source idx 1 is set to Mic.
Quoted 3 lines
Takashi
Signature · 8 lines
Zinx Verituse ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/
Quoted 26 lines · Zinx Verituse
Quoted 25 lines · Takashi Iwai
At Thu, 23 Oct 2003 20:05:02 -0500,
Quoted 22 lines · Zinx Verituse
Any ideas on the problem with me not being able to record if the Input Source is set to Mic?
arecord records when it's set to Line (as it was forced, before), and does playback as well..
When it's set to Mic, I get no playback from a Mic (and I'm not wanting to hook up powered output in to the jack when it's set to Mic), but I suspect it's still Line-in, and the register being twiddled isn't right, or needs some more setup.
arecord waits a bit, then gives the error I mentioned:
arecord: pcm_read:1110: read error: Input/output errordmesg says nothing :/
If nothing else, the settings do have to do with the actual capture sources (idx 0 vs. idx 1), because when I set idx 0 to mic, it can't record, but idx 1 can, and when I set idx 1 to mic, it can't record, but idx 0 can. When both are set to mic, neither can record.
Quoted 11 lines
Quoted 3 lines
sorry, could you elaborate this? i'm confused.
did you try hw:0,0 and hw:0,1, right?Yeah, hw:0,0 fails when Input Source idx 0 is set to Mic, and hw:0,1 fails when Input Source idx 1 is set to Mic.
Quoted 3 lines
Takashi
I have more to report on this issue:
When I was recording with 'Line' selected as the 'Input Source', 'Mic' was the selected recording device, and 'Line' was completely silent. Also, I have noticed that if I'm playing something on hw:0,0, then hw:0,1 fails like recording does. However, if I try to play two things to hw:0,0, it works. And if I try to play something to hw:0,1 while hw:0,0 is closed, it also works.
Signature · 8 lines
Zinx Verituse ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/
At Sat, 25 Oct 2003 09:31:59 -0500,
Quoted 40 lines · Zinx Verituse
Quoted 26 lines · Zinx Verituse
Quoted 25 lines · Takashi Iwai
At Thu, 23 Oct 2003 20:05:02 -0500,
Quoted 22 lines · Zinx Verituse
Any ideas on the problem with me not being able to record if the Input Source is set to Mic?
arecord records when it's set to Line (as it was forced, before), and does playback as well..
When it's set to Mic, I get no playback from a Mic (and I'm not wanting to hook up powered output in to the jack when it's set to Mic), but I suspect it's still Line-in, and the register being twiddled isn't right, or needs some more setup.
arecord waits a bit, then gives the error I mentioned:
arecord: pcm_read:1110: read error: Input/output errordmesg says nothing :/
If nothing else, the settings do have to do with the actual capture sources (idx 0 vs. idx 1), because when I set idx 0 to mic, it can't record, but idx 1 can, and when I set idx 1 to mic, it can't record, but idx 0 can. When both are set to mic, neither can record.
Quoted 11 lines
Quoted 3 lines
sorry, could you elaborate this? i'm confused.
did you try hw:0,0 and hw:0,1, right?Yeah, hw:0,0 fails when Input Source idx 0 is set to Mic, and hw:0,1 fails when Input Source idx 1 is set to Mic.
Quoted 3 lines
Takashi
Quoted 7 lines
I have more to report on this issue:
When I was recording with 'Line' selected as the 'Input Source', 'Mic' was the selected recording device, and 'Line' was completely silent. Also, I have noticed that if I'm playing something on hw:0,0, then hw:0,1 fails like recording does. However, if I try to play two things to hw:0,0, it works. And if I try to play something to hw:0,1 while hw:0,0 is closed, it also works.
well, playing hw:0,0 and hw:0,1 is different from capture. hw:0,0 is the multi-play device (DXS channels) while hw:0,1 is the multi-channel play device for 5.1 outputs. and you cannot access to both devices at the same time, anyway.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/
Quoted 3 lines · Takashi Iwai
At Sat, 25 Oct 2003 09:31:59 -0500,
Quoted 1 line · Zinx Verituse
[snip]
Quoted 9 lines
Quoted 8 lines
I have more to report on this issue:
When I was recording with 'Line' selected as the 'Input Source', 'Mic' was the selected recording device, and 'Line' was completely silent. Also, I have noticed that if I'm playing something on hw:0,0, then hw:0,1 fails like recording does. However, if I try to play two things to hw:0,0, it works. And if I try to play something to hw:0,1 while hw:0,0 is closed, it also works.
Quoted 5 lines
well, playing hw:0,0 and hw:0,1 is different from capture. hw:0,0 is the multi-play device (DXS channels) while hw:0,1 is the multi-channel play device for 5.1 outputs. and you cannot access to both devices at the same time, anyway.
Might I suggest that it gives device or resource busy, or blocks on open, then? :) Right now, it's pretending everything is fine, until you try to actually play something, then it just sits there doing nothing.
Signature · 8 lines
Zinx Verituse ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/
At Mon, 27 Oct 2003 15:35:49 -0600,
Quoted 21 lines · Zinx Verituse
Quoted 3 lines · Takashi Iwai
At Sat, 25 Oct 2003 09:31:59 -0500,
Quoted 1 line · Zinx Verituse
[snip]
Quoted 9 lines
Quoted 8 lines
I have more to report on this issue:
When I was recording with 'Line' selected as the 'Input Source', 'Mic' was the selected recording device, and 'Line' was completely silent. Also, I have noticed that if I'm playing something on hw:0,0, then hw:0,1 fails like recording does. However, if I try to play two things to hw:0,0, it works. And if I try to play something to hw:0,1 while hw:0,0 is closed, it also works.Quoted 5 lines
well, playing hw:0,0 and hw:0,1 is different from capture. hw:0,0 is the multi-play device (DXS channels) while hw:0,1 is the multi-channel play device for 5.1 outputs. and you cannot access to both devices at the same time, anyway.
Quoted 4 lines
Might I suggest that it gives device or resource busy, or blocks on open, then? :) Right now, it's pretending everything is fine, until you try to actually play something, then it just sits there doing nothing.
i would set this bugzilla priority to LATER (if any exists :) it's not a critical bug, so the fix will be postponed after 1.0 release.
of course, a patch is always welcome :)
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/