xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Chen Baozi <baozich@gmail.com>
To: ian.campbell@citrix.com
Cc: xen-arm@lists.xen.org, stefano.stabellini@eu.citrix.com,
	samuel.thibault@ens-lyon.org, xen-devel@lists.xen.org
Subject: Question about DTB in Mini-OS on ARM
Date: Tue, 4 Jun 2013 11:24:08 +0800	[thread overview]
Message-ID: <20130604032408.GA7344@cbz-workstation> (raw)

Hi Ian,

I've turned to arm32 porting of Mini-OS as you suggested. Right now, I've
finished most of entry header, which setups an initial page table, saves
DTB pointer (from r2 which arm booting protocol defines), setups the stack
before jumping to start_kernel, and includes the exception's entry.

At this stage, I could get the DTB's address in arch_init(), parse it and
translate it to fill start_info structure Mini-OS used. In order to
implement this logic, I was seeking and reading DTB's related codes of
arm guest creation and found that the DTB used in domU in arm is thought
to be appended with the guest kernel:

	/*
	 * ATAGS/DTB: We currently require that the guest kernel to be
	 * using CONFIG_ARM_APPENDED_DTB. Ensure that r2 does not look
	 * like a valid pointer to a set of ATAGS or a DTB.
	 */

In this case, I cannot get the DTB's phys address to fill start_info from
r2 currently. Does it means we need to wrap the mini-os kernel together with
a DTB?

Any ideas?

Thanks.

	Baozi

             reply	other threads:[~2013-06-04  3:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04  3:24 Chen Baozi [this message]
2013-06-04  8:19 ` Question about DTB in Mini-OS on ARM Ian Campbell

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=20130604032408.GA7344@cbz-workstation \
    --to=baozich@gmail.com \
    --cc=ian.campbell@citrix.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-arm@lists.xen.org \
    --cc=xen-devel@lists.xen.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).