EmbLogic » saurabh2015ece

character driver till ioctl.

saurabh2015ece — Sun, 15 Jun 2014 21:20:35 +0000

This is rcs file of init function where this function helps in initialisation of our driver and

file operations .

file operations which are used further to mapped various function to the kernel mode function.

similarly there is open function , read function ,lseek function , ioctl function .

(these all are different from generic open ,read function).

RCS file: init.c,v
Working file: init.c
head: 1.58
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 58; selected revisions: 58
description:
inserting our msg in kernel table list.
—————————-
revision 1.58
date: 2014/06/15 08:00:09; author: root; state: Exp; lines: +8 -1
mapped ioctl function with unlocked ioctl in file operations .
used module param for taking the device size and quantum_size through command line argument i.e argument during run time .
—————————-
revision 1.57
date: 2014/06/13 11:20:08; author: root; state: Exp; lines: +3 -2
*** empty log message ***
—————————-
revision 1.56
date: 2014/05/27 09:12:07; author: root; state: Exp; lines: +3 -1
fileoperations updated .
added function for llseek.
nd mapped with that function.
—————————-
revision 1.55
date: 2014/05/19 07:23:22; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.54
date: 2014/05/18 19:38:37; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.53
date: 2014/05/15 15:31:37; author: root; state: Exp; lines: +2 -1
*** empty log message ***
—————————-
revision 1.52
date: 2014/05/15 09:09:59; author: root; state: Exp; lines: +0 -1
*** empty log message ***
—————————-
revision 1.51
date: 2014/05/15 09:08:24; author: root; state: Exp; lines: +2 -1
*** empty log message ***
—————————-
revision 1.50
date: 2014/05/15 08:28:40; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.49
date: 2014/05/11 08:55:50; author: root; state: Exp; lines: +0 -1
*** empty log message ***
—————————-
revision 1.48
date: 2014/05/11 08:51:00; author: root; state: Exp; lines: +2 -2
added open nd close function nd mapped with generic call function
—————————-
revision 1.47
date: 2014/05/11 08:15:27; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.46
date: 2014/05/11 08:14:01; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.45
date: 2014/05/11 08:13:07; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.44
date: 2014/05/11 08:11:01; author: root; state: Exp; lines: +4 -5
just checking if the mapping of fops is done correctly or not.
by checking the value it from dev of cdev.
—————————-
revision 1.43
date: 2014/05/09 10:41:03; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.42
date: 2014/05/09 09:29:46; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.41
date: 2014/05/09 06:52:11; author: root; state: Exp; lines: +0 -1
*** empty log message ***
—————————-
revision 1.40
date: 2014/05/09 06:51:16; author: root; state: Exp; lines: +8 -10
*** empty log message ***
—————————-
revision 1.39
date: 2014/05/07 13:16:58; author: root; state: Exp; lines: +4 -4
solved the syntax errors.
—————————-
revision 1.38
date: 2014/05/07 12:56:32; author: root; state: Exp; lines: +10 -2
defined the structure for sculldev
defined the structure scull c_dev .
used cdev_init to make internally mapping…just it initliase the cdev_ onto kernel
—————————-
revision 1.37
date: 2014/05/05 14:55:51; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.36
date: 2014/05/05 14:54:53; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.35
date: 2014/05/05 14:52:44; author: root; state: Exp; lines: +1 -0
printing the size of structure that we have already allocated for cdev in scull dev
—————————-
revision 1.34
date: 2014/05/05 10:07:36; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.33
date: 2014/05/05 09:40:43; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.32
date: 2014/05/05 09:37:55; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.31
date: 2014/05/05 09:36:40; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.30
date: 2014/05/05 09:33:52; author: root; state: Exp; lines: +2 -0
assigned the memory for struct scull .
further it can hold the memory for virtual devices.
—————————-
revision 1.29
date: 2014/05/04 09:37:28; author: root; state: Exp; lines: +1 -1
moved the position of dev1
—————————-
revision 1.28
date: 2014/05/04 09:35:27; author: root; state: Exp; lines: +6 -4
*** empty log message ***
—————————-
revision 1.27
date: 2014/05/04 09:24:48; author: root; state: Exp; lines: +1 -1
changed the value of i so that no repititon ocur
occur
—————————-
revision 1.26
date: 2014/05/04 09:19:16; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.25
date: 2014/05/04 09:17:53; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.24
date: 2014/05/04 09:16:27; author: root; state: Exp; lines: +4 -2
*** empty log message ***
—————————-
revision 1.23
date: 2014/05/04 08:56:59; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.22
date: 2014/05/04 08:54:17; author: root; state: Exp; lines: +1 -0
defined header file
—————————-
revision 1.21
date: 2014/05/04 08:47:22; author: root; state: Exp; lines: +1 -1
warning problem solved
/
—————————-
revision 1.20
date: 2014/05/04 08:45:10; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.19
date: 2014/05/04 08:37:38; author: root; state: Exp; lines: +1 -0
created n no. of arrays ….basicallly n no. of nodes that will linked to one driver.
—————————-
revision 1.18
date: 2014/05/04 08:16:36; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.17
date: 2014/05/04 07:58:45; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.16
date: 2014/05/04 07:56:26; author: root; state: Exp; lines: +4 -2
taking nod value 3
—————————-
revision 1.15
date: 2014/05/04 07:05:22; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.14
date: 2014/05/04 07:03:20; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.13
date: 2014/05/04 06:56:04; author: root; state: Exp; lines: +4 -1
now giving a nod no. using command line argument
using module_param
—————————-
revision 1.12
date: 2014/05/04 06:44:42; author: root; state: Exp; lines: +1 -2
registerd the driver.
nd its working
—————————-
revision 1.11
date: 2014/05/04 06:32:03; author: root; state: Exp; lines: +2 -1
*** empty log message ***
—————————-
revision 1.10
date: 2014/05/03 17:18:29; author: root; state: Exp; lines: +7 -6
updated included #ifdef
..
—————————-
revision 1.9
date: 2014/04/30 14:07:00; author: root; state: Exp; lines: +5 -4
removed def micro
—————————-
revision 1.8
date: 2014/04/30 08:07:57; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.7
date: 2014/04/29 17:33:46; author: root; state: Exp; lines: +2 -1
*** empty log message ***
—————————-
revision 1.6
date: 2014/04/29 17:04:29; author: root; state: Exp; lines: +17 -0
new character driver can be allocated in kernel using alloc_chrdev_region();

