From: rkuo <rkuo@codeaurora.org>
To: cotulla@yandex.ua
Cc: linux-hexagon@vger.kernel.org
Subject: Re: [DISCUSSION] Hexagon code inside kernel
Date: Mon, 18 Feb 2013 22:36:05 -0600 [thread overview]
Message-ID: <20130219043605.GB12127@codeaurora.org> (raw)
In-Reply-To: <1163031361018389@web26d.yandex.ru>
On Sat, Feb 16, 2013 at 04:39:49PM +0400, cotulla@yandex.ua wrote:
> > Don't know v2. But v3 had a 'real' MMU
> Hm, are you sure in that?
> I had never seen any usage of it. As well as binutils registers definition doesn't include any suitable registers for that.
Both have an MMU, but both are software managed. That's one of the
functions that the hypervisor provides for us.
> > Good, because the bootloader was going to be the other issue.
> Yes, in my case it's working :)
> But another guys who also want participate in this project with MSM8960/APQ8064 they still can't run any unsigned code on Q6.
> In modern phones it's often locked from changes :(
Congrats on getting the bootloader working.
Linas already answered some of your questions (thanks Linas!)
Hexagon Linux so far has been just used on internal projects; it's
not a part of any products even though the processor itself is. A
non-hypervisor port is certainly possible, but for our purposes
around here, it's always running under the hypervisor.
Thanks,
Richard Kuo
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-02-19 4:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 14:28 [DISCUSSION] Hexagon code inside kernel cotulla
[not found] ` <CAHrUA364XES66kXhr0Gg1dh_MQBAS0+R8Q4x+EY3dgz6s=QRww@mail.gmail.com>
2013-02-15 22:33 ` Linas Vepstas
2013-02-16 1:35 ` cotulla
2013-02-16 2:34 ` Linas Vepstas
2013-02-16 12:39 ` cotulla
2013-02-16 17:33 ` Linas Vepstas
2013-02-16 19:21 ` cotulla
2013-02-19 4:36 ` rkuo [this message]
2013-02-19 14:29 ` Linas Vepstas
2013-02-20 1:07 ` cotulla
2013-02-20 1:17 ` cotulla
2013-02-23 4:24 ` Rob Landley
2013-02-24 12:00 ` cotulla
2013-02-24 16:32 ` Linas Vepstas
2013-02-24 17:29 ` cotulla
2013-02-24 21:03 ` Linas Vepstas
2013-02-25 17:26 ` Rob Landley
2013-02-26 18:54 ` cotulla
2013-02-27 0:58 ` Rob Landley
2013-02-27 12:39 ` cotulla
2013-02-24 12:23 ` cotulla
2013-02-26 6:55 ` Rob Landley
2013-02-26 19:30 ` cotulla
2013-02-26 19:32 ` cotulla
2013-02-26 19:59 ` Linas Vepstas
2013-02-26 20:25 ` cotulla
2013-02-26 20:57 ` Linas Vepstas
2013-02-27 1:06 ` Rob Landley
2013-02-27 1:30 ` Linas Vepstas
2013-02-27 3:03 ` Rob Landley
2013-02-27 12:35 ` cotulla
-- strict thread matches above, loose matches on Subject: below --
2013-02-24 0:24 Linas Vepstas
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=20130219043605.GB12127@codeaurora.org \
--to=rkuo@codeaurora.org \
--cc=cotulla@yandex.ua \
--cc=linux-hexagon@vger.kernel.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.