Archive

Posts Tagged ‘arm’

Linaro 14.08 Release with Kernel 3.16 and Android 4.4.4

September 2nd, 2014 No comments

I’m a little late for that one, as Linaro 14.08 was released last Thursday. Nevertheless, this release features Linux kernel 3.16 (baseline), Linux 3.10.52 (LSK), and Android 4.4.4.

As usual Linaro has worked on member hardware such as Qualcomm based IFC6410 and ARM Juno &Vexpress boards. They’ve also committed changes for LLVM, big Endian, and added a workload generator tool (rt-app) to the Ubuntu and Android image. This tool has been developed and used by the power management working group, presumably to measure and optimize power consumption under various loads.

Here are the highlights of this release:

  • Linux Linaro 3.16-2014.08
    • GATOR version 5.19 (new version)
    • updated topic from Qualcomm LT (ifc6410 board support)
    • updated Versatile Express ARM64 support (FVP Base and Foundation models, Juno) from ARM LT (Landing Team)
    • updated Versatile Express patches from ARM LT
    • updated LLVM topic (follows the community llvmlinux-latest branch)
    • Big endian support (the 2014.05 topic version rebased to 3.16 kernel)
    • config fragments changes: CONFIG_DEBUG_INFO=y added to linaro-base.conf. This is needed to get the debug package containing vmlinux to be built, and vmlinux is required to run perf.
  • Linaro Toolchain Binaries 2014.08 – Based on GCC 4.9, and updated to latest Linaro TCWG releases:
    • Linaro GCC 4.9-2014.08
    • Linaro EGLIBC 2.19-2014.08
    • Linaro binutils 2.24-2014.08
    • Linaro GDB 7.8-2014.08
  • Linaro Android 14.08 – Built with Linaro GCC 4.9-2014.08
  • Linaro OpenEmbedded 2014.08
    • integrated Linaro GCC 4.9-2014.08, Linaro EGLIBC 2.19-2014.08, Linaro binutils 2.24-2014.08, and Linaro GDB 7.8-2014.08
    • added rt-app (contributed from Power Management WG)
    • updated GATOR to 5.19,  LSK kernels, and QEMU to 2.1.0
    • fixed boot wrapper build
    • upstreaming:
      • fixed kexec-tools
      • fixed udev startup script to fix mysql launch failure
      • updated PM QA to 0.4.12
      • fixed PHP build
      • fixed hugetlbfs
  • Linaro Ubuntu 14.08
    • added rt-app
    • updated packages: GATOR 5.19, LSK 3.10.52/3.14.16 and linux-linaro 3.16 kernels.
  • KVM ARMv8 Continuous Integration and Testing is completed
  • Make debug symbols available for Versatile Express ALIP image

You can visit https://wiki.linaro.org/Cycles/1408/Release for a list of known issues, and further release details about the LEB, LMB (Linaro Member Builds), and community builds, as well as Android, Kernel, Graphics, Multimedia, Landing Team, Platform, Power management and Toolchain components.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Embedded Linux Conference Europe 2014 Schedule – IoT, ARM vs x86, Optimization, Power Management, Debugging…

August 21st, 2014 2 comments

The Embedded Linux Conference Europe (ELC 2014), CloudOpen, and LinuxCon Europe will jointly take place at the Congress Centre Düsseldorf, in Germany on October 13 – 15, 2014. The 3-day events will consists of keynotes, presentations, and tutorials. Each day will open with two or three keynotes by speakers including  Jim Zemlin (Executive Director, Linux Foundation), and Jono Bacon (XPRIZE), followed by presentation and tutorials. There will be 45 presentations for ELCE, 58 for LinuxCon, and 47 for CloudOpen, I’ll make a virtual schedule with a few sessions part of the Embedded Linux Conference Europe “track”.

ELCE_2014

Monday, October 13

