LWN: Comments on "Porting device drivers to the 2.6 kernel"

Porting device drivers to the 2.6 kernel

卡卡罗特 — Mon, 08 Jun 2020 06:26:08 +0000

Marking for myself.

Update to 2.6.38

coolaj86 — Sun, 30 Jan 2011 17:37:48 +0000

I'm really really interested in seeing the most up-to-date examples. I'm sure a lot has changed since 2003.

I could swing a few subscribers for that privilege. Probably not enough to pay for the cost of time, but a few nonetheless.

char device drivers on the 2.6 kernel

soorejp — Fri, 22 Jun 2007 11:54:57 +0000

I got these warnings:

include/linux/cdev.h:24: warning: struct inode declared inside parameter list
include/linux/cdev.h:24: warning: its scope is only this definition or declaration, which is probably not what you want

I changed the order of header file definition from:
#include <linux/cdev.h>
#include <linux/fs.h>
to
#include <linux/fs.h>
#include <linux/cdev.h>
and the error gone

char device drivers on the 2.6 kernel

hy71 — Fri, 01 Jun 2007 08:09:46 +0000

i am facing the same problem...
could anyone give some suggestion?

thanks a lot!

char device drivers on the 2.6 kernel

psh2001 — Mon, 23 Apr 2007 04:15:58 +0000

Hi,

Any one has any solutions for this ?
even i am facing the same issue ...

Thanks,
Shiv

Porting device drivers to the 2.6 kernel

vonbrand — Wed, 03 May 2006 17:37:15 +0000

Some random comments...

Have you thought of updating the articles (perhaps letting others do the (re)writing)? Some have comments indicating that updates are in order.
What about a cleanup of the comments? Most ones I see here aren't really about the subject matter, and are definitely useless for "longer term reference"...

Many thanks!

Porting device drivers to the 2.6 kernel

vikramkg82 — Wed, 15 Mar 2006 10:29:07 +0000

i am new to device driver can any body tell me how to access the device file...exactly i need to access the harddisk inforamation at block level..or else can u tell where i can get the information about this plz

Porting device drivers to the 2.6 kernel

Pype.Clicker — Tue, 14 Mar 2006 10:43:15 +0000

it looks like the "Big Kernel Lock" headers have been moved from <asm/smplock.h> to <linux/smp_lock.h> between 2.4 and 2.6 ... patching the #include directive did it for me, i guess it will do for you aswell.

Porting device drivers to the 2.6 kernel

agllno — Thu, 23 Feb 2006 15:05:11 +0000

Hi all,
I want a small information about interruptible_sleep_on .I want it to make compatible for kernel version 2.6 from 2.2.So What modification i have to do or any altenatives are there. Please reply and give some details
Thanks in advance
Agnello

Porting device drivers to the 2.6 kernel

York — Tue, 21 Feb 2006 02:33:03 +0000

Dear Jonnathan:
where are the differences between 2.4 and 2.6 about pci driver program?
How can I get the way to port a pci driver in 2.6?

Thank you!

Porting device drivers to the 2.6 kernel

LSM — Sun, 22 Jan 2006 11:39:35 +0000

This is the kind of stuff that made me subscribe to this community. Thanks Jonnathan!

LSM N etwor ks Blog

Porting device drivers to the 2.6 kernel

johnlin — Wed, 17 Aug 2005 03:55:18 +0000

Hello,

I got a problem proting device driver from 2.4 to 2.6, i.e. the asm/smplocak.h seems not in 2.6 kernel/include/asm, so could anyone help ?

Thanks

John

Porting modem drivers to the 2.6 kernel

dabenavidesd — Thu, 11 Aug 2005 04:41:27 +0000

Hi Phil.
A time ago, i tried to install a driver of my Intel 537 EP that is instaled on my ASUS board for AMD.
The driver was made for working on SuSE 9.1. However when trying to install in this OS, and compiling, following the specified steps, I've got 9 warnings.
The modem works perfectly under Windows XP (another company delivers the driver on CD besides the finished Intel chipset and other applications like Classic Phone Tools http://www.bvrp.com).
The driver is still hung in the Intel´s site, and this release supports 2.4.x and 2.6.x kernels.
Attached is my web site where is a historical record of the conversation between me and a support programmer from Intel Support Service; over all, we work in the makefile and correcting the files and dependencies of the used packages, although the trouble is still there.
Im interested in continue working about this kind of troubles. So let me know how can i help.
http://es.geocities.com/dabenavidesd/
email: dabenavidesd@unal.edu.co

Porting PCTel modem driver to the 2.6 kernel

DMXMusic — Wed, 15 Jun 2005 16:59:13 +0000

Here is our situation - we have a working 2.4 driver for the PCTel PCT789T chip/modem. I have been looking high and low for a 2.6 version of this driver, but nobody seems to have taken on the task of porting the driver. I'm wondering if anyone can give me a rough time estimate for porting this driver - (it's basically a serial port driver, the dsp code is in a proprietary lib file) - I have done a couple simple Unix / Linux drivers, and worked on windows display drivers for a couple years, although I have not worked on serial port drivers. Any help is very much appreciated!

Our company has something like 5000 of these modems on our devices in the field, and we need to support our customers.

Thanks - Phil Brooks, Philip.Brooks@DMXMusic.com

swearing in the linux kernel

tomek — Fri, 13 May 2005 14:33:03 +0000

graphs over swearing in the linux kernel: http://www.vidarholen.net/contents/wordcount/ Tom

char device drivers on the 2.6 kernel

prashy — Fri, 06 May 2005 21:56:51 +0000

I am new to Linux Kernel Programming. Trying to build a basic char driver (register, open, release, unregister). When I compile the source I get the following errors, (even on kernel - 2.4). I try to compile the char drivers provided with the source and even get errors and warnings with them, here is the error dump,

prcdd.c:6:1: warning: "__KERNEL__" redefined
prcdd.c:1:1: warning: this is the location of the previous definition
prcdd.c:7:1: warning: "MODULE" redefined
prcdd.c:1:1: warning: this is the location of the previous definition
In file included from /usr/include/linux/fs.h:23,
from prcdd.c:11:
/usr/include/linux/string.h:8:2: warning: #warning Using kernel header in userland!
prcdd.c:12:25: asm/uaccess.h: No such file or directory
prcdd.c:17: warning: `struct file' declared inside parameter list
prcdd.c:17: warning: its scope is only this definition or declaration, which is probably not what you want
prcdd.c:17: warning: `struct inode' declared inside parameter list
prcdd.c:18: warning: `struct file' declared inside parameter list
prcdd.c:18: warning: `struct inode' declared inside parameter list
prcdd.c:26: variable `fops' has initializer but incomplete type
prcdd.c:27: unknown field `owner' specified in initializer
prcdd.c:27: warning: excess elements in struct initializer
prcdd.c:27: warning: (near initialization for `fops')
prcdd.c:28: unknown field `open' specified in initializer
prcdd.c:28: warning: excess elements in struct initializer
prcdd.c:28: warning: (near initialization for `fops')
prcdd.c:29: unknown field `release' specified in initializer
prcdd.c:29: warning: excess elements in struct initializer
prcdd.c:29: warning: (near initialization for `fops')
prcdd.c: In function `prcdd_init':
prcdd.c:34: warning: implicit declaration of function `register_chrdev'
prcdd.c:38: warning: implicit declaration of function `printk'
prcdd.c: In function `prcdd_exit':
prcdd.c:48: warning: implicit declaration of function `unregister_chrdev'
prcdd.c: At top level:
prcdd.c:55: warning: `struct file' declared inside parameter list
prcdd.c:55: warning: `struct inode' declared inside parameter list
prcdd.c:56: conflicting types for `prcdd_open'
prcdd.c:17: previous declaration of `prcdd_open'
prcdd.c: In function `prcdd_open':
prcdd.c:59: `EBUSY' undeclared (first use in this function)
prcdd.c:59: (Each undeclared identifier is reported only once
prcdd.c:59: for each function it appears in.)
prcdd.c:63: warning: implicit declaration of function `atomic_inc'
prcdd.c:63: union has no member named `usecount'
prcdd.c: At top level:
prcdd.c:67: warning: `struct file' declared inside parameter list
prcdd.c:67: warning: `struct inode' declared inside parameter list
prcdd.c:68: conflicting types for `prcdd_release'
prcdd.c:18: previous declaration of `prcdd_release'
prcdd.c: In function `prcdd_release':
prcdd.c:71: warning: implicit declaration of function `atomic_dec'
prcdd.c:71: union has no member named `usecount'
prcdd.c: At top level:
prcdd.c:26: storage size of `fops' isn't known

This is the source code,

#if defined(CONFIG_MODVERSIONS) && ! defined(MODVERSIONS)
#include <linux/modversions.h>
#define MODVERSIONS
#endif

#define _KERNEL_
#define MODULE

#include <linux/kernel.h>
#include <linux/module.h>
#include <linux/fs.h>
#include <asm/uaccess.h>

//static int module_init(void);
//static void module_exit(void);
static int prcdd_open(struct inode *,struct file *);
static int prcdd_release(struct inode *,struct file *);

#define SUCCESS 0
#define DEVICE_NAME "prcdd"

static int Major;
static int Device_open = 0;

static struct file_operations fops = {
.owner = THIS_MODULE,
.open = prcdd_open,
.release = prcdd_release,
};

static int prcdd_init(void)
{
Major = register_chrdev(0,DEVICE_NAME,&fops);
if (Major < 0)
{
printk("Registering the character device failed with %d \n",Major);
return Major;
}

printk("<1>The assigned major number is %d \n",Major);
return 0;
}

static void prcdd_exit(void)
{
int ret = unregister_chrdev(Major,DEVICE_NAME);
if (ret < 0)
{
printk("Error in unregister_chrdev: %d \n",ret);
}
}

static int prcdd_open(struct inode *inode, struct file *file)
{
if (Device_open)
{
return -EBUSY;
}
Device_open++;

MOD_INC_USE_COUNT;
return SUCCESS;
}

static int prcdd_release(struct inode *inode, struct file *file)
{
Device_open--;

MOD_DEC_USE_COUNT;
return 0;
}

module_init(prcdd_init);
module_exit(prcdd_exit);

Any pointers on how to proceed from here?

Porting device drivers to the 2.5 kernel

arafel — Tue, 14 Dec 2004 14:06:42 +0000

Make that two...

Porting device drivers to the 2.6 kernel

prakash07 — Fri, 26 Nov 2004 03:30:34 +0000

I am using the function
alloc_chrdev_region(dev_t *dev,61,1,"prakash");
in module but while compilation it is giving the error.

***parse error before dev_t;

i also added the <linux/fs.h> .
please any one help me .

Porting drivers from kernel 2.4 to kernel 2.6,where can I find the documents

gXyZOd — Mon, 08 Nov 2004 18:49:35 +0000

I'm looking for some information too.
Seeing that devfs is obsolent I would have to port a module that implements a "Utime Calibration" (taken from the Kansas University Real Time patch) from the 2.4.18 to the 2.6.8/9 kernel.
Not using devfs any more in the 2.6 kernel the devfs_[register/unregister]_chrev functions are useless.

I'm a n00b and am trying hard to learn.

Thanks for any response.

Porting drivers from kernel 2.4 to kernel 2.6,where can I find the documents

dkotian — Fri, 29 Oct 2004 03:56:31 +0000

Porting drivers from kernel 2.4 to kernel 2.6,where can I find the documents

Porting device drivers to the 2.6 kernel

Marsclic — Mon, 14 Jun 2004 22:31:49 +0000

This is the material that made me subscribe to this site. Keep it coming Jonnathan!

On whether this stuff should be free

nhasan — Wed, 24 Dec 2003 15:19:45 +0000

How about releasing it as a book? It should provide additional revenue to LWN and give us a hard copy reference.

Porting device drivers to the 2.5 kernel

LogicG8 — Thu, 08 May 2003 17:05:36 +0000

I would just like to say that the release of this material prompted
me to purchase a subscription. It is a delicate balance providing
open content and providing incentive to readers to subscribe. I think
that LWN has done a great job and will continue to do so in the future.

Releasing quality content for free has nabbed at least one
subscriber.

Porting device drivers to the 2.5 kernel

vonbrand — Fri, 28 Feb 2003 20:09:01 +0000

I think this deserves a place in the head of the page (perhaps replacing Old Site or Weekly edition). It is not a "Recent feature" anymore...

One minor gripe is that the articles don't default to a printable page format (yes, I do promise to buy the next book of yours regardless ;-)

An idea that works elsewhere

materlik — Thu, 27 Feb 2003 15:20:03 +0000

You might think about adding a little, polite blurb asking for a small donation to the end of each article, similar to what tidbits (a free Macintosh newsletter) is doing with PayBits. Maybe one only visible to non-subscribers?
Their experiences so far have not been overwhelming, but there is some money being donated because of the constant reminders on the value of filtered, edited information.

On whether this stuff should be free

corbet — Wed, 12 Feb 2003 20:07:33 +0000

Just as a response to all the comments here... I appreciate the input, and certainly do not feel criticized by any of the comments.

For what it's worth, I did consider keeping this material non-free for longer than the usual period. It is different from the usual news, and it has a slightly longer useful life. In the end, I decided against such a move; I would like these articles to be generally useful, and to serve as a contribution to the kernel project. Maintaining the same access policy also lets me fold some of the articles into the Kernel Page, which could use it - development news tends to slow down a lot during feature freezes.

So the driver porting articles go free after a week. We may yet do things differently for similar material in the future.

jon

Re: Porting device drivers to the 2.5 kernel

Ross — Wed, 12 Feb 2003 19:52:38 +0000

Bruno,

I think you are mischaracterizing what other people are saying. Using the device driver documentation as an advertisement was only a suggestion. We all recognize that LWN can decide what to release and when to release it. You're point is also only a suggestion. If Jonathan felt he needed to say something, I'm sure he would. You don't need to speak for him.

Porting device drivers to the 2.5 kernel

rknop — Wed, 12 Feb 2003 17:17:37 +0000

"You MUST give your work for free"... If KotH really thinks that is important that this information be free,

Be fair. That's not what KotH said. He said he thought it was in LWN.net's best interest to do what they've done, because of their good reputation in the community. He's not insisting that they must do what they've done, he's just congratulating them and saying he understands why they might think it's a good idea to do that.

-Rob

Porting device drivers to the 2.5 kernel

bruno — Wed, 12 Feb 2003 15:27:35 +0000

The excellent writing at lwn.net is only possible if there are someone that
works in it full time. I think is wonderfull if someone can (and want) to
work full time in something and give it away for nothing, but I don't think
that you can say to someone "You MUST give your work for free", at the end
of the day, with your work you have the right to make whatever you want:
Give if for free, sell, rent, lease or burn it, is your work and your
decision.

If KotH really thinks that is important that this information be free, he can
study the linux kernel, write a book and put it on the web for free, instead
of criticise the actitude of lwn.net

Porting device drivers to the 2.5 kernel

Webexcess — Wed, 12 Feb 2003 14:14:59 +0000

Do you work for nothing? Do you give all your time to other in exchange of nothing?

I think you're oversimplifying a bit. The excellent writing at lwn.net is both its product and its advertising. How will potential subscribers be enticed if they can't see what lwn.net has to offer?

Also, the target audience largely consists of enthusiasts, many of whom are students and/or live in parts of the world where american dollars are very expensive. These are the same people that helped to build Linux into what it is today -- are you suggesting that they should be excluded?

Porting device drivers to the 2.5 kernel

bruno — Wed, 12 Feb 2003 11:00:43 +0000

Do you work for nothing? Do you give all your time to other in exchange
of nothing? You can't pretend that other people do that, the people have
childrens, wives, mortgages... and work in exchange of money to pay their
bills. Sometimes you have a bussiness plan that lets you to give away
your work and get money from other sources, sometimes you need to put a
price or close the shop.

Porting device drivers to the 2.5 kernel

KotH — Wed, 12 Feb 2003 09:58:23 +0000

I wouldnt do that. LWN has a very good reputation as information source
around the open source community. A "closed for all but subscribed ppl"
policy would surely destroy that reputation.

Yes, i know that LWN doesnt have as much subscribers as it should have :(
but this is IMHO not the right way to get more.

Porting device drivers to the 2.5 kernel

fdesloges — Wed, 12 Feb 2003 01:55:03 +0000

Wow!

This is highly valuable stuff. Are you certain you want to give this away
for free after only a few days ?

This alone would be a very good reason to subscribe. And as reference
stuff it will still be valuable many months down the road.

Maybe it could fit in a "available to non-subsciber 4 months later"
category ? Or make only a few articles available (and the index of course
to hook subscribers) ?

Whatever you do, thanks!

FD