nd same we allocated our own driver .
—————————-
revision 1.5
date: 2014/04/28 15:04:01; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.4
date: 2014/04/28 14:59:33; author: root; state: Exp; lines: +0 -19
just checking , is mesg get printed in kernel table or not!
—————————-
revision 1.3
date: 2014/04/28 08:25:55; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.2
date: 2014/04/28 08:20:38; author: root; state: Exp; lines: +1 -1
upadated
—————————-
revision 1.1
date: 2014/04/28 08:14:39; author: root; state: Exp;
Initial revision
===========================================================================

A Chat BOx (full duplexer)

saurabh2015ece — Wed, 14 May 2014 09:08:20 +0000

RCS file: user1.c,v
Working file: user1.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
this is mainly a chat box btween two users ,a full duplexer one
each user can simultaneously recieve or can send the msg
for this to be happened we used mesaagequeue which helps in holding the messages .
nd its dual processor that mean user one can both recieve or can send the msg to another user at a same time
this to be happened we need multithread concept
moving back to this project use 1 can both recieve or can send msgs at a same time .
as soon user 1 typed “end” then it will ask user 2 to type same end string after that session gets terminated.
—————————-
revision 1.1 locked by: root;
date: 2014/05/14 08:32:37; author: root; state: Exp;
Initial revision
=============================================================================

