|
Bugzilla – Full Text Bug Listing |
| Summary: | Modaliases for dvb? | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Andreas Gruenbacher <agruen> |
| Component: | Other | Assignee: | Torsten Duwe <duwe> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 6 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andreas Gruenbacher
2006-03-10 00:16:07 UTC
This is true. However, the dvb package provides the drivers for 2.4 series kernels; as they are synched with 2.6. Besides that, the relationship between hardware and drivers is not bijective; as many of the DVB chips currently in use (Philips and old Brooktree / Conexant) are merely data pumps, and require either a DVB driver or an analog TV (frame grabber) driver to interpret the incoming data properly. Newer chips only currently hit the market (new Conexant, SkyStar) that are unambiguously DVB. Conclusively, the dvb package (for 2.4 kernels ;-) _requires_ one of the to-be-listed PCI IDs, but it would be dangerous to trigger on all of these. So, 1. does this qualify for a Modalias list? and 2. is this relevant at all because of the old kernel dependence? Fixed; see bug 156864. |