specs

Latest

  • UPnP Forum releases v2 specs

    by 
    Donald Melanson
    Donald Melanson
    07.13.2006

    The UPnP Forum has rolled out version two of its UPnP specifications, which promises to make it easier for users to network various devices together, while at the same time keeping companies happy by ensuring that all the content flying around remains protected by DRM. Some of the biggest additions to the v2 specs come in the UPnP AV MediaServer and MediaRenderer device classes, which encompass everything from PCs, DVD players, and PVRs to televisions, stereo systems, and portable media players. The Forum's mostly talking in generalities in their announcement, but it looks like among other things, the new specs define how programs and other digital content is recorded and stored for later viewing. You'll also be pleased to know that the new specs are also fully backwards compatible with the v1 specifications, so your gear's not obsolete just yet -- well it is, but not because of this upgrade.[Via eHomeUpgrade]

  • Another blurry Treo "Hollywood" shot, plus specs?

    by 
    Chris Ziegler
    Chris Ziegler
    07.12.2006

    Palm's sieve-like reputation for keeping a lid on unreleased devices continues to the current round of Treos in the pipeline, and we're happy to feed the fire today with possible specs of the upcoming "Hollywood" accompanied by the obligatory hastily-snapped shot (blurred here to protect our valiant tipster). Though we still don't fully understand the relationship between this bad boy and Cingular's upcoming "Nitro" and "Lennon," it's said that we're looking at an antenna-less GSM Treo rocking Windows Mobile 5, 128MB of internal storage, and a 412MHz XScale core, all gussied up in a package "considerably lighter" than its 700w stablemate. If our source is accurate, all this goodness will drop sometime this September -- not a moment too soon for Treo fans on GSM carriers getting a little jealous of their CDMA brethren. Naturally, skepticism is in order here, but the engraving on the device lends some validity to the thought that it's a prototype, and this all lines up pretty nicely with Cingular's roadmap, no?[Thanks, anonymous tipster]

  • PS3 smoke and mirrors?: IBM stats

    by 
    Ken Weeks
    Ken Weeks
    04.30.2006

    I don't pretend to be an expert on matters technical, but reader Crimson Angelus sure sounds like he knows what he's talking about:At this year's E3 (or thereabouts) Sony proclaimed that their processor could achieve 200GFLOPS! However, according to IBM's white paper, only 155.5 GFLOPS was actually achieved (Table 4). BUT, IBM's tests used all 8 SPEs. The PS3 will only use 7 SPE's, due to manufacturing yield issues.The efficiency of the Cell is 75.9% (Table 4), with of a theoretical peak of 201GFLOPs (Figure 5)--running 8 SPEs at 25.12GFLOPS apiece (Table 2). Similarly, the theoretical peak for the PS3's processor will be 176GFLOPS, using 7 SPEs at 25.12GFLOPS apiece. Assuming the same 75.9% effieciency, we could easily interpolate the PS3's Cell to be capable of 133.6GFLOPS.The take home message is that with the PS3 being cabable of 133.6 GFLOPS and the Xbox 360 being capable of 115.2 GFLOPS, the PS3 is not nearly as far ahead of the Xbox 360 as we were lead to believe. we should expect relatively similar power coming from both consoles, processor power, and ease of programming all considered.Not to mention that one of the SPE's in the PS3 are reserved for the OS and the bottlenecking of the data transfer between the SPE's and the on board memory. I see the 360 hand in hand with a gaming Revolution taking home this next round at least, if not the whole cake over time.He's working off this data, which has been around for a while.So much for "twice the processing power,"  though I'm interested to learn just how many GFLOPS it takes to enter the fourth dimension. Any tech-minded PS3 fanboys care to argue, or are you still busy making fun of the Wii fanboys?

  • Revealed: Revolution CPU and GPU specs

    by 
    David Hinkle
    David Hinkle
    03.29.2006

    Matt promised to post on the Revolution's "Hollywood" and "Broadway" GPU and CPU  tonight, and he has delivered with the goods. Supposed sources possessing development kits of all shapes and sizes have confirmed what the final specs are."IBM's "Broadway" CPU is clocked at 729MHz, according to updated Nintendo documentation. By comparison, GameCube's Gekko CPU ran at 485MHz. The original Xbox's CPU was clocked at 733MHz. Meanwhile, Xbox 360 runs three symmetrical cores at 3.2GHz.""Revolution's ATI-provided "Hollywood" GPU clocks in at 243MHz. By comparison, GameCube's GPU ran at 162MHz, while the GPU on the original Xbox was clocked at 233MHz. Sources we spoke with suggest that it is unlikely the GPU will feature any added shaders, as has been speculated. The 'Hollywood' is a large-scale integrated chip that includes the GPU, DSP, I/O bridge and 3MBs of texture memory." Matt also goes on to write:"Revolution will operate using 24MBs of "main" 1T-SRAM. It will additionally boast 64MBs of "external" 1T-SRAM. That brings the total number of system RAM up to 88MBs, not including the 3MB texture buffer on the GPU. By comparison, GameCube featured 40MBs of RAM not counting the GPU's on-board 3MBs. The original Xbox included 64MBs total RAM. Xbox 360 and Playstation 3 operate on 512MBs of RAM."So it's pretty much confirmed that the Revolution is a direct extension of the GameCube hardware, just upgraded, without all of the bells and whistles Sony and Microsoft seem to think that are needed in their next generation of consoles. All the specs in the world don't matter unless you have engaging titles on your console and thankful that has never been a problem when it comes to the house Mario built.

  • How the Xbox 360 works

    by 
    Ken Weeks
    Ken Weeks
    03.18.2006

     HowStuffWorks has a dumbed-down  (and probably old) primer on the inner workings of  the Xbox 360 console that doesn't tell you much more than what's on the packaging. Nothing new for the hardcore, but best to re-familiarize yourself with basics before wading into the technical minutia of DVD drive hacks. [Thanks Nick M.]