search for: mx515

Displaying 7 results from an estimated 7 matches for "mx515".

2009 Mar 27
3
[LLVMdev] GSoC 2009: proposals!
...on this so far: * Automated Synthesis Of Efficient Binary Decoders for Retargetable Software Toolkits, DAC 2003 * Generating decision trees for decoding binaries 3) Improve ARM be adding necessary ARMv7 instructions and support for VFPv3 and Thumb-2, all this for the ARMv7 Cortex A8 (I can get a i.MX515 board to play if this project is selected) 4) Improve MIPS be to support the Malta board (I'm working on this already, but I rather not work only with MIPS to change things a little bit, but I'd not bother working on this too) I'll improve the proposals in the GSoC app, but for now I&...
2012 Nov 06
0
Announcing Foundation Funded Project!
Dear FreeBSD Community, The FreeBSD Foundation is pleased to announce that Aleksandr Rybalko has been awarded a grant to port FreeBSD to the Genesi Efika MX SmartBook laptop and SmartTop nettop devices. Both use the Freescale i.MX515, an ARM Cortex-A8 System-on-Chip (SoC). These low power devices will provide convenient reference platforms for FreeBSD on ARM, as they are low-cost complete systems. The Smartbook includes a 10" display, 3G connectivity and a battery life of 6 to 8 hours for $199. When this project is comple...
2011 Apr 08
0
[LLVMdev] Assuring ARM code quality in LLVM
...ve thought about some routes: > - Install some build slaves on our side, so you can test them (linux, > bare-metal), if it's possible to cross-compile on build slaves. there are several idle ARM buildslaves. There are the following slaves: gcc35: # 1TB 0.8 GHz Freescale i.MX515 (ARM Cortex-A8) / 512 MB RAM / Efika MX Client Dev Board gcc50: # 250G 0.6 GHz ARM XScale-80219 / 512 MB RAM / Thecus N2100 NAS gcc55: # 250G 1.2 GHz ARM Feroceon 88FR131 (kirkwood) / 512 MB RAM / Marvell SheevaPlug gcc56: # 320G 1.2 GHz ARM Feroceon 88FR131...
2011 Apr 07
4
[LLVMdev] Assuring ARM code quality in LLVM
Hi all, I was recently investigating the build bot infrastructure and noticed that the arm-linux target is failing for quite a long time. I believe that it means ARM code is not executed all that often in LLVM tests, is that correct? We were wondering what kind of support we could give to make sure ARM code is correct and don't regress, specially before releases (I know it's a bit late
2012 Mar 29
0
[LLVMdev] Announcing 3.1 Release Branch Date!
On Mar 29, 2012, at 12:57 PM, Jim Grosbach <grosbach at apple.com> wrote: > On Mar 29, 2012, at 2:46 AM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > >>> By the way, we are looking for ARM testers. There was a lot of interest in the 3.0 release for an ARM release. We will try to do one this release on a trial basis. We are looking for ARMv7 cortex-a8 and cortex-a9 on
2012 Mar 29
3
[LLVMdev] Announcing 3.1 Release Branch Date!
On Mar 29, 2012, at 2:46 AM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: >> By the way, we are looking for ARM testers. There was a lot of interest in the 3.0 release for an ARM release. We will try to do one this release on a trial basis. We are looking for ARMv7 cortex-a8 and cortex-a9 on Linux. > > We have two pandard board (ARMv7 cortex-a9) and perhaps one ARMv6 > 4-cores
2011 Apr 08
2
[LLVMdev] Assuring ARM code quality in LLVM
...routes: >> - Install some build slaves on our side, so you can test them (linux, >> bare-metal), if it's possible to cross-compile on build slaves. > there are several idle ARM buildslaves. There are the following slaves: > > gcc35: # 1TB 0.8 GHz Freescale i.MX515 (ARM Cortex-A8) / 512 MB RAM > / Efika MX Client Dev Board > > gcc50: # 250G 0.6 GHz ARM XScale-80219 / 512 MB RAM / Thecus N2100 NAS > > gcc55: # 250G 1.2 GHz ARM Feroceon 88FR131 (kirkwood) / 512 MB RAM / > Marvell SheevaPlug > > gcc56: # 3...