RE: Timer manipulation in 2.6.13

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Arjan,

Thanks for your reply.

I have created a standalone device and a device driver for it. scullc, to be
specific, from ldd3 source code. Anyways I am sending you the source code as
attachment. This is compilable standalone. You need to do an insmod as
follows:

	insmod scullc
	mknod -m 666 scullc0 <major_no> 0

major_no can be obtained from /proc/devices.

To test we have executed the following command

	cat a_text_file >/tmp/scull0

One observation is that the command runs successfully for the first time but
on the second time it generates OOPS. Is it important to remove the timer
explicitly when it is done with?

Eagerly waiting for your response.

~Abu.

Abu M. Muttalib
Sr. Engineer, Embedded System,
Aftek Infosys Ltd.,
Pune, India
Office: 91-20-25449260-65 X-256
Mobile: (0)9881322820
Email: abum@xxxxxxxxx


-----Original Message-----
From: Arjan van de Ven [mailto:arjan@xxxxxxxxxxxxx]
Sent: Saturday, February 25, 2006 6:27 PM
To: Abu M. Muttalib
Cc: kernelnewbies@xxxxxxxxxxxx
Subject: Re: Timer manipulation in 2.6.13


On Sun, 2006-02-26 at 04:01 +0530, Abu M. Muttalib wrote:
> Hi,
>
> I am using Linux Kernel version 2.6.13.
>
> In one of the processes, I am modifying the timer manually using mod_timer
> function. The system generates an oops inconsistently. The log is as
> follows:

you forgot to attach your source code (and enough of it that it's
compilable stand alone ;)

Attachment: main.c
Description: Binary data

Attachment: Makefile
Description: Binary data

Attachment: scullc.h
Description: Binary data

Attachment: 25feblog-5
Description: Binary data


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux