01-04-2006
how to read and write device registers
hello friends,
While in the process of writing device drivers,
i am facing problem in reading and writing device registers.I got base address of those mapped device registers. Can i add offset of those registers to that Base address to get access of those registers or do i have to use readl or writel sort of apis.
thanks in advance
sriram
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi everybody,
i am working in device drivers.As a beginner to this field ,i dont know how to read or write device files. Will copy_to_user and copy_from_user help me?
I have created a device file using mknod command .Can anybody help me in this regard :confused
thanks in advance
sriram (1 Reply)
Discussion started by: sriram.ec
1 Replies
2. UNIX for Dummies Questions & Answers
I am trying to create new files under my directory...but i getting the following message...
cat: write error: No space left on device
How do we handle this error.
I am not getting this error when I login as the super user (3 Replies)
Discussion started by: igandu
3 Replies
3. Shell Programming and Scripting
I need to find all the files that have group Read or Write permission or files that have user write permission.
This is what I have so far:
find . -exec ls -l {} \; | awk '/-...rw..w./ {print $1 " " $3 " " $4 " " $9}'
It shows me all files where group read = true, group write = true... (5 Replies)
Discussion started by: shunter63
5 Replies
4. IP Networking
Hi,
We have smb client running on two of the linux boxes and smb server on another linux system. During a backup operation which uses smb, read of a file was allowed while write to the same file was going on.Also simultaneous writes to the same file were allowed.Following are the settings in the... (1 Reply)
Discussion started by: swatidas11
1 Replies
5. Hardware
Hi,
I am working in device drivers. I am new to device drivers. i have invoked chardev.c.
the driver is insmoded. now i want to write something into this and i want to look what i have written. but i don't know how to write and see. please help me (0 Replies)
Discussion started by: boidi
0 Replies
6. Debian
Hello,
I need to run an application in wine that requires write permission to a USB device. Wine users must not have root privileges. On FreeBSD this could be accomplished by adding the user to the wheel group but I am using Debian 6.0. From looking at the passwd file it is not obvious what... (6 Replies)
Discussion started by: snorkack59
6 Replies
7. Solaris
Hi All,
This is Sandeep Gupta,
I am facing a problem with sudo command.
Whenever i am executing the command "visudo" i am getting the error "visudo: write error: No space left on device".
but i have checked on my Solaris Box everything is ok, i have enough free space on my box, and also... (13 Replies)
Discussion started by: Sandeepgupta
13 Replies
8. Shell Programming and Scripting
I am getting error in a shell script having a simple date command.
Error is " write to 1 failed ".
We saw that /tmp folder was 100% full. When we cleared some space in /tmp folder then script worked fine. Why does date command(or any other command) require space in /tmp folder? Which settings... (6 Replies)
Discussion started by: mahish20
6 Replies
9. UNIX for Advanced & Expert Users
Hi ,
In file first line start with "",when trying to remove using sed i am getting the below error .Please advise
sed -e 's///g' -e 's/$]//g' segment1.txt >>segment_m1
sed: couldn't write 1378 items to stdout: No space left on device
Thanks,
Mohan (1 Reply)
Discussion started by: mohan705
1 Replies
10. Solaris
Running a installation on Solaris 11 and getting error write to 1 failed
If anyone can advise ?
ORIGINAL_PATH="${PATH}"
# prepend /usr/xpg4/bin to PATH as needed
temporaryPath=`expr "${PATH}:" : '\(/usr/xpg4/bin:\)'`
if
then
PATH="/usr/xpg4/bin:${PATH}"
seem to have... (6 Replies)
Discussion started by: Mpumi
6 Replies
LEARN ABOUT DEBIAN
modbus_read_input_registers
MODBUS_READ_INPUT_RE(3) Libmodbus Manual MODBUS_READ_INPUT_RE(3)
NAME
modbus_read_input_registers - read many input registers
SYNOPSIS
int modbus_read_input_registers(modbus_t *ctx, int addr, int nb, uint16_t *dest);
DESCRIPTION
The modbus_read_input_registers() function shall read the content of the nb input registers to address addr of the remote device. The
result of the reading is stored in dest array as word values (16 bits).
You must take care to allocate enough memory to store the results in dest (at least nb * sizeof(uint16_t)).
The function uses the Modbus function code 0x04 (read input registers). The holding registers and input registers have different historical
meaning, but nowadays it's more common to use holding registers only.
RETURN VALUE
The modbus_read_input_registers() function shall return the number of read input registers if successful. Otherwise it shall return -1 and
set errno.
ERRORS
EMBMDATA
Too many bits requested
SEE ALSO
modbus_read_input_bits(3) modbus_write_register(3) modbus_write_registers(3)
AUTHORS
The libmodbus documentation was written by Stephane Raimbault <stephane.raimbault@gmail.com[1]>
NOTES
1. stephane.raimbault@gmail.com
mailto:stephane.raimbault@gmail.com
libmodbus 3.0.3 05/26/2012 MODBUS_READ_INPUT_RE(3)