On Thu, Jun 29, 2017 at 08:50:32PM +0100, Alan Cox wrote:
> So IMHO there are two cases
>
> 1. The configuration is fixed in the hardware - in which case we should
> automatically set it in kernel, or from device tree.
Right.
> 2. The configuration is soft - in which case you need an ioctl you
So IMHO there are two cases
1. The configuration is fixed in the hardware - in which case we should
automatically set it in kernel, or from device tree.
2. The configuration is soft - in which case you need an ioctl you can
use on the port to change it - irrespective of whether sysfs also
On Wed, Jun 28, 2017 at 08:07:54AM +1000, Stuart Longland wrote:
> This beats the official Moxa solution: their Windows driver wants a
> reboot of the entire machine to switch between serial standards.
Interesting approach.
Johan
--
To unsubscribe from this list: send the line "unsubscribe
On Tue, Jun 27, 2017 at 02:08:51PM +0200, Oliver Neukum wrote:
> Am Dienstag, den 27.06.2017, 19:43 +1000 schrieb Stuart Longland:
> > Maybe a good start would be a "standard" option (referring to the
> > physical signalling standard, TTL/RS-232/RS-422/RS-485), that lists the
> > available
On Tue, Jun 27, 2017 at 07:43:28PM +1000, Stuart Longland wrote:
> On 27/06/17 19:04, Johan Hovold wrote:
> >> What's the "proper" way to configure such ports for RS-422 and/or 4-wire
> >> RS-485? Is there an example driver in the tree that I can use as a
> >> guide to porting Moxa's mode-switch
Oliver Neukum writes:
> Am Mittwoch, den 28.06.2017, 14:01 +0200 schrieb Greg KH:
>> On Wed, Jun 28, 2017 at 11:19:09AM +0200, Oliver Neukum wrote:
>> >
>> > 1) module option
>>
>> No, just no, sorry.
>
> I am sorry, but this is just ideological an answer. This is rather
>
Am Mittwoch, den 28.06.2017, 14:01 +0200 schrieb Greg KH:
> On Wed, Jun 28, 2017 at 11:19:09AM +0200, Oliver Neukum wrote:
> >
> > Am Mittwoch, den 28.06.2017, 08:07 +1000 schrieb Stuart Longland:
> >
> > Hi,
> >
> > >
> > > >
> > > > >
> > > > > and to select 4-wire ("full duplex") RS-485,
On Wed, Jun 28, 2017 at 11:19:09AM +0200, Oliver Neukum wrote:
> Am Mittwoch, den 28.06.2017, 08:07 +1000 schrieb Stuart Longland:
>
> Hi,
>
> > >> and to select 4-wire ("full duplex") RS-485, one does:
> > >> # echo rs485fd > /sys/class/tty/ttyUSB0/standard
> > > This looks like something that
Am Mittwoch, den 28.06.2017, 08:07 +1000 schrieb Stuart Longland:
Hi,
> >> and to select 4-wire ("full duplex") RS-485, one does:
> >> # echo rs485fd > /sys/class/tty/ttyUSB0/standard
> > This looks like something that people will put into udev.
> > So the switch will be done via udev, but the
On 27/06/17 22:08, Oliver Neukum wrote:
> Am Dienstag, den 27.06.2017, 19:43 +1000 schrieb Stuart Longland:
>> Maybe a good start would be a "standard" option (referring to the
>> physical signalling standard, TTL/RS-232/RS-422/RS-485), that lists the
>> available standards when read and shows the
Am Dienstag, den 27.06.2017, 19:43 +1000 schrieb Stuart Longland:
> Maybe a good start would be a "standard" option (referring to the
> physical signalling standard, TTL/RS-232/RS-422/RS-485), that lists the
> available standards when read and shows the "selected" standard in
> brackets (like the
On 27/06/17 19:04, Johan Hovold wrote:
>> What's the "proper" way to configure such ports for RS-422 and/or 4-wire
>> RS-485? Is there an example driver in the tree that I can use as a
>> guide to porting Moxa's mode-switch code over to the ti_usb_3410_5052
>> driver?
>
> I'm afraid not. We have
[ +CC: Alan and linux-usb ]
On Fri, Jun 23, 2017 at 09:44:31AM +1000, Stuart Longland wrote:
> Hi all,
>
> A silly question: I have a Moxa UPort 1150 USB serial interface that I
> am trying to coax into either RS-422 or 4-wire RS-485 mode. Internally,
> this is a TI USB 3410 device, and works
13 matches
Mail list logo