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 ques
Von: Holger Bruns :
> 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 usually called "d
Von: Holger Bruns :
> 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 of that UART a
Hi!
> Hello
> I get strange results form GetLasError in WinCe;
> something like 1449435930, for example;
>
> I use this:
> {$include d:\lazarus\fpc\2.2.4\source\rtl\wince\wininc\coredll.inc}
> function GetLastError:DWORD; external KernelDLL name 'GetLastError';
>
> var
> err: dword;
>
> begin
>
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 in
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
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 /dev
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
cannot
Hi,
I have written a TRAC client in lazarus / FPC that uses XML RPC to contact TRAC.
It is base on INDY10 when using Lazarus / FPC.
see:
http://code.google.com/p/tracker-for-trac/
-- Hinnack
>> Hello,
>>
>> Are there any parsers for SOAP and XML-RPC (and works in Linux) that
>> written in pu
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 f
10 matches
Mail list logo
