| Summary: | net-misc/r8168 CONFIG_CHECK="!R8169" is not neccesary | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Vladimir Berezhnoy <non7top> |
| Component: | Current packages | Assignee: | James Le Cuirot <chewi> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | adebeus, demmamussabebonk, rodrigo |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Patch that allows inline r8169 kernel driver to coexist with Realteks r8168 driver | ||
At least one other dev and a user had issues when building both. I'm not ready to do this now. It's possible to build and use when R8169 is built as module, but not when R8169 is compiled in-kernel. Created attachment 357434 [details, diff]
Patch that allows inline r8169 kernel driver to coexist with Realteks r8168 driver
Simple patch to r8169 kernel's driver so it can be installed together with Realteks r8168 one.
I'm taking on the r8168 package now. Sorry but I'm not going to accept this because I feel that upstream included 0x8168 in that list for a reason. We already give users the choice to build one driver or the other. When would you ever need both? *** Bug 628872 has been marked as a duplicate of this bug. *** |
The module can be built successfully even when in kernel module is enabled, and often in kernel module will work. So it is not required to add strict dependency on !R8169. Possible option is to use MODULESD_R8168_ADDITIONS=('blacklist r8169') Reproducible: Always