Porting driver module!? From 2.4.19 to 2.5.67

[Diezel]

Now this must be a really dumb quustion but I really intressted in knowing how har it is to "port" a driver thats made for the 2.4.19 kernel to 2.4.20 or maybe even 2.5.67.
I have an C-Media audio chip and i've managed to find drivers for it but unfortunatly they are for the 2.4.19 kernel and I'm using the 2.5.67 kernel(2.4.20 as backup).
So if anyone wants to give any pointers in where to start my quest for glory I would be really really happy
_________________
A bus station is where a bus stops, a train station is where a train stops. On
my desk I have a work station..
Nixadmins.net
FLUG member 473

[ebrostig]

From 2.4.19 to 2.4.20, is just basically a question aboutr recompiling the driver with the correct kernel source.

When moving to 2.5.x series, the best answer I can give is: It depends....

It may be very trivial and it may involve a complete rewrite. It depends on how much the driver relies on features/code/structures/header files that have been changed since the 2.4.x series.

Why don't you go ahead and try to compile it under 2.5.x and see what kind of errors you get, then you can start tracking down the necessary changes.

Erik
_________________
'Yes, Firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'

[narensankar]

The module/driver architecture has changed with the 2.5.xx kernels.
Some of the changes are trivial, but others will take more work.
Detailed instructions for porting drivers can be found at -
http://lwn.net/Articles/driver-porting/

The series is not complete. But it should give you a start. This is written by the guys who wrote Linux Device Drivers which is available from OReilly.

Hope that helps.

Naren