When faced with a performance problem, the initial steps towards a solution include identifying the sections of code responsible and the precise reasons they are time-consuming. To this end, the ‘perf’ profiling tools provide valuable insight into the characteristics of a program. The presentation will show, using real-world examples, how the ‘perf’ tools can be used to pinpoint the parts of a program in need of optimization.

It’s not uncommon to produce embedded Linux based devices that end up with long and inconvenient boot times – yet eliminating boot time delays can be difficult and time consuming. Furthermore once a minimal boot time has been achieved it’s often just as difficult to maintain it through subsequent software development.

In this presentation, Andrew unfolds 12 keys lessons learned in his experience of boot time reduction. These lessons provide an insight into the common causes of boot time delays, why they are present and how they can be overcome. In describing these lessons Andrew will also take you on a journey that indicates why file system benchmarks should probably be ignored (with respect to boot time reduction) and a journey that illustrates that the Linux kernel is rarely the worst offender for boot delays.

With the introduction of Bluetooth Smart (aka Low Energy), the ubiquity of Bluetooth is more and more present. Millions of devices support Bluetooth Low Energy and with Bluetooth 4.1 specification, they are ready for the Internet of Things. This presentation will give an overview of Bluetooth Low Energy, and its usage for the Internet of Things. It will also introduce 6loWPAN over Bluetooth and show the possibilities this opens for Linux.

With experience developing community based open hardware for both the ARM based PandaBoard project and the x86 based MinnowBoard project, this presentation will provide a detailed comparison of the pros and cons of each platform with highlights of what each platform can learn from the other. Not only limited to the hardware aspect of the platforms, but also discuss community, software, corporate and general embedded aspects.

For almost as long as there have been deployments of Linux, there has been someone wondering “how can I get the device started quicker?” and “how do I configure some redundancy, easily, in case something goes wrong?”. And for the longest time, the answer has been “hack this and this and that” or “hire these consultants, they have done it before”. In this presentation, Tom will show what you need to turn on and the prep work required for, getting a lot of those items out of the box in U-Boot, what the hardware (and/or ROM) needs to do, and the what works is left going forward.

Got a question, comment, gripe, praise, or other communication for the Yocto Project and/or OpenEmbedded? Or maybe you’d just like to learn more about these projects and their influence on the world of embedded Linux? Feel free to join us for an informal BoF.

Tuesday, October 14

While user experiences are increasingly moving to 3D, rendering of 2D content remains at the core of how we interact with computer applications today. Skia is an open-source project maintained by Google whose goal is to bring the best 2D graphics library to a variety of targets, from mobile to desktop and embedded. Skia is used in highly popular projects like Mozilla Firefox, the Chromium browser and Android.

This talk will introduce Skia to developers and users, giving an overview of its design, architecture and features. It will also discuss briefly how hardware acceleration improves performance of Skia in the context of new devices, form-factors and the industry shift to mobile; with focus set on Linux and Android platforms.

The 4.4 KitKat release includes the results of “Project Svelte”: a set of tweaks to the operating system to make it run more easily on devices with around 512 MB RAM. This is especially important for people working with Android Wearables and “Embedded Android”, that is, implementing Android on devices at the lower end of the Android ecosystem. A large part of the problem is knowing how much RAM is really being used. Android offers a variety of tools for the purpose: procrank, procmem, meminfo and procstats, which Chris covers in the first part of the talk. In the second part, he takes a real-world example and show the practical steps you can take to optimize memory use including tuning the size of the Dalvik heap, enabling KSM (Kernel samepage merging) and swap to zRAM.

Android has relied from its early days on the Linux kernel for sandboxing the processes it runs. Yet, the permission model presented to app developers is significantly different from the Unix permission model. What’s the relationship between those two models? How is Android’s app security framework tied to the Linux kernel’s security model? More recently, Android has started using SELinux and has been extended by SEAndroid to support similar functionality. How is SELinux used by Android and what is SEAndroid about? Furthermore, how does Android provide support for multiple users?

