AMD Catalyst 10.2 & 10.3 驱动更新信息 催化剂 10.2 今天发布

Edison

While we were at CES, AMD briefed us about several things. We’ve already had a chance to tell you about the Redwood chip behind the Radeon HD 5670 and 5570, and the Cedar chip behind the Radeon HD 5450. There was one last thing we haven’t had a chance to tell you about yet, and that’s drivers. Along-side our briefings about AMD’s new cards, they spent some time discussing what would be happening with the Catalyst 10.2 and Catalyst 10.3 drivers.

The Catalyst 10.2 drivers come out today, while the Catalyst 10.3 drivers will be next month’s release. We’ll just jump right in to the heart of things and list what’s coming with each release:

Catalyst 10.2

   1. Crossfire profile – Per-game Crossfire profiles are being moved out of the drivers, so that AMD can distribute out-of-band profile updates.
   2. CrossfireX rearchitecture - Certain parts of AMD’s multi-GPU code has been moved from the 3D driver to another driver component; this segmentation is largely to benefit Fuzion integrated CPU/GPUs later this year.
   3. Ultra Low Power State – This feature for lower-idling on Crossfire slave cards has been in the entire 5000 series. However it’s only being enabled across the board starting with this release.
   4. Crossfire Eyefinity – Eyefinity now works with all Crossfire configurations, not just on the 5970..
   5. DisplayPort Audio – The 5000 series is now capable of outputting audio over the DisplayPort in accordance with the DisplayPort standard.

Catalyst 10.3

   1. Catalyst Mobility – AMD will once again be releasing Catalyst drivers for most Mobility GPUs.
   2. Eyefinity Bezel Correction – Eyefinity setups can finally be adjusted to compensate for the space occupied by monitor bezels.
   3. Eyefinity Per Display Controls – Per display color correction, particularly useful for mismatched monitors.  
   4. Eyefinity Multiple Groups
   5. Eyefinity Display Configuration Switching
   6. 3D Stereo driver hooks – AMD is implementing some low-level hooks to help 3rd-party 3D displays work with Radeon cards.

For today’s 10.2 release, much of what AMD is enabling has already snuck out in earlier driver releases in some form or another. December’s 9.12 Hotfix enabled Crossfire Eyefinity, DisplayPort Audio, and Ultra Low Power State, so it’s best to think of the 10.2 driver as the shipping version of what we saw with the 9.12 hotfix.

10.3 on the other hand has not been released in a hotfix form, so everything here is brand-new.
10.2: Ultra Low Power State Confusion & Crossfire E

181534013

英文帝翻译一下

Edison

10.2: Ultra Low Power State Confusion & Crossfire Eyefinity

When AMD was first briefing us on the 10.2 drivers, one of the first things they discussed was Ultra Low Power State (ULPS) support – this was probably a mistake. In our initial Radeon HD 5870 article covering the whole Evergreen architecture we discussed ULPS, albeit not under that name. ULPS was one of the many features AMD had briefed us about in September when they introduced the 5000 series, where ULPS allows AMD to power down the slave card(s) in a Crossfire configuration to a state even lower than idle. For the 5870/5970, this meant being able to reduce the slave(s) from 27W at idle to 20W under ULPS. This is only a 7W difference, but combined with other idle-efficient hardware it can become a notable difference. At the time it had been our understanding that this feature was enabled right out of the gate.
So imagine our confusion when at CES AMD is telling us that they are just enabling that feature for the entire 5000 series. Until that moment as far as we knew this feature was already enabled.

This started an almost immediate chain of confusion between ourselves and AMD. Terry Makedon – AMD’s Manager of Software Product Management – was giving the presentation and found himself at the end of an odd stare from us rather quickly. When we asked for clarification on this, he said that this feature was just finally going to be enabled in the mainstream Catalyst drivers, and that previously it had only been enabled for the 5970 in the launch drivers for that card. After expressing our displeasure on the issue, we quickly moved on due to time constraints.

The Radeon HD 5970: The card ULPS was practically made for

This brings us to February, where we started work on this article after wrapping up the Radeon HTPC investigation last week. Seeking further clarification on the issue and to once again express our displeasure with how this was handled, we sent an email to our favorite PR contact over at AMD, Evan Groenke. Evan has only been AMD’s PR frontman for hardware editors since the start of the year, and he’s been the guy largely responsible for helping us nail down all the issues we were seeing with the new Radeon 5000 series cards in HTPC use.

After sending that email early Friday morning, we got a phone call from Evan later that day… from the ski slopes. What was supposed to be a long weekend for him turned out to be a bit of a working weekend as he did what he could to dig in to the issue and to find a better explanation for us. Thanks to him we have a solid explanation on what’s going on and why our earlier tests were not as compromised as we once thought they were.

The key issue for AMD is that they did not consider the software side of ULPS to be ready for public use when the 5000 series launched, so it was not enabled in the Catalyst drivers at the time. ULPS was then enabled for the 5970 launch, where AMD was confident it was going to work correctly under the very limited conditions encountered by a single-card dual-GPU setup. But this was only enabled for the launch driver for the 5970 – it was never enabled in the mainline Catalyst drivers.
The issue for us, and why we were initially so displeased, was that it had never been communicated to us that ULPS wasn’t enabled from the beginning. We thought that it was enabled, AMD thought we knew that it wasn’t. So when we did our testing of the 5700, 5800, and 5900 series, we based all of our data on the idea that this feature was enabled, when in retrospect it wasn’t. Worse, it was enabled on the drivers we used to test the 5970 but not the 5870/5850, so our results would have the 5970 consuming less power at idle than what a real user would get if they used the mainline Catalyst drivers. This makes the results invalid, and was the source of our concerns.

Our original 5970 results

All of this was finally clarified when Evan was able to tell us two things: that the driver set we used to test the 5970 had been posted as a hotfix driver for the 5970 launch, and that it wasn’t the only driver with ULPS enabled. The former is of particular importance since coming from CES our interpretation had been that ULPS was not enabled on any public driver build, when in fact it just hadn’t been enabled on any mainline driver build – it had in fact been available in public hotfixes such as the 5970 launch driver. The latter is important because it was an undocumented feature of the 9.12 hotfix, which as we explained earlier is the precursor to much of what’s in the 10.2 driver being released today. So if you used the 9.12 hotfix, then you’ve already been enjoying ULPS on your 5000-series Crossfire setups.

With that in mind, here’s what the issue ultimately boils down to: Unless you were using the 5970 launch driver or the 9.12 hotfix, you have not been enjoying the benefit of ULPS. Specifically, unless you have used those drivers your idle power usage on the 5970 would have been around 7W higher than what we found in our initial 5970 review. It’s only now with today’s 10.2 driver that this is finally being enabled for customers using the mainline driver. If that’s you, then the 10.2 drivers should reduce your idle power usage some.

To settle this point, here we have a re-test of the 5970 using the 10.1 Catalyst drivers, and the 10.3 beta drivers AMD has provided us.

Our new 5970 results. Note: This is a different test setup than for our original results

The end result: a difference of 8W, out of 170W, meaning enabling it reduces idle power usage by around 5% on our overclocked Core i7 920 setup.

Moving on from ULPS, we have Crossfire Eyefinity, one of the other features that was previously exposed in the 9.12 hotfix driver. Much like ULPS, this feature was originally only enabled for the 5970 while AMD worked out the kinks in the technology. Since the 5970’s launch this feature has made a great deal of progress – it’s no longer a whitelist feature that only works on certain games, but rather it’s a blacklist feature where AMD only disables it on games where there are known issues.

We strongly suspect that anyone that had a vested interest in a Crossfire Eyefinity setup with a pair of 5800/5700 series cards already is on the 9.12 hotfix, but nevertheless this brings Crossfire Eyefinity in to the mainline drivers for everyone else.

Edison

10.2: Crossfire Profiles, DisplayPort Audio, & Crossfire Rearchitecture

The last big feature coming with the 10.2 drivers is a change to how AMD profiles games for Crossfire support. Currently the profiles are integrated in to AMD’s drivers, meaning AMD has to produce a complete hotfix driver whenever they need to publish what’s otherwise a minor profile update to enable Crossfire support for a game. This is clumsy for the user (it’s 110MB+), a source of extra work for AMD, and a nuisance for all parties since it means it can take quite some time before Crossfire support gets enabled on a game.

For 10.2, AMD is finally stepping up to the plate and separating the Crossfire profiles from the drivers. The profiles are now stored in a separate encrypted file (atiapfxx.blb) that can easily be updated whenever AMD needs to publish a new set of profiles. AMD will now be able to offer a small executable download that will install the latest profile set, and can update that out-of-band without interfering with driver releases and development.

For NVIDIA users, this is nothing new. NVIDIA has offered the same feature for quite some time, so this brings AMD up to parity with NVIDIA on the matter.  The recently released Mass Effect 2 is a great example of this: NVIDIA was able to publish a half-megabyte profile update, while AMD had to publish a 112MB Catalyst hotfix. With profile support, AMD will now be able to publish small (and potentially frequent) profile updates just like NVIDIA has been doing.

The files in a Catalyst profile update

There is still going to be one difference between the two companies however, and that’s letting end-users meddle with profiles. NVIDIA has allowed end-users to write and edit profiles for games (including through the use of tools like nHancer) while AMD has not. This will not be changing – AMD users will still not be able to write their own profiles.

When we asked Terry about this at CES, he said that AMD’s position is that they believe users are better off with professionally created and validated profiles, rather than enthusiast created profiles that may end up having problems. We don’t disagree with the logic of this statement, but as enthusiasts we have never been above getting our hands dirty and/or creating problems in the process of solving them (it’s half the fun!). AMD absolutely needs to publish profiles for games, but we still want to see AMD relinquish some of their control of game profiles so that enthusiasts have the ability to play with them if they desire.

To that end, we did some digging and at least in the 10.3 driver set being sampled to us, AMD includes a utility called atiapfxx that can read and write the encrypted files that store profiles. However in spite of its proclaimed ability to decrypt AMD’s profiles, we have been unable to successfully do so as the tool keeps crashing. Furthermore AMD declined to provide us with any kind of sample of what an unencrypted profile (which would be in XML form) would look like, so we don’t even know quite what’s in a profile. Finally, it looks like AMD is signing the profiles with a key (not included) judging from the command-line options in the utility. So in spite of having moved profiles out of the drivers, it doesn’t look like enthusiasts are any closer to getting to write profiles for AMD’s drivers.

Moving on, we have the addition of DisplayPort Audio to AMD’s drivers. This is another 10.2 feature that originally showed up in the 9.12 hotfix drivers, so its inclusion here should come as no surprise. The DisplayPort standard allows for audio to be transmitted along-side the video stream, and while AMD’s hardware has supported it, it’s only finally being enabled in the drivers. Right now it’s a forward-looking feature – since DisplayPort isn’t meant to replace HDMI for TV connections, it’s only used by a few monitors that have some kind of integrated audio capabilities such as built-in speakers or a built-in headphone jack, such as Dell’s U2410.

Finally, AMD has been doing some work to rearchitect how Crossfire works at the driver level, and those changes are in the 10.2 drivers. AMD has moved some Crossfire code from the 3D driver to a separate driver component as a forward-looking gesture. By doing this, AMD is getting the Catalyst drivers ready for future products such as Llano, AMD’s first CPU/GPU Fuzion product. The ultimate purpose is going to be to allow them to better combine IGP and discrete GPUs, much like Hybrid Crossfire did on AMD’s earlier products but with a greater tolerance for feature differences. Bear in particular mind that AMD’s next IGP (before Fuzion) will be DX10.1 based, while AMD’s current GPUs are DX11 based.

Llano: The reason for the Crossfire rearchitecture

Edison

10.3: Eyefinity Bezel Correction, Grouping, & Per-Display Controls

Following CrossFire Eyefinity support across the board in Catalyst 10.2, Catalyst 10.3 finally enables per-display color controls - which is particularly handy if you don't have a set of identical displays:

Each display gets color correction, saturation, brightness, contrast and temperature control. To test this I had a triplet of identical Dell 24" displays connected via HDMI, DisplayPort and DVI. An artifact of the premature nature of the drivers was that I couldn't control color temperature on the display connected via HDMI.

Another feature for users with sub-optimal display setups is bezel correction. If you have particularly thick bezels, or displays of differing bezel thickness, Catalyst Control Center now lets you compensate through a fairly easy to use tool.

What you're seeing above are two displays, the bezel divides the yellow triangle. Using the controls on the right you adjust to compensate for bezel thickness. Below is what it looks like on all three displays:

The one key feature that AMD needs to enable support for is real-time aspect ratio correction in games. Unfortunately, despite AMD's efforts, Eyefinity remains something that is poorly supported by many important titles. Yes you'll get full resolution support in most games, but what you'll end up with is a super wide resolution with content stretched to fit it. Currently Widescreen Fixer is one of the best ways to force aspect ratios not properly supported by games.
The easiest way to get around the aspect ratio issues is to simply run in 3x1 portrait mode:

My three 16:10 panels rotated in portrait mode offer a 1.875:1 aspect ratio, not too far off of the 1.6:1 native AR. In landscape mode the aspect ratio is an out of this world 4.8:1 and causes many games to let you play in a very high resolution distorted world:

AMD has apparently done nothing to fix this as recently released titles like Bioshock 2 are simply unplayable in 3x1 Landscape Eyefinity mode. The most important Eyefinity feature we're lacking is developer support at this point. AMD has had a tremendous headstart over NVIDIA in the DirectX 11 GPU generation, to not have this working by now is unacceptable.

The final Eyefinity features supported by Catalyst 10.3 are support for multiple groups and fast switching between Eyefinity modes. Multiple Eyefinity groups could be used to support configurations like one single large surface made up of two monitors and one additional monitor as a desktop extension.  This becomes more useful as you get into 4, 5 and 6 display configurations which should be enabled sometime this year.

It's pretty quick to switch between cloned and single large surface display mode (in case you're tired of your start menu being multiple feet to your left but still want to keep the immersive gaming mode). Just a right click and an unnecessarily deep couple of menus and you're there.


You're also supposed to be able to define profiles that include your Eyefinity configuration, to allow you to switch between 3x1 and 1x3 for example if you happen to be some sort of crazyperson and like to reorganize your monitors frequently. Unfortunately neither groups nor profile switching worked reliably for me. The last profile I would create seemed to overwrite the previous one. AMD has until March to finalize the drivers, so I'm guessing these bugs will be gone by then (famous last words).

Edison

10.3: AMD’s New Mobility Driver Program



Last month, we discussed AMD’s announcement of the ATI Mobility Radeon 5000 Series, the first DX11 capable mobile GPUs. On paper, the lineup looks very capable, but we had a few concerns with the announcement. The first question is one of hardware availability: we know ATI has the GPUs available, but we didn’t know when manufacturers would start shipping actual laptops using the GPUs—or which GPUs they would use. The other more pressing concern is one of driver support. The best graphics hardware on the planet will do you no good if your drivers aren’t up to snuff, and while ATI’s desktop drivers have come a long way we haven’t had very good experience with getting official drivers for mobile parts.

Before we get to the latest announcement, it’s worth noting that ATI is no stranger to providing updated mobile drivers. Six years ago, ATI began releasing drivers on their website that could work with any ATI-equipped laptop. The only problem was that the program was opt-in, so the laptop manufacturers needed to agree to participate. For whatever reason, OEM buy-in never took off, so the vast majority of AMD-equipped laptops during the past six years have only received sporadic driver updates. On a side note, yes, we know it was possible to hack the desktop drivers in order to install them on ATI laptops, but hacked drivers generally disable hotkeys and power saving features outright, and performance isn’t always as high as official drivers. Getting drivers to install is only half the battle; making them work is another matter.

NVIDIA launched a similar mobile driver program in 2008 called Verde, with the goal of providing quarterly driver updates to all supported laptops. Again, the program is opt-in, but NVIDIA has managed to get far more support for their Verde drivers. We’ve covered NVIDIA’s mobile drivers quite a bit during the past year, including the unprecedented accomplishment of providing Windows 7 drivers for all of their recent (8000 series and newer) mobile and desktop drivers on the same day. Since the Win7 release, however, NVIDIA has returned to their quarterly driver updates. AMD informed us that with NVIDIA’s success at the Verde program, they decided it was time to reevaluate their program and make it better.

Today, AMD looks to change what we can expect from their mobile driver programs in some fundamental ways. They're launching a new mobile driver program, but there are some major differences between the AMD program and NVIDIA’s program. First and perhaps more important, the new AMD program will be opt-out rather than opt-in. Sadly, many OEMs simply can’t be bothered with agreeing to opt in to driver programs like these—they like having control over driver updates, most likely, but sometimes they’re just too busy to be bothered. Going opt-out means more laptops will be supported by the AMD drivers, since a manufacturer will have to request to not be included. The second difference is only slightly less important: AMD is committed to providing monthly driver updates for mobile GPUs. Quarterly driver updates is good, but there’s no question that getting a monthly driver update will take care of all but the most demanding users. Note that the new driver program will only cover Windows Vista and 7, while XP will remain on the old opt-in model—but since most modern laptops don’t use XP, this isn’t a serious concern.

As far as the drivers are concerned, AMD/ATI informs us that the same basic driver will be available for both desktops and mobile parts, but the mobile drivers will include some extras focused on mobility features. Power saving will be more important on laptops, obviously, but the mobile drivers also need to include all of the hooks to work with laptop hotkeys like brightness adjustment, external display toggle, etc. The current plan is to roll all of the drivers out in a single package, so we expect the new Catalyst drivers to get a bit larger but they'll cover even more products. All ATI Mobility Radeon 2000, 3000, and 4000 parts should be supported, unless a manufacturer chooses to opt out of the program. (We would expect this to occur primarily with business focused laptops, i.e. the Dell Vostro line, where manufacturers and IT departments like to have more control over what drivers get installed.) “Future ATI Mobility products” will also be included, which should mean the latest 5000 series as well as future hardware.

The official launch of AMD’s new mobile drivers will begin with the public release of Catalyst 10.3. We won’t know for sure until March how the actual roll-out works, but at present we don't see any reason for concern. AMD has been providing updated drivers at the request of OEMs for a long time, so now they're just doing that without the request part. We do have pre-release 10.3 drivers for testing, but unfortunately we don’t have any current mobile ATI hardware to test. We installed the drivers on an older laptop with HD 3670 drivers and found they worked without any problems, including Blu-ray support, so that’s a good sign. We expect to receive some notebooks with HD 5000 GPUs shortly, so we’ll test the public drivers in the future as applicable. Naturally, the other new features for the Catalyst drivers will carry over to the mobile side, so CrossFire profiles in a separate XML file will be supported (i.e. on the Alienware M17x and ASUS W90 CrossFire notebooks).

There remain a few things we want to discuss regarding notebook drivers and platforms. First, NVIDIA recently launched their Optimus platform, which is the best implementation of switchable graphics we’ve tested to date. ATI supports switchable graphics as well, but the technology is more akin to NVIDIA’s gen2 technology: hardware muxes with a software switch, screen blanking, programs that can cause blocking, etc. The drawbacks of such an approach are the same for AMD as they are for NVIDIA: increased motherboard complexity, signaling issues, validation and testing all yield a more expensive product. The other problem is that you need drivers for both the IGP and discrete GPU in a single package as far as we’re aware, so we’re not sure how ATI’s updated mobile drivers will address this concern—we’ll look into it more when we get a laptop with ATI switchable graphics. (Of course, Optimus does have a few drawbacks, the biggest being that it is currently Win7 only. Since it’s a software solution, NVIDIA could support OS X and Linux as well should they choose, but the focus is definitely on Windows 7.)

After our AMD Mobility Radeon 5000 article, we heard from at least one source that it was the most negative of all the articles regarding the new ATI hardware. (We've heard the same thing regarding some of our NVIDIA mobile coverage in the past, so we figure we must be doing something right.) If you read the article, you’ll find that nearly all of our negatively revolved around the question of drivers. At the time, AMD told us they would have an announcement regarding updated mobile drivers in the near future, but it took almost six months from the time we first heard about NVIDIA's Verde until we actually got the first drivers, and even then those drivers were several revisions behind the desktop drivers. To say that we weren't holding our breath would be a gross understatement.

Now, with the new mobility driver program, AMD is set to clear the air and make it easy for us to recommend gaming laptops with Radeon graphics. That’s good, since right now the only DX11 hardware in a laptop will have to come from AMD. We expected something similar to NVIDIA's Verde program, but AMD has committed to something much more ambitious, and it all starts next month. If you’re looking to play Battleforge, DiRT2, Aliens vs. Predator, STALKER: Call of Pripyat, Battlefield: Bad Company 2, or Lords of the Ring Online with DX11 features enabled, AMD’s 5000 hardware is the only current mobile solution. It will remain so until NVIDIA gets around to announcing and shipping a new mobile architecture, which looks to be at least a month or two away, and likely more.

If you want to take the plunge, HP’s ENVY 15 is already available with the HD 5830, as is the new ASUS G73JH with HD 5870. Acer/Gateway also have the Aspire 5740G/7740G and NV59/NV79 with HD 5650 hardware. The only catch is that none of these products support switchable graphics, so battery life definitely isn’t going to be a major feature. If you’re more interested in performance, however, those are all some very potent gaming solutions. The ASUS G73JH in particular looks very impressive, with a Core i7-720QM CPU, the aforementioned HD 5870 1GB, and a whopping 8GB of DDR3 memory—all priced at just $1600 online. That looks to be a ton of mobile gaming goodness at an extremely attractive price, and thankfully we no longer need to worry about driver support.

Edison

10.3: Stereo Driver Hooks & Final Thoughts

The last feature making its appearance in next month’s Catalyst 10.3 drivers will be the inclusion of some underlying hooks in the drivers for 3rd party 3D display hardware. AMD hasn’t been completely ignoring NVIDIA’s success with 3DVision, and while they’re not getting directly in to the 3D arena like NVIDIA has, they’re going to be providing the tools for 3rd parties to get in if they want to.

The big change here is that they’re going to provide driver hooks for 3rd party products to use to improve and simplify the operation of those products. One example AMD is throwing out is that their drivers will now be able to do quad buffering so that 3D products can double-buffer each eye separately. These hooks will also allow the hardware to output stereo images at 120Hz similar to how NVIDIA implements 3DVision, so that each eye can be offered images at 60Hz without needing to use a more esoteric solution such as iZ3D’s double-DVI setup.

Our expectation here is that with these new hooks a 3rd party will offer a 3DVision-like kit utilizing shutter glasses and a 120Hz monitor, although the quad buffer changes in particular are rather generic and can be used (not to mention necessary ) for any other form of 3D technology that takes off. Nothing has been announced yet, but it’s likely only a matter of time.

Final Thoughts

Although AMD is always working on the Catalyst drivers, major updates tend to come in spurts and this is a prime example of that case. With the 10.2 and 10.3 releases we are seeing the first post-launch driver drop for the Radeon 5000 series. Some of the things we’re seeing today such as Catalyst profiles and fully-functional Ultra Low Power State are things we would have liked to see at the 5000 series launch, while other things such as the new Eyefinity tweaks are going to be a nice addition to the existing capabilities of the hardware.

For the Catalyst profiles and Mobility driver support in particular, it’s going to be worth keeping an eye on how well AMD does in implementing these things. Profile support is simply a matter of being timely with new game releases, although we’re still going to ask for the ability to write our own profiles anyhow. As for the Mobility driver program, moving from an opt-in to an opt-out model should prove to make the program much more successful than AMD’s previous effort, but the one remaining wildcard is what OEMs have opted-out of the program, and with what products. AMD is only expecting business products to be opted-out, but as far as we know, any OEM can opt-out for any reason, so there’s still a remote chance of snatching defeat from the jaws of victory.

There’s also one thing we were hoping to see in the 10.2/10.3 drivers which has not come to pass, and that’s OpenCL support. AMD is continuing to only provide OpenCL runtime functionality through the installation of the Stream SDK, which means even though AMD’s 4000 and 5000 series hardware is capable of OpenCL, none of those cards can run those programs out of the box. AMD’s current reason is that they don’t want to expand the size of their drivers any further (they’re currently 123MB for the 10.3 betas) which is a valid concern looking at the size of their OpenCL runtime, but at the same time we can’t imagine this is good for OpenCL adoption in the long-run.

Who is going to develop applications using OpenCL if half your user base (not counting Intel IGP users) can’t run your application out of the box? Even worse, you currently need to sign up for an AMD Developer Central account before you can download the Stream SDK in order to get the runtime - and what user is going to do that? NVIDIA is way ahead of AMD here, having shipped OpenCL support in their drivers for several months now, and they’ve been able to do so while keeping their drivers at about the same size as AMD’s (let’s not forget the PhysX runtime either). Unless AMD expects everyone to go the DirectCompute route (in which case we can kiss cross-platform GPGPU usage goodbye) AMD’s GPGPU efforts are currently stuck in place.

Finally, from a testing perspective the 10.3 drivers are still in beta, but much like the Catalyst 9.12 hotfix was to the 10.2 driver launching today, the 10.3 driver set we’re working with has been shaping up rather well. AMD hasn’t told us when they’ll be launching besides the fact that it will be in March, but based on the drivers we’re seeing we wouldn’t be surprised if it was an early launch rather than a mid-month or later launch as AMD is common for AMD.

Edison

原文：http://www.anandtech.com/video/showdoc.aspx?i=3743&p=1

基本上只要有初中水平都能读懂这些简单的英文。

ngsms

我在想管理员最近是不是在玩A卡。

容和仔

原文：

基本上只要有初中水平都能读懂这些简单的英文。
Edison 发表于 2010-2-17 21:22

    不是吧，我起码是本科了，老本科了，怎么一个字都不认识啊

什么？

希望别像CAT10.1那么糟糕。。

IPO

我大学毕业，看不懂英文啊