mmc subsystem needs MODALIAS love
Bug #30335 reported by
Scott James Remnant (Canonical)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Andy Whitcroft | ||
linux-source-2.6.17 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
The mmc subsystem doesn't currently generate MODALIAS and the device drivers (mmc_block, anyway) don't define aliases that map to this.
This means we don't know we have to load the secret mmc_block module to make the newly inserted device actually work.
Related branches
Changed in linux-source-2.6.15: | |
status: | Fix Committed → Confirmed |
Changed in linux-source-2.6.17: | |
status: | Incomplete → Won't Fix |
Changed in linux: | |
assignee: | ben-collins → apw |
status: | Confirmed → In Progress |
Changed in linux: | |
status: | In Progress → Fix Committed |
Changed in linux-source-2.6.17: | |
status: | Won't Fix → Fix Committed |
To post a comment you must log in.
Actually, someone just needed to think about what was going on here.
Since mmc is all about MMC block devices, and is pretty useless without this one module to implement the block layer of it, it made more sense to just build mmc_block as part of mmc_core. Even the Kconfig said "if you want mmc, you want this module".
The seperation of the two makes little sense.
So now that it's built in, whenever an MMC host is detected, and it's driver loaded, mmc_core will be have mmc_block functionality automatically.