In adjustment to baddest the able accessory driver, NuBus included an ID arrangement that accustomed the cards to analyze themselves to the host computer during startup. This meant that the user didn't accept to configure the system, the affliction of bus systems up to that point. For instance, with ISA the disciplinarian had to be configured not alone for the card, but for any anamnesis it required, the interrupts it used, and so on. NuBus appropriate no such configuration, authoritative it one of the aboriginal examples of plug-and-play architecture.
On the downside, while this adaptability fabricated NuBus abundant simpler for the user and accessory disciplinarian authors, it fabricated things added difficult for the designers of the cards themselves. Whereas a lot of "simple" bus systems were calmly accurate with a scattering of input/output chips advised to be acclimated with that CPU in mind, with NuBus every agenda and computer had to catechumen aggregate in a platform-agnostic "NuBus world". Typically this meant abacus a NuBus ambassador dent amid the bus and any I/O chips on the card, accretion costs. While this is a atomic exercise today, one that all newer buses require, at the time in the 1980s NuBus was advised circuitous and expensive.
On the downside, while this adaptability fabricated NuBus abundant simpler for the user and accessory disciplinarian authors, it fabricated things added difficult for the designers of the cards themselves. Whereas a lot of "simple" bus systems were calmly accurate with a scattering of input/output chips advised to be acclimated with that CPU in mind, with NuBus every agenda and computer had to catechumen aggregate in a platform-agnostic "NuBus world". Typically this meant abacus a NuBus ambassador dent amid the bus and any I/O chips on the card, accretion costs. While this is a atomic exercise today, one that all newer buses require, at the time in the 1980s NuBus was advised circuitous and expensive.
No comments:
Post a Comment