Artem Kachitchkine wrote:
>
>
>> 2) It looks like in response to EC_DEVFS_DEVI_ADD (which is sent
>> after the node as done attach(9e), add_minor_pathname() in devfsadm
>> is called, which ultimately I'd have expected to cause an event for
>> the minor node creations to be called for each of the nodes
>> established by sd(7d).
>
> HAL needs _logical_ devices (/dev) to be present at the time of event,
> we're not really interested in physical devices (/devices). EV_DEVFS
> events are emitted too early for us; devfsadm emits EV_DEV events
> after it creates logical devices.
That makes sense, in particular with respect to why you can't use
EC_DEV_BRANCH_ADD or whatever it is called.... its too soon.
>
> > These don't seem to get to be seen by hald, so either they aren't
> > getting sent at all, or I'm misunderstanding hald somewhat.
>
> You can write a very simple program that subscribes to
> EV_DEV_ADD/REMOVE sysevents (or use mine
> /home/artem/ws/tamarack/misc/ev.c). If these events are emitted
> correctly for your device, we can do further analysis inside HAL; if
> not, the problem is elsewhere.
Hmm... the events surely are not getting delivered, at least they are
not reported by your ev.c. But what is funny is that for USB mass
storage they do, but usually a second or two after the hotplug operation.
The other thing is that I can definitely see that for my device the
minor nodes have been created, as they show up with prtconf. I'm
wondering if devfsadm isn't submitting the events for some reason, or
maybe it isn't receiving them. More debug to do, I think.
So now I have to figure out why USB mass storage works, but my device
doesn't. :-(
-- Garrett
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
