22 hours of BAD CONNECTION GATEWAY

it's been 22 hours ago and every time i have to look and like my connection's post the web server will always say 'BAD CONNECTION' and 'ERROR CONNECTION GATEWAY'. i'm also having trouble posting my blogs here so i assume all of you are experiencing this kind of problem.

i am very sorry mate because i did not found a way to like your post because of bad gateway connection and also the web server too are in big trouble.

NOTE: this isn't mine, this will credit to bubblews site.
22 hours of BAD CONNECTION GATEWAY

ARMHF versus ARMEL part 2

here's another explaination about armel and armhf version of kernel.


Arm processors come in all makes and sizes, a certain percentage of which address a market where cost, footprint and power requirements are at a premium. In this space, the inclusion of even a floating point unit would be considered an unnecessary luxury. To perform floating point operations with these processors, software emulation is required.

Higher-end Arm processors come bundled with additional capability that enables hardware execution of floating point operations. The difference between these two architectures gave rise to two separate Embedded Application Binary Interfaces or EABIs for ARM: soft float and VFP (Vector Floating Point). Although there is forward compatibility between soft and hard float, there is no backward compatibility. And in fact, when it comes to providing binaries for Java SE Embedded for Arm, Oracle provides two separate options: a soft float binary and a VFP binary. In the Linux community, releases built upon both these EABIs are refereed to as armel based distributions.

Enter armhf. Although a big step up in performance, the VFP EABI utilizes less-than-optimal argument passing when a floating point operations take place. In this scenario, floating point arguments must first be passed through integer registers prior to executing in the floating point unit. A new EABI, referred to as armhf optimizes the calling convention for floating point operations by passing arguments directly into floating point registers. It furthermore includes a more efficient system call convention. The end result is applications compiled with the armhf standard should demonstrate modest performance improvement in some cases, and significant improvement for floating point intensive applications.

Alas, armhf represents yet another binary incompatible standard, but one that has already gained considerable traction in the community. Although still relatively early, the transition from armel to armhf is underway. In fact, Ubuntu has already announced that future releases will only be built to the armhf standard, effectively obsoleting armel. As mentioned in Henrik's Stahl's Blog, an armhf version of Java SE Embedded is in the works, and we have already made available a armhf-based developer Preview of JDK 8 with JavaFX.

In the interim, we will have to deal with the incompatibilities between armel and armhf. Most recently we've seen a rash of failed attempts to run the ArmV7 VFP Java SE Embedded binary on top of an armhf-based Linux distro. During diagnosis, the question becomes, how can I determine whether my Linux distribution is based on armel or armhf? Turns out this is not as straightforward as one might think.



-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE: this article found in:
ARMHF versus ARMEL part 2

hope you like it

ARMHF versus ARMEL part 1

i know that some of you were troubling about armel and armhf so i found a way to answer your question regarding on that matter.

1 ∼ ARMHF versus ARMEL
ARMHF versus ARMEL

Debian officially provides two ARM architectures, armel and armhf. 

The armel architecture supports the ARMv4 instruction set.

This architecture handles floating-point computation in a compatibility mode which it slows performance but allows compatibility with code written for processors without floating point units.

So you can use the armel architecture to build high compatible systems.




-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The armhf architecture supports ARMv7 platform, and more, it adds direct hardware floating-point support.

This means the armhf architecture is faster than the armel one, but it lacks the compatibility with the old architectures.



On memetic you can see some benchmark run on Raspberry Pi with the two architectures. Take a look to Raspbian Benchmarking – armel vs armhf.



If I want to build a system running on a big number of already installed board I have to consider using armel architecture (since some installation could use old ARM boards).

If I have to build a totally new system, working with audio and video, with high probability I'll choose the armhf architecture.



NOTE: this article found in: ARMHF versus ARMEL part 1

hope you like it