abbreviation of mips

shown below1, homepage--the current package of the website address "Homepage": "Https://github.com/napcs/node-livereload#readme",2, os--operating system support list. The values for these operating systems include AIX, FreeBSD, Linux, MacOS, Solaris, VxWorks, Windows. If the list is set to NULL, no assumptions are made on the operating system[Note that the]livereload plugin does not have OS properties set3. The support list for the CPU--CPU architecture, with an effective architecture name of

RISC is the abbreviation of "Reduced instruction set Computing" in English, meaning "simplified instruction set" in Chinese. It is developed on the basis of the CISC instruction system, and some people test the CISC machine to show that the use frequency of various instructions is quite disparity, the most commonly used is some simple instructions, they only accounted for 20% of the total number of instructions, but the frequency of the progra

shell command commands-to-set-it is run. These commands should not have side effects, except for setting variable Cache-id. In particular, they should not call Ac_define, followed by the code after the call to Ac_cache_val should invoke ac_define based on the cached value. In addition, they should not print any messages, such as using ac_msg_checking, and should print before calling Ac_cache_val so that the message is printed regardless of whether the test results are retrieved from the cache o

By Falcon 2008-01-13 If you want to develop loongson software without a Development Board, you can use its virtual machine gxemul (for loongson) to emulate. However, the latest gxemul that supports loongson is 0.4.3 and only supports loongson 2E. In addition, the network support is not good enough. Next we will introduce how to simulate a loongson basic software development environment through gxemul on the Ubuntu system on the X86 platform. 1. Introduction Loongson [1] is a high-performance, lo

Now we can use the tool chain provided by Android ndk in the form of an independent compiler! This is useful if you already have your own build system. A typical application scenario is to call a 'configure 'script dependent on the CC environment variable open source library for cross-platform compilation. This document explains how to do that.1. Select your tool chain: First, you need to determine whether your independent toolchain targets the target CPU architecture, which is an ARM-based dev

, we'll analyze the implementation of __SWAB32, the essence is in this function.But before this first consider a problem, for different CPUs, such as Arm MIPS PPC, how to choose to use Little_endian.h or big_endian.h it.The answer is, for different processor platforms, there are arch/xxx/include/asm/byteorder.h header files, to see what arm MIPS PPC Byteorder.h respectively.Arch/arm/include/asm/byteorder.h

-windows.zip 109928336 bytes 37b1a2576f28752fcc09e1b9c07e3f14 Mac OS X (Intel) Android-ndk-r8-darwin-x86.tar.bz2 96650992 bytes 81ce5de731f945692123b377afe0bad9 Linux 32/64-bit (x86) Android-ndk-r8-linux-x86.tar.bz2 88310791 bytes 5c9afc9695ad67c61f82fbf896803c05 Revisions The sections below provide information and notes about successive releases ofthe ndk, as denoted by revision number.Android ndk, revision 8 (May 1, 2012) This release of the ndk

execute it correctly. Definition of some CPU identifiers: Intel i386 0x14cIntel i860 0x14dMIPs r300 0x162MIPs r400 0x166DEC Alpha AXP 0x184Power PC 0x1f0 (little endian)Motorola 68000 0x268Pa Proteus 0x290 (precision Architecture) # Define image_file_machine_unknown 0# Define image_file_machine_i386 0x014c // The intel 386.# Define image_file_machine_r3000 0x0162 // MIPS little-Endian, 0x160 big-Endian# Define image_file_machine_r4000 0x0166 //

Author: Falcon Copy Link By Falcon 2009-03-31 [I almost had to write a long article (I wrote two sections in E). I thought about it, but I copied it directly from weekreport and sorted it out.] Recently, the Linux real-time extension patch rt_preempt has been transplanted to the loongson2f platform. Now it is basically finished. Here is a summary. I. porting process The porting process is as follows (serial numbers are generally promoted, but some may be cross-parallel ): 0. Search for loongson

/little_endian.h, as follows:#define __LE32_TO_CPU (x) ((__force __u32) (__LE32) (x))It is equivalent to doing nothing. For big-endian processors, in./include/linux/byteorder/big_endian.h, as follows:#define __LE32_TO_CPU (x) __swab32 ((__force __u32) (__LE32) (x))the literal meaning can also be seen, __swab32 realize data rollover. Wait, we'll analyze the implementation of __SWAB32, the essence is in this function. But before this first consider a problem, for different CPUs, such as Arm

Original website: http://blog.csdn.net/akatope/article/details/6506101bootloader introduction of embedded Linux system SupportLinuxBootloader more, the development to 2010, there have been some inevitable results, some bootloader have disappeared, someBootloaderReplaced, some bootloader were merged, some, although in development, have retreated to a remote corner. Now for the mainstream or the application of a little broad bootloader do an introduction.GRUB/GRUB2:Grub is primarily targeted at t

RX ISR to traverse packets describing token (reap). Some places call BD(Buffer descriptor), because it is hardware specific, so developers generally do not need to modify H/W descriptor data structure. The address of the DMA descriptor array hw_desc[] is the virtual address of the DMA map, which describes the token base site and needs to be configured in the relevant DMA registers of the SOC chip, such as the Ar9331datasheet DMARXDESCR (Pointer to Rx descrpitor) and dmatxdescr_q0 (descriptor ad