Announcement

Collapse
No announcement yet.

Granite Bay MoBo

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Granite Bay MoBo

    Xbitlabs posted infos on a Gigabyte mainboard based on Intels E7205 chipset.



    I wonder how these board will be priced. Heard rumors that the boards will be very expensive (300 - 400€ in Germany)
    With the P4 3.06GHz priced at about 800€ this hardware will remain a dream for me
    Hati
    Last edited by Hati; 13 November 2002, 07:33.

  • #2
    Nice....damn, I hope that comes out before Christmas. If not I wonder if I should just wait....
    System Specs:
    Gigabyte 8INXP - Pentium 4 2.8@3.4 - 1GB Corsair 3200 XMS - Enermax 550W PSU - 2 80GB WDs 8MB cache in RAID 0 array - 36GB Seagate 15.3K SCSI boot drive - ATI AIW 9700 - M-Audio Revolution - 16x Pioneer DVD slot load - Lite-On 48x24x48x CD-RW - Logitech MX700 - Koolance PC2-601BW case - Cambridge MegaWorks 550s - Mitsubishi 2070SB 22" CRT

    Our Father, who 0wnz heaven, j00 r0ck!
    May all 0ur base someday be belong to you!
    Give us this day our warez, mp3z, and pr0n through a phat pipe.
    And cut us some slack when we act like n00b lamerz,
    just as we teach n00bz when they act lame on us.
    For j00 0wn r00t on all our b0x3s 4ever and ever, 4m3n.

    Comment


    • #3
      I wonder... will dual channel ddr333 be available shortly?
      P4 Northwood 1.8GHz@2.7GHz 1.65V Albatron PX845PEV Pro
      Running two Dell 2005FPW 20" Widescreen LCD
      And of course, Matrox Parhelia | My Matrox histroy: Mill-I, Mill-II, Mystique, G400, Parhelia

      Comment


      • #4
        Originally posted by WyWyWyWy
        I wonder... will dual channel ddr333 be available shortly?
        I doubt that is needed, as dual channel ddr 266 already saturates the p4 fsb afaik, even at 533 Mhz.
        -Slougi

        Comment


        • #5
          But isn't Intel supposed to crank up the FSB to 667 (?) MHz after the transition to Prescott and 90 nm process.
          Heard there is a new chipset in the making (Springdale) for those CPUs that will come out next year.
          Good old Intel 'change chipsets as often as you can' game again.
          Hati

          Comment


          • #6
            Originally posted by Slougi

            I doubt that is needed, as dual channel ddr 266 already saturates the p4 fsb afaik, even at 533 Mhz.
            But hey! Some said ddr333 saturates 133fsb athlon too, then why is there ddr400? I think dual channel ddr333 is still needed for 533 fsb. Dual channel ddr400 is going a bit too far though...
            P4 Northwood 1.8GHz@2.7GHz 1.65V Albatron PX845PEV Pro
            Running two Dell 2005FPW 20" Widescreen LCD
            And of course, Matrox Parhelia | My Matrox histroy: Mill-I, Mill-II, Mystique, G400, Parhelia

            Comment


            • #7
              Iwill boards are announced for 11/18
              See:


              Hati

              Comment


              • #8
                ddr333 does saturate the athlon because the athlon runs at 133 while the memory runs at 166 so the processor cannot take advantage of the extra memory bandwidth due to its fsb speed, unlock your xp however and you can crank the fsb up and up i rin mine at 192 mhz which gives a pretty significant boost in 3d.
                is a flower best picked in it's prime or greater withered away by time?
                Talk about a dream, try to make it real.

                Comment


                • #9
                  Originally posted by WyWyWyWy
                  I wonder... will dual channel ddr333 be available shortly?
                  Yeah...SIS655 chipset...
                  Let us return to the moon, to stay!!!

                  Comment


                  • #10
                    SIS655 is the one Im waiting for. Released in next month.

                    Pe-Te

                    Comment


                    • #11
                      Originally posted by WyWyWyWy


                      But hey! Some said ddr333 saturates 133fsb athlon too, then why is there ddr400? I think dual channel ddr333 is still needed for 533 fsb. Dual channel ddr400 is going a bit too far though...
                      1) because most of the computer enthusiast market is gullible enough to believe that the bigger number is better.

                      2) most of the computer enthusiast market would use the larger number to convince their friends that theirs is better (and the jealous people buy more shiz)

                      3) overclockers. DDR400 memory can be used in even a DDR333 board when doing heavy overclocks.

                      DDR400 acctually performs slower on the nForce2 than DDR333. the added latency of running the memory asychronously is more than enough to negate any benefit having the extra memory bandwidth might provide.
                      "And yet, after spending 20+ years trying to evolve the user interface into something better, what's the most powerful improvement Apple was able to make? They finally put a god damned shell back in." -jwz

                      Comment


                      • #12
                        Originally posted by DGhost
                        1) because most of the computer enthusiast market is gullible enough to believe that the bigger number is better.

                        2) most of the computer enthusiast market would use the larger number to convince their friends that theirs is better (and the jealous people buy more shiz)

                        3) overclockers. DDR400 memory can be used in even a DDR333 board when doing heavy overclocks.

                        DDR400 acctually performs slower on the nForce2 than DDR333. the added latency of running the memory asychronously is more than enough to negate any benefit having the extra memory bandwidth might provide.
                        I couldn't have put it better myself. Of course, since northwoods overclock so damn well, not overclocking them does not make much sense. So in a way it is needed, but what you must also think off is that info to and from ram is not the only thing that moves through the FSB.
                        -Slougi

                        Comment


                        • #13
                          Hi,

                          I agree with you. But...


                          DDR400 acctually performs slower on the nForce2 than DDR333. the added latency of running the memory asychronously is more than enough to negate any benefit having the extra memory bandwidth might provide.
                          Why more mhz means less latency? I always wanted to know why... you know, most SDRAM can do CAS-2, but now most DDR can only do CAS-3, some better ones can do CAS-2.5...

                          Thanks.
                          P4 Northwood 1.8GHz@2.7GHz 1.65V Albatron PX845PEV Pro
                          Running two Dell 2005FPW 20" Widescreen LCD
                          And of course, Matrox Parhelia | My Matrox histroy: Mill-I, Mill-II, Mystique, G400, Parhelia

                          Comment


                          • #14
                            most ddr 400 is cas 2.5 or higher with their other timing set conservatively by SPD.

                            good 333 is cas2 with some tight timings.

                            but if you get very good ddr 400, manually adjust timings and then use it synchronously you get very low latencies...but athlon boards that do 200 fsb(400ddr) are hard to find

                            Comment


                            • #15
                              Originally posted by WyWyWyWy
                              Hi,

                              I agree with you. But...



                              Why more mhz means less latency? I always wanted to know why... you know, most SDRAM can do CAS-2, but now most DDR can only do CAS-3, some better ones can do CAS-2.5...

                              Thanks.
                              the higher the latency the more cycles are wasted waiting for the memory. because a memory chip can only do so much work because of its grade of manufacturing, many companies often release current generation memory modules running at higher speeds but also with higher latencies so there is very little increase in the amount of work it does. to make up numbers, if it was accessing the memory at 100 times a second but it was only on average taking 2 cycles to retrieve the memory, it would certainly do better that can access the memory 133 times per second but has to wait on average 3 cycles to get any data.

                              as far as running the memory asynchronously from the processor bus, take my lovely ascii art depicting the processor bus and memory bus:

                              Example #1 - Syncronous operation

                              -----_____-----_____-----_____-----_____ (processor)
                              -----_____-----_____-----_____-----_____ (memory)

                              Example #2 - Asyncronous operation
                              -----_____-----_____-----_____-----_____ (processor)
                              ----____----____----____----____----____ (memory)

                              every time that the signal both rises (---) and falls (___) that is considered one cycle.

                              the first example shows busses running at 4hz (it could also be a very small amount of time on a 133mhz bus) ... if you were to request data from the memory, it would require 1 cycle to put the request, another cycle for the memory to get it (unlikely), and then the third cycle for it to retreive it. there is no waiting because the signals are all lined up and no problems ensue. it would take pretty much 3/4ths of a second to retreive the data.


                              Now consider the second example the the top bus is the processor bus running at 4hz) and the bottom bus is the memory bus running at 5hz, (which could also work as 166mhz if you added a ton and a half more cycles onto the end). when the processor requests a piece of data from memory, it takes one cycle. however, the memory is currently in the middle of its second cycle so it has to wait until its 3rd cycle to acctually retreive the data. however, when its done the processor has already spent its second cycle waiting on the memory and is half way through the third cycle waiting for the data. by the time the processor can get the data the bus on its 4th cycle, and a whole second has been wasted by the time the processor sees the data.

                              now, i'm not an EE and my understanding of this stuff is pretty basic, so i'm probably wrong on details and terms. this is just my understanding of it. someone who has more of a clue on the topic feel free to correct me.

                              I'm also sure there are ways around this by using memory caching, different memory timings (i was assuming only a 1 cycle latency on the memory access, on most memory types it is higher on certain types of reads), etc...
                              "And yet, after spending 20+ years trying to evolve the user interface into something better, what's the most powerful improvement Apple was able to make? They finally put a god damned shell back in." -jwz

                              Comment

                              Working...
                              X