xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dushyant Behl <myselfdushyantbehl@gmail.com>
To: Meng Xu <mengxu@cis.upenn.edu>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Dushyant K Behl <dushyantbehl@in.ibm.com>,
	Xen Devel <xen-devel@lists.xen.org>,
	Julien Grall <julien.grall@arm.com>
Subject: Re: Running Xen on Nvidia Jetson-TK1
Date: Sun, 15 May 2016 00:28:40 +0530	[thread overview]
Message-ID: <CAHF350K8i2dJGwEJJgEgO4jXsYOn=M1ivNhEx5d-AmvCe8=Kkg@mail.gmail.com> (raw)
In-Reply-To: <CAENZ-+mFD8MqrXB_hgjDQvO1eimsfFFyNBcMqP3fUWerURnz3Q@mail.gmail.com>

On Sun, May 15, 2016 at 12:07 AM, Meng Xu <mengxu@cis.upenn.edu> wrote:
>>> some facilities to blacklist a device tree node (see blacklist dev in
>>> arm/platforms/tegra.c).
>>
>> I have blacklisted the tegra20_timer
>
> I guess you blocked the "tegra20-timer" (which uses "-" instead of
> "_") right as shown in the following patch? Am I right?

That was a typo in the email but I had blocked the correct timer, without
blacklisting the tegra timer the linux only boots to a few steps and
fails, in my next
bootlog linux booted a lot further and then failed due to some other reason.

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

  reply	other threads:[~2016-05-14 18:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08  8:23 Dushyant K Behl
2016-03-09 13:37 ` Wei Liu
2016-03-10  5:08   ` Julien Grall
2016-03-12 14:20     ` Dushyant Behl
2016-03-12 15:27       ` Meng Xu
2016-03-12 20:23         ` Dushyant Behl
2016-03-13  2:10           ` Meng Xu
2016-03-14  9:31             ` Dushyant Behl
2016-03-14 14:12               ` Konrad Rzeszutek Wilk
2016-03-14 14:19                 ` Dushyant Behl
2016-03-17 14:52                   ` Julien Grall
2016-03-18 15:01                     ` Dushyant Behl
2016-03-18 17:23                       ` Julien Grall
2016-03-21 10:12                         ` Dushyant Behl
2016-03-24 11:05                           ` Dushyant Behl
2016-03-29 19:01                             ` Julien Grall
2016-03-29 20:56                               ` Dushyant Behl
2016-04-01 10:04                                 ` Julien Grall
2016-04-07  7:48                                   ` Dushyant Behl
2016-04-08 10:10                                     ` Julien Grall
2016-04-08 12:27                                       ` Ian Campbell
2016-04-14 15:54                                         ` Dushyant Behl
2016-05-14 18:43                                           ` Meng Xu
2016-05-14 19:03                                             ` Dushyant Behl
2016-05-14  2:09                                       ` Meng Xu
2016-05-14 17:36                                         ` Dushyant Behl
2016-05-14 18:34                                           ` Meng Xu
2016-05-14 18:37                           ` Meng Xu
2016-05-14 18:58                             ` Dushyant Behl [this message]
2016-05-12  1:00 ` Meng Xu
2016-05-12  9:19   ` Dushyant Behl

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='CAHF350K8i2dJGwEJJgEgO4jXsYOn=M1ivNhEx5d-AmvCe8=Kkg@mail.gmail.com' \
    --to=myselfdushyantbehl@gmail.com \
    --cc=dushyantbehl@in.ibm.com \
    --cc=julien.grall@arm.com \
    --cc=mengxu@cis.upenn.edu \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --subject='Re: Running Xen on Nvidia Jetson-TK1' \
    /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

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).