So I looked for a systematic naming convention, but according to the Linux
allocated devices list (https://static.lwn.net/kernel
doc/admin-guide/devices.html) there is a large number of tty* names in use
for different serial drivers. Perhaps a different approach (
On Fri, Aug 18, 2017 at 9:39 AM, Graeme Geldenhuys <
mailingli...@geldenhuys.co.uk> wrote:
> On 2017-08-18 07:51, Christo Crause wrote:
>
>> I've also just noted a typing error in GetSerialPortNames: '/dev/ttyAM*'
>> should rather be '/dev/ttyACM*''
>>
>
> My version also has the first instance
On 2017-08-18 10:34, Mark Morgan Lloyd wrote:
I saw some of those in th serial.pp in FPC trunk. Thanks for the
information.
I've got this terrible habit of inserting comments...:-)
You and I must be a rare breed of programmer then. :-)
Regards,
Graeme
On 18/08/17 07:45, Graeme Geldenhuys wrote:
On 2017-08-18 08:15, Mark Morgan Lloyd wrote:> There's a> specific
gotcha related to differences in the way Linux and Solaris> handle
select(),
I saw some of those in th serial.pp in FPC trunk. Thanks for the
information.
I've got this terrible
On 2017-08-18 07:51, Christo Crause wrote:
I've also just noted a typing error in GetSerialPortNames: '/dev/ttyAM*'
should rather be '/dev/ttyACM*''
My version also has the first instance (ttyAM*) with a comment "ARM
boards". Your implementation in the bug report looks a lot better than
what
On 2017-08-18 08:15, Mark Morgan Lloyd wrote:
There's a
specific gotcha related to differences in the way Linux and Solaris
handle select(),
I saw some of those in th serial.pp in FPC trunk. Thanks for the
information.
I'm not aware of a reliable, cross-platform way of getting a complete
On 17/08/17 14:00, Graeme Geldenhuys wrote:
Hi,
If somebody with more experience (than me) with the Synaser and FPC
serial.pp units could comment, that would be much appreciated.
For a new cross-platform project where I need to talk to a device hooked
up to a serial port, which unit would be
I see the common Linux port names got added to Synaser (trunk) but the BDS
variants (https://sourceforge.net/p/synalist/bugs/21/) wasn't added.
I've also just noted a typing error in GetSerialPortNames: '/dev/ttyAM*'
should rather be '/dev/ttyACM*''
On Thu, Aug 17, 2017 at 3:45 PM, Graeme
On 2017-08-17 18:05, gebylist wrote:
For most actual Synaser version you must look at Synapse SVN server.;-)
Synaser have class TBlockSerial. It can work with*any* device name. (It
know to emulate Windows COMxx names on Linux too.)
Thank you Lukas, I'll make sure to get the latest from SVN
Dne 17.08.2017 v 15:45 Graeme Geldenhuys napsal(a):
>
> Now for the Synaser unit - the one I have is from 2013, and I already
> noticed that there is no support for FreeBSD's /dev/* names to access
> serial ports. Granted I added FreeBSD support to the
> GetSerialPortNames() function in 5
Hi,
If somebody with more experience (than me) with the Synaser and FPC
serial.pp units could comment, that would be much appreciated.
For a new cross-platform project where I need to talk to a device hooked
up to a serial port, which unit would be the best to use? Normally I
would go with
11 matches
Mail list logo
