From: Amit Kumar <free.amit.kumar@gmail.com>
To: Shyam Saini <mayhs11saini@gmail.com>
Cc: Kernel Newbies <kernelnewbies@kernelnewbies.org>
Subject: Re: BeagleBone Black patches
Date: Wed, 15 May 2019 14:27:40 +0530 [thread overview]
Message-ID: <CAPTh4OuqS-AJO=dz+LuR5kk2PEG58DR+u436eJYwMA4Fi1hOtA@mail.gmail.com> (raw)
In-Reply-To: <CAOfkYf54b_stht-9XxuCNYygTxRd7TZg+qCFpUO6TO_2zHY-Hw@mail.gmail.com>
On Wed, May 15, 2019 at 12:53 PM Shyam Saini <mayhs11saini@gmail.com> wrote:
>
> > Hi,
>
> Hi Amit,
>
> >
> > I have started trying my hands on BBB. When I use this repo,
> > https://github.com/RobertCNelson/linux-dev
> > to build BBB kernel, patches are applied on mainline/stable kernel release.
> >
> > When I build mainline kernel, there is not any defconfig for BBB
> > (there is omap2plus).
> >
> > Should BBB specific patches be sent to the mailing list step by step?
>
> By looking at [1] Buildroot beaglebone defconfig, it suggests that
> beaglebon is using omap2plus as defconfig
> and seems like it uses [2]am335x-boneblack.dts, which is already there
> in mainline.
>
> [1] https://git.buildroot.net/buildroot/tree/configs/beaglebone_defconfig#n11
> [2] https://git.buildroot.net/buildroot/tree/configs/beaglebone_defconfig#n13
Thank you for your quick reply.
Mainline kernel build is going on BBB with omap2plus_defconfig.
There is another option, to use repo,
https://github.com/beagleboard/linux
with bb.org_defconfig
It is always possible to configure kernel as required.
Leave issue of defconfig behind.
Mainly I am worried about patches not in upstream/mainline kernel.
I'm going to compare above repository and mainline kernel source.
>
> Thanks a lot,
> Shyam
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2019-05-15 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 6:47 BeagleBone Black patches Amit Kumar
2019-05-15 7:22 ` Shyam Saini
2019-05-15 8:57 ` Amit Kumar [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='CAPTh4OuqS-AJO=dz+LuR5kk2PEG58DR+u436eJYwMA4Fi1hOtA@mail.gmail.com' \
--to=free.amit.kumar@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=mayhs11saini@gmail.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;
as well as URLs for NNTP newsgroup(s).