Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Intel i386


Related Topics

In the News (Fri 19 Apr 19)

  
  i386 and x86-64 Options - Using the GNU Compiler Collection (GCC)
Intel Pentium2 CPU based on PentiumPro core with MMX instruction set support.
Intel Pentium3 CPU based on PentiumPro core with MMX and SSE instruction set support.
This is the default choice for i386 compiler.
gcc.gnu.org /onlinedocs/gcc-3.4.4/gcc/i386-and-x86_002d64-Options.html   (1891 words)

  
  Intel 80386 - Wikipedia, the free encyclopedia
The Intel 80386 is a microprocessor which was used as the central processing unit (CPU) of many personal computers from 1986 until 1994 and later.
Designed and manufactured by Intel, the i386 processor was taped-out in October of 1985.
The predecessor of the 80386 was the Intel 80286, a 16-bit processor with a segment-based memory management and protection system.
en.wikipedia.org /wiki/Intel_80386   (934 words)

  
 [No title]   (Site not responding. Last check: )
Intel syntax accomplishes this by prefixes memory operands (*not* the opcodes themselves) with `byte ptr', `word ptr', and `dword ptr'.
Thus, Intel `mov al, byte ptr FOO' is `movb FOO, %al' in AT&T syntax.
AT&T: `foo(,%eax,4)', Intel: `[foo + eax*4]' INDEX is `%eax' (scaled by a SCALE 4); DISP is `foo'.
www.cs.umb.edu /cs241/pcbook/gnu_as.txt   (1894 words)

  
 IA-32 - Wikipedia, the free encyclopedia
Intel was forced to follow suit, quickly introducing new NetBurst family processors, initially referred to as the "IA-32e" family.
Intel was the inventor and is the biggest supplier of processors compatible with this instruction set, but it is not the only supplier of such processors.
Intel started using the set starting with the Xeon Nocona core in late 2004, introducing it to the desktop market with the Pentium 4 E0 revision in early 2005.
en.wikipedia.org /wiki/I386   (2424 words)

  
 Board Support Packages Processor Initialization   (Site not responding. Last check: )
This initialization code is responsible for initializing all data structures required by the i386 in protected mode and for actually entering protected mode.
The i386 must be placed in protected mode and the segment registers and associated selectors must be initialized before the initialize_executive directive is invoked.
In this mode, the i386 automatically converts every address from a logical to a physical address each time it is used.
www.engr.usask.ca /classes/EP/414/lab/rtemsdocs/i386/i38600030.html   (457 words)

  
 Embedded Intel® Architecture
The Intel® platform approach combines a multi-core architecture with complementary system enhancing technologies to deliver scalable, power efficient processing for a wide range of applications.
Or choose implementation-ready boards and systems from Intel and third party vendors to meet your most stringent time-to-market requirements.
Quad-Core Intel® Xeon® processor E5335 is industry’s first quad-core processor for compute intensive embedded, storage and communications equipment.
developer.intel.com /design/intarch   (170 words)

  
 [No title]
For example, for the Intel i386 without an i387 coprocessor, this macro is set to the string "i386 with i387".
The i386 segment registers and associated selectors must be initialized when the initialize_executive directive is invoked.
When the i386 is reset, * The EAX register is set to indicate the results of the processor's power-up self test.
www.rtems.com /onlinedocs/rtems-doc-20030417/info/i386.info-1   (5337 words)

  
 Intel386™ Processors - Overview
Intel's 186 processor family has been designed in many embedded applications over the years.
The Intel® System Management Mode is built into the Intel386 EX chip.
The Intel System Management Mode (SMM) is typically used to execute specific routines for power management.
www.intel.com /design/intarch/intel386/index.htm   (1464 words)

  
 Peeve: why "i386"?
The receptionist on the front desk might know it's something to do with Intel - "you know, the ones with that funny tune in the adverts" - but don't care what it is. Putting something in the release docs about IA-32 is going to confuse them as much as i386.
Geeks, on the other hand, know that (say) Intel P4s are IA-32, x86, i386 compatible processors and probably don't care much which one of them is used within the documents and source providing that they know it will work, and where there are issues (e.g.
In other words, the only people who care are probably Intel's marketing guys and pedants (a venn diagram of these two sectors can be provided on request) and absolutely nobody else at all, gives a damn.
lists.freebsd.org /pipermail/freebsd-chat/2003-June/000435.html   (497 words)

  
 CS 302 - i386   (Site not responding. Last check: )
The links below describe the syntax for i386 assembly languages (there are, unfortunately, two different syntaxes in use) and the basics of the architecture of an i386 type CPU.
AT&T Syntax versus Intel Syntax from Using as The GNU Assembler
These are references to the assembly language syntax used by the GCC and Lcc-Win32 compilers (called the "AT&T syntax") and how it differs from Intel syntax used by Microsoft's compiler.
ems.calumet.purdue.edu /mcss/kraftrl/cs302/i386.html   (303 words)

  
 history development of Intel microprocessor, intel history, cpu performance history
To introduce a history of Intel Architecture, we could warm up with a discussion of one of the first computers, the Analytical Engine by Charles Babbage, and take the history of computers from first inception to present day.
Though an interesting read, it would be a long drawn out paper which would start with the development of computers that filled large rooms and contained thousands of transistors and conclude with the.13 micron processors that we have today.
Meanwhile Intel processor designers also make improvements to the back end to improve overall performance and maintain x86 compatibility, all the time working to make these transparent to the software developer.
www.developers.net /intelisdshowcase/view/915   (697 words)

  
 Exploring Windows 2000 Memory > INTEL i386 MEMORY MANAGEMENT   (Site not responding. Last check: )
In this context, the virtual memory addressing and paging capabilities of the Intel i386 CPU family are explained, focusing on how the Windows 2000 kernel exploits them.
Before delving into the technical details of the i386 architecture, let's travel back in time to the year 1978, when Intel released the mother of all PC processors: the 8086.
In the context of i386 memory management, three sorts of addresses must be distinguished, termed logical, linear, and physical addresses in Intel's system programming manual for the Pentium (Intel 1999c).
www.awprofessional.com /articles/article.asp?p=167857   (3778 words)

  
 Windows 2000 Memory Management > i386 Memory Management Data Structures   (Site not responding. Last check: )
The term i386 might look somewhat anachronistic because the 80386 CPU dates back to the Stone Age of Windows computing.
Because many data items inside the i386 CPU are concatenations of single bits or bit groups, C bit-fields come in handy.
According to the Intel manuals, the remaining 31 bits are "Available to Operating System or Executive." If a linear address maps to a PNPE, this means that this address is either unused, or it points to a page that is currently swapped out to one of the pagefiles.
www.awprofessional.com /articles/article.asp?p=22444   (1537 words)

  
 Add new comment | Linux Journal
Since the implementation of memory management is based on hardware architecture, we have to have a look at the i386 architecture first.
In the i386 architecture, ``task'' is an alternative name for process.
As defined in i386 architecture, the maximum size of GDT is 8192*8 bytes, which means it can contain 8,192 descriptors.
www.linuxjournal.com /comment/reply/4407   (2021 words)

  
 VMware for Linux: A preview
With the Intel i386 architecture came the ability to create virtual machines (VM).
i386 and i486 processors could emulate 8086 VMs in hardware, making applications such as dosemu (which runs DOS in VMs) possible.
This extension to the Intel architecture makes an x86 emulation product such as VMware possible.
www.developer.com /open/print.php/610581   (438 words)

  
 #00202: i386 syscalls   (Site not responding. Last check: )
Sun announces the release of patches for Intel Platform Editions of Solaris(tm) 8, 7, and 2.6 (SunOS(tm) 5.8_x86, 5.7_x86, and 5.6_x86) which relate to a vulnerability in user-supplied arguments to a syscall on i386 platforms.
Who is Affected Vulnerable: Intel Platform Edition of Solaris 8, 7, and 2.6 (SunOS 5.8_x86, 5.7_x86, and 5.6_x86).
Understanding the Vulnerability The Intel i386 architecture supports a protection and segmentation model which allows different levels of privilege.
sunsolve.sun.com /search/document.do?assetkey=1-22-00202-1   (622 words)

  
 [No title]
Intel Syntax ------------------------------------------------------------------------ Since most assembler documentation for the i386 platform is written using intel syntax, some comparison between the 2 formats is in order.
This is due to the way intel i386 opcode lea handles NULL pointers.
EAX was never loaded with 0 on a null pointer (just some invalid pointer), which caused line 47 to access an area of memory not available to this process (hence the segmentation fault).
database.sarang.net /study/linux/asm/linux-asm.txt   (2120 words)

  
 Technical Bulletin #03   (Site not responding. Last check: )
Some 64-bit processors, such as the Itanium from Intel, use an instruction set that is not backwards-compatible with the Pentium processor family.  Such processors are beyond the scope of this document.
It is important to note that x86_64 editions of the Red Hat Enterprise Linux 3 operating system support packages built for any of the i386, i486, i586, i686, and x86_64 architectures.  It is generally possible for a single system to have a mix of i386 and x86_64 packages installed.
The libf2c package supports side-by-side installation of its i386 and x86_64 editions also (provided the version numbers are identical).  Reciprocal Net site software depends upon the i386 edition, but other software present on your system may depend upon the x86_64 edition.
www.reciprocalnet.org /networkinfo/docs/tb03/tb03.html   (301 words)

  
 OpenBSD/i386
Intel 82802 random number generator found on i810, i815, i820, i840, i850 and i860 based systems.
Intel PRO/Wireless 2100 IEEE 802.11b PCI adapters (ipw)
Intel i82540, i82541, i82542, i82543, i82544, i82545, i82546, i82547, i82571, i82572 and i82573 based adapters (em), including:
www.openbsd.org /i386.html   (3133 words)

  
 FreeOS.com: The Resource Center for Free Operating Systems   (Site not responding. Last check: )
Apple is working hard here and is also giving back a lot of code to the open source community.
Support for the Intel platform is also planned.
Intel, Mips, DEC Alpha, and Power PC This OS was recently released to the open source community but it seems to have been a bit too late.
www.freeos.com /compare   (412 words)

  
 eBeam | attributions
Intel Corporation, 2200 Mission College Blvd., Santa Clara, CA 95052-8119, USA.
Intel, Pentium, the Intel logo, the Intel Inside logo, and the Pentium Processor logo are registered trademarks of Intel.
i386, i486, Intel386, Intel486, Pentium® II Xeon, Pentium® III Xeon, the MMX logo, the Pentium OverDrive Processor logo, and the ProShare logo, are trademarks of Intel.
www.e-beam.com /support/attributions.html   (437 words)

  
 The Intel Years (1968-2006) on Flickr - Photo Sharing!
Intel Inside: Pentium 4 HT Extreme Edition (2003-2006)
I started slowly and gathered the information, when I realized that there are more then I had expected.
Logophile Compendium is a never ending research on the development of logos, and while gathering information for it I was looking for the logos of Intel Corporation.
www.flickr.com /photos/zoharma/103503467   (293 words)

  
 NetBSD: kernel USER_LDT - The Community's Center for Security
This problem is only present on the i386 platform, and only when the USER_LDT kernel configuration option is enabled at compile time.
Technical Details ================= The Intel i386 architecture supports a complex and confusing protection and segmentation model relying on rings, segment selectors, segment descriptors, gates, descriptor tables and the like.
Note that this behaviour is not restricted to Intel processors; the bug applies to implementations of the x86 architecture by other manufacturers as well.
www.linuxsecurity.com /content/view/102959/107   (945 words)

  
 i386 Addressing Modes and Assembler Instructions
This chapter contains information specific to the Intel i386 processor architecture, which includes the i386, i486, and Pentium processors.
The first section, " i386 Registers and Addressing Modes," lists the registers available and describes the addressing modes used by assembler instructions.
The Mac OS X Assembler for Intel processors makes use of instructions specific to the i486 processor, and will not run on an i386 processor.
www.cs.cuc.edu /~biehl/326/document/i386_Instructions.html   (104 words)

  
 Intel 80386 processor family
The third generation of x86 family, the Intel 80386 (i386) was a complete 32-bit processor with ability to address 4 GB of physical memory.
The processor included new protected mode, that allowed the processor to fully utilize new 32-bit architecture and new features, like memory protection, paging, etc. Another new mode - virtual mode - could be used to run old 8086 applications without switching the processor back from protected mode to real mode.
The Intel 80386 was produced at speeds up to 33 MHz, AMD produced even faster 40 MHz version.
www.cpu-world.com /CPUs/80386   (173 words)

  
 Search Intel I386 Software - Free Software Download - Programs For All
This emulator is meant to be used for *didactic* purposes, as for introducing assembly programming, or demonstrating how computers work in general.
Provide a user-level API (C library) for communicating with the intel Pocket Concert MP3 player under Linux and *BSD, as well as a simple command-line utility for managing files/tracks on the device.
Eventually he will be capable of making choices based on his past experiences in order to reach his goals.
www.programs4all.net /software/intel-i386_2.htm   (251 words)

  
 FreeBSD/i386 6.2-RELEASE Hardware Notes
It lists devices known to work on this platform, as well as some notes on boot-time kernel customization that may be useful when attempting to configure support for new devices.
All Intel processors beginning with the 80486 are supported, including the 80486, Pentium, Pentium Pro, Pentium II, Pentium III, Pentium 4, and variants thereof, such as the Xeon and Celeron processors.
The use of ACPI causes instabilities on some machines and it may be necessary to disable the ACPI driver, which is normally loaded via a kernel module.
www.freebsd.org /releases/6.2R/hardware-i386.html   (3480 words)

  
 Hardware Supported by NetBSD
Hardware docs are likely to be nonexistent, since the machine was built before NCR abandoned the 68000 line for Intel, which in turn was before ATandT bought them out and then spun them off again.
There is i386 MCA bus code in NetBSD tree now, which would help with the MCA aspect.
Many drivers could be shared with the sun3 and sparc ports.
www.netbsd.org /Ports   (1620 words)

  
 FreeBSD/i386 Project
If you have a machine from any large PC company (such as Dell™, HP, or eMachines®) chances are that you have either an AMD™; or Intel® CPU and thus fall into this category.
FreeBSD 6.0 and newer no longer supports the original Intel 80386 CPU; these computers are over seven years old and are only supported by FreeBSD 5.X and earlier.
Note that the GENERIC kernel only supports 80386 CPUs in FreeBSD 4.X and earlier.
www.freebsd.org /platforms/i386.html   (108 words)

  
 MacFixIt - Stripping Universal Binaries of Intel or PowerPC code (#2): Simplified Terminal command, more information
We previously noted that the presence of Intel code in Universal binaries can cause some troubleshooting issues.
For instance, a problem we've been covering where the presence of iTunes 6.0.2 causes Disk Utility to be unable to run can be solved by stripping the application of its Intel-based code.
In the above example, a new file called "iTunes-thin.app" will be created that is missing either PowerPC (ppc) or Intel (i386) code.
www.macfixit.com /article.php?story=20060126080805257   (476 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.