Now I intend to develop some object for accessing RS-485 UART on RaspComm board (which is itself driven via SPI).
SPI has same basic characteristics like serial port (baud rate, parity.) and even (kind of) asynchronous in/out driven by kernel device so this is why I expected same object could manage them both. (I am able to workaround based on QFile of course, however I would love to do things Qt way ).). What to do to make /dev/spidev0.0 appear in the list? Any clues and advices heartily welcome. I guess I can not (simply) use QSerialPort constructor with '/dev/spidev0.0' parameter before 'somehow' getting /dev/spidev0.0 accepted by QSerialPortInfo. Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.ĭid anybody make QSerialPort(Info) work on /dev/spidev* kernel driver? I have running (visible, configured, operable via spidev_test.c) /dev/spidev0.0, however QSerialPortInfo::availablePorts returns list with just one member, for /dev/ttyAMA0. QextSerialPort add new BaudRate QextSerialPort add new BaudRate.
Hey, I want to add the '691200' and '921600' baud rate to the Qextserialport baud rates list.