yes, it's used to set the driver's dying flag. those are the most common places a driver would be marked as dying. maybe also in an interrupt currently it is just a wrapper for setting the dying flag in the driver's usbd_device. maybe it will do other things, but probably not. the pupose of setting the dying flag in the usbd_device is so that this flag can be checked in generic stack functions, because the almost always have access to the usbd_device. if there were just the dying flag ...

Hi, I've finally found some time to work on the fan control support for my thinkpad. But I'm having problems calling to acpiec_write() from sysctl or timeout_set(9) context. (Assertion failure in acpiec_gpehandler()). According to dev/acpi/acpiec.c:229 this function is meant to be called only from "acpi thread context". Now how am I supposed to talk to the acpi controller? One solution would be to use the aml_register_notify(..., ACPIDEV_POLL) callback mechanism already in use by the ...

partition 'c' as a RAID partition? That's not good, is it? Or am I missing something? Nick.

Hello, I've noticed that the size of softraid(4) disks is one sector too large. In the following description, the native disk is sd4c (which is of type RAID), and the corresponding virtual softraid(4) disk will be sd5. I will assume that sd5 is of discipline CRYPTO, but the problem should be the same for all disciplines. The size for sd5 gets eventually stored in struct sr_metadata as sd_meta->ssdi.ssd_size in function sr_crypto_create (dev/softraid_crypto.c). Its value gets initially ...

About this interface, I looked around in the code and it seems to be used mostly in activate functions and in failure cases inside attach. My question is if its not better to make usbd_deactivate() a function similar to an activate() one. That way we can just add something like ubdi_activate in the cfattach instead of a wrapper to it in each driver. I don't know what the plan is for usbd_deactivate thus what I'm proposing might not make sense. Just a thought. Otherwise it would sure get ...

You are not supposed to talk directly to the ec device. Jordan has a diff floating around for acpi tasklets. This really should be the way to get this done. I'll forward the diff to tech with the caveat that it isn't finalized yet. I would prefer for this fan stuff to be automatic instead of by hand

I can repro. Crypto raid. sd0g: size 20986560 this is the real disk sd1a: 20985952 offset 64 sd1c: 20986033 softraid reserves metaoffset + metasize + loadersize + bootblocks == 528 sectors. 20986560 - 528 = 20986032 So that's one smaller than the fake disk thinks it is. Lucky for me, my 'a' partition with the filesystem is only 20985952 + 64 = 20986016 sectors, so it didn't try to use the last few. Numbers again, minus prefix: Base disk: 560 Space after SR meta: 32 SR ...