xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Meng Xu <mengxu@cis.upenn.edu>
To: Dushyant Behl <myselfdushyantbehl@gmail.com>
Cc: sstabellini@kernel.org, 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>,
	Ian Campbell <ijc@hellion.org.uk>
Subject: Re: Running Xen on Nvidia Jetson-TK1
Date: Sat, 14 May 2016 14:34:00 -0400	[thread overview]
Message-ID: <CAENZ-+mfUm=cVOjoyb0Lm-gfgg1GwD9f_Z9_ouGQwRzduZ9B=g@mail.gmail.com> (raw)
In-Reply-To: <CAHF350L6AiTUHpz7Sp5Jfme4Yhrx6Pq-Hy3_GubooCVffKy0Yw@mail.gmail.com>

Hi Dushyant,

On Sat, May 14, 2016 at 1:36 PM, Dushyant Behl
<myselfdushyantbehl@gmail.com> wrote:
> Hey Meng,
>
> On Sat, May 14, 2016 at 7:39 AM, Meng Xu <xumengpanda@gmail.com> wrote:
>>>
>>> http://dev.ktemkin.com/misc/xenarm-gic-parents.patch
>>
>> It seems this link is invalid now...
>> Has this patch been upstreamed?
>>
>> Hi Dushyant,
>> Could you help repost this patch in this email if it's not that large?
>> (Since we used the same repo, which is IanC's, it may be even better
>> if you could kindly share the patch based on the tegra-tk1-jetson-v1
>> branch of Ian's repo.?)
>
> The patch is attached with the mail.
>

Thank you so much for your help! I applied the patch and the kernel
can have further progress in booting.

I'm replying to your last email about the issue I'm facing to, which
seems not same with what you saw.

Best Regards,

Meng
-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/

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

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

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08  8:23 Running Xen on Nvidia Jetson-TK1 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 [this message]
2016-05-14 18:37                           ` Meng Xu
2016-05-14 18:58                             ` Dushyant Behl
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='CAENZ-+mfUm=cVOjoyb0Lm-gfgg1GwD9f_Z9_ouGQwRzduZ9B=g@mail.gmail.com' \
    --to=mengxu@cis.upenn.edu \
    --cc=dushyantbehl@in.ibm.com \
    --cc=ijc@hellion.org.uk \
    --cc=julien.grall@arm.com \
    --cc=myselfdushyantbehl@gmail.com \
    --cc=sstabellini@kernel.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --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).