[MinnowBoard] GSOC 2015 Aspirant for U-Boot EFI Support
saket.sinha89 at gmail.com
Wed Mar 11 18:42:45 UTC 2015
I am posting below my understanding of the u-boot code flow for bringing up
a board until giving up the control to Linux -
Now u-boot is up and running and is in u-boot prompt and ready to accept
commands. Assume that kernel image is loaded into RAM and issued bootm
Control is given to linux.
Let me know if I you agree with it? Now where can I bring in UEFI here?
On Fri, Mar 6, 2015 at 12:20 AM, Simon Glass <sjg at chromium.org> wrote:
> Hi Saket,
> On 3 March 2015 at 19:45, Saket Sinha <saket.sinha89 at gmail.com> wrote:
> > Hi Simon,
> > I guess now is the time for me to get started and dive deeper
> > the project.
> > I am familiar with U-Boot usage at the command level as well as
> > and deployment.
> > I have tried to hack through u-boot in various ways in the past which
> > include
> > 1. Modifications in U-Boot’s initialization process, so that a custom
> > board’s specific hardware is set up early enough
> > 2. Adding support to specific hardware, by virtue of adding or modifying
> > low-level drivers
> > 3. Expanding the command interface to support a needed functionality,
> > possibly as a front-end for new hardware
> > I guess I have the minimal experience to get started with this project.
> > Kindly guide me as to how to go ahead with reference to this project.
> I've figured out the problem with my IRC so will be on
> #minnowboard-gsoc from time to time.
> I'll go through this in more detail and post something next week. In
> the meantime it would be worth taking a look at the code for the
> 'bootm' command in U-Boot. You can start at cmd_bootm.c and work down
> from there.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the elinux-MinnowBoard