On Mon, Dec 12, 2016 at 04:15:29PM -0800, Russell Senior wrote:
> On Mon, Dec 12, 2016 at 10:19 AM, Johan Hovold wrote:
> > Can you try also the below diagnostics patch on top of usb-next (not
> > usb-linus this time)?
> >
> > It seems we should be able to revert to setting the divisors and lcr
>
On Mon, Dec 12, 2016 at 10:19 AM, Johan Hovold wrote:
> On Mon, Dec 12, 2016 at 08:03:03AM -0800, Russell Senior wrote:
>> On Mon, Dec 12, 2016 at 7:54 AM, Johan Hovold wrote:
>> > On Mon, Dec 12, 2016 at 07:51:59AM -0800, Russell Senior wrote:
>> >> On Mon, Dec 12, 2016 at 7:40 AM, Johan Hovold
On Mon, Dec 12, 2016 at 08:03:03AM -0800, Russell Senior wrote:
> On Mon, Dec 12, 2016 at 7:54 AM, Johan Hovold wrote:
> > On Mon, Dec 12, 2016 at 07:51:59AM -0800, Russell Senior wrote:
> >> On Mon, Dec 12, 2016 at 7:40 AM, Johan Hovold wrote:
> >> > On Mon, Dec 12, 2016 at 07:09:34AM -0800, Rus
On Mon, Dec 12, 2016 at 10:55:14AM -0500, Alan Stern wrote:
> On Mon, 12 Dec 2016, Johan Hovold wrote:
>
> > Ok, so that seems to confirm the suspicion that changing settings after
> > the initial configuration is failing (even though the device does indeed
> > support 5-bit mode).
>
> Perhaps is
On Mon, Dec 12, 2016 at 7:54 AM, Johan Hovold wrote:
> On Mon, Dec 12, 2016 at 07:51:59AM -0800, Russell Senior wrote:
>> On Mon, Dec 12, 2016 at 7:40 AM, Johan Hovold wrote:
>> > On Mon, Dec 12, 2016 at 07:09:34AM -0800, Russell Senior wrote:
>> >> On Mon, Dec 12, 2016 at 1:54 AM, Johan Hovold
On Mon, 12 Dec 2016, Johan Hovold wrote:
> Ok, so that seems to confirm the suspicion that changing settings after
> the initial configuration is failing (even though the device does indeed
> support 5-bit mode).
Perhaps issuing a USB device reset before trying to change the settings
will help.
On Mon, Dec 12, 2016 at 07:51:59AM -0800, Russell Senior wrote:
> On Mon, Dec 12, 2016 at 7:40 AM, Johan Hovold wrote:
> > On Mon, Dec 12, 2016 at 07:09:34AM -0800, Russell Senior wrote:
> >> On Mon, Dec 12, 2016 at 1:54 AM, Johan Hovold wrote:
> >>
> >> > Ok, so maybe your device simply does not
On Mon, Dec 12, 2016 at 7:40 AM, Johan Hovold wrote:
> On Mon, Dec 12, 2016 at 07:09:34AM -0800, Russell Senior wrote:
>> On Mon, Dec 12, 2016 at 1:54 AM, Johan Hovold wrote:
>>
>> > Ok, so maybe your device simply does not support changing the line
>> > settings more than once. That is, the init
On Mon, Dec 12, 2016 at 07:09:34AM -0800, Russell Senior wrote:
> On Mon, Dec 12, 2016 at 1:54 AM, Johan Hovold wrote:
>
> > Ok, so maybe your device simply does not support changing the line
> > settings more than once. That is, the initial settings chosen are used
> > until re-connected. This w
On Mon, Dec 12, 2016 at 1:54 AM, Johan Hovold wrote:
> Ok, so maybe your device simply does not support changing the line
> settings more than once. That is, the initial settings chosen are used
> until re-connected. This would seem to be in accordance with a comment
> found in one of the out-of-
On Mon, Dec 12, 2016 at 04:36:54AM -0800, Russell Senior wrote:
> On Mon, Dec 12, 2016 at 1:54 AM, Johan Hovold wrote:
>
> > If you connect the ch340 you have in loopback mode, with the removed
> > initial LCR write that fixed the 5-bit behaviour, can you get that
> > behaviour back by setting 5-
On Mon, Dec 12, 2016 at 1:54 AM, Johan Hovold wrote:
> If you connect the ch340 you have in loopback mode, with the removed
> initial LCR write that fixed the 5-bit behaviour, can you get that
> behaviour back by setting 5-bit word size after opening the port? (This
> was what I was going for wit
On Mon, Dec 12, 2016 at 1:48 AM, Johan Hovold wrote:
> What exactly did you mean by "the baudrate change" above? If you revert
> to setting the divisors directly (rather than using SERIAL_INIT), we
> should be back to how things work in 4.9 (which you can get to work with
> the pl2303 by removing
On Fri, Dec 09, 2016 at 07:38:51AM -0800, Russell Senior wrote:
> > Also, when the above change makes usb-linus works, does changing the
> > word size appear to work after probe?
>
> I'm not sure what changing the word size is supposed to do. The
> usb-linus + previous patch in loopback seems to
On Fri, Dec 09, 2016 at 07:14:02AM -0800, Russell Senior wrote:
> >> Okay, I built your usb-linus
> >>
> >> 46490c347df406b3368680dd911620e52dc7bfa4
> >>
> >> with the line:
> >>
> >>r = ch341_control_out(dev, 0x9a, 0x2518, 0x0050);
> >>
> >> commented out. More precisely:
> >
> >> Loopback wo
Hi Karl,
The pl2303 has always worked in 8N1 mode for me, talking to serial
devices. That's all I can say with certainty.
On Fri, Dec 9, 2016 at 8:00 AM, Karl Palsson wrote:
>
> Can you actually trust that pl2303 module? They're not exactly
> known for being trouble free, and have often been cl
Can you actually trust that pl2303 module? They're not exactly
known for being trouble free, and have often been cloned in the
past as well, with varyings levels of success. Do you have a
cp210x or ft23x at all?
This is one of the great pitfalls of loopback testing, it doesn't
test that anything
> Also, when the above change makes usb-linus works, does changing the
> word size appear to work after probe?
I'm not sure what changing the word size is supposed to do. The
usb-linus + previous patch in loopback seems to work with minicom
regardless of wordsize. More so even than I would guess
>> Okay, I built your usb-linus
>>
>> 46490c347df406b3368680dd911620e52dc7bfa4
>>
>> with the line:
>>
>>r = ch341_control_out(dev, 0x9a, 0x2518, 0x0050);
>>
>> commented out. More precisely:
>
>> Loopback works, and also interoperates with pl2303 (through a null
>> modem adapter).
>
> Interes
On Fri, Dec 09, 2016 at 10:21:32AM +, Aidan Thornton wrote:
> On Fri, Dec 9, 2016 at 3:26 AM, Russell Senior
> wrote:
> > On Thu, Dec 8, 2016 at 10:02 AM, Johan Hovold wrote:
> >> On Thu, Dec 08, 2016 at 04:41:44AM -0800, Russell Senior wrote:
> >>> > "Johan" == Johan Hovold writes:
> >
On Thu, Dec 08, 2016 at 07:26:26PM -0800, Russell Senior wrote:
> On Thu, Dec 8, 2016 at 10:02 AM, Johan Hovold wrote:
> > On Thu, Dec 08, 2016 at 04:41:44AM -0800, Russell Senior wrote:
> >> > "Johan" == Johan Hovold writes:
> >>
> >> [...]
> >>
> >> Johan> Ok, and you were using a terminal
On Fri, Dec 9, 2016 at 3:26 AM, Russell Senior
wrote:
> On Thu, Dec 8, 2016 at 10:02 AM, Johan Hovold wrote:
>> On Thu, Dec 08, 2016 at 04:41:44AM -0800, Russell Senior wrote:
>>> > "Johan" == Johan Hovold writes:
>>>
>>> [...]
>>>
>>> Johan> Ok, and you were using a terminal program such as
On Thu, Dec 8, 2016 at 10:02 AM, Johan Hovold wrote:
> On Thu, Dec 08, 2016 at 04:41:44AM -0800, Russell Senior wrote:
>> > "Johan" == Johan Hovold writes:
>>
>> [...]
>>
>> Johan> Ok, and you were using a terminal program such as minicom that
>> Johan> properly configures the port for say 8-
On Thu, Dec 08, 2016 at 04:41:44AM -0800, Russell Senior wrote:
> > "Johan" == Johan Hovold writes:
>
> [...]
>
> Johan> Ok, and you were using a terminal program such as minicom that
> Johan> properly configures the port for say 8-bit words?
>
> I was using GNU screen, which I don't specif
> "Johan" == Johan Hovold writes:
Johan> This may be a bit of long shot (or maybe not) but could you try
Johan> the below patch on top of usb-next as well? [...]
Russell> Your patch seems to have fixed it! Yay!
Oops, not so fast. It worked in loopback, but it didn't interoperate
with my
> "Johan" == Johan Hovold writes:
[...]
Johan> Ok, and you were using a terminal program such as minicom that
Johan> properly configures the port for say 8-bit words?
I was using GNU screen, which I don't specifically configure to be
8-bits, but I retried with minicom and specifically set a
On Thu, Dec 08, 2016 at 10:37:28AM +0100, Johan Hovold wrote:
> [ +CC: Adain, Grigori, Karl ]
>
> On Wed, Dec 07, 2016 at 05:51:33PM -0800, Russell Senior wrote:
> > I still suspect shoddy hardware. It would be nice to hear someone else
> > with the ch341-based hardware to say it works for them.
[ +CC: Adain, Grigori, Karl ]
On Wed, Dec 07, 2016 at 05:51:33PM -0800, Russell Senior wrote:
> > "Johan" == Johan Hovold writes:
>
> >> I attach the tty's with GNU screen (but I have also tried microcom
> >> and minicom with the same results). This was my first experience
> >> with or even
> "Johan" == Johan Hovold writes:
>> I attach the tty's with GNU screen (but I have also tried microcom
>> and minicom with the same results). This was my first experience
>> with or even awareness of ch341. I have much more experience with
>> pl2303 and somewhat less with ftdi. With these
On Wed, Dec 07, 2016 at 04:42:21AM -0800, Russell Senior wrote:
> I just bought a bag of usb-serial converters off of ebay, from china for
> super low price (~$2/each). I just plugged a couple of them in,
> connected together through a null-modem adapter. When I plug them, on
> both stock ubuntu
Hi,
I just bought a bag of usb-serial converters off of ebay, from china for
super low price (~$2/each). I just plugged a couple of them in,
connected together through a null-modem adapter. When I plug them, on
both stock ubuntu 16.04's kernel and 4.8.9 built from git, I get a
reasonable lookin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johan Hovold wrote:
> On Mon, Jul 06, 2015 at 03:24:17PM +0200, Peter Stuge wrote:
>
> > Unrelated, but I also have some ch341 hardware, and mine does not
> > work with the mainline driver, it does however work reliably with the
> > vendor driver.
>
Sorry for misunderstanding, I've tested the behavior of Arduino board
on 2 machines and the result is following:
PASSED - Arduino board connected successfully
FAILED - ch341 errors arose
1st machine [USB 3.0] -- Linux 3.18 -- PASSED
1st machine [USB 3.0] -- Linux 4.* -- FAILED
2nd machine [USB 2
Sorry for misunderstanding, I've tested the behavior of Arduino board
on 2 machines and the result is following:
PASSED - Arduino board was connected successfully
FAILED - ch341 errors arose
1st machine [USB 3.0] -- Linux 3.18 -- PASSED
1st machine [USB 3.0] -- Linux 4.* -- FAILED
2nd machine [U
I'm seeing this as well, I've got some work in progress towards this,
but not finding the time I'd hoped. CH340 devices work "fine" with the
current linux driver, but CH341, very very very flaky, if at all.
I'm connecting it to an external modem on the RS232 side. If I use
some other program to connect to the modem, it reports "modem not
responding". To debug further I'm minicom'ing to it. Once connected, I
type "AT" then press Enter. Screen output is pasted below (with Local
Echo set to No and Hex Di
On Sat, Dec 13, 2014 at 01:15:07PM +0800, Liangent wrote:
> Hello,
>
> I bought a new USB-RS232 cable and the system loads ch341.ko for me
> (Debian with kernel 3.14-2-amd64 and 3.16.0-4-amd64). However this
> module does not work with my cable (/dev/ttyUSB0 appears but the
> serial device doesn't
37 matches
Mail list logo