This talk will explore Android’s security model in great detail and explain how the functionality found in the kernel is used to isolate user processes and the SE enhancements are leveraged by Android. As we’ll see, there are quite a few moving parts in Android’s security model.

Since last year, Free Electrons has been working on supporting the SoCs from Allwinner, a Chinese SoC vendor, in the mainline kernel. These SoCs are cheap, wide-spread, backed by a strong community and, until last year, only supported by an out-of-tree kernel. Through this talk, Maxime will share the status of this effort: the status a year ago, what solutions were in place, where we are currently, and what to expect from the future. He will also focus on the community around these SoCs, the work that is done there, etc.

Enlightenment Foundation Library is a set of libraries designed to use the full potential of any hardware to do great UI. It has been designed with the embedded devices in mind, but it is a desktop class toolkit. Being done in C, it is providing a stable API/ABI, high efficiency, low memory and low battery usage for all kind of Linux devices. Enabling development of modern UI adapted to any hardware that run Linux. These are the reason why Samsung uses it in its Tizen devices. This talk, after a short overview of what this libraries cover, will focus on this year improvement, and where it is heading. It will also be an opportunity to learn about project around EFL that will help people develop product with it. And it would also be a good opportunity to see where EFL are used with some real use case.

Wednesday, October 15

A major issue the community faces is the lack of power measurement (PM) instrumentation, coupled with poor integration: development boards not designed for it, expensive high-precision lab equipment not accessible to hobbyists (plus limited Linux support), limited low-cost solutions (precision, sampling rate) to monitor high-performance SoC (System On Chips) platforms (e.g. smartphones, tablets, IoT, …). After a brief introduction to the problematic (PM techniques, sense resistor / ADC selection, …) and a comparative study of existing solutions, this presentation will focus on a new upcoming initiative to close these gaps and bring a full-blown multi-channel but low-cost power (and temperature) measurement equipment to the community, including the definition of an open standard PM connector. After having covered motivations, challenges, key decisions, a live demo will close the talk.

In 2013, at the Embedded Linux Conference in Europe in Edinburgh, there was a race between a dog and a blimp. It was said that despite the dogs win, that the blimp had participated in the miracle of flight. In 2014, John wants to show that the brains of that dog can be transplanted and that it too, can participate in the miracle of flight. The talk is mainly targeting taking an off the shelf embedded platform, Minnowboard Max, and it’s use in UAVs, specifically quad-copters. With the ability to do real time computer vision, as well as various GPIO capabilities he will explore the directions that significantly more autonomous UAVs can take with Linux and embedded platforms using, mostly, off the shelf components.

There have been many presentations on what a device tree looks like and how to create a device tree. This talk instead examines how the Linux kernel uses a device tree. Topics include the kernel device tree framework, device creation, resource allocation, driver binding, and connecting objects. Troubleshooting will consider initialization, allocation, and binding ordering; kernel configuration; and driver problems.

Providing real-time capabilities to a general purpose operating system is an outstanding technical problem, and Linux Preempt-RT has been developed for 10 years for this goal. In this presentation, Jim proposes a lightweight open source para-virtualization layer, called “rtmux”, using resource-multiplexing techniques to provide a highly deterministic RT environment for Linux/ARM. Typically, less than 500 lines modification against Linux kernel are required to enable rtmux accompanied by POSIX/PSE51 compatible runtime.

During the last 2.5 years, a team of engineers at Free Electrons has been involved in mainlining the support for several ARM processors from Marvell, converting the not-so-great vendor-specific BSP into mainline quality code progressively merged upstream. This effort of several hundreds working days, has led to the integration of hundreds of patches in the kernel. Through this talk, Thomas will share some lessons learned regarding this mainlining effort, which could be useful to other engineers involved in ARM SoC support, as well as detail the steps Free Electrons engineers have gone through, the mistakes made and how they’ve been solved, as well as their overall experience on this project.

To make your own schedule matching your interests, you can check out the events’ program.

To attend the conference, you can register online.

