These have been in the tree for over a month. =sys-fs/vhba-20110915 "hppa x86" =dev-libs/libmirage-1.5.0-r1 "amd64 hppa x86" =app-cdr/cdemud-1.5.0 "amd64 hppa x86" =app-cdr/cdemu-1.5.0 "amd64 hppa x86" =app-cdr/gcdemu-1.5.0 "amd64 x86"
*** Bug 397709 has been marked as a duplicate of this bug. ***
Wouldn't it be nice to have bug #299586 fixed first?
(In reply to comment #2) > Wouldn't it be nice to have bug #299586 fixed first? No, not really. For two reasons: 1. As far as I can tell, to load/unload a module automatically with udev, a static /dev file owned by the module needs a statically assigned node number. Claiming a static node number in an out-of-kernel-tree module is fundamentally a bad idea, just like using an unassigned static IP on another person's network; another driver might well try to use the same number legitimately. 2. Even if one could somehow verify that nothing else in kernel or the out-of-tree drivers in portage or the widely used overlays is using the same node number (and keep verifying it on every kernel version bump!), one would still need a patch that works with recent kernels and recent udev versions. Nobody has submitted such a patch yet (the patch attached in bug #299586 doesn't work), and due to concerns about #1, I did not want to spend hours on attempting to fix it. All that said, if you have a working patch for auto-loading vhba and some way of alleviating concerns about #1, I would love to take a look at it.
(In reply to comment #3) > As far as I can tell, to load/unload a module automatically with udev, a > static /dev file owned by the module needs a statically assigned node > number. Just to clarify, this is only needed for automatically loading a module on opening the /dev file. Modules can also auto-load on various events (e.g. hardware being inserted), but unfortunately that doesn't help with loading vhba.
amd64: emerge pass
amd64 stable
x86 stable
sys-fs/vhba was marked stable for HPPA, but I've reverted that. I think ~hppa is good enough for this batch. Closing.