On Mon, Jun 12, 2017 at 4:33 PM, Hans Peter Möller wrote:
> What do you mean with "release of workqueue" ?? The podhd_disconnect
> function?
>
> The other two (claim interface in and sysfs out) I think it might by solved
> with creating a new if in podhd_init funtion:
>
>
> static int podhd_init(s
What do you mean with "release of workqueue" ?? The podhd_disconnect
function?
The other two (claim interface in and sysfs out) I think it might by solved
with creating a new if in podhd_init funtion:
static int podhd_init(struct usb_line6 *line6,
const struct usb_device_id *id)
{
Hi there,
On Jun 12, 2017 12:30 AM, "Hans Peter Möller" wrote:
You were right, I forgot to test if disabling the initialization
worked. I tested and it worked, the "receive length failed (error
-11)" error disapear.
I actually change all of the LINE6_CAP_CONTROL to
LINE6_CAP_CONTROL_INIT and it
Sorry to bother you again Andrej,
I will have to learn a bit of git to make the patch.
I believe that pod hd pro x works the same way as podhd500x, so it should
be copying the same parameters, but I cannot test it because I don't have a
pod hd pro x. Sould I include the parameters in the git or
You were right, I forgot to test if disabling the initialization worked. I
tested and it worked, the "receive length failed (error -11)" error
disapear.
I actually change all of the LINE6_CAP_CONTROL to LINE6_CAP_CONTROL_INIT
and it worked. I don't know in 4.12 but in 4.10 there is used in
static
Hey there,
On Sun, Jun 11, 2017 at 4:07 AM, Hans Peter Möller wrote:
> Hi Andrej,
>I believe I will have to sniff to get rid of that error.
>
Well, if you insist... :-) I guess since it works without the
initialization, and noone really needs the device serial number, you
could for now just
Hi Andrej,
I believe I will have to sniff to get rid of that error.
Is there a reason why in kernel 4.10 the podhd.c has no midi init? Now I
don't see the pod midi ports, I remember that in some of my other tries
(kernel 4.4 or 4.8 or quirck) I could see the midi ports of my pod in
qjacktl conn
Hi Hans Peter,
On Sat, Jun 10, 2017 at 5:05 AM, Hans Peter Möller wrote:
>I made the tests,
> - Removing LINE6_CAP_CONTROL disable playback in the unit, I can still
> capture but no sound come out of the unit. The "receive length failed (error
> -11)" disappear. Since Initialization is requ
Hi Andrej,
I made the tests,
- Removing LINE6_CAP_CONTROL disable playback in the unit, I can still
capture but no sound come out of the unit. The "receive length failed
(error -11)" disappear. Since Initialization is required for playback, the
.ctrl_if is needed and thus the simple patch will o
Ah yes, that one patch... I already forgot about it (and of course
didn't check the sources at the time of merge in 4.12 :)) Ok, but you
shouldn't need the ctrl_if thing if you only use the audio stuff.
Regarding the maxpacket error, my prints the same - Line6 apparently
violates the USB specifica
Hi,
I will thest droping those things and see what happened.
What about the " config 1 interface 1 altsetting 0 bulk endpoint 0x1 has
invalid maxpacket 64" ??? It has appear since the first time I plug my pod
with the stock kernel 4.4.
in your kernel 4.12 the if_ctrl doesn't appear? How did the
Hey,
On Fri, Jun 9, 2017 at 5:35 AM, Hans Peter Möller wrote:
> Hi Andrej,
>good news!!
> I can capture and listen from my pod.
>
Perfect!
> I compare the lsusb from de x3 and I found that it has the same alternative
> setting issue than the hd500x, which is different from hd300 (I couldn'
Hi Andrej,
good news!!
I can capture and listen from my pod.
I compare the lsusb from de x3 and I found that it has the same alternative
setting issue than the hd500x, which is different from hd300 (I couldn't
get one from h400 nor from h500). In x3 and 500x the altsetting is
different for audi
On Jun 7, 2017 1:23 AM, "Hans Peter Möller" wrote:
Thanks Andrej,
I will do that.
I also found in the ardour blog some quirk on snd-usb-audio for pod hd pro
in https://community.ardour.org/node/13646. The lsusb of the pod hd pro is
almost identical (except for the product id) from the one of the
Thanks Andrej,
I will do that.
I also found in the ardour blog some quirk on snd-usb-audio for pod hd pro
in https://community.ardour.org/node/13646. The lsusb of the pod hd pro is
almost identical (except for the product id) from the one of the pod
hd500x.
I would try that path to, I still don't
On Mon, Jun 5, 2017 at 7:16 PM, Hans Peter Möller wrote:
> The 4 EP (2 audio and 2 ctrl) match the ones from PODHD500_0 and PODHD500_1
> (do you know what are the ctrl or User for??) so it appears to be simple.
Not sure what you mean by "User", but the ctrl are used (well, can be
used) to transfe
Thanks Andrej!
with audio working I will be more than happy.
The 4 EP (2 audio and 2 ctrl) match the ones from PODHD500_0 and PODHD500_1
(do you know what are the ctrl or User for??) so it appears to be simple.
Now to test if this simple edit would be enough, I assume I have to
uninstall the
Hi there,
On Thu, Jun 1, 2017 at 1:19 AM, Hans Peter Möller wrote:
>I want to help to inlude the pod hd500x in the driver. I've never done
> some driver programming but I have done a lot of coding myself, from ASM in
> a PIC to php, java, javascript, vb, c, c#, etc... If you can give me some
Hi,
I want to help to inlude the pod hd500x in the driver. I've never done
some driver programming but I have done a lot of coding myself, from ASM in
a PIC to php, java, javascript, vb, c, c#, etc... If you can give me some
info to read and study it would be great to start.
Do you use wireshar
19 matches
Mail list logo
