From: Abraham Varricatt <abraham.varricatt@gdatech.co.in>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] documentation help
Date: Fri, 09 Nov 2007 21:32:38 +0530 [thread overview]
Message-ID: <4734849E.8080307@gdatech.co.in> (raw)
Hi all,
For the past week I've been trying to trace the program flow of u-boot
and I've not had much success so far.
When I mean 'program flow' I am referring to how u-boot works. As an
example, I have a MPC8555E running on a board with PCI configured. Now,
during boot up u-boot initializes the PCI bus.
What I've found out so far, is that the main program calls a function
called 'pci_init()' (or similar to that). This function is located in a
file present in the 'board' directory. Now, the code in the 'board'
directory redirects program flow to the 'cpu' directory where much of
the initialization really takes place. There is a lot of jumping around
there and it is hard for me to keep track of the flow.
One of the biggest difficulties I am facing is that there does not seem
to be any documentation on this matter. The comments in the source are
just not enough for me.
Any suggestions?
One of my colleagues specifically asked me to explain to him how u-boot
does the PCI enumeration and I'm stuck.
Yours,
Abraham V.
reply other threads:[~2007-11-09 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4734849E.8080307@gdatech.co.in \
--to=abraham.varricatt@gdatech.co.in \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox