From: Greg KH <greg@kroah.com>
To: Pankaj Vinodrao Joshi <Pankaj.VJ@exaleapsemi.com>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: Linux kernel BSP
Date: Wed, 14 Apr 2021 09:05:58 +0200 [thread overview]
Message-ID: <YHaUVkCV0SfXLYZO@kroah.com> (raw)
In-Reply-To: <BMXPR01MB2870644A6AD671E9B78AE458EE4E9@BMXPR01MB2870.INDPRD01.PROD.OUTLOOK.COM>
On Wed, Apr 14, 2021 at 06:54:49AM +0000, Pankaj Vinodrao Joshi wrote:
> Hi Greg KH,
>
> i understood BSP (Board support packages ) contains u-boot , drivers
> ,dts apart from this what are the elements of BSP i am not able to
> understand.
It all depends on who you got this "BSP" from. You are paying for
support from the vendor whose chip you bought, why not consult their
documentation and ask them for help?
> Scenario is, i want to port linux BSP to the android BSP and for that
> i am trying to gather the information about the BSP, what exectly it
> is, where i should change all kind of stuff
At the kernel level, there is no difference between "linux bsp" and
"android bsp", it's all just Linux down there.
And again, ask your vendor for this help, you are paying for it already.
> Hope i made you clear with what i am looking for
Not really, sorry. Please be specific as to what you have tried and what
did not work.
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-04-14 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 6:38 Linux kernel BSP Pankaj Vinodrao Joshi
2021-04-14 6:47 ` Greg KH
2021-04-14 6:54 ` Pankaj Vinodrao Joshi
2021-04-14 7:05 ` Greg KH [this message]
2021-04-14 7:24 ` Pankaj Vinodrao Joshi
2021-04-14 7:47 ` Greg KH
2021-04-14 7:50 ` Saket Sinha
2021-04-14 8:03 ` Pankaj Vinodrao Joshi
2021-04-14 8:15 ` Greg KH
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=YHaUVkCV0SfXLYZO@kroah.com \
--to=greg@kroah.com \
--cc=Pankaj.VJ@exaleapsemi.com \
--cc=kernelnewbies@kernelnewbies.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 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).