All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrii Anisov <andrii.anisov@globallogic.com>
To: Chen Baozi <baozich@gmail.com>
Cc: Julien Grall <julien.grall@linaro.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Domain 0 crashed when booting OMAP5 uEVM
Date: Tue, 13 Aug 2013 12:36:26 +0300	[thread overview]
Message-ID: <CAGQvs6jX1geF5vMi-KjiPZt4riRqtY_n1WZxkVCadKwtaNS0dQ@mail.gmail.com> (raw)
In-Reply-To: <20130813091007.GA16513@cbz-workstation>


[-- Attachment #1.1: Type: text/plain, Size: 833 bytes --]

Chen,


> So I think I have to implement a .specific_mapping such as
> exynos5_specific_mapping in arch/arm/platforms/exynos5.c?
>
> I gave this hint a few messages ago in this thread ;)


> Just one more question. Read from OMAP5 datasheet, its IO memory address
> space ranges from 0 to 2G (with holes of course). Do I have to map all
> of them?


It really depends on what you want to achieve.
If you need things up and running ASAP - just map all the range. But
mention following:

   - exclude GIC range
   - exclude your xen console UART range

Other hints:

   - set kernel console to hvc0
   - disable printings from LK decompressor (it writes directly to omap
   debug UART3, and if you give it to xen and don't map to Dom0 - will have
   data abort)

BTW, have you got CPU1 brought up by XEN?

*Sincerely,*
*Andrii Anisov*

[-- Attachment #1.2: Type: text/html, Size: 1502 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-08-13  9:36 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 12:24 Domain 0 crashed when booting OMAP5 uEVM Chen Baozi
2013-08-12 12:47 ` Julien Grall
2013-08-12 14:15   ` Andrii Anisov
2013-08-12 14:30   ` Andrii Anisov
2013-08-12 15:08     ` Julien Grall
2013-08-12 15:32       ` Andrii Anisov
2013-08-12 15:40         ` Andrii Anisov
2013-08-13  2:40           ` Chen Baozi
2013-08-13  7:56     ` Chen Baozi
2013-08-13  8:45       ` Chen Baozi
2013-08-13  9:55         ` Julien Grall
2013-08-12 14:54   ` Andrii Anisov
2013-08-13  9:10   ` Chen Baozi
2013-08-13  9:36     ` Andrii Anisov [this message]
2013-08-13  9:40       ` Chen Baozi
2013-08-13  9:58       ` Julien Grall
2013-08-14  9:46         ` Chen Baozi
2013-08-14  9:55           ` Julien Grall
2013-08-14 12:38             ` Chen Baozi
2013-08-15  9:13               ` Julien Grall
2013-08-15  9:47                 ` Chen Baozi
2013-08-15 10:07                   ` Julien Grall
2013-08-15 10:54                     ` Andrii Anisov
2013-08-15 11:00                       ` Chen Baozi
2013-08-15 11:07                         ` Andrii Anisov
2013-08-15 10:59                     ` Chen Baozi
2013-08-15 12:24                       ` Ian Campbell
2013-08-15 12:43                         ` Julien Grall
2013-08-14 16:07             ` Andrii Anisov
2013-08-14 19:47               ` Julien Grall
2013-08-14  9:53       ` Chen Baozi
2013-08-14 16:03         ` Andrii Anisov
2013-08-15  2:31           ` Chen Baozi
2013-08-15  7:37             ` Chen Baozi
2013-08-15  8:34               ` Andrii Anisov
2013-08-15  8:51                 ` Chen Baozi
2013-08-15  9:12                   ` Andrii Anisov
2013-08-15  9:17                     ` Chen Baozi
2013-08-15  8:45               ` Andrii Anisov

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=CAGQvs6jX1geF5vMi-KjiPZt4riRqtY_n1WZxkVCadKwtaNS0dQ@mail.gmail.com \
    --to=andrii.anisov@globallogic.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=baozich@gmail.com \
    --cc=julien.grall@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.