| /kernel/liteos_a/ |
| D | CHANGELOG.md | 8 …89b0f95a65354d7d86)), closes [#I4I0O8](https://gitee.com/openharmony/kernel_liteos_a/issues/I4I0O8)
9 …6a543c029cc6dd75be)), closes [#I4NY49](https://gitee.com/openharmony/kernel_liteos_a/issues/I4NY49)
10 …45c0534db88b9c666f)), closes [#I4CLL9](https://gitee.com/openharmony/kernel_liteos_a/issues/I4CLL9)
11 …124b538e423023a259)), closes [#I4ATQX](https://gitee.com/openharmony/kernel_liteos_a/issues/I4ATQX)
12 …48a50a253bc2a3b604)), closes [#I4BL3S](https://gitee.com/openharmony/kernel_liteos_a/issues/I4BL3S)
13 …aa041ab4da8570c6a1)), closes [#I452Z7](https://gitee.com/openharmony/kernel_liteos_a/issues/I452Z7)
17 …690403ac652bbcea72)), closes [#I4NOC7](https://gitee.com/openharmony/kernel_liteos_a/issues/I4NOC7)
18 …65ebfe494d491fe20f)), closes [#I4KEZ1](https://gitee.com/openharmony/kernel_liteos_a/issues/I4KEZ1)
19 …a2b48fe0ac6dd19ff2)), closes [#I4CYPZ](https://gitee.com/openharmony/kernel_liteos_a/issues/I4CYPZ)
20 …56f575e3abc6c10702)), closes [#I2WARC](https://gitee.com/openharmony/kernel_liteos_a/issues/I2WARC)
[all …]
|
| /kernel/liteos_m/ |
| D | CHANGELOG.md | 6 …5a099e90f62c86abd1)), closes [#I4D129](https://gitee.com/openharmony/kernel_liteos_m/issues/I4D129)
7 …01873fe8e8d8cdd3c6)), closes [#I4K7LL](https://gitee.com/openharmony/kernel_liteos_m/issues/I4K7LL)
8 …768198eccc7448df6c)), closes [#I4SQIQ](https://gitee.com/openharmony/kernel_liteos_m/issues/I4SQIQ)
9 …eab976bdc1b32d1db9)), closes [#I4D1HY](https://gitee.com/openharmony/kernel_liteos_m/issues/I4D1HY)
12 …0fc9ca9e392537419f)), closes [#I4DAOU](https://gitee.com/openharmony/kernel_liteos_m/issues/I4DAOU)
13 …3b1b5aeca2d097289b)), closes [#I4ENQ1](https://gitee.com/openharmony/kernel_liteos_m/issues/I4ENQ1)
15 …185382e3228ed4b0a7)), closes [#I4N9P8](https://gitee.com/openharmony/kernel_liteos_m/issues/I4N9P8)
16 …3cf74645f470edf9b5)), closes [#I4O204](https://gitee.com/openharmony/kernel_liteos_m/issues/I4O204)
17 …46a73a7fb291588eda)), closes [#I4EJI4](https://gitee.com/openharmony/kernel_liteos_m/issues/I4EJI4)
18 …3f7a4280460bbf353a)), closes [#I4SJPZ](https://gitee.com/openharmony/kernel_liteos_m/issues/I4SJPZ)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 3 Embargoed hardware issues
9 Hardware issues which result in security problems are a different category
13 Hardware issues like Meltdown, Spectre, L1TF etc. must be treated
16 hardware vendors and other parties. For some of the issues, software
29 issues. Reports of pure software security bugs in the Linux kernel are not
46 While hardware security issues are often handled by the affected hardware
79 is aware of the sensitive nature of such issues and offers a Memorandum of
87 keep hardware security issues under embargo for coordination between
91 issues in the past and has the necessary mechanisms in place to allow
95 initial contact, which oversees the process of handling such issues under
[all …]
|
| D | stable-api-nonsense.rst | 45 First off, I'm not going to address **any** legal issues about closed
50 the technical issues here (not to make light of the legal issues, they
84 Now a number of these issues can be addressed by simply compiling your
120 issues:
146 Security issues are also very important for Linux. When a
|
| D | stable-kernel-rules.rst | 18 - Serious issues as reported by a user of a distribution kernel may also
25 - No "theoretical race condition" issues, unless an explanation of how the
152 members object to the patch, bringing up issues that the maintainers and
|
| /kernel/linux/linux-5.10/tools/testing/selftests/rseq/ |
| D | compiler.h | 21 * https://github.com/llvm/llvm-project/issues/52735
23 * Work around these issues by adding a volatile inline asm with
26 * issues are found in the future.
|
| /kernel/linux/linux-5.10/drivers/media/pci/tw5864/ |
| D | tw5864-core.c | 33 * BEWARE OF KNOWN ISSUES WITH VIDEO QUALITY
43 * There is a workaround for both issues: avoid P-frames by setting GOP size
48 * These issues are not decoding errors; all produced H.264 streams are decoded
50 * analog-to-digital conversion issues nor internal memory errors; we conclude
51 * it's internal H.264 encoder issues.
53 * worked properly at all in our development environment. So these issues may
304 dev_info(&pci_dev->dev, "Note: there are known video quality issues. For details\n"); in tw5864_initdev()
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 41 performance but will catch some internal issues.
119 performance but will catch some internal issues.
131 performance but will catch some internal issues.
143 performance but will help resolve GuC related issues.
|
| /kernel/linux/build/ |
| D | kernel_build.py | 80 issues = {}
101 if filename in issues:
102 issues[filename].extend(details)
104 issues[filename] = details
111 if filename in issues:
112 issues[filename].extend(details)
114 issues[filename] = details
116 for filename, details in issues.items():
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | zsmalloc.rst | 13 This was one of the major issues with its predecessor (xvmalloc).
15 To overcome these issues, zsmalloc allocates a bunch of 0-order pages
31 issues on 32-bit systems where the VA region for kernel space mappings
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/ |
| D | TODO | 5 V4L2 driver, there are still some issues preventing it to
8 Solving the related bugs and issues preventing it to work is
40 5. There are several issues related to memory management, causing
66 6. There is some issues at the frame receive logic, causing the
|
| /kernel/linux/linux-5.10/drivers/staging/fwserial/ |
| D | TODO | 4 - I/O is handled asynchronously which presents some issues when error
11 -- Issues with firewire stack --
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/panfrost/ |
| D | panfrost_gpu.c | 163 u64 issues; member
166 u64 issues; member
175 .issues = hw_issues_##_name, \
182 .issues = hw_issues_##name##_r##_rev##p##_p##stat, \
281 hw_issues |= model->issues; in panfrost_gpu_init_features()
291 hw_issues |= model->revs[best].issues; in panfrost_gpu_init_features()
301 dev_info(pfdev->dev, "features: %64pb, issues: %64pb", in panfrost_gpu_init_features()
|
| /kernel/linux/linux-5.10/fs/xfs/libxfs/ |
| D | xfs_health.h | 39 /* Observable health issues for metadata spanning the entire filesystem. */
45 /* Observable health issues for realtime volume metadata. */
49 /* Observable health issues for AG metadata. */
61 /* Observable health issues for inode metadata. */
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | ehci.rst | 51 used on PPC hardware so big/little endianness issues should be gone.
53 systems with interesting DMA mapping issues.
84 There are some issues with power management; suspend/resume doesn't
156 but aggregate throughput is also affected by issues like delays between
224 Interrupt and ISO transfer performance issues. Those periodic
|
| /kernel/linux/linux-5.10/include/asm-generic/ |
| D | bug.h | 68 * significant kernel issues that need prompt attention if they should ever
74 * These macros should be used for recoverable kernel issues only.
78 * conditions distinguishable from kernel issues.
246 * function address, and can be useful for catching issues with
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/reset/ |
| D | keystone-reset.txt | 38 WDT0 is triggered it issues hard reset for SoC.
59 WDT0 or WDT2 is triggered it issues soft reset for SoC.
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/intel/ |
| D | ixgbevf.rst | 14 - Known Issues
41 Known Issues/Troubleshooting
|
| D | fm10k.rst | 15 - Known Issues
85 each jumbo packet. This should help to avoid buffer starvation issues when
120 Known Issues/Troubleshooting
|
| /kernel/linux/linux-5.10/drivers/platform/x86/ |
| D | i2c-multi-instantiate.c | 171 * issues. The most common problem seen is interrupt flood.
180 * Because of the issues with the interrupt, the device is disabled for now. If
181 * you wish to debug the issues, uncomment the below, and add an entry for the
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/kunit/ |
| D | faq.rst | 78 3. Running the UML kernel directly can often reveal issues or error messages
82 mounted), and has had issues in the past when built statically and the host
102 If none of the above tricks help, you are always welcome to email any issues to
|
| /kernel/linux/linux-5.10/arch/arm/mm/ |
| D | fault-armv.c | 49 * fault (ie, is old), we can safely ignore any issues. in do_adjust_pte()
177 * an object, we need to deal with the cache aliasing issues.
213 * issues. If it has, we need to avoid them for the case where
|
| /kernel/linux/linux-5.10/drivers/misc/cb710/ |
| D | sgbuf2.c | 79 * handling any alignment issues. Bytes past the buffer's end
124 * handling any alignment issues. Bytes which would be written
|
| /kernel/linux/linux-5.10/Documentation/i2c/busses/ |
| D | i2c-ali15x3.rst | 36 by a power cycle. Cause unknown (see Issues below).
109 Issues chapter
|
| /kernel/linux/linux-5.10/drivers/staging/wfx/Documentation/devicetree/bindings/net/wireless/ |
| D | silabs,wfx.yaml | 25 WFx. Without it, you may encounter issues with warm boot. The mmc-pwrseq
61 during probe. Without this property, you may encounter issues with warm
|