On 20.07.2013 05:44, Alan Stern wrote:
static int snd_usb_sb_x_fi_boot_quirk(struct usb_device *dev)
{
u16 buf = 1;
snd_printk(KERN_ERR X-Fi Surround 5.1 newer quirk\n);
snd_usb_ctl_msg(dev, usb_rcvctrlpipe(dev, 0), 0x2a,
USB_DIR_IN | USB_TYPE_VENDOR |
Alan Stern wrote:
On Sat, 20 Jul 2013, Mariusz Grecki wrote:
+u16 buf = 1;
+
+snd_usb_ctl_msg(dev, usb_rcvctrlpipe(dev, 0), 0x2a,
+USB_DIR_IN | USB_TYPE_VENDOR | USB_RECIP_OTHER,
+0, 0, buf, 2);
There's a serious problem here. It's present
On Sat, 20 Jul 2013, Clemens Ladisch wrote:
Alan Stern wrote:
On Sat, 20 Jul 2013, Mariusz Grecki wrote:
+ u16 buf = 1;
+
+ snd_usb_ctl_msg(dev, usb_rcvctrlpipe(dev, 0), 0x2a,
+ USB_DIR_IN | USB_TYPE_VENDOR | USB_RECIP_OTHER,
+ 0, 0, buf, 2);
On Sat, 20 Jul 2013, Mariusz Grecki wrote:
This is the same as the Audigy function, except for the printk string
and the 2-byte buffer instead of the 1-byte buffer, right? Therefore I
suggest combining them into a single function. You can pass the string
and the buffer size as
Hi Alan,
thanks for the fast response and useful infos. Unfortunately your patch
does not work but triggered by it I made it working.
The changes as as follows:
First we should diverse between Audigy and X-Fi in snd_usb_apply_boot_quirk:
case USB_ID(0x041e, 0x30df):
/*
On Sat, 20 Jul 2013, Mariusz Grecki wrote:
Hi Alan,
thanks for the fast response and useful infos. Unfortunately your patch
does not work but triggered by it I made it working.
The changes as as follows:
First we should diverse between Audigy and X-Fi in snd_usb_apply_boot_quirk:
On Thu, 4 Jul 2013, Mariusz Grecki wrote:
Hi all,
I have made some experiments and things looks much more clear. Although
I do not understand why once a time the device was initialized by Linux
to HS operation but probably this is not so important.
It seems that some additional configuration
Mariusz Grecki wrote:
Does anybody have any idea what can be the problem? The card is
recognized as HS device by MS Windows (XP version) without any exceptions...
When you say Windows, do you mean Windows itself, or a driver from
Creative that you installed and that can send some
W dniu 06/28/2013 09:00 AM, Clemens Ladisch pisze:
Mariusz Grecki wrote:
Does anybody have any idea what can be the problem? The card is
recognized as HS device by MS Windows (XP version) without any exceptions...
When you say Windows, do you mean Windows itself, or a driver from
Creative
On Wed, Jun 26, 2013 at 10:43:39PM +0200, Mariusz Grecki wrote:
The problem relates directly to the old one:
http://thread.gmane.org/gmane.linux.usb.general/20816/focus=20850
The problem is, that usually (in fact all the time with one! exception
so far) the card is recognized by operating
On Wed, 26 Jun 2013, Mariusz Grecki wrote:
The problem relates directly to the old one:
http://thread.gmane.org/gmane.linux.usb.general/20816/focus=20850
The problem is, that usually (in fact all the time with one! exception
so far) the card is recognized by operating system as a
The problem relates directly to the old one:
http://thread.gmane.org/gmane.linux.usb.general/20816/focus=20850
The problem is, that usually (in fact all the time with one! exception
so far) the card is recognized by operating system as a full-speed (FS)
device not the high-speed (HS) one. This
12 matches
Mail list logo
