| /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
|
| /kernel/linux/linux-4.19/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 36 performance but will catch some internal issues.
87 performance but will catch some internal issues.
99 performance but will catch some internal issues.
111 performance but will help resolve GuC related issues.
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| 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
|
| /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-4.19/drivers/media/pci/tw5864/ |
| D | tw5864-core.c | 42 * BEWARE OF KNOWN ISSUES WITH VIDEO QUALITY
52 * There is a workaround for both issues: avoid P-frames by setting GOP size
57 * These issues are not decoding errors; all produced H.264 streams are decoded
59 * analog-to-digital conversion issues nor internal memory errors; we conclude
60 * it's internal H.264 encoder issues.
62 * worked properly at all in our development environment. So these issues may
313 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/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-4.19/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/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-4.19/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/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/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-4.19/Documentation/usb/ |
| D | ehci.txt | 46 used on PPC hardware so big/little endianness issues should be gone.
48 systems with interesting DMA mapping issues.
77 There are some issues with power management; suspend/resume doesn't
144 but aggregate throughput is also affected by issues like delays between
209 TBD: Interrupt and ISO transfer performance issues. Those periodic
|
| /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-4.19/Documentation/networking/ |
| D | i40evf.txt | 11 - Known Issues/Troubleshooting
37 Known Issues/Troubleshooting
|
| D | ixgbevf.txt | 11 - Known Issues/Troubleshooting
35 Known Issues/Troubleshooting
|
| /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-4.19/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/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/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-4.19/include/asm-generic/ |
| D | bug.h | 78 * significant kernel issues that need prompt attention if they should ever
84 * These macros should be used for recoverable kernel issues only.
88 * conditions distinguishable from kernel issues.
|