SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : 3DFX -- Ignore unavailable to you. Want to Upgrade?


To: bruce rogers who wrote (12910)5/22/1999 12:02:00 AM
From: Patrick Grinsell  Read Replies (2) | Respond to of 16960
 
Plaz, thanks for the response. I don't know if I made myself clear though. The bandwidth you stated is for AGP in general, not just AGP texturing. Why can't somebody come up with a solution (maybe even at the driver level) that's just as good as AGP texturing if it's necessary to move textures from main memory. I mean, is AGP texturing the ONLY way to move from textures from main memory. Of course not. Is there something special at the hardware level that gives AGP an advantage vs. a software only solution? If it isn't, then why are we (reviewers) making a big deal about it?

Pat



To: bruce rogers who wrote (12910)5/24/1999 12:31:00 PM
From: Plaz  Respond to of 16960
 
Just a quick note that the 48000 MB/sec is probably quoted for the internal framebuffer bandwidth (on chip DRAM) for the PS2.
I think the new Rambus chips run 16 bits per channel, so it's more like 3200 MB/sec for Rambus at 800 mhz x 2.


Thanks for the info. I wasn't quite sure how to calculate the rambus bandwidth; I thought the 48GB/sec seemed high. You're right, that's probably an embedded DRAM number.

Plaz