The strange part is that your 2.6.39 dir returns 3.0.36 kernel version ..!?
> /lib/modules/2.6.39-300.17.1.el6uek.x86_64/build/Makefile:VERSION = 3
> /lib/modules/2.6.39-300.17.1.el6uek.x86_64/build/Makefile:PATCHLEVEL = 0
> /lib/modules/2.6.39-300.17.1.el6uek.x86_64/build/Makefile:SUBLEVEL = 36
>
On Tue, Mar 11, 2014 at 11:09 PM, Yann Droneaud wrote:
> Le mardi 11 mars 2014 à 22:42 +0530, Saket Sinha a écrit :
>> Please find my response inline
>>
>> >> I have a scenario where I need to build a driver for
>> >> different kernel versions.
>> >> I have kernel-headers of different ver
Le mardi 11 mars 2014 à 22:42 +0530, Saket Sinha a écrit :
> Please find my response inline
>
> >> I have a scenario where I need to build a driver for
> >> different kernel versions.
> >> I have kernel-headers of different version in /lib/modules/
> >> 2.6.32-
> >> 2.6.39-
> >>
>
Please find my response inline
>> I have a scenario where I need to build a driver for
>> different kernel versions.
>> I have kernel-headers of different version in /lib/modules/
>> 2.6.32-
>> 2.6.39-
>>
>> and currently I am booted into 2.6.32-(which I find out by uname -r)
Hi,
Le mardi 11 mars 2014 à 21:16 +0530, Saket Sinha a écrit :
>
> I have a scenario where I need to build a driver for
> different kernel versions.
> I have kernel-headers of different version in /lib/modules/
> 2.6.32-
> 2.6.39-
>
> and currently I am booted into 2.6.32-(w
Hi,
I have a scenario where I need to build a driver for
different kernel versions.
I have kernel-headers of different version in /lib/modules/
2.6.32-
2.6.39-
and currently I am booted into 2.6.32-(which I find out by uname -r)
Now in my driver makefile, I generate .ko of d