The fees are listed as follows:

  • All-access Registration Fee – $600 until August 22 (tomorrow), $750 until October 2, and $850 afterwards
  • Attendee Networking Pass Registration – No access to conference sessions. $250 until August 22, $300 afterwards.
  • Student Registration Fee – $200 (valid student id required).
  • Registration Discount Scholar – $300. For active open source community members who can’t be sponsored by their company. .

Fees are significantly higher than last year, because there are only all-in-one (ELCE, CloudOpen and LinuxCon )options, and you can’t simply register to one single event.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

AllWinner A80 OptimusBoard Octa-core big.LITTLE Development Board is Now Available … for $169

August 16th, 2014 33 comments

A80 OptimusBoard powered by AllWinner A80 octa-core processor with four Cortex A15 and four Cortex A7 in big.LITTLE configuration had been announced at the end of 2013, and after numerous delays, several boards have recently been sent to developers and companies such as miniNodes, Linuxium, and others. The company behind the board is actually Shenzhen Merrii Technology (aka WITS), which had done all earlier development kits for AllWinner, and they’ve now made the board available for purchase on Aliexpress. Unfortunately the company has decided to leave to low cost development boards market to the likes of Cubieboard8 and PCDuino8, as A80 OptimusBoard sells for $345 plus about $30 for shipping by courier.[Update: they now offer it for $169]

A80 OptimusBoard (Click to Enlarge)

A80 OptimusBoard (Click to Enlarge)

  • SoC – AllWinner Ultra Core A80 4x Cortex 15, 4x Cortex A7 big.LITTLE processor with Imagination Technologies PowerVR GC6230 GPU with 64-cores, and support for OpenGL ES 1.1/2.0/3.0, Directx 9.3
  • System Memory – 2GB DDR3
  • Storage – 8GB NAND Flash + micro SD card up to 32GB
  • Video Output – HDMI 1.4a up to 4K30
  • Audio – AC100 Codec, headphone jack
  • Video Playback – UHD/4K H.264/VP8 4Kx2K @ 30 fps
  • Connectivity – Dual band Wi-Fi 802.11 b/g/n, Bluetooth 4.0 (AP6330), and Gigabit Ethernet (GMAC)
  • USB – 1x USB 3.0 OTG port, 2x USB 2.0 host ports
  • Camera I/F – 16MP MIPI CSI
  • Debugging – UART and JTAG
  • Expansion – 32-pin GPIO header
  • Misc – IR receiver, reset and power LEDs.
  • Power management – AXP806, AXP809 “smart power management specialist”
  • Power Supply – 5V/3A, or battery
  • Dimensions – 135x70mm

The board comes with a power adapter, and a UART to USB cable. The board comes pre-loaded with Android 4.4.2 on top of Linux 3.4.39. So it’s not a device tree capable kernel, allegedly because AllWinner does not have enough good kernel developers… AllWinner promised support for 5 Operating Systems, but AFAIK, only Android has been provided at this stage, so we may need to wait a little longer for Ubuntu, Chrome/Chromium OS, Firefox OS, and Windows.

You can watch the video below for an overview of the board, and they also quickly show a “professional” AllWinner A80 development board.

Via armdevices.net

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

MYIR ARM9 Linux Development Boards & Computer-on-Modules Powered by Freescale i.MX28 Processor

August 14th, 2014 No comments

MYIR MYD-IMX28X development boards and MYC-IMX28X CPU modules had been announced in May 2014, but I’ve just found out about them via the company’s newsletter. The CoMs are powered by Freescale i.MX28 ARM9 processors (i.MX283 or i.MX287), feature 128 MB RAM, 256 MB Flash, and connect to a baseboard to make the development boards. Target applications include smart gateways, human-machine interfaces (HMIs), handheld devices, scanners, portable medical, experimental education as well as other industrial applications.

MYC-IMX28X CoMs

