Whitepaper System x New IBM xSeries Firmware and Device Driver Update Naming Convention Whitepaper Written By: Revision Level: Last Revised: Mike Nolterieke 16 October 4th 2007 New IBM xSeries Firmware and Device Driver Update Naming Convention Whitepaper Page 2 of 20 Written By: Mike Nolterieke Table of Contents: Introduction 3 Why Make The Change?
Sstem x Written By: Mike NolteriekeRevision Level: 16Last Revised: October 4th 2007 New IBM xSeriesFirmware and DeviceDriver Update NamingConvention Whiteaer Whiteaer Page 2 of 20 New IBM xSeries Firmware and DeviceDriver Update Naming ConventionWhitepaper Written By: Mike Nolterieke Table of Contents: Introduction3 Why Make The Change?4 Customer Complaints4 Architecture Overview5 Architecture Exceptions5 Architected Fields6 Field 1 – Vendor:6 Field 2 – Type:6 Field 3 – Component:7 Field 4 – Version:10 Field 5 – Operating System:13 Field 6 – Processor Architecture15 File Extension:17 Naming Examples Using the Architecture18 Appendix A: Special Characters20 Page 3 of 20 New IBM xSeries Firmware and DeviceDriver Update Naming ConventionWhitepaper Written By: Mike Nolterieke Introduction IBM xSeries is changing the way we build and release firmware and device driverupdates We will no longer be using a part number as the file name of theupdates Instead, an architecture has been developed that will allow customersan easier method to identify an update and its version based on the file nameitselfCustomers will start see IBM xSeries updates being released over the next fewmonths that follow this architectureThis whitepaper provides the following information: • Why we are changing • An overview of the new architecture • Possible values of the architected fields where applicable • Examples of new file names using the new architecture