From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Paramahamsa, Viplav" <Viplav.Paramaham@slingmedia.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Cc: "Raikar, Yatish" <yatishjnr@slingmedia.com>
Subject: Re: Backports - v3.18-rc1 build problems
Date: Tue, 28 Oct 2014 23:00:35 +0100 [thread overview]
Message-ID: <54501203.1090900@hauke-m.de> (raw)
In-Reply-To: <65B68BAF3C31D54B9A10B0592C9E025B9050F9B2@CHWPIEXC10.SATS.CORP>
Hi Viplav,
On 10/28/2014 10:02 AM, Paramahamsa, Viplav wrote:
> Hi Hauke,
> I am actually trying to find a driver for vendor ID : 625, product ID : 1026 & firmware 3.0 for linux kernel version - 2.6.35.
> Backports-3.14.22-1 & earlier releases doesn't support this product ID. Backports - v3.18-rc1 seem to have the support for the device but doesn't seem to be building for 2.6.35.
What device/chip are you talking about and what driver do you want to use?
> Is there a plan to support this kernel version for this device?
Currently there is no plan to add compatibility for kernel versions
older than 3.0 from my side, someone else planed to add support for
older kernel versions for B.A.T.M.A.N. Advanced, but I do not think this
will automatically cover your device driver.
> Is there any restrictions or compatibility issues on 2.6.x kernels to support this device?
We removed support for older kernel versions because we did not have the
recourses to support compatibility with so many kernel versions,
technically it should be possible to add support for kernel 3.6.25 again.
Hauke
> -----Original Message-----
> From: Hauke Mehrtens [mailto:hauke@hauke-m.de]
> Sent: Tuesday, October 28, 2014 2:12 PM
> To: Paramahamsa, Viplav; backports@vger.kernel.org
> Cc: Raikar, Yatish
> Subject: Re: Backports - v3.18-rc1 build problems
>
> On 10/27/2014 02:39 PM, Paramahamsa, Viplav wrote:
>> Hi All,
>> I am facing build problems with latest release of backports - v3.18-rc1.
>>
>> I am trying to cross compile with Freescale's LTIB. These are the details of the platform on which I am trying to build:
>> Linux kernel version : 2.6.35
>> ARCH : ARM
>> Freescale BSP : L2.6.35_1.1.0_130130
>>
>> This is the build command I am using : make
>> CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib
>> -1.0/arm-fsl-linux-gnueabi/bin/arm-none-linux-gnueabi- ARCH=arm KLIB=
>> ${TOP}/rootfs/lib/modules/2.6.35.3-571-gcca29a0/ KLIB_BUILD=
>> ${TOP}/rpm/BUILD/linux/
>>
>> PFA file which has compilation errors I am getting.
>> I tried fixing these. But I was getting more errors in compat-3.x.x.c file compilation.
>>
>> I am able to successfully compile an older version of backports - 3.10.17.
>>
>> Please suggest how can I fix these errors. Is there any patch I need to apply to get rid of these? If yes, can you please provide the link for the same.
>>
>> Regards,
>> Viplav
>>
>
> Hi Viplav,
>
> starting with backports-3.15 we only support kernel versions >= 3.0. For kernel 3.6.35 you should try bcackports-3.14.22-1.
>
> Hauke
>
next prev parent reply other threads:[~2014-10-28 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 13:39 Backports - v3.18-rc1 build problems Paramahamsa, Viplav
2014-10-28 8:41 ` Hauke Mehrtens
2014-10-28 9:02 ` Paramahamsa, Viplav
2014-10-28 22:00 ` Hauke Mehrtens [this message]
2014-10-29 6:08 ` Paramahamsa, Viplav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54501203.1090900@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=Viplav.Paramaham@slingmedia.com \
--cc=backports@vger.kernel.org \
--cc=yatishjnr@slingmedia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox