Mon . 20 Aug 2020
TR | RU | UK | KK | BE |

ATi Radeon R100 Series

ati radeon r100 series reflections

Radeon R100-based chipsets
CPU supported Mobile Athlon XP 320M IGP
Mobile Duron 320M IGP
Pentium 4-M and mobile Pentium 4 340M IGP, 7000 IGP
Socket supported Socket A, Socket 563 AMD
Socket 478 Intel
Desktop / mobile chipsets
Performance segment 7000 IGP
Mainstream segment 320 IGP, 320M IGP
340 IGP, 340M IGP
Value segment 320 IGP, 320M IGP AMD
340 IGP, 340M IGP Intel
Miscellaneous
Release dates March 13, 2002 300/300M IGP
March 13, 2003 7000 IGP
Successor Radeon 8500/9000/9100 IGP

The Radeon R100 is the first generation of Radeon graphics chips from ATI Technologies The line features 3D acceleration based upon Direct3D 70 and OpenGL 13, and all but the entry-level versions offloading host geometry calculations to a hardware transform and lighting T&L engine, a major improvement in features and performance compared to the preceding Rage design The processors also include 2D GUI acceleration, video acceleration, and multiple display outputs "R100" refers to the development codename of the initially released GPU of the generation It is the basis for a variety of other succeeding products

Contents

  • 1 Development
    • 11 Architecture
    • 12 R100's pixel shaders
  • 2 Implementations
    • 21 R100
    • 22 RV100
    • 23 RV200
  • 3 Models
  • 4 Competing chipsets
  • 5 See also
  • 6 References
  • 7 External links

Developmentedit

Architectureedit

The first-generation Radeon GPU was launched in 2000, and was initially code-named Rage 6 later R100, as the successor to ATI's aging Rage 128 Pro which was unable to compete with the GeForce 256 The R100 was built on a 180 nm semiconductor manufacturing process Like the GeForce, the Radeon R100 featured a hardware transform and lighting T&L engine to perform geometry calculations, freeing up the host computer's CPU

With respect to the 3D hardware within Radeon, the processor can write 2 pixels to the framebuffer and sample 3 texture maps per pixel per clock This is commonly referred to as a 2×3 configuration Of Radeon's competitors, the 3dfx Voodoo 5 5500 is a 4×1 design and the GeForce2 GTS is 4×2 Unfortunately, the third texture unit did not get much use in games during the card's lifetime because software was not frequently performing more than dual texturing

Radeon also introduced a new memory bandwidth optimization and overdraw reduction technology called HyperZ It basically improves the overall efficiency of the 3D rendering processes Consisting of 3 different functions, it allows the Radeon to perform very competitively compared to competing 2 and 4 pipeline designs

ATI produced a real-time demo for their new card, to showcase its new features The Radeon's Ark demo presents a science-fiction environment with heavy use of features such as multiple texture layers for image effects and detail Among the effects are environment-mapped bump mapping, detail textures, glass reflections, mirrors, realistic water simulation, light maps, texture compression, planar reflective surfaces, and portal-based visibility1

In terms of performance, Radeon scores lower than the GeForce2 in most benchmarks, even with HyperZ activated The performance difference was especially noticeable in 16-bit color, where both the GeForce2 GTS and Voodoo 5 5500 were far ahead However, the Radeon could close the gap and occasionally outperform its fastest competitor, the GeForce2 GTS, in 32-bit color

Aside from the new 3D hardware, Radeon also introduced per-pixel video-deinterlacing to ATI's HDTV-capable MPEG-2 engine

R100's pixel shadersedit

R100-based GPUs have programmable shading capability in their pipelines; however, the chips are not flexible enough to support the Microsoft Direct3D specification for Pixel Shader 11 A forum post by an ATI engineer in 2001 clarified this:

prior to the final release of DirectX 80, Microsoft decided that it was better to expose the RADEON's and GeForce's extended multitexture capabilities via the extensions to SetTextureStageState instead of via the pixel shader interface There are various practical technical reasons for this Much of the same math that can be done with pixel shaders can be done via SetTextureStageState, especially with the enhancements to SetTextureStageState in DirectX 80 At the end of the day, this means that DirectX 80 exposes 99% of what the RADEON can do in its pixel pipe without adding the complexity of a "05" pixel shader interface

Additionally, you have to understand that the phrase "shader" is an incredibly ambiguous graphics term Basically, we hardware manufacturers started using the word "shader" a lot once we were able to do per-pixel dot products ie the RADEON / GF generation of chips Even earlier than that, "ATI_shader_op" was our multitexture OpenGL extension on Rage 128 which was replaced by the multivendor EXT_texture_env_combine extension Quake III has "shader" files it uses to describe how materials are lit These are just a few examples of the use of the word shader in the game industry nevermind the movie production industry which uses many different types of shaders, including those used by Pixar's RenderMan

With the final release of DirectX 80, the term "shader" has become more crystallized in that it is actually used in the interface that developers use to write their programs rather than just general "industry lingo" In DirectX 80, there are two versions of pixel shaders: 10 and 11 Future releases of DirectX will have 20 shaders, 30 shaders and so on Because of what I stated earlier, RADEON doesn't support either of the pixel shader versions in DirectX 80 Some of you have tweaked the registry and gotten the driver to export a 10 pixel shader version number to 3DMark2001 This causes 3DMark2001 to think it can run certain tests Surely, we shouldn't crash when you do this, but you are forcing the leaked and/or unsupported driver down a path it isn't intended to ever go The chip doesn't support 10 or 11 pixel shaders, therefore you won't see correct rendering even if we don't crash The fact that that registry key exists indicates that we did some experiments in the driver, not that we are half way done implementing pixel shaders on RADEON DirectX 80's 10 and 11 pixel shaders are not supported by RADEON and never will be The silicon just can't do what is required to support 10 or 11 shaders This is also true of GeForce and GeForce2

Implementationsedit

Radeon DDR box R100 Radeon 7500 RV200 Radeon RV100 DDR

R100edit

The first versions of the Radeon R100 were the Radeon DDR, available in Spring 2000 with 32 MB or 64 MB configurations; the 64 MB card had a slightly faster clock speed and added VIVO video-in video-out capability The core speed was 183Mhz and the 55 Ns DDR SDRAM memory clock speed was 183 MHz DDR 366 MHz effective The R100 introduced HyperZ, an early culling technology maybe inspired by the Tile Rendering present in St Microelectronics PowerVR chips that became the way to go in graphic evolution and generation by generation rendering optimization, and can be considerend the first non tile rendering-based and so DX7 compatible card to use a Z-Buffer optimization These cards were produced until mid-2001, when they were essentially replaced by the Radeon 7500 RV200

A slower and short-lived Radeon SDR with 32 MB SDRAM memory was added in mid-2000 to compete with the GeForce2 MX

Also in 2000, an OEM-only Radeon LE 32MB DDR arrived Compared to the regular Radeon DDR from ATI, the LE is produced by Athlon Micro from Radeon GPUs that did not meet spec and originally intended for the Asian OEM market The card runs at a lower 143 MHz clock rate for both RAM and GPU, and its Hyper Z functionality has been disabled Despite these handicaps, the Radeon LE was competitive with other contemporaries such as the GeForce 2 MX and Radeon SDR Unlike its rivals, however, the LE has considerable performance potential, as is possible to enable HyperZ through a system registry alteration, plus there is considerable overclocking room Later drivers do not differentiate the Radeon LE from other Radeon R100 cards and the HyperZ hardware is enabled by default, though there may be visual anomalies on cards with HyperZ hardware that is defective2

In 2001, a short-lived Radeon R100 with 64 MB SDR was released as the Radeon 7200 After this and all older R100 Radeon cards were discontinued, the R100 series was subsequently known as the Radeon 7200, in keeping with ATI's new naming scheme

RV100edit

A budget variant of the R100 hardware was created and called the Radeon VE, later known as the Radeon 7000 in 2001 when ATI re-branded its products

RV100 has only one pixel-pipeline, no hardware T&L, a 64-bit memory bus, and no HyperZ It did however add HydraVision dual-monitor support and integrated a 2nd RAMDAC into the core for Hydravision

From the 3D performance standpoint, the Radeon VE did not fare well against the GeForce2 MX of the same era, though its multi-display support was clearly superior to the GeForce2 MX, however The Matrox G450 has the best dual-display support out of the GPUs but the slowest 3D performance

RV100 was the basis for the Mobility Radeon notebook solution

RV200edit

The Radeon 7500 RV200 is basically a die-shrink of the R100 in a new 150 nm manufacturing process The increased density and various tweaks to the architecture allowed the GPU to function at higher clock speeds It also allowed the card to operate with asynchronous clock operation, whereas the original R100 was always clocked synchronously with the RAM It was ATI's first Direct3D 7-compliant GPU to include dual-monitor support Hydravision3

The Radeon 7500 launched in the second half of 2001 alongside the Radeon 8500 R200 It used an Accelerated Graphics Port AGP 4x interface Around the time that the Radeon 8500 and 7500 were announced, rival Nvidia released its GeForce 3 Ti500 and Ti200, the 8500 and Ti500 are direct competitors but the 7500 and Ti200 are not

The desktop Radeon 7500 board frequently came clocked at 290 MHz core and 230 MHz RAM It competed with the GeForce2 Ti and later on, the GeForce4 MX440

Modelsedit

Main article: Comparison of ATI Graphics Processing Units

Competing chipsetsedit

  • NVIDIA GeForce 256 and GeForce2
  • PowerVR Series 3
  • 3dfx Voodoo 5
  • S3 Savage 2000

See alsoedit

  • Comparison of ATI Chipsets

Referencesedit

  1. ^ http://alexvlachoscom/graphics/
  2. ^ 1
  3. ^ 2
  • "ATI Radeon 256 Preview" by Anand Lal Shimpi, AnandTechcom, April 25, 2000, retrieved January 17, 2006
  • "ATI Radeon 32MB SDR" by Anand Lal Shimpi, AnandTechcom, October 13, 2000, retrieved January 17, 2006
  • "ATI Radeon 64MB DDR" by Matthew Witheiler, AnandTechcom, July 17, 2000, retrieved January 17, 2006
  • "Beyond3D 3D Tables" Beyond3Dcom, retrieved January 17, 2006
  • Vlachos, Alex Radeon's Ark demo, 2000

External linksedit

  • techPowerUp! GPU Database

ati radeon r100 series reflections


ATi Radeon R100 Series Information about

ATi Radeon R100 Series


  • user icon

    ATi Radeon R100 Series beatiful post thanks!

    29.10.2014


ATi Radeon R100 Series
ATi Radeon R100 Series
ATi Radeon R100 Series viewing the topic.
ATi Radeon R100 Series what, ATi Radeon R100 Series who, ATi Radeon R100 Series explanation

There are excerpts from wikipedia on this article and video

Random Posts

Timeline beyond October following the September 11 attacks

Timeline beyond October following the September 11 attacks

The following list contains certain dates beyond October 2001 involving the September 11 attacks ...
Smash Hits

Smash Hits

Smash Hits was a pop music magazine, aimed at teenagers and young adults and originally published in...
2014–15 USC Trojans women's basketball team

2014–15 USC Trojans women's basketball team

The 2014–15 USC Trojans women's basketball team will represent University of Southern California dur...
Trademark classification

Trademark classification

A trademark classification is a way the trademark examiners and applicants' trademark attorneys arra...