IP Library Granted Patent US 12681701
Granted Patent B2
US 12681701 · App. 18/642,378 · Granted Jul 14, 2026

Driver generation device and driver generation method

Inventor: Yoshihiro Komatsubara (Mishima Shizuoka, JP)
Assignee: TOSHIBA TEC KABUSHIKI KAISHA
G06F8/41G06F9/45558
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12681701
App. No.
18/642,378
Granted
Jul 14, 2026
Kind
B2
Abstract

A driver generation device includes a processor and a memory. The memory stores kernel source code for an embedded device with Linux installed, driver source code for a device driver for the embedded device, a container including a cross compiler that compiles the driver source, and container virtualization software that manages the container. The memory is configured to store a driver generation program, when executed by the processor, causes the computer to (a) mount the kernel source code from the computer to a first directory within the container, the first directory having the same path as a second directory on the computer containing the kernel source code, (b) mount the driver source code within the container, and (c) compile the driver source code to generate the device driver.

Claims (66)

1 . A driver generation device comprising:

a computer including:

a processor; and

a memory configured to store:

kernel source code for an embedded device with Linux installed;

driver source code for a device driver for the embedded device;

a container including a cross compiler that compiles the driver source code; and

container virtualization software that manages the container,

wherein the memory is configured to store a driver generation program that, when executed by the processor, causes the computer to:

mount the kernel source code from the computer to a first directory within the container, the first directory having the same path as a second directory on the computer containing the kernel source code;

mount the driver source code within the container; and

compile the driver source code to generate the device driver.

2 . The driver generation device of claim 1 , wherein the driver generation program causes the computer to:

compile the driver source code to generate the device driver within the container based on the path of the first directory.

3 . The driver generation device of claim 1 , wherein the driver generation program causes the computer to:

compile the driver source code to generate the device driver on the computer using a set of commands; and

compile the driver source code to generate the device driver within the container using the same set of commands.

4 . The driver generation device of claim 1 , wherein the driver generation program causes the computer to:

refer to path information of the kernel source code on the computer while the container virtualization software starts the container; and

create the first directory within the container based on the path information.

5 . The driver generation device of claim 4 , wherein the driver generation program causes the computer to:

control the container virtualization software to create the first directory within the container based on the path information;

control the container virtualization software to mount the kernel source code from the computer to the first directory within the container;

control the container virtualization software to mount the driver source code within the container; and

control the container virtualization software to compile the driver source code to generate the device driver.

6 . The driver generation device of claim 1 , wherein the driver generation program causes the computer to:

control the container virtualization software to mount the kernel source code from the computer to the first directory within the container;

control the container virtualization software to mount the driver source code within the container; and

control the container virtualization software to compile the driver source code to generate the device driver within the container.

7 . The driver generation device of claim 1 , wherein the embedded device includes at least one of a multi-function peripheral, a barcode printer, a point of sale (POS), or a POS peripheral.

8 . The driver generation device of claim 1 , wherein the container virtualization software is a Docker engine.

9 . A driver generation method comprising:

causing a computer to perform a set of operations, the computer including a processor and a memory configured to store:

kernel source code for an embedded device with Linux installed;

driver source code for a device driver for the embedded device;

a container including a cross compiler that compiles the driver source code; and

container virtualization software that manages the container,

the set of operations including:

mounting the kernel source code from the computer to a first directory within the container, the first directory having the same path as a second directory on the computer containing the kernel source code;

mounting the driver source code within the container; and

compiling the driver source code to generate the device driver.

10 . The driver generation method of claim 9 , wherein the set of operations includes:

referring to path information of the kernel source code on the computer while the container virtualization software starts the container; and

creating the first directory within the container based on the path information.

11 . The driver generation method of claim 10 , wherein the set of operations includes:

compiling the driver source code to generate the device driver on the computer using a set of commands; and

compiling the driver source code to generate the device driver within the container using the same set of commands.

12 . The driver generation method of claim 11 , wherein the set of operations includes:

compiling the driver source code to generate the device driver within the container based on the path of the first directory using the same set of commands.

13 . The driver generation method of claim 9 , wherein the embedded device includes at least one of a multi-function peripheral, a barcode printer, a point of sale (POS), or a POS peripheral.

14 . The driver generation method of claim 9 , wherein the container virtualization software is a Docker engine.

15 . A driver generation method comprising:

causing a computer to perform a set of operations, the computer including:

a kernel source for an embedded device with Linux installed;

a driver source for a device driver for the embedded device;

a container including a cross compiler that compiles the driver source;

container virtualization software that manages the container; and

a driver generation program that controls the container virtualization software,

the set of operations including:

referring to path information of the kernel source on the computer while the container virtualization software starts the container;

allowing the container virtualization software to create a first directory within the container based on the path information, the first directory having the same path as a second directory of the computer containing the kernel source;

allowing the container virtualization software to mount the kernel source within the container;

allowing the container virtualization software to mount the driver source within the container; and

allowing the container virtualization software to operate such that the cross compiler compiles the driver source to generate the device driver using a set of commands that is also used to generate the device driver on the computer.

16 . The driver generation method of claim 15 , wherein the embedded device includes at least one of a multi-function peripheral, a barcode printer, a point of sale (POS), or a POS peripheral.

17 . The driver generation method of claim 15 , wherein the container virtualization software is a Docker engine.