Lines Matching full:linux

16 ACPICA and Linux.  It also describes how ACPICA code in drivers/acpi/acpica,
26 adapted by various host OSes.  By directly integrating ACPICA, Linux can
33 The following figure depicts the Linux ACPI subsystem where the ACPICA
64       | |   +------------------+     Linux/ACPI Components  |   |
78                  Figure 1. Linux ACPI Software Components
81     A. OS Service Layer - Provided by Linux to offer OS dependent
96     C. Linux/ACPI Functionality - Providing Linux specific ACPI
97        functionality to the other Linux kernel subsystems and user space
102          include/linux/acpi.h
103          include/linux/acpi*.h
108        ACPI interfaces.  They are Linux specific components and are out of
124 Linux, there is a release process to convert the ACPICA git commits into
125 Linux patches.  The patches generated by this process are referred to as
129 ACPICA release patchset for the Linux ACPI community.  This process is
161     < Linux ACPI Community Review >
166     | linux-pm / linux-next |-->< Linux Merge Window >-->| linux / master |
169                 Figure 2. ACPICA -> Linux Upstream Process
174        scripts located in generate/linux folder.
177     C. linux-pm / linux-next - "linux-next" branch of the git repository at
178        <https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git>.
179     D. linux / master - "master" branch of the git repository at
180        <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git>.
182    Before the linuxized ACPICA patches are sent to the Linux ACPI community
191 Ideally, all of the ACPICA commits should be converted into Linux patches
192 automatically without manual modifications, the "linux / master" tree should
198 the ACPICA code in Linux and the upstream ACPICA code, referred to as
203       established, there already had been divergences between Linux and
208       made directly in the Linux sources obviously hurts the ACPICA release
212    3. Linux specific features - Sometimes it's impossible to use the
213       current ACPICA APIs to implement features required by the Linux kernel,
214       so Linux developers occasionally have to change ACPICA code directly.
220       break the Linux kernel, leaving us build/boot failures.  In order to
221       avoid breaking Linux bisection, fixes are applied directly to the
235 This paragraph guides Linux developers to use the ACPICA upstream release
236 utilities to obtain Linux patches corresponding to upstream ACPICA commits
249    $ generate/linux/gen-patch.sh -u [commit ID]
257    changes that haven't been applied to Linux yet.
264    $ generate/linux/make-patches.sh -u [commit ID]
266    The commit ID should be the last ACPICA commit accepted by Linux.  Usually,
273    If you have local copies of both Linux and upstream ACPICA, you can generate
277    # git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
279    # generate/linux/divergence.sh -s ../linux