Documentation/admin-guide/media/dvb-usb-mxl111sf-cardlist.rst
Source file repositories/reference/linux-study-clean/Documentation/admin-guide/media/dvb-usb-mxl111sf-cardlist.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/admin-guide/media/dvb-usb-mxl111sf-cardlist.rst- Extension
.rst- Size
- 972 bytes
- Lines
- 37
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: documentation
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
.. SPDX-License-Identifier: GPL-2.0
dvb-usb-mxl111sf cards list
===========================
.. tabularcolumns:: |p{7.0cm}|p{10.5cm}|
.. flat-table::
:header-rows: 1
:widths: 7 13
:stub-columns: 0
* - Card name
- USB IDs
* - HCW 117xxx
- 2040:b702
* - HCW 126xxx
- 2040:c602, 2040:c60a
* - Hauppauge 117xxx ATSC+
- 2040:b700, 2040:b703, 2040:b753, 2040:b763, 2040:b757, 2040:b767
* - Hauppauge 117xxx DVBT
- 2040:b704, 2040:b764
* - Hauppauge 126xxx
- 2040:c612, 2040:c61a
* - Hauppauge 126xxx ATSC
- 2040:c601, 2040:c609, 2040:b701
* - Hauppauge 126xxx ATSC+
- 2040:c600, 2040:c603, 2040:c60b, 2040:c653, 2040:c65b
* - Hauppauge 126xxx DVBT
- 2040:c604, 2040:c60c
* - Hauppauge 138xxx DVBT
- 2040:d854, 2040:d864, 2040:d8d4, 2040:d8e4
* - Hauppauge Mercury
- 2040:d853, 2040:d863, 2040:d8d3, 2040:d8e3, 2040:d8ff
* - Hauppauge WinTV-Aero-M
- 2040:c613, 2040:c61b
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.