All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Baozi <baozich@gmail.com>
To: Andrii Anisov <andrii.anisov@globallogic.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: Wed, 14 Aug 2013 17:53:55 +0800	[thread overview]
Message-ID: <A2612E87-03A3-41D9-BF25-5C1BFF60AD33@gmail.com> (raw)
In-Reply-To: <CAGQvs6jX1geF5vMi-KjiPZt4riRqtY_n1WZxkVCadKwtaNS0dQ@mail.gmail.com>

On Aug 13, 2013, at 5:36 PM, Andrii Anisov <andrii.anisov@globallogic.com> wrote:

> 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

Andrii,

Did you face any mmc problem when booting dom0?

After I did some io mappings, I could finally get Linux kernel booting message now. But it seems it still has some problems with mmc0:

mmc0: unrecognised SCR structure version 1
mmc0: error -22 whilst initializing SD card
...

Any ideas?

Cheers,

Baozi

  parent reply	other threads:[~2013-08-14  9:53 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
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 [this message]
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=A2612E87-03A3-41D9-BF25-5C1BFF60AD33@gmail.com \
    --to=baozich@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=andrii.anisov@globallogic.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.