log files :——————————–
>> read :
2 RCS file: dev_read.c,v
3 Working file: dev_read.c
4 head: 1.3
5 branch:
6 locks: strict
7 root: 1.3
8 access list:
9 symbolic names:
10 keyword substitution: kv
11 total revisions: 3; selected revisions: 3
12 description:
13 read module for transfering 7 mb of data over the serial channel using RS-232 protocol.
14 —————————-
15 revision 1.3 locked by: root;
16 date: 2014/11/21 19:28:25; author: root; state: Exp; lines: +0 -2
17 removed debugging symbols.
18 driver in release mode
19 successful implementation of the read module.
20 7 MB of data successfully received.
21
22
23 The reader has no way of knowing when the writer will stop sending data, thus to overcome this the application on the
24 DCE end is to know(explicitly) how musch data is to be send by the DTE.
25 —————————-
26 revision 1.2
27 date: 2014/11/21 19:26:21; author: root; state: Exp; lines: +2 -18
28 successfully implemented the reader module for the DCE.
29 able to receive 7MB of data.
30 time taken to transfer 7MB is 13 minutes.

——————————————————–
>> write :

2 RCS file: dev_write.c,v
3 Working file: dev_write.c
4 head: 1.3
5 branch:
6 locks: strict
7 access list:
8 symbolic names:
9 keyword substitution: kv
10 total revisions: 3; selected revisions: 3
11 description:
12 Sending a file of 7 mb on a serial channel, using the RS 232 protocol.
13 —————————-
14 revision 1.3
15 date: 2014/11/21 19:21:46; author: root; state: Exp; lines: +1 -7
16 Removed the comments.
17 write module ready for release.
18 —————————-
19 revision 1.2
20 date: 2014/11/21 19:15:27; author: root; state: Exp; lines: +3 -5
21 Implemented hand shaking between the DTE and DCE.
22 DTE has a circular buffer (max size of buffer = 4k bytes).
23 —————————-

Following are the RCS files and code snippet of the project :

1. intialization module :
RCS file: ./initialization.c,v
Working file: initialization.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
IEEE Std. 1284-1994
Standard Signalling method for a Bi-directional parallel peripheral Interface for personal computer.
IC : 74LS244
Mode : Nibble Mode
Module Info : initialization
This module is responsible for :
- creating scull for the device.
- allocating required address for the driver to work.
- add driver to kernel tree.
—————————-
revision 1.2 locked by: root;
date: 2014/11/03 06:38:42; author: root; state: Exp; lines: +0 -8
Successfully allocated memory to the device scull.
requested and acquired the required address space i.e. 0×0378 – 0x037a
0×0378 for data lines.
0×0379 for status lines.
0x037a for control lines.
—————————-
Code Snippet :
tatic int __init initialization_function(void){
/* the name of the driver which you want your driver to be visible */
const char *name = “character_device_latest”;
int ret, i;
printk(KERN_ALERT”%s : Begin”, __func__);

/* checking and acquiring region for parallel port*/
ret = check_region(START, RANGE);
if(ret >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2. write module :
RCS file: ./dev_write.c,v
Working file: dev_write.c
head: 1.3
branch:
locks: strict
root: 1.3
access list:
symbolic names:
keyword substitution: kv
total revisions: 3; selected revisions: 3
description:
Module : the module implements the protocol for sending a byte of data in two nibbles.
The module implements the protocol in the following manner :
1. reset the data and control lines.
2. write data to data lines.
3. check the busy status of the device by polling.
4. if device is free send strobe signal.
5. wait for acknowledgement corresponding the first nibble.
6. repeat steps 2-6 for sending the second nibble.
—————————-
revision 1.3 locked by: root;
date: 2014/11/03 07:15:13; author: root; state: Exp; lines: +0 -7
the writer performs the following operations successfully following the protocol for nibble mode.
1. read data to be sent from user application.
2. write first nibble to data lines.
3. get acknowledgement for first nibble and then send the second nibble
4. wait for acknowledgement of second nibble.
—————————-
Code Snippet :
int protocol(const char __user* buffer){
unsigned char temp;
volatile unsigned char busy;
volatile unsigned char ack;
struct nibble n;

/* remove garbage content from the control and data lines */
outb(0×0000, CTRL_REG);
outb(0×0000, DATA_REG);

/* prepare the first nibble to be sent */
temp = buffer[0];
printk(KERN_INFO”data to be sent to the reader = %d\n”, temp);
n.val = temp;
printk(KERN_INFO”nibble 1 to be sent to the reader = %d\n”, n.val);
outb(n.val, DATA_REG);
/* check the busy status of the device */
do{
busy = inb(STATUS_REG);
busy = busy & 0×0080;
}while(busy!=0×0080);
printk(“Device free\n”);
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
3. read module :
RCS file: ./dev_read.c,v
Working file: dev_read.c
head: 1.3
branch:
locks: strict
root: 1.3
access list:
symbolic names:
keyword substitution: kv
total revisions: 3; selected revisions: 3
description:
this module implements the protocol for receiving the data on the reader side.
protocol implemented for Nibble mode.
—————————-
revision 1.3 locked by: root;
date: 2014/11/03 07:12:53; author: root; state: Exp; lines: +1 -0
the reader correctly reads a byte of data as sent by the writer.
—————————-
revision 1.2
date: 2014/11/03 07:09:30; author: root; state: Exp; lines: +14 -14
corrected the error in reading the value from the status register.
——————————
Code Snippet :
ssize_t dev_read(struct file *filep, char __user *ubuff, size_t size, loff_t *loff)
{
volatile unsigned char strobe;
unsigned char data;
unsigned char temp;
printk(KERN_INFO”BEGIN %s\n”, __func__);

/* reset the data and control lines and update the busy status to free. */
outb(0×0000, CTRL_REG);
outb(0×0001, CTRL_REG);
outb(0×0000, DATA_REG);

/* wait on strobe value = 1, first nibble */
do{
strobe = inb(STATUS_REG);
strobe = strobe & 0×0080;
}while(strobe!=0×0080);
printk(KERN_INFO”Got strobe signal from the writer = %d\n”, strobe);

outb(0×0000, CTRL_REG); // make device appear busy to reader

// read the first nibble
temp = inb(STATUS_REG);
printk(KERN_INFO” inb, temp = %d\n”, temp);
temp = temp & 0×0078;
temp = temp >>3;
printk(KERN_INFO”temp after masking= %d\n”, temp);
printk(KERN_INFO”Data received (nibble – 1)= %d\n”, temp);

RCS file: ./initialization.c,v
Working file: initialization.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
Initialization file for Centronics port driver based on IEEE-1284 standard.
—————————-
revision 1.4 locked by: root;
date: 2014/11/01 04:44:07; author: root; state: Exp; lines: +0 -4
Successfully implemented the following operations :
1. Acquire the address 0×0378 – 0x037a for the device.
2. Create the device scull.
3. Initialise the cdev structure..
4. Add the device to the kernel tree.
—————————-
revision 1.3
date: 2014/10/31 15:19:12; author: root; state: Exp; lines: +0 -40
Successfully created the scull for the device.
—————————-
revision 1.2
date: 2014/10/31 15:16:36; author: root; state: Exp; lines: +1 -0
Released the region acquired by the default parallel port driver.
Acquired the same space for own driver.
Entry successfully created in /proc/ioports.
—————————-
revision 1.1
date: 2014/10/31 15:16:07; author: root; state: Exp;
Initial revision
=============================================================================

2. cleanup module for device :

RCS file: ./cleanup.c,v
Working file: cleanup.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
Cleanup module for deriver
—————————-
revision 1.4 locked by: root;
date: 2014/11/01 04:59:28; author: root; state: Exp; lines: +0 -1
The module successfully performs the following functions :
1. Unregister the driver.
2. Release the address space acquired i.e. 0×378 – 0x37a
—————————-
revision 1.3
date: 2014/11/01 04:57:56; author: root; state: Exp; lines: +0 -1
Able to release the acquired range successfully.
The driver releases the 0×0378-0x037a address space on rmmod.
Entry removed from the /proc/ioports file.
—————————-
revision 1.2
date: 2014/11/01 04:56:34; author: root; state: Exp; lines: +0 -2
Successfully unregistered the driver on rmmod.
—————————-
revision 1.1
date: 2014/11/01 04:56:15; author: root; state: Exp;
Initial revision
=============================================================================

3. write module :

RCS file: ./dev_write.c,v
Working file: dev_write.c
head: 1.5
branch:
locks: strict
root: 1.5
access list:
symbolic names:
keyword substitution: kv
total revisions: 5; selected revisions: 5
description:
dev_write.c : runs when user space application writes the node.
module implements the protocol under Compatability mode.
—————————-
revision 1.5 locked by: root;
date: 2014/10/31 16:56:12; author: root; state: Exp; lines: +0 -1
The writer is able to perform the following :
1. Take the data from the user application.
2. Write the data to the port.
3. Check busy status of the device at the other end of the cable.
4. Send strobe.
—————————-
revision 1.4
date: 2014/10/31 16:53:29; author: root; state: Exp; lines: +1 -0
Implemented the protocol in 3 steps.
wddl : write data to data lines.
cbs : check busy status of the device, keep pollng until the device is found free.
sss : once the device is found free send the strobe signal to indicate that the data on data lines is valid content.
—————————-
revision 1.3
date: 2014/10/31 15:33:36; author: root; state: Exp; lines: +0 -59
Able to send a single byte of data.
Protocol successfully implemented.
Acknowledgement from device has not been used.
Some problem with the hardware.
—————————-
revision 1.2
date: 2014/10/31 15:32:12; author: root; state: Exp; lines: +2 -0
able to send the data successfully without any protocol.
—————————-
revision 1.1
date: 2014/10/31 15:31:39; author: root; state: Exp;
Initial revision
=============================================================================

4. read module :

RCS file: ./dev_read.c,v
Working file: dev_read.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
dev_read : module runs when an application tries to read from the node.
Implements compatability mode for data transfer between two systems.
—————————-
revision 1.2 locked by: root;
date: 2014/10/31 16:44:09; author: root; state: Exp; lines: +1 -0
Successfully implemented the protocol.
The device sends the busy status.
Waits for strobe.
Once strobe arrives, reads data.
Sends the data to the user application by copy_to_user.
—————————-
revision 1.1
date: 2014/10/31 16:42:58; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: dev_open.c,v
3 Working file: dev_open.c
4 head: 1.1
5 branch:
6 locks: strict
7 root: 1.1
8 access list:
9 symbolic names:
10 keyword substitution: kv
11 total revisions: 1; selected revisions: 1
12 description:
13 Implements the underline mechanism of what happens when a file is opened by user space process
14 —————————-
15 revision 1.1 locked by: root;
16 date: 2014/10/09 18:39:19; author: root; state: Exp;
17 Initial revision
18 ===================================================

CS file: dev_write.c,v
3 Working file: dev_write.c
4 head: 1.6
5 branch:
6 locks: strict
7 root: 1.6
8 access list:
9 symbolic names:
10 keyword substitution: kv
11 total revisions: 6; selected revisions: 6
12 description:
13 dev_write implementation for character driver.
14 Implements the routine needed to write in driver space using an application.
15 —————————-
16 revision 1.6 locked by: root;
17 date: 2014/10/11 18:48:38; author: root; state: Exp; lines: +5 -6
18 added comments
19 —————————-
20 revision 1.5
21 date: 2014/10/11 18:41:19; author: root; state: Exp; lines: +2 -5
22 Added some debugging messages.
23 —————————-
24 revision 1.4
25 date: 2014/10/11 18:33:21; author: root; state: Exp; lines: +87 -12
26 Successfully implemented the copy_to_user routine.
27 The user application successfully writes the data inside sculldev.
28 correctly returning the amount of data written.
29 —————————-
30 revision 1.3
31 date: 2014/10/09 19:47:57; author: root; state: Exp; lines: +62 -1
32 Successfully created the required number of quantums and qsets.

RCS file: cleanup.c,v
3 Working file: cleanup.c
4 head: 1.3
5 branch:
6 locks: strict
7 root: 1.3
8 access list:
9 symbolic names:
10 keyword substitution: kv
11 total revisions: 3; selected revisions: 3
12 description:
13 Char driver cleanup file..
14 —————————-
15 revision 1.3 locked by: root;
16 date: 2014/10/11 18:33:10; author: root; state: Exp; lines: +2 -1
17 Removed the proc_remove code.
18 —————————-
19 revision 1.2
20 date: 2014/10/09 17:19:43; author: root; state: Exp; lines: +10 -1
21 added code to remove proc entry and unregister driver.
22 Upto this, driver registration, proc file, and unregister work fine.
23 —————————-

1
2 RCS file: server.c,v
3 Working file: server.c
4 head: 1.5
5 branch:
6 locks: strict
7 root: 1.5
8 access list:
9 symbolic names:
10 keyword substitution: kv
11 total revisions: 5; selected revisions: 5
12 description:
13 Implementing ftp server under AF_INET family.
14 —————————-
15 revision 1.5 locked by: root;
16 date: 2014/09/29 20:33:26; author: root; state: Exp; lines: +0 -1
17 Removed the statement that printed the number of bytes written by the server.
18 —————————-
19 revision 1.4
20 date: 2014/09/29 20:23:53; author: root; state: Exp; lines: +143 -29
21 Successfully implemented the ftp server.
22 The server successfully responds to the client requests.
23 File sending successful.
24 No issues as of now w.r.t. to functionality of the server.
25 —————————-
26 revision 1.3
27 date: 2014/09/29 11:42:01; author: root; state: Exp; lines: +59 -28
28 The server threads for individual clients behave properly, i.e. even if a client quits the server continues execution.
29 —————————-
30 revision 1.2
31 date: 2014/09/29 10:25:56; author: root; state: Exp; lines: +30 -8
32 Implemented the following functionality.
“server_log_file” 42L, 1587C 25,1 Top