[Info-vax] X86 first boot? - A Really Stupid Question

[Dave Froble]

On 3/29/2019 2:48 PM, Michael Moroney wrote:
> David Turner <islandcomputersuscorp at gmail.com> writes:
>
>> Seeing as how incompatibilities exist even on 1 Alphaserver or Integrity
>> server, how the hell is VSI going to maintain drivers/support for
>> options and servers and workstations running VSI x86-64 VMS?
>
>> I mean, just buy a DELL server for example.
>> Even under the same part number,  1 server may have a Broadcom network
>> chip on the board, while the other may have an intel chipset.
>> Same goes for SAS controllers, with ever changing firmware levels...
>
>> And the support for a multitude of different branded servers using ever
>> changing chipsets and cpus?
>
>> Even Proliant servers, which are more parts-vendor stable, come from the
>> manufacturer with different firmware levels. Everything seems to go out
>> to the highest bidder on memory products, USB chips.....
>
>> This is going to be TRUE HELL unless there is a very small and finite
>> date code, product code, firmware version etc.
>
>> Otherwise it is going to be a Sh*tstorm for VSI Support.....
>
>> Methinks 2 very specific servers - HPE only - with some seriously
>> limited options and expansion capabilities, is the only way forward...
>
>> My opinion but experience does sometimes trump logic.
>
> I've wondered about that.
>
> VMS configuration typically recognizes the device and loads the correct driver for
> it, if known. Many drivers can deal with subtypes/firmware variations/etc. The
> problem is writing a bazillion drivers for a bazillion different devices.
>
>
> How does Linux/BSD deal with all the hardware/need for drivers?
> Can they handle that because they have a zillion people willing to develop drivers?

In many cases, the device mfg writes most or all of the driver, for 
WEENDOZE, so they can sell the device.  Some also write for Linux, but 
not all do.  I've seen user complaints about not being able to get a 
specific device working on Linux.  None are, and probably won't, for VMS.

With the video now on CPU chips, one would think there is some 
standardization, but, I don't have a clue.

> Another issue are companies who may not want to release proprietary device info to
> some rinky-dink company called VSI. I saw this myself once long ago, when I asked
> for information on talking to a UPS over a serial port.  The person I talked to
> seemed willing at first but later wouldn't, and it sounded like an order not to from
> above.
>
> And another is despite specifications, some companies have an attitude that if it
> works under Windoze, ship it! (and M$ may have their own deviations from the specs)
>

As an example, the motherboards I'm using have RealTech LAN, I believe. 
  VMware would not work, because it didn't like the LAN device.  I'm 
guessing the target audience(s) do not include running VMware.

-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486