linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Syn <john3909@gmail.com>
To: linux-omap@vger.kernel.org
Cc: Nishanth Menon <nm@ti.com>, Robert Nelson <robertcnelson@gmail.com>
Subject: Re: SGX support on AM572x
Date: Tue, 11 Nov 2014 13:58:20 -0800	[thread overview]
Message-ID: <D087AB25.5A4A5%john3909@gmail.com> (raw)
In-Reply-To: <20141111195403.GA16958@kahuna>


On 11/11/14, 11:54 AM, "Nishanth Menon" <nm@ti.com> wrote:

>On 11:17-20141111, John Syn wrote:
>> With the release of the Beagleboard-X15 in February 2015, I¹m trying to
>> get a handle on the status of SGX support for the AM572x processor. Is
>> anyone working on adding this support and is there any schedule for
>> releasing SGX on AM572x? There is a lot of interest on the beagleboard
>> mailing list, but SGX support seems to be a big stumbling block.
>
>1. Are you looking for SGX driver support in
>https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ ?
>
>OR
>
>2. Are you looking for distro support?
>
>OR
>3. Are you looking for what TI release(if any) will contain?
>
>for (1) you already have response from beagleboard mailing list - TI, to
>my knowledge will not support IMG[1] drivers in kernel.org - at least no
>known activity in the past present or future to do that.
Yeah, I think this is clearly understood.
>
>For (2): as the distro folks how they want to do things - again depends
>on where you are getting your distro from.
The official distro for Beagleboard-X15 is Robert Nelson’s Debian distro,
but as long as SGX is available for AM572x, I’m sure Robert will find a
way to get this working.
>
>For (3): use TI support channel over e2e Phorums[2] and look at relevant
>TI release's release notes. Things like [3] are handled properly that
>way.
I took a look in e2e and I did find one promising posting:

http://e2e.ti.com/support/omap/f/885/t/366372.aspx

However, this article and your reference [3] are for V3.8 and I believe
BeagleBoard-X15 will be released with V3.14 or V3.18. So my question is
related to [3] and SGX support for either V3.14 or V3.18.

Regards,
John
>
>
>Other recent references:
>https://plus.google.com/100242854243155306943/posts/TKX7GfHkTow
>http://beagleboard.org/Community/Forums?place=msg%2Fbeagleboard%2F1t3yxkPY
>SB8%2FxCbkoWC_GhQJ
>
>
>[1] http://www.imgtec.com/community/
>[2] e2e.ti.com
>[3] 
>http://git.omapzoom.org/?p=device/ti/proprietary-open.git;a=tree;f=jacinto
>6;h=6203e0dfe7cf89456517a1b877610f8ac2b4fd86;hb=refs/heads/d-lollipop-rele
>ase
>-- 
>Regards,
>Nishanth Menon


--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-11-11 21:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 19:17 SGX support on AM572x John Syn
2014-11-11 19:54 ` Nishanth Menon
2014-11-11 21:58   ` John Syn [this message]
2014-11-11 22:22     ` Nishanth Menon
2014-11-11 23:30       ` John Syn

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=D087AB25.5A4A5%john3909@gmail.com \
    --to=john3909@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robertcnelson@gmail.com \
    /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).