PCI Backwards compatibility


Recommended Posts

Then why would this:

http://www.znyx.com/products/pdf/ZX370_Datasheet_02_web.pdf

say this:

64 bit /66 MHZ PCI bus connection

Backward compatible with 32 bit, 33 MHz PCI slots

and this:

http://engr.smu.edu/~niranjan/pci.html

say this:

A transparent 64-bit extension of the 32-bit data and address buses is defined, doubling the bus bandwidth and offering forward and backward compatibility of 32-bit and 64-bit PCI Local Bus peripherals. A forward and backward compatible 66 MHz specification is also defined, doubling the bandwidth capabilities of the 33 MHz definition.

and this:

http://www.adaptec.com/worldwide/product/m...SI%2F&type=SCSI

say this:

A 66-MHz bus is capable of operating at 0 to 66 MHz speeds. 33-MHz devices operate at 33 MHz in a 66-MHz bus; likewise 66-MHz devices operate at 33 MHz in a 33-MHz bus.

And this:

http://www.attotech.com/software/files/tec...PCIFC3300TS.pdf

say this:

PCI 2.2 compliant? 64-bit/66 MHz PCI (backward compatible with 32-bit and 33 MHz PCI)

and this:

http://www.qlogic.com/news-events/details/...ails.asp?id=490

say this:

The ISP2100A is specially targeted at SCSI storage and clustering applications and combines a 66 MHz, 64-bit PCI host interface (fully backward-compatible with 33 MHz, 32-bit PCI systems)

and so on

Thanks again guys, I'm sure your expert opinions on the subject are more valid than the above, particularly adaptec's. Sometimes I wonder why I bother asking questions, all I ever get are answers from people who only think they know what they're talking about.

curious..... why would you post a question that you already have the answers for? interesting.......if you were curious if it would work still, why ask your question, just go ahead and plug the card in and bootup. if you fry the card, return it to the place you bought it from and give them the information that you found. it just seems rude, or downright mean, to ask the question, let people give their own answers and then shoot them down for trying to help out. just my opinion, but i hope it makes you think first before you continue posting.

:whistle:

barnabas

I didn't know the answer, I researched it when the answer that I got did not agree with what I thought the case to be. Knowing that 99% of what people tell you is wrong, I decided not to put my faith in people who didn't even think it would fit, and so I looked it up myself, and was not surprised to find that my original thought was correct.

And I'm normally not rude but it angers me more than anything when people just post without knowing a damn thing about what they're talking about. Erroneous information for the sake of post counts helps no one. That's why I usually would put a disclaimer to the effect of "if you don't know what the hell you're talking about, don't tell me what you think you know." but that usually results in people getting cranky over my rudeness. Well now I can conveniently refer to this whenever I get such whining.

Edited by darkmark327
I believe the way that some PCI-X cards are designed, they are backwards compatible with regular PCI slots, but you get reduced speed/bandwidth/size. To take full advantage of it, you will need a motherboard that has 64-bit PCI-X slots.

Yeah, I realize I will get reduced performance, I will be using 32-bit/66 MHz at 33 MHz, so the effective bandwidth goes from 266 MB/s to 133. It's 3 hard drives (RAID 0 + Parity) so I don't foresee having fully utilized such bandwidth anyway. The 5-drive version uses 64-bit/66 MHz which makes sense, because then you'd probably break the 266 MB ceiling, especially if you used all raptors.

Also, all PCI-X cards are backwards compatible with PCI, it's part of the specification.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!