Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-21 Thread Amir Sabbaghi
I think it is only useful to know if kernel is behind or after a specific version. On Tue, Feb 21, 2017 at 9:17 AM, Rafał Miłecki wrote: > On 20 February 2017 at 20:03, Mauro Mozzarelli wrote: >> There is in some cases where kernel drivers have changed.

Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-21 Thread Phyu The
Dear All, My apologies, press wrongly. -Original Message- From: Phyu The Sent: Tuesday, February 21, 2017 5:50 PM To: Jonas Gorski ; Mauro Mozzarelli Cc: LEDE Development List ; Magnus Kroken Subject: Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file) Dear

Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-21 Thread Phyu The
. -Original Message- From: Mauro Mozzarelli Sent: Tuesday, February 21, 2017 3:03 AM To: Jonas Gorski Cc: LEDE Development List ; Magnus Kroken Subject: Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file) Jonas, There is in some cases where kernel drivers have

Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-20 Thread Rafał Miłecki
On 20 February 2017 at 20:03, Mauro Mozzarelli wrote: > There is in some cases where kernel drivers have changed. As you might see > in the ip_vs patch I posted, kernel drivers differ in Kernel 3 and 4 Jonas is correct. Such a change could happen between 3.18 and 3.19 as

Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-20 Thread Jonas Gorski
Hi, please don't top-post. On 20 February 2017 at 20:03, Mauro Mozzarelli wrote: > Jonas, > > > There is in some cases where kernel drivers have changed. As you might see > in the ip_vs patch I posted, kernel drivers differ in Kernel 3 and 4 and > thus it is necessary to

Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-20 Thread Mauro Mozzarelli
Jonas, There is in some cases where kernel drivers have changed. As you might see in the ip_vs patch I posted, kernel drivers differ in Kernel 3 and 4 and thus it is necessary to know which kernel I am building for to select the appropriate kernel configuration. If the granularity requires

Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-20 Thread Jonas Gorski
On 19 February 2017 at 12:50, Mauro Mozzarelli wrote: > Thanks to those who provided directions. > > I will settle with checking on LINUX_3_18. > > I am not sure who manages build variables, but in future it would be useful > to be able to identify which kernel major version

Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-19 Thread Mauro Mozzarelli
Thanks to those who provided directions. I will settle with checking on LINUX_3_18. I am not sure who manages build variables, but in future it would be useful to be able to identify which kernel major version we are building for. Mauro On 18/02/17 20:51, Magnus Kroken wrote: Hi Mauro

Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-18 Thread Magnus Kroken
Hi Mauro On 18.02.2017 12.49, Mauro Mozzarelli wrote: So far with trial and error (unfortunately I could not find specific documentation) I found that I can test reliably a variable that includes both kernel version and patchlevel as follows:

Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-18 Thread Alexandru Ardelean
Hey Mauro, Your case seems a bit specific. But I guess you can try a few things and inspire yourself from include/kernel-version.mk https://github.com/lede-project/source/blob/master/include/kernel-version.mk Not sure if the KERNEL_BASE variable is what you need. i.e. I can't tell what the

[LEDE-DEV] Identifying kernel version (major) during build (.mk file)

2017-02-18 Thread Mauro Mozzarelli
I was wondering someone could help me the following problem: I want to add some device drivers to the kernel build, but the kernel configuration in kernel version 3 is different from the configuration in kernel version 4. I was looking for a parameter that I could use inside an .mk file to