Re: [PATCH 06/13] USB: serial: ch341: fix initial line settings

2016-12-20 Thread Russell Senior
On Tue, Dec 20, 2016 at 8:07 AM, Johan Hovold wrote: > Perhaps we should determine what else is working or broken first, > though. > > Russel, could you test if break-signalling works, and if the > modem-control signals (DTR/RTS) are asserted at open? Do you get any >

Re: [PATCH 06/13] USB: serial: ch341: fix initial line settings

2016-12-20 Thread Russell Senior
On Tue, Dec 20, 2016 at 7:52 AM, Johan Hovold <jo...@kernel.org> wrote: > On Tue, Dec 20, 2016 at 07:31:55AM -0800, Russell Senior wrote: >> Not sure what the complaint about keys is about, I had not seen that >> before. > > Related to module signing, not sure why you

Re: [PATCH 06/13] USB: serial: ch341: fix initial line settings

2016-12-20 Thread Russell Senior
On Tue, Dec 20, 2016 at 1:13 AM, Johan Hovold wrote: > Perhaps you could give the attached vendor driver a quick spin just to > confirm that? It's a rebased version against usb-next. This is plain jane usb-next with your vendor patch, which I applied in a local branch:

Re: [PATCH 06/13] USB: serial: ch341: fix initial line settings

2016-12-20 Thread Russell Senior
> I'm not sure what device we're dealing with here, but it seems it would > not be supported by the vendor (whose version of this driver also uses > the init-command). > > Perhaps you could give the attached vendor driver a quick spin just to > confirm that? It's a rebased version against

Re: [PATCH 06/13] USB: serial: ch341: fix initial line settings

2016-12-19 Thread Russell Senior
>> Apart from the two additional tests mentioned above, can you also >> provide a log from when connecting the device using the following commit >> that I just pushed to the ch341 branch: >> >> f341ee36198d ("dbg: ch341: add register dumps to probe") >> >> which provides dumps of the

Re: [PATCH 06/13] USB: serial: ch341: fix initial line settings

2016-12-19 Thread Russell Senior
On Mon, Dec 19, 2016 at 2:58 AM, Johan Hovold <jo...@kernel.org> wrote: > On Sat, Dec 17, 2016 at 03:27:43AM -0800, Russell Senior wrote: >> All testing is with minicom. > > Thanks for this through report. > >> Starting with 00013-gc510871: >> >>

Re: [PATCH 06/13] USB: serial: ch341: fix initial line settings

2016-12-17 Thread Russell Senior
00, [0x1213] = 00 00 (post init - lcr reset) Let me know if I can test anything else! On Fri, Dec 16, 2016 at 9:30 AM, Johan Hovold <jo...@kernel.org> wrote: > On Fri, Dec 16, 2016 at 05:13:50PM +0100, Johan Hovold wrote: >> On Fri, Dec 16, 2016 at 08:04:18AM -0800, Russe

Re: [PATCH 06/13] USB: serial: ch341: fix initial line settings

2016-12-16 Thread Russell Senior
Sorry, I got distracted. I'm back now. Do you want me to test your 13 patch series? And what is that on top of? Thanks On Fri, Dec 16, 2016 at 6:46 AM, Johan Hovold wrote: > On Fri, Dec 16, 2016 at 01:19:05PM +, Aidan Thornton wrote: >> On Wed, Dec 14, 2016 at 3:28 PM,

Re: ch341

2016-12-12 Thread Russell Senior
On Mon, Dec 12, 2016 at 10:19 AM, Johan Hovold <jo...@kernel.org> 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 <jo...@kernel.org> wrote: >> > On Mon, Dec 12, 2016 at 07:51:59AM -0800, Russ

Re: ch341

2016-12-12 Thread Russell Senior
On Mon, Dec 12, 2016 at 7:54 AM, Johan Hovold <jo...@kernel.org> 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 <jo...@kernel.org> wrote: >> > On Mon, Dec 12, 2016 at 07:09:34AM -0800, Russ

Re: ch341

2016-12-12 Thread Russell Senior
On Mon, Dec 12, 2016 at 7:40 AM, Johan Hovold <jo...@kernel.org> 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 <jo...@kernel.org> wrote: >> >> > Ok, so maybe your device simpl

Re: ch341

2016-12-12 Thread Russell Senior
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

Re: ch341

2016-12-12 Thread Russell Senior
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

Re: ch341

2016-12-12 Thread Russell Senior
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

Re: ch341

2016-12-09 Thread Russell Senior
gt; whatever it does consistently. > > Sincerely, > Karl P > > > Russell Senior <russ...@personaltelco.net> 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

Re: ch341

2016-12-09 Thread Russell Senior
> 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

Re: ch341

2016-12-09 Thread Russell Senior
>> 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). > >

Re: ch341

2016-12-08 Thread Russell Senior
On Thu, Dec 8, 2016 at 10:02 AM, Johan Hovold <jo...@kernel.org> wrote: > On Thu, Dec 08, 2016 at 04:41:44AM -0800, Russell Senior wrote: >> >>>>> "Johan" == Johan Hovold <jo...@kernel.org> writes: >> >> [...] >> >> Johan>

Re: ch341

2016-12-08 Thread Russell Senior
or 1, depending on the tty. Though, I seem to get the same behavior with minicom. -- Russell Senior, President russ...@personaltelco.net -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: ch341

2016-12-08 Thread Russell Senior
d7fb5e77e78,8) [ 824.635309] usb 6-2: ch341-uart converter now attached to ttyUSB0 -- Russell Senior, President russ...@personaltelco.net -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: ch341

2016-12-07 Thread Russell Senior
t TTL), and did not ('a' -> 0x01, 'b' -> 0x02, etc) with ch341-based usb-serial adapter (again with PC levels, measured MIN/MAX voltages with a DVM and saw, about -7V/+7V). I still suspect shoddy hardware. It would be nice to hear someone else with the ch341-based hardware to say it works

Re: ch341

2016-12-07 Thread Russell Senior
deal on them, which they passed on to me! -- Russell Senior, President russ...@personaltelco.net -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html