All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhuvanchandra DV <bhuvanchandradv@gmail.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: Kernel backports mailinglist <backports@vger.kernel.org>
Subject: Re: Issues while integrating backports(20150525) to target Kernel 3.1.10
Date: Thu, 11 Jun 2015 10:34:48 +0530	[thread overview]
Message-ID: <557916F0.9060400@gmail.com> (raw)
In-Reply-To: <556F4819.3020706@hauke-m.de>

Hello Hauke,

On 06/04/2015 12:01 AM, Hauke Mehrtens wrote:

> On 06/02/2015 02:11 PM, Bhuvan wrote:
>> Hello,
>>
>> I'm trying to integrate backports(20150525) to target Kernel 3.1.10.
>> Followed the instructions available in the backports wiki for kernel
>> integration procedure. Nice! documentation.
>> Used linux-next.git, backports.git with next-20150525 and
>> backports-20150525 tags respectively.
>> The target Linux kernel version is based on NVIDIA's L4T and it was not
>> a clean 3.1 baseline but
>> rather some pre 3.2 version with further Android additions.
>> My aim is to backport the iwlwifi drivers on 3.1.10 kernel.
>>
>> Backporting 20150525 on 3.1.10 using gentree.py was not successful:
>>
>> # ./gentree.py --integrate --clean --gitdebug --git-revision
>> next-20150525 ../linux-next ~/linux
>> Get original source files from git ...
>> Applying patches from patches to ~/backports ...
>> Modify Kconfig tree ...
>> Rewrite Makefiles and Kconfig files ...
>> Applying patches from integration-patches/ to ~/linux ...
>> Failed to apply changes from
>> 001-enable-backports/0001-enable-backports-built-in.patch
>>> patching file Makefile
>>> Hunk #1 succeeded at 506 (offset -36 lines).
>>> Hunk #2 succeeded at 713 (offset -108 lines).
>>> Hunk #3 FAILED at 841.
>>> 1 out of 3 hunks FAILED -- saving rejects to file Makefile.rej
>> Traceback (most recent call last):
>>    File "./gentree.py", line 1091, in <module>
>>      ret = _main()
>>    File "./gentree.py", line 724, in _main
>>      logwrite=logwrite)
>>    File "./gentree.py", line 1078, in process
>>      bpid.project_dir, logwrite)
>>    File "./gentree.py", line 552, in apply_patches
>>      raise Exception('Patch failed')
>> Exception: Patch failed
>> ....
>>
>> Makefile.ref :
>>
>> --- Makefile
>> +++ Makefile
>> @@ -841,7 +845,7 @@ libs-y        := $(libs-y1) $(libs-y2)
>>
>>   # Externally visible symbols (used by link-vmlinux.sh)
>>   export KBUILD_VMLINUX_INIT := $(head-y) $(init-y)
>> -export KBUILD_VMLINUX_MAIN := $(core-y) $(libs-y) $(drivers-y) $(net-y)
>> +export KBUILD_VMLINUX_MAIN := $(core-y) $(libs-y) $(drivers-y) $(net-y)
>> $(backports-y)
>>   export KBUILD_LDS          := arch/$(SRCARCH)/kernel/vmlinux.lds
>>   export LDFLAGS_vmlinux
>>   # used by scripts/pacmage/Makefile
>>
>> Am i missing some thing or doing some thing wrong!.
>> Can some one provide few pointers for fixing the issues and few pointers
>> on backporting kernel integration
>> on non standard kernel trees, like the one which i am working on.
>>
>> Best regards,
>> Bhuvan
> I think the documentation is not so good. ;-)
>
> If you just want to compile the drivers against your kernel the easiest
> way is to download the tar from here:
> http://www.kernel.org/pub/linux/kernel/projects/backports/2015/05/25/backports-20150525.tar.xz
>
> You can compile it against your kernel like any other external kernel
> module.
> The git repository is only needed if you want to generate your own tar
> with the drivers form your kernel.

Thanks!
Compiled the iwlwifi drivers successfully with backports-3.11.8 with some small
change: KERNEL_VERSION(3,2,0) to KERNEL_VERSION(3,1,0) in backports-incluse/linux/export.h, found this fix in mailing list.
Tried with the later backport versions, but couldn't compile the drivers successfully for 3.1.10 kernel.


>
> Hauke
>
>
Best regards,
Bhuvan


      parent reply	other threads:[~2015-06-11  5:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 12:11 Issues while integrating backports(20150525) to target Kernel 3.1.10 Bhuvan
2015-06-03 18:31 ` Hauke Mehrtens
2015-06-04  9:16   ` Issubh " Bhuvanchandra DV
2015-06-11  5:04   ` Bhuvanchandra DV [this message]

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=557916F0.9060400@gmail.com \
    --to=bhuvanchandradv@gmail.com \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.