ipc-

saurabh2015ece — Thu, 27 Mar 2014 11:29:30 +0000

Inter Process Communication-synchronised by semaphore

saurabh2015ece — Thu, 27 Mar 2014 11:23:11 +0000

RCS file: server.c,v
Working file: server.c
head: 1.3
branch:
locks: strict
saurabh: 1.3
access list:
symbolic names:
keyword substitution: kv
total revisions: 3; selected revisions: 3
description:
here we are doing a project called ipc ,we have taken a server where three clients simultaneously sending their request over a single fifo.
That mean three clients respectively will send their request to server on a same fifo at a same time ….thus a concept of semaphore arises
this helps in seperating the one client req from others or from being messy!!!! we used semaphore ….
one client request is send over fifo one at a tym.
—————————-basically it synchronised the data coming to server…..
revision 1.3 locked by: saurabh;
date: 2014/03/27 11:12:28; author: saurabh; state: Exp; lines: +10 -0
server has passed the result accurately to all requesting clients.
finally it works
—————————-
revision 1.2
date: 2014/03/26 19:30:52; author: saurabh; state: Exp; lines: +17 -8
updated
—————————-
revision 1.1
date: 2014/03/26 17:50:36; author: saurabh; state: Exp;
Initial revision

Cross compiler

saurabh2015ece — Wed, 26 Mar 2014 05:35:01 +0000

Introduction to Cross Compilation

This post is the first in a series on cross compilation. In this series I’ll introduce the concept of cross compilation, and how to used it. Although there are many different uses for cross compilation, I’ll focus in this series in its use for embedded Linux systems development.

What is Cross Compilation?

When you develop a desktop or server application, almost always the development platform (the machine that runs your compiler) and the target platform (the machine that runs your application) are the same. By “platform” I mean the combination of CPU architecture, and Operating System. The process of building executable binaries on one machine, and run them on another machine when the CPU architecture or the Operating System are different is called “cross compilation”. A special compiler is needed for doing cross compilation that is called “cross compiler“, and sometimes just “toolchain”.

For example, desktop PC application developers for Windows or Linux can build and run their binaries on the very same machine. Even developers of server applications generally have the same basic architecture and Operating System on both their development machine and server machine. The compiler used in these cases is called “native compiler”.

On the other hand, developers of an embedded Linux application that runs on a non PC architecture (like ARM, PowerPC, MIPS, etc.) tend to use a cross compiler to generate executable binaries from source code. The cross compiler must be specifically tailored for doing cross compilation from the development machine’s architecture (sometimes called “host”), to the embedded machine’s architecture (called “target”).

Note: cross compilation is only needed when generating binary executables from source code written in a compiled language, like C or C++. Programs written in interpreted language, like Perl, Python, PHP, or JavaScript, do not need a cross compiler. In most cases interpreted programs should be able run unchanged on any target. You do need, however, a suitable interpreter running on the target machine.

What is Cross Compilation Good for?

I have covered above one reason for doing cross compilation, that is, the target machine has a different CPU architecture that the development host. In this case cross compilation is necessary because the binaries that the native compiler generates won’t run on the target embedded machine.

Sometimes cross compilation is not strictly necessary, but native compilation in not practical, or inconvenient. Consider, for example, a slow ARM9 based target machine running Linux. Having the compiler run on this target will make the build process painfully slow. In many cases target machine is just under-powered, in terms of storage and RAM, for the task of running a modern compiler.

Practically speaking, almost all embedded Linux development is being done with cross compilers. Strong PC workstation machines are used as development hosts to run the development environment (text editor, IDE), and the cross compiler.

In the next post in this series I’ll show how get a cross compiler for embedded Linux development.

linklist implementation using functions.

saurabh2015ece — Fri, 28 Feb 2014 14:33:37 +0000

