Let cryptosoft(4) add its pseudo-device with a specific unit number and its

probe method return BUS_PROBE_NOWILDCARD so it doesn't get attached to real
devices hanging off of nexus(4) with no specific devclass set. Actually, the
more desirable fix for this would be to get rid of the newbus interface of
cryptosoft(4) altogether but apparently crypto(9) was written with support
for cryptographic hardware in mind so that approach would require some KPI
breaking changes which don't seem worth it.

MFC after:	1 week
This commit is contained in:
Marius Strobl 2010-11-14 13:09:32 +00:00
parent fcd01b8a6c
commit 86c585d929
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=215295

View File

@ -1060,7 +1060,7 @@ swcr_identify(driver_t *drv, device_t parent)
{
/* NB: order 10 is so we get attached after h/w devices */
if (device_find_child(parent, "cryptosoft", -1) == NULL &&
BUS_ADD_CHILD(parent, 10, "cryptosoft", -1) == 0)
BUS_ADD_CHILD(parent, 10, "cryptosoft", 0) == 0)
panic("cryptosoft: could not attach");
}
@ -1068,7 +1068,7 @@ static int
swcr_probe(device_t dev)
{
device_set_desc(dev, "software crypto");
return (0);
return (BUS_PROBE_NOWILDCARD);
}
static int