From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Mantle Open source GPU engine
Date: Fri, 4 Oct 2013 11:04:37 -0500 [thread overview]
Message-ID: <20131004160437.GJ10604@server> (raw)
In-Reply-To: <loom.20131004T132426-272@post.gmane.org>
On Fri, Oct 04, 2013 at 03:02:07PM +0000, James wrote:
> Howdy one and all,
>
> Well I heard about about AMD's push, referred to as Mantle
> to unseat DirectX as the defacto gaming platform (yawn)...
>
>
> But recently, an egg_head mathematician that irritates me
> from time to time, called me in the middle of the night.
> He, being an eceptionally bright and difficult humnoid; would
> not shut up at what AMD is doing.
>
> Finally it seems that an open source, raw hardware access
> API is going to allow truely unfettered access to the
> computational blocks inside of a GPU. (ok now I was awake).
>
> Upon googing this am, I do see quite a buzz, particularly
> since all Nvidia would have to do, is decide to implement
> the open source -- open standard access to the bare metal
> of the GPU. This should not be taken likely as it is akin
> to all of the FPGA hardware folks giving away the billions
> of dollars in IP, software and integration tools that make
> building a custom processor, possible. Those tools are locked
> away, due to expense and the business approach of hardware
> vendors asking for money each time they reveal the tricks,
> trade secrets and heuritical methods to build low level components.
>
> What this means is that MANTLE is a game changer and opens
> up "bare metal access" to multitudes of ordinary computational
> and recreatioal computer weenies....(whoa Pee!)
>
>
> If this is true, it is a GAME CHANGERS (could not resist the pun).
>
>
> So:
> A. it is time for me to dig into this issue.
> B. Are any of the folks on this list working to get
> Mantle support available on Gentoo?
> C. Anyone tested one of the "Hawaii" radeon cards?
> D. Anyone working on running SteamOS virtualize on (gentoo) linux?
>
>
> as always, your thoughts are most welcome
>
> James
>
> [1]
> http://www.pcworld.com/article/2049369/amd-nvidia-ramp-up-linux-driver-support-after-valves-steamos-announcement.html
>
> [2] http://www.tomshardware.com/news/amd-mantle-api-gcn-battlefield-4,24418.html
computer gaming (yawn)...
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2013-10-04 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 15:02 [gentoo-user] Mantle Open source GPU engine James
2013-10-04 16:04 ` Bruce Hill [this message]
2013-10-04 16:26 ` [gentoo-user] " James
2013-10-04 16:49 ` James
2013-10-04 17:36 ` Bruce Hill
2013-10-04 19:20 ` [gentoo-user] " Alan McKinnon
2013-10-04 20:53 ` Bruce Hill
2013-10-05 9:10 ` Alan McKinnon
2013-10-05 10:37 ` Mark David Dumlao
2013-10-05 10:56 ` Volker Armin Hemmann
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=20131004160437.GJ10604@server \
--to=daddy@happypenguincomputers.com \
--cc=gentoo-user@lists.gentoo.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