> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/man/man4/vpd.4.md).

# vpd.4

`vpd` — 重要产品数据内核接口

## 名称

`vpd`

## 概要

`device vpd`

## 描述

IBM ThinkPad 笔记本（以及大多数 IBM 台式机）在 BIOS Shadow RAM 中有一个 48 字节的重要产品数据（Vital Product Data，VPD）结构。

VPD 提供机型和型号信息、构建 ID（大致相当于 BIOS 版本）以及序列号信息。

`vpd` 驱动扫描 BIOS 区域并声明 VPD 结构使用的内存。它提供 sysctl(3) 分支 `hw.vpd` 以允许用户态访问此信息。以下变量由每个 VPD 附件提供（应当只有一个）：

**`MACHINE_TYPE`**（`machine.type`）机型。

**`MACHINE_MODEL`**（`machine.model`）型号。

**`BUILD_ID`**（`build.id`）BIOS 构建 ID。

**`SERIAL_BOX`**（`serial.box`）机箱序列号。

**`SERIAL_PLANAR`**（`serial.planar`）主板序列号。

## 参见

> "TP General - Using the BIOS Build ID to identify IBM ThinkPad systems", Reference #: MIGR-45120, November 22, 2002.

## 历史

`vpd` 驱动最早出现于 FreeBSD 5.1。

## 作者

`vpd` 驱动及本手册页由 Matthew N. Dodd <mdodd@FreeBSD.org> 编写。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://book.bsdcn.org/man/man4/vpd.4.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.