Hi Gil,
Gil Weber writes:
>>> To make sure, I have also performed some additional tests. The problem
>>> seems unrelated to the gadget being used: I have tried various
>>> combinations (zero, ethernet, etc.), even setting up an ACM device
>>> using configfs, and the result is the same: a host de
Hi,
>> To make sure, I have also performed some additional tests. The problem
>> seems unrelated to the gadget being used: I have tried various
>> combinations (zero, ethernet, etc.), even setting up an ACM device
>> using configfs, and the result is the same: a host detects the device
>> for a br
Hi,
JB writes:
>>> To make sure, I have also performed some additional tests. The problem
>>> seems unrelated to the gadget being used: I have tried various
>>> combinations (zero, ethernet, etc.), even setting up an ACM device
>>> using configfs, and the result is the same: a host detects the d
Hello,
>> To make sure, I have also performed some additional tests. The problem
>> seems unrelated to the gadget being used: I have tried various
>> combinations (zero, ethernet, etc.), even setting up an ACM device
>> using configfs, and the result is the same: a host detects the device
>> for a
Hi,
JB writes:
>> did you check that getty is still running ? That "deactivated" message
>> means that whatever had /dev/ttyGS0 opened, decided to close it. This
>> could mean that getty got a SIGHUP and just decided to close that fd.
>
> I have only briefly experimented with getty (I also tried
Hello,
> did you check that getty is still running ? That "deactivated" message
> means that whatever had /dev/ttyGS0 opened, decided to close it. This
> could mean that getty got a SIGHUP and just decided to close that fd.
I have only briefly experimented with getty (I also tried opening the
por
Hi,
JB writes:
> [ text/plain ]
>> IIRC ACM will only do anything after you open /dev/ttyGS0 on the
>> peripheral side. Are you running getty on ttyGS0 ?
>
> I did try that, that would explain why it appears only once.
did you check that getty is still running ? That "deactivated" message
means
> IIRC ACM will only do anything after you open /dev/ttyGS0 on the
> peripheral side. Are you running getty on ttyGS0 ?
I did try that, that would explain why it appears only once.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.ke
JB writes:
> Hello,
>
>> 4.5.0+, which patches do you have on top of 4.5 vanilla ?
>
> No code patches, just the configuration and dts file for the board.
>
>> Also, can you try this patch:
>
> I tried it, but the result is the same.
>
> Sometimes I can see another entry in the log:
>
> g_serial g
Hello,
> 4.5.0+, which patches do you have on top of 4.5 vanilla ?
No code patches, just the configuration and dts file for the board.
> Also, can you try this patch:
I tried it, but the result is the same.
Sometimes I can see another entry in the log:
g_serial gadget: suspend
And there is a
Hi,
(please, don't top-post)
JB writes:
> [ text/plain ]
> But that's it. On the host side, the device is detected for a brief
> moment - I managed to get the device info, and it looks like the real
> deal:
>
> Gadget Serial v2.4:
>Product ID: 0xa4a7
>Vendor ID: 0x0525
But that's it. On the host side, the device is detected for a brief
moment - I managed to get the device info, and it looks like the real
deal:
Gadget Serial v2.4:
Product ID: 0xa4a7
Vendor ID: 0x0525 (PLX Technology, Inc.)
Version: 4.05
Speed: Up to 48
12 matches
Mail list logo