RCS file: lll.c,v
Working file: lll.c
head: 1.8
branch:
locks: strict
saurabh: 1.8
access list:
symbolic names:
keyword substitution: kv
total revisions: 8; selected revisions: 8
description:
created a linklist program where diff aspects are being done.
first created new linklist
second add a new node to the linklist which is already been created.
so far a new node in inserted from the begining
and from the end .

—————————-
revision 1.8 locked by: saurabh;
date: 2014/02/28 14:16:42; author: saurabh; state: Exp; lines: +3 -4
sorting function working properly
insertion at nth node is working well.
while deletion at the nth node is too working well
—————————-
revision 1.7
date: 2014/02/28 13:49:08; author: saurabh; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.6
date: 2014/02/28 13:46:44; author: saurabh; state: Exp; lines: +1 -1
problem in function insert at nth solved .
—————————-
revision 1.5
date: 2014/02/28 13:42:50; author: saurabh; state: Exp; lines: +33 -15
function called sort_ has been implemented in program .
but there are some problem in function “insert_nth”.
will solve later on
—————————-
revision 1.4
date: 2014/02/27 20:03:10; author: saurabh; state: Exp; lines: +26 -2
sorting not working
—————————-
revision 1.3
date: 2014/02/27 19:10:54; author: saurabh; state: Exp; lines: +19 -3
implemented function called deletition from end .

—————————-
revision 1.2
date: 2014/02/27 18:17:33; author: saurabh; state: Exp; lines: +159 -30
created function called insertion at the end
created function insertion at the nth node
created function deletion
implemented all above function the are working well
implemented deletion from begining node using function
implemented deletion from the nth node successflly
prior to all such functions ,defined display function too .

—————————-
revision 1.1
date: 2014/02/24 21:09:57; author: saurabh; state: Exp;
Initial revision
=============================================================================

project-1 multiple data compression & encryption using iterative techniques.

saurabh2015ece — Fri, 28 Feb 2014 10:31:13 +0000

RCS file: fun.c,v
Working file: fun.c
head: 1.9
branch:
locks: strict
saurabh: 1.9
access list:
symbolic names:
keyword substitution: kv
total revisions: 9; selected revisions: 9
description:
this is updated file of fun.c of project 1 dir.
here master array is passed in every fnction instead of declaring globally
which could create protection problem.
—————————-
revision 1.9 locked by: saurabh;
date: 2014/02/27 20:06:16; author: saurabh; state: Exp; lines: +3 -1
updated
—————————-
revision 1.8
date: 2014/02/26 21:47:06; author: saurabh; state: Exp; lines: +10 -6
updated ,errors solved
—————————-
revision 1.7
date: 2014/02/26 15:09:06; author: saurabh; state: Exp; lines: +14 -55
updated

but not working well :/
—————————-
revision 1.6
date: 2014/02/26 14:06:59; author: saurabh; state: Exp; lines: +6 -7
error
—————————-
but not working well :/
—————————-
revision 1.6
date: 2014/02/26 14:06:59; author: saurabh; state: Exp; lines: +6 -7
error

—————————-
revision 1.5
date: 2014/02/26 12:53:27; author: saurabh; state: Exp; lines: +58 -4
created a decompressed function
where the file is decrypted back to orignal file using decompression_key addition to encryption_key

—————————-
revision 1.4
date: 2014/02/26 09:49:56; author: saurabh; state: Exp; lines: +12 -3
logical fault solved
previously marray ws compressed
but actually we want to compressed whole text file
so that it cud be retrieve easily

—————————-
revision 1.3
date: 2014/02/26 06:38:48; author: saurabh; state: Exp; lines: +20 -0
created a function encryption_ky
holding a file consisting a master array.
—————————-
revision 1.2
date: 2014/02/24 16:59:13; author: saurabh; state: Exp; lines: +6 -14
warning issue solved
updated some other display issues.
—————————-
revision 1.1
date: 2014/02/24 16:41:32; author: saurabh; state: Exp;
Initial revision
=============================================================================
62,17 Bot
10,14 Top