MYIR_MYC-iMX28X_ARM9_CoMMYC-IMX28X computer-on-module specifications:

  • Processor – Freescale i.MX283 or i.MX287 ARM926EJ-STM processor up to 454MHz with 128KB SRAM, 128KB ROM, 1280 bits of OCOTP ROM, 16KB/32KB I and D Cache
  • System Memory – 128MB DDR2 SDRAM
  • Storage – 256MB NAND flash, 128KB SPI flash
  • Connectivity – On-board Ethernet PHY
  • Connectors – 2x 1.27mm pitch 2 x 40-pin SMT male expansion connectors with access to
    • Ethernet – Up to 2 Ethernet (two for i.MX287, one for i.MX283)
    • USB – 2x USB2.0 High-speed ports
    • Serial – Up to 6x Serial ports (including one Debug port)
    • 1x I2C, 2x SPI
    • Up to 8x ADC (one high-speed ADC, seven low-resolution ADC)
    • Up to 5x PWM
    • 1x SDIO
    • 2x CAN (i.MX287 only)
  • Misc – Power and user LEDs
  • Power Supply – 5V
  • Dimensions – 62mm x 38mm
  • Operating Temperature Range – Commercial: -20~70 Celsius; Industrial: -40 to +85 Celsius

The main differences between i.MX283 and i.MX287, are support for only 1 Ethernet port against 2 for i.MX287, and the latter features 2 CAN buses. The company provides an SDK with u-boot, Linux 2.6.35, and relevant drivers for the module.

MYD-IMX28X Boards

Click To Enlarge

MYD-IMX28X Development Board (Click To Enlarge)

The development boards have the following hardware specifications:

  • SoC/Memory/Storage – Based on MYC-IMX283 or MYC-IMX287 modules as described above: Freescale i.MX28 @ 454 MHz, 128 MB DDR2, 256 NAND flash, and 128KB SPI flash
  • External Storage – micro SD card slot
  • Display I/F – 1x LCD interface (16-bit true color, supports optional 4.3-inch and 7-inch TFT LCD), 1x 4-wire resistive touch screen interface
  • Audio – 3.5mm jacks for Audio IN and OUT, and headphone output, digital audio out (RCA), MIC IN interface, Buzzer
  • Serial ports – 1x 3-wire RS232 Debug serial port (DB9), 1x 5-wire RS232 serial port (UART0), 1x RS485
  • USB – 1x USB2.0 Host port, 1x USB2.0 OTG
  • Connectivity – 10/100Mbps Ethernet (two for i.MX287, one for i.MX283)
  • CAN – 2 x CAN interfaces (only for i.MX287)
  • Expansion connector – 2x 20-pin headers with access to 3x ADC (one high-speed ADC, two low-resolution ADC), 1x SPI, 2x I2C, 3x UART, 3x PWM
  • Debugging – 20-pin JTAG interface
  • Misc – 4 x Buttons (1 x Reset button, 3 x User buttons), 2 x User LEDs (Blue)
  • Power Supply – 5V barrel connector
  • Dimensions – 140mm x 90mm

MYD-IMX28X_Block_DiagramPublicly available documentation is limited with only Freescale i.MX28 datasheet, and MYD-IMX28X board and MYC-IMX28X module simplified datasheets with overview of the boards, header pinout, and a list of document and software packages available for the board. U-boot, Linux 2.6.35, and drivers will be provided with source code, as well as some code samples to control various peripherals (SPI. I2C, touchscreen, LCD…) and a Qt demo. MYIR also provides 4.3″ and 7″ resistive or capacitive touchscreen as option for $60 to $99.

The modules and development kits appears to be available now, MYC-IMX28X module starts at $39 for the commercial version, $59 for the industrial version, and the development board, probably excluding the CPU module, sells for $99 and $119, respectively for the commercial and industrial versions. You can find more details on MYIR’s MYC-IMX28X module page.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

SPMC is a Fork of XBMC Available on Google Play Store, Amazon AppStore

August 12th, 2014 4 comments

