Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
AMD Programming Hardware

HSA Foundation Formed By AMD, ARM, Ti, Imagination, and MediaTek 51

New submitter Phopojijo writes "To wrap up his 'Programmers Guide to a Universe of Possibility' keynote during the 2012 AMD Fusion Developer Summit, Phil Rogers of AMD announced the establishment of the Heterogeneous System Architecture Foundation. The foundation has been instituted to create and maintain open standards to ease programming for a wide variety of processing resources including discrete and integrated GPUs. Founding members include ARM, Texas Instruments, Imagination, MediaTek, Texas Instruments, as well as AMD. Parallels can be drawn between this and AMD's 'virtual gorilla' initiative back from the late 1990s."
This discussion has been archived. No new comments can be posted.

HSA Foundation Formed By AMD, ARM, Ti, Imagination, and MediaTek

Comments Filter:
  • Ti (Score:5, Funny)

    by Anonymous Coward on Tuesday June 12, 2012 @07:06PM (#40302475)

    But tell me, does it include Texas Instruments?

    • by c0lo ( 1497653 )
      But no (i)nvidia which, I reckon, doesn't like to unleash the next era [wikipedia.org] of computing innovation </grin>
      • Yeah... the list of major absentees is NVIDIA, Apple, Samsung, and Intel. Pretty big holes... but pretty big names present too. We shall see.
        • nVidia and Intel I can see, but Apple and Samsung? They're widget makers, not chipset makers.

          • Re: (Score:3, Informative)

            by Phopojijo ( 1603961 )
            Samsung is a big developer of processors and one of the world's few FABs actually. ((I actually forgot to mention Qualcomm as an absentee for some reason -- they're a big no-show too.)) Though Apple, I agree, is little love lost. They design chips... but barely; they would not really contribute much to this arrangement; and if they sink by excluding themselves then it will only be them to be hurt in that deal.
            • by CAIMLAS ( 41445 )

              Add to the list Motorola. Though, really, Samsung and Motorola are 'just' big (good) hardware intigrators, as opposed to being instigators of the actual core technologies. But if TI has signed on, I think they should certainly consider it.

              Apple? Most certainly they should be off the list, if for no other reason than the fact that they design their x86 hardware to not be fully compatible with other common x86 systems (thinking of their UEFI), seemingly for the sake of being different...

          • To be fair, Apple basically invented OpenCL. AMD has been trying to push OpenCL as a valid alternative to CUDA for programming GPU's, and thus APU's. Apple certainly focuses on consumer electronics these days, but they do still have a lot of "core technology" people working in less visible rolls, and doing some very real work.

        • ... the list of major absentees is NVIDIA, Apple, Samsung, Intel and NVIDIA...

          FTFY

    • Hah -- yeah I noticed that just after I clicked submit. Somehow I missed it while I was writing it and previewing it. Oh well.
    • One of the main thing the programming community needs is getting to the innards of GPUs

      We can sense the raw power of the GPU engines, the parallel structures, but, so far, there is no way we can tap into all those power buried inside with assembly language

      We are forced to jump through official hoops such as CUDA (from Nvidia) and OpenCL (from ATi)

      I am not saying that CUDA or OpenCL are craps, but they should let us, the programming community, the option of getting to the very guts of the graphic engines in

      • by Shag ( 3737 )

        We are forced to jump through official hoops such as CUDA (from Nvidia) and OpenCL (from ATi)

        You should fix Wikipedia, which thinks OpenCL originated with... Apple?

        I'm inclined to back the one with "Open" in its name, in hopes that it actually will be, but if everybody could get together and hash out a single thing including the best points of CUDA, OpenCL and this new HSA thing (how many times must we invent this particular wheel?) we'd probably all be better off.

        • if everybody could get together and hash out a single thing including the best points of CUDA, OpenCL and this new HSA thing (how many times must we invent this particular wheel?) we'd probably all be better off.

          This lies the irony

          The more "committee" we set up, the more wheels get re-invented, and, this is the most important part, the programming community ends up waiting, and waiting, and waiting, with no end in sight

          The Intel X86 architecture became successful partly because it offers the programming community to tap into its raw power

          If the Intel X86 architecture hides itself behind layers upon layers of hardware/software obfuscations, I do not think it would be as successful as it is, today

          That is exactly why

          • The ironic part is that an X86 instruction hasn't been mapped to dedicated hardware for decades. It just signals a series of micro-ops to perform the calculation.

            That started back when we were still doing most of our applications in assembly... and people were begging Intel for the most arbitrary of operations in-silicon.

            Then of course when we switched to compilers only about 10% of those operations were used 90% of the time... which is why ARM got so efficient and cheap... because they built their commit
      • Actually it is a bit bigger of a problem than that.

        There actually is a form of assembly language for GPUs. NVIDIA has PTX... I don't know what ATi/AMD's is called but I saw some of it in passing.

        The actual problem from my perspective is that the assembly language is modified and optimized by the drivers before it reaches the chip. The assembly-style PTX code you send to the drivers does not relate to the machine code which the GPU executes. That kind-of defeats the purpose of the assembly language.

        That
    • by Trogre ( 513942 )

      Yes it does, and yes.

  • by rrohbeck ( 944847 ) on Tuesday June 12, 2012 @07:27PM (#40302695)

    AMD needs to get on the ARM bandwagon. I want an APU with an integrated ARM core that works as a service processor and low power auxiliary CPU when the big CPU is powered off. Good enough for email and browsing and if the GPU has good power management the battery should last forever.

    • by Anonymous Coward

      They're already partway there, using ARM for the embedded controller in their south bridges.

    • by Anonymous Coward

      It seems more likely that they will eventually add a low-powered x86 core. Intel's Medfield shows that x86 can compete with ARM in the use cases you're suggesting (both in terms of power use and speed). Additionally, having a low-power x86 core would mean less concern about mixing ARM and x86 operating systems in some sort of weird, simultaneous mish-mash.

    • AMD needs to get on the ARM bandwagon. I want an APU with an integrated ARM core that works as a service processor and low power auxiliary CPU when the big CPU is powered off. Good enough for email and browsing and if the GPU has good power management the battery should last forever.

      So you would have a mix of instruction sets (ARM vs. X86). It's very unlikely that we'll see such a scenario, not just because of the hardware, but because of the software: porting an OS to run on two different architectures simultaneously is something (AFAIK) never done before. That would be coding hell. Too bad, because I like the idea, too.

  • Why don't they explain what is the foundation supposed to do and promote, that Khronos OpenCL doesn't yet promote? Without a clear, and well communicated mission this foundation will be just on paper, I am afraid. Anybody knows what they are supposed to do?
    • by rrhal ( 88665 )
      From TFA (emphasis mine)

      The HSA (Heterogeneous System Architecture) Foundation is a not-for-profit consortium for SoC IP vendors, OEMs, academia, SoC vendors, OSVs and ISVs whose goal is to make it easy to program for parallel computing. HSA members are building a heterogeneous compute ecosystem, rooted in industry standards, for combining scalar processing on the CPU with parallel processing on the GPU while enabling high bandwidth access to memory and high application performance at low power consumption. HSA defines interfaces for parallel computation utilizing CPU, GPU and other programmable and fixed function devices, and support for a diverse set of high-level programming languages, thereby creating the next foundation in general purpose computing.

      One click in:

      Members of the HSA Foundation plan to deliver robust development solutions for heterogeneous compute to drive innovative content and applications with developer tools, software developer kits (SDKs), libraries, documentation, training, support and more.

      Basically they are going to maintain a set of open standards for platforms that allow programmers to integrate code that runs on the GPU with code that runs on the CPU's.

  • Okay, I had to Google for this, but for those curious about the simian reference in the summary, here's what Wikipedia has to say [wikipedia.org]:

    AMD ex-CEO and founder Jerry Sanders developed strategic partnerships during the late 1990s to improve AMD's presence in the PC market based on the success of the AMD K6 architecture. One major partnership announced in 1998 paired AMD with semiconductor giant Motorola. In the announcement, Sanders referred to the partnership as creating a "virtual gorilla" that would enable AMD t

    • by Epi-man ( 59145 )

      I had some friends who worked at AMD and were involved with this partnership. The thing I remember most was how different two companies could be. AMD and Motorola had two dramatically different design philosophies, polar opposites, it was not a pretty picture.

  • Wow, its very rare to see both of them cooperating on the same project.

It is easier to write an incorrect program than understand a correct one.

Working...