Gustavo Enrique Jimenez schrieb:
Accessing serial ports in linux could be as simple as to write/read
to/from /dev/ttySx . You don't need io ports. For a multiplatform
solution, use synapsis/synaser.
Sometimes it is useful to get more information about device drivers.
Searching the internet
Holger,
The only way to use serial ports successfully to me, is to use the unit
serial on fpc, if I choose fpc to deal with serial ports. Another
problem results from misleading comments on the implemented procedures
and functions. As explained, seropen would return a zero, if a device
Paul Breneman schrieb:
Here is a very simple serial example using FPC and SynaSer:
http://www.turbocontrol.com/simpleserial.htm
Hope that is of some help.
Thank you. I have already solved the problem to access serial ports, but
I am rather clueless while dealing with device drivers like
Holger Bruns wrote:
I need to read
and write every register of that UART as explained in the National
Semiconductor databook, register by register, address by address.
If I may ask, just what sort of application are you developing that
needs such complete and total access to the UART? Using
Jeff Wormsley schrieb:
If you really need to go that route, with full access to 100% of the
UART, perhaps this book would help (chapter 6 is on serial device
drivers).
*http://tinyurl.com/yjk4c9j*
I'll follow your link.
Just know that you will have to do that part of your application
Von: Holger Bruns holger.br...@gmx.net:
If I intend
to use device drivers, I need to know how to access the ports of a
device, which means in my case to a serial port based on the 16550D
Universal Asynchronous Receiver/Transmiter with FIFOs.
No.
I need to read
and write every register
Von: Holger Bruns holger.br...@gmx.net:
I am rather clueless while dealing with device drivers like /dev/ttyS0
on linux. My question is, what do I grab while reading from a device
driver file like /dev/ttyS0?
You don't read from a device driver. You read from a device. What you read
is
Vinzent Höfler schrieb:
I doubt it. You sure sound write-only...
I am aware, that I raise problably anger while asking on mailing lists
for information, because every question can be interpreted as an insult.
I do not post for interpersonal relationships, but for answers to
technical
In our previous episode, Holger Bruns said:
I decided to copy all the necessary files for x86.pp and oldlinux.pp
into one directory for compiling these two units. This compilation
failed due to syntax errors. A bunch of warnings also appeared. I post
only the syntax error messages:
-
Holger Bruns wrote on Tue, 03 Nov 2009:
Jonas Maebe schrieb:
The next release of FPC will include a version of the x86 unit for
Linux/x86_64. In general, if a unit is not available in a
precompiled version for your platform, the reason is that it does
not work. Unless you intend to
Jonas Maebe schrieb:
And regarding your later remark about FPC only being usable as root:
it's the Linux kernel that only allows direct port access by root.
Please stop blaming every single one of your problems on the compiler
or the RTL.
Under the bottom line, the result is just the same.
Holger Bruns wrote:
Under the bottom line, the result is just the same. You need to become
a superuser on a linux system, if you want to compile source code for
accessing ports directly, regardless of the compiler or any other tool.
All modern OS's have this restriction. Even on Windows,
2009/11/3 Holger Bruns holger.br...@gmx.net:
Jonas Maebe schrieb:
And regarding your later remark about FPC only being usable as root: it's
the Linux kernel that only allows direct port access by root. Please stop
blaming every single one of your problems on the compiler or the RTL.
Under
Hi,
I decided to copy all the necessary files for x86.pp and oldlinux.pp
into one directory for compiling these two units. This compilation
failed due to syntax errors. A bunch of warnings also appeared. I post
only the syntax error messages:
oldlinux.pp(1696,2) Error: User defined: Cannot
Holger Bruns wrote on Tue, 03 Nov 2009:
I decided to copy all the necessary files for x86.pp and oldlinux.pp
into one directory for compiling these two units. This compilation
failed due to syntax errors. A bunch of warnings also appeared. I
post only the syntax error messages:
You
Jonas Maebe schrieb:
Holger Bruns wrote on Tue, 03 Nov 2009:
I decided to copy all the necessary files for x86.pp and oldlinux.pp
into one directory for compiling these two units. This compilation
failed due to syntax errors. A bunch of warnings also appeared. I
post only the syntax error
16 matches
Mail list logo