XBMC 13, released a few months ago, is the first official release to support hardware video decoding on many ARM based Android devices. However, although both XBMC Android apks for ARM and x86 can be downloaded from xbmc.org, Team-XBMC have decided not to publish XBMC for Android on app stores such as Google Play, partially because video hardware decoding is not yet fully working on all popular Android SoC platforms and devices, but also because of the upcoming name change from XBMC to Kodi. Since the code is open source under GPLv2, anybody can build it, and somebody published XBMC on Android as a paid app, which would have been legal if they changed the name, but as they used XBMC trademark, it has been removed since then. Seeing this, Chris Browet (Koying), one of XBMC developer, decided to fork XBMC, apply some patches not yet approved in mainline XBMC, and publish it under the name SPMC (Semper Media Center / SemperPax media Center) in Google Play Store and Amazon AppStore for free.

SPMCThe main advantages are that you don’t need to modify your Android security settings to side-load an apk, and you’ll get automatic updates, if Koying decides to update the fork regularly.

The latest version is based on XBMC 13.2 with at least the following improvements:

  • Add suspend on rooted devices
  • Possible fix for recurrent startup crash
  • Switch TV to 3D automatically on amlogic
  • Allow mouse long left click to bring up context menu

SPMC on Amazon App currently can’t be installed on Fire TV, but this is checked on, and you can follow the relevant thread on XBMC forums. You can follow SPMC project on spmc.semperpax.com, including access to the source code.

If you’d rather have the official XBMC apk, or try both, since SPMC and XBMC have different signatures, but don’t want to follow or check releases manually, XBMC updater Android app will automatically download and install the latest apk from xbmc.org.

There has been a few other XBMC / Kodi news lately, including Kodi 14 for Google’s Android TV (ADT-1 devkit), and Kodi 14 Alpha 2 release that includes an update to FFMpeg 2.2.4 allows H.265 (HEVC) and VP9 software video  playback, support for 4K videos on Amlogic S802 processor, and more.

Thanks to Harley for the tip.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Categories: AMLogic AML8726, Android Tags: Android, arm, kodi, spmc, xbmc

Linux 3.16 Released

August 6th, 2014 3 comments

Linus Torvalds announced the release of Linux Kernel 3.16 over the week-end:

So nothing particularly exciting happened this week, and 3.16 is out there.

And as usual (previous release being the exception) that means that the merge window for 3.17 is obviously open. And for the third time in a row, the timing sucks for me, as I have travel coming up the second week of the merge window. Many other core developers will be traveling too, since it’s just before the kernel summit in Chicago.

So we’ll see how the next merge window goes, but I’m not going to worry about it overmuch. If I end up not having time to do all the merges, I might delay things into the week of the kernel summit, but I’ll hope to get most of the big merging done this upcoming week before any travel takes place, so maybe it won’t come to that. So this is just a heads-up that the merge window *might* be extended.

Anyway, back to the changes since -rc7: it’s really fairly small stuff randomly all over, with a third being architecture updates, a third drivers, and a third “misc” (mainly mm and networking). The architecture stuff is small ARM updates (mostly DT), some x86 Xen fixups, some random small powerpc things. The shortlog gives a good idea of what kind of stuff it all is, but it’s really just 83 commits (plus merges and the release commit) and about a third of them are marked for stable.

So while 3.16 looked a bit iffy for a while, things cleared up nicely, and there was no reason to do extra release candidates like I feared just a couple of weeks ago.

Linus

