All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Om Prakash PAL <omprakash.pal@stericsson.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Porting of specific Kernel/Driver into yocto.
Date: Mon, 9 Apr 2012 00:02:45 -0400	[thread overview]
Message-ID: <4F825F65.4040706@windriver.com> (raw)
In-Reply-To: <3ED83A9DB3B6D94CA68BF7C03F2981D35AE63C1B66@EXDCVYMBSTM006.EQ1STM.local>

On 12-04-08 10:04 AM, Om Prakash PAL wrote:
> Hi Bruce,
> Thanks for your reply.
> I am totally new to Yocto.
> I have gone through the section BSP/Linux kernel configuration and if I am not wrong then it explains how can we configure the kernel, not the how we can add/replace a  component(driver etc).
> lets take the example of UART driver, I want to add my own UART driver code.
> Should I write a separate recipe file (.bb) for UART Driver?.
> if yes then I have to write the recipe files for all my drivers that will be very time consuming.
> Is there any other way that I can port all my desired drivers into Yocto kernel?.

No recipes are required per-driver, unless you are building them all
as out of tree modules.

The typical way this is done is to simply work in the extracted linux
src tree (build/tmp/work/<your board>/linux-yocto-<hashes>/linux), manually
patch, or copy your drivers into the tree. At this point, you'll port
the drivers, doing test builds (bitbake -f -c compile linux-yocto) to
ensure that your port is working. When you've completed the build phase,
boot tests would be in order. (Do not do a 'clean' or you'll lose in
progress changes).

When you are happy with the changes, the directory where you were working
is with the kernel git repository. So you can simply commit your 
changes, and generate patches.

    git format-patch -o <your directory> HEAD^ (or however many commits
you have)

Take those patches, create a layer with a bbappend and add them like
any other patch to any package. They'll be applied to subsequent builds
of the kernel.

I'm skipping a lot of detail there, but it is all found in the various
manuals, and I don't want to repeat it here.

Cheers,

Bruce

> Please help me.
> Thanks a lot in advance.
>
> Best Regards,
> Om Prakash Pal
> ________________________________________
> From: Bruce Ashfield [bruce.ashfield@windriver.com]
> Sent: Wednesday, April 04, 2012 6:17 PM
> To: Om Prakash PAL
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>
> On 12-04-04 04:46 AM, Om Prakash PAL wrote:
>> Hi,
>> I want to build my local kernel/Driver code, not the default one.
>> please help how can i do it ?.
>> any wiki/docs on this?.
>
> The BSP developer guides show how to extend the yocto kernels, and
> also have sections on custom/different kernel versions. Have you
> seen that doc yet ? Or have you seen it, and have specific questions ?
>
> Bruce
>
>>
>> Best Regards,
>> Om Prakash Pal
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>



  reply	other threads:[~2012-04-09  4:02 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  8:46 Porting of specific Kernel/Driver into yocto Om Prakash PAL
2012-04-04 12:47 ` Bruce Ashfield
2012-04-08 14:04   ` Om Prakash PAL
2012-04-09  4:02     ` Bruce Ashfield [this message]
2012-04-09 16:31       ` Om Prakash PAL
2012-04-09 17:34         ` Bruce Ashfield
2012-04-11 15:24           ` Om Prakash PAL
2012-04-11 15:54             ` Bruce Ashfield
2012-04-11 15:34           ` Om Prakash PAL
2012-04-11 15:56             ` Bruce Ashfield
2012-04-29  9:58           ` Om Prakash PAL
2012-04-29 18:48             ` Khem Raj
2012-04-30  8:45               ` Om Prakash PAL
2012-04-30  2:27             ` Bruce Ashfield
2012-04-30 10:34             ` Om Prakash PAL
2012-04-30 14:12               ` Bruce Ashfield
2012-05-03  9:24                 ` Om Prakash PAL
2012-05-03 12:29                   ` Bruce Ashfield
2012-05-06  9:43                     ` Om Prakash PAL
2012-05-06 12:30                       ` Bruce Ashfield
2012-05-23 12:39                         ` Om Prakash PAL
2012-05-23 18:16                           ` Darren Hart
2012-06-21 12:27                             ` Om Prakash PAL
2012-06-21 12:47                               ` Gary Thomas
2012-06-21 14:16                                 ` Om Prakash PAL
2012-06-21 14:28                                   ` Gary Thomas
2012-06-21 15:30                                     ` McClintock Matthew-B29882
2012-06-22  5:37                                     ` Om Prakash PAL
2012-06-22  5:48                                       ` Khem Raj
2012-06-22  9:29                                         ` Om Prakash PAL
2012-06-22 12:38                                           ` Om Prakash PAL
2012-06-25 12:53                                         ` Om Prakash PAL
2012-06-25 13:08                                           ` Bruce Ashfield
2012-06-25 13:12                                             ` Gary Thomas
2012-06-25 14:09                                               ` Om Prakash PAL
2012-06-25 14:06                                             ` Om Prakash PAL
2012-06-25 14:08                                               ` Bruce Ashfield
2012-06-25 14:12                                                 ` Om Prakash PAL
2012-06-25 15:13                                                   ` Khem Raj
2012-06-26  5:33                                                     ` Om Prakash PAL
2012-06-26  7:22                                                       ` Chris Tapp
2012-06-26  7:53                                                         ` Om Prakash PAL
2012-06-26  7:56                                                         ` Om Prakash PAL
2012-05-28 17:55                           ` Bruce Ashfield
2012-06-21 12:43                             ` Om Prakash PAL

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=4F825F65.4040706@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=omprakash.pal@stericsson.com \
    --cc=yocto@yoctoproject.org \
    /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.