| /openbmc/linux/fs/ext2/ |
| H A D | Kconfig | 32 If you don't know what Access Control Lists are, say N
|
| /openbmc/linux/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-davinci.txt | 3 This file provides information, what the device node for the
|
| /openbmc/linux/arch/alpha/ |
| H A D | Kconfig.debug | 38 order to debug the code. Say Y unless you know what you are doing.
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | davinci_emac.txt | 3 This file provides information, what the device node
|
| /openbmc/openbmc/meta-phosphor/recipes-core/os-release/ |
| H A D | os-release.bbappend | 6 # what that means!
|
| /openbmc/openpower-vpd-parser/vpd-manager/include/ |
| H A D | exceptions.hpp | 39 inline const char* what() const noexcept override in what() function in vpd::Exception
|
| /openbmc/phosphor-bmc-code-mgmt/common/src/ |
| H A D | software_manager.cpp | 124 error(e.what()); in initDevices()
|
| /openbmc/openpower-vpd-parser/vpd-manager/src/ |
| H A D | gpio_monitor.cpp | 51 logging::logMessage(std::string(l_ex.what())); in handleChangeInGpioPin()
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | i2c-sysfs.rst | 232 we can now find the 0x72 MUX and what logical I2C bus numbers
307 what we can learn from the I2C device directory whose link name is in the format
316 This file tells what device name it was used for the kernel driver to
326 There is a symbolic link named ``driver`` to tell what Linux kernel driver was
344 Depending on what the I2C device is and what kernel driver was used to probe the
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | hpfs.rst | 105 chgrp symlinks but I don't know what is it good for. chmoding symlink results
126 really what IBM developers wanted? But problems continued. When I created in
138 lowercasing no matter what's file codepage index. Usually all file names are in
139 this codepage - if you don't try to do what I described above :-)
174 You can't rename over directories (what is it good for?).
187 anybody know what does it mean?
|
| H A D | idmappings.rst | 26 To see what this looks like in practice, let's take the following idmapping::
62 what id ``k11000`` corresponds to in the second or third idmapping. The
83 The algorithm to calculate what a given id maps to is pretty simple. First, we
85 for simplicity. After that if we want to know what ``id`` maps to we can do
108 want to know what id this was mapped from in the upper idmapset of the first
115 idmapping and we want to know what this id maps down to in the lower idmapset
227 This algorithm allows us to answer the question what userspace id a given
236 means ``u1000`` will be mapped to ``k21000`` which is what will be stored in
278 This allows us to answer the question what kernel id we would need to use to
342 filesystem objects. For simplicity we will only look at what happens when the
[all …]
|
| H A D | index.rst | 9 works, along with the filesystems that sit below it. For now, what we have
|
| /openbmc/linux/arch/sparc/mm/ |
| H A D | srmmu.c | 782 int what; /* 0 = normal-pte, 1 = pmd-level pte, 2 = pgd-level pte */ in srmmu_inherit_prom_mappings() local
797 what = 0; in srmmu_inherit_prom_mappings()
802 what = 1; in srmmu_inherit_prom_mappings()
807 what = 2; in srmmu_inherit_prom_mappings()
813 if (what == 2) { in srmmu_inherit_prom_mappings()
827 if (what == 1) { in srmmu_inherit_prom_mappings()
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | siteinfo.bbclass | 12 # Returns information about 'what' for the named target 'target'
15 # 'what' can be one of
22 # If 'what' doesn't exist then an empty value is returned
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-edac | 101 Description: This attribute file will display what type of DRAM device is
108 Description: This attribute file will display what type of Error detection
138 Description: This attribute file will display what type of memory is
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | building.rst | 142 temporary directory (:term:`TMPDIR`) can be shared will depend on what is
143 similar and what is different between the configurations. Multiple MACHINE
303 what is added to the image as compared to the defaults you might not
462 - :ref:`dev-manual/building:understand what contributes to your image size`
563 First, find out what is hogging your root filesystem by running the
577 You need to be sure that what you eliminate does not cripple the
615 aspects. What subsystems do you enable? For what architecture are you
623 get an idea of what is making up the kernel::
645 Use your log file to see what you can eliminate from the kernel based on
649 After figuring out what to eliminate, you need to reconfigure the kernel
[all …]
|
| /openbmc/linux/Documentation/doc-guide/ |
| H A D | contributing.rst | 12 Unfortunately, the kernel's documentation currently falls far short of what
18 general and find a place in the community. The bulk of what follows is the
78 simplistic idea of what C comment blocks look like. This problem had been
81 history for that file showed what the normal format for subject lines is,
135 is necessary to work out what the role of those members or parameters is
|
| /openbmc/openbmc/meta-security/dynamic-layers/meta-perl/recipes-security/bastille/files/ |
| H A D | fixed_defined_warnings.patch | 38 # Figure out what kind of system we're on.
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | index.rst | 46 Each driver that implements ``devlink`` is expected to document what
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | tracepoint.rst | 23 the available tracepoints. The intention is to understand not only what
|
| /openbmc/phosphor-power/tools/power-utils/ |
| H A D | version.cpp | 189 log<level::ERR>(std::format("Error: {}", e.what()).c_str()); in getVersion()
|
| /openbmc/openpower-hw-diags/util/ |
| H A D | ffdc.cpp | 192 trace::inf(e.what()); in createFFDCTraceFiles()
|
| /openbmc/openbmc/poky/meta/recipes-graphics/vulkan/ |
| H A D | vulkan-validation-layers_1.3.296.0.bb | 47 # The tags versions should always be sdk-x.y.z, as this is what
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | rule_tests.cpp | 73 EXPECT_STREQ(error.what(), "Communication error"); in TEST()
|
| /openbmc/linux/fs/ceph/ |
| H A D | Kconfig | 40 If you don't know what Access Control Lists are, say N
|