Kernel 3.15 brought various file systems improvements, faster resume from suspend, etc… Some of Linux 3.16 main changes include:

  • Various KVM improvements: optimizations, support for migration, and GDB support for s390, little-endian support for POWER8, as well as MIPS improvements.
  • Xen – Virtual network interfaces now have multi-queue support for much better performance.
  • Goldfish virtual platform now has 64-bit support.
  • Hugepage migration has been turned off for all architectures except x86_64 since it is only tested on that architecture and there are bugs for some of the others.
  • Automatic NUMA balancing has been turned off for 32-bit x86. Existing 32-bit NUMA systems are not well supported by the code and the developers did not think the effort to support them would be worthwhile.
  • EFI – The kernel EFI code will now handle Unicode characters, and initial support for ARM64 (aarch64) had been added.
  • NFS – Patches to make loopback NFS mounts work reliably have been merged through the NFS tree.  External data representation (XDR) handling in NFS has been reworked to support access control lists (ACLs) larger than 4KB. It also returns readdir() results in chunks larger than 4KB giving better performance on large directories.
  • Modules now have the read-only (RO) and no-execute (NX) bits set on their data sections much earlier in the loading process, before parsing any module arguments. This will further reduce the time window in which a misbehaving (or malicious) module can modify or execute its data.
  • Support for TCP fast open over IPv6 has been added.
  • Support for busy polling on stream control transmission protocol (SCTP) sockets has been added. Busy polling is set on a socket using the SO_BUSY_POLL socket option; it can reduce the latency of receives on high-traffic interfaces that support the option.

New features and improvements specific to the ARM architecture include:

  • AllWinner – All platforms: AXP20x PMIC and MMC support, 5 drivers + SMP reworked for AllWinner A31, touchscreen drivers for AllWinner A10. DTS added for Mele M9 and R7. You can read details about AllWinner changes here.
  • Rockchip – RK3xxx SoC I2C drivers
  • Xen on ARM systems now supports suspend and resume.
  • Hibernation support added for ARM targets.
  • Initial support for ARM64 (aarch64) had been added
  • SMP support has been added for Marvell Armada 375 and 38x SoCs. SMP has been reworked for the Allwinner A31 SoC.
  • New ARM SoC added: ST Microelectronics STiH407; Freescale i.MX6SX; Samsung Exynos 3250, 5260, 5410, 5420, and 5800; and LSI Axxia AXM55xx.
  • Nouveau driver has initial support for NVIDIA Tegra K1 GK20A devices.
  • Various changes for Atmel AT91, Marvell Armada, Fresscale i.MX, Samsung Exynos, and TI AM43xx SoCs.

Further details on Linux 3.16 will eventually be available on Kernelnewbies.org. For more details about ARM changes, remember to also check ARM architecture and drivers sections.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

AMD Announces Availability of their $3,000 Opteron A1100-Series 64-bit ARM Development Kit

July 31st, 2014 3 comments

AMD Opteron A1100 Server SoCs, codenamed “Seattle”, come with four to eight ARM Cortex A57 cores, and earlier this year, the company unveiled both the processors and a development kit. You can now apply for “AMD Opteron A1100 Series 64-bit ARM developers kit”, and if you’re selected, you’ll “just” need to pay $2,999 to receive the board and related tools. The kit targets software and hardware developers, as well as early adopters in large datacenters.

AMD_Opteron_A1110_Development_BoardAMD Opteron A1100 Board hardware specifications:

  • SoC – ARM Opeteron A1000 with 4 ARM Cortex-A57 cores
  • System Memory – 2x Registered DIMM with 16 GB of DDR3 DRAM (upgradeable to 128GB)
  • Storage – 8 Serial-ATA connectors
  • Connectivity – Not mentioned, but there seems to be an RJ45 port on the pic, and another SFP cage, both probably 10 Gbit Ethernet since it’s the speed supported by Opteron A1100.
  • Expansion slots – PCI Express connectors configurable as a single x8 or dual x4 ports
  • Dimensions – Micro ATX form factor (244 × 244 mm)
  • Power – Compatibility with standard power supplies

The kit also includes a standard UEFI boot environment, a Linux environment based on “Fedora technology from the Red Hat-sponsored Fedora community”, a standard Linux GNU (cross and native) toolchains, device drivers, apache web server, MySQL database engine, and PHP scripting language for developing robust Web serving applications, and Java 7 & 8.

Thanks to Peter, via AMD.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter