Migrating driver from stock kernel to vanilla kernel

Submitted by serefarikan
on February 10, 2005 - 11:04am

Ok, this is a problem i've asked in many forums and lists, and so far, i have not recieved a single response. Maybe it's my fault that i could not ask my question in a proper way, but i'll give it a try again.
ı have a notebook with suse 9.0 installed, and suse 9.0 comes with kernel 2.4.21-99. The notebook includes an AMD athlon mobile processor, and it's possible to use cpu scaling by using powernow drivers. Powernow drivers are included in 2.4.21-99 and (after a little patching because of a bios bug) they work fine. However, i want to be able to use vanilla kernels, and for 2.6 series switching between stock and vanilla kernels did not create any problems for me. 2.4 kernel on the other hand, does not include powernow drivers.
so i'm trying to carry powernow drivers from suse kernel to vanilla kernel. This is the only option i could think of (please don't tell me to upgrade to 2.6), since my firewire only seems to work with 2.4.
So what should i do to carry powernow drivers from suse kernel to 2.4.29 vanilla kernel ? If i could find powernow modules in a suitable format, everything would be fine, but i could not. I'm really out of hope since i could not find anything about this. I've tried to move files, but i've got compilation errors . So, anyone around to lead me to any clues ?
Best Regards
Seref Arikan

backports

Anonymous (not verified)
on
February 10, 2005 - 2:42pm

well I don't know much about suse's way... but AFAIK RedHat have two different types of kernel-sources (so suse maybe also) ... one (kernel-source...rpm ( already patched tree) the other ONEs (kernel*.src.rpm a packed vanilla tree + PATCHES (simple diffs, which could "patch -p1" against vanilla)... so maybe it also work for you... (anyway: what's the problem with firewire in 2.6? maybe you should ask the Maintainer what the problem could be... )

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.