Questions on physdev vs. classdev

[Joe Marcus Clarke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Looks like I needed to subscribe to get this message out.

In addition to my questions below, would it be possible for me to get
CVS commit access so I can add my FreeBSD work so others can contribute?
   Thanks.

[Old message follows]

I've finally started writing the FreeBSD port of HAL, and I have two
questions regarding device types and embedded hotplug events.

It seems like Linux distinguishes between physical devices (e.g. a PCI
card), and logical devices (a PCI card that happens to be a sound card).
 Therefore, one physdev event will be triggered as well as one classdev
event.  Is that correct?

In FreeBSD, we have one device tree in devinfo.  I want to send my
soundcard event as a physdev event with a subsystem of pci.  Once the
soundcard is added as a physical PCI card, I'd like to then add a
classdev entry that is sound-specific.  Is this possible?  Is there are
better way of doing this?

Additionally, FreeBSD doesn't register hotplug events for SCSI devices
(e.g. disks, tapes, CD-ROMS, etc.).  What I'm doing now is upon
detection of such a device, I add the blockdev, then fire off hotplug
events for the various slices and partitions.  In essence, I have events
within events.  Is this legal?

Okay, I guess I have a third question.  I've created some
FreeBSD-specific properties such as freebsd.dev_name and
info.freebsd.driver.  Do I need to register these anywhere, or is this
something I can do after the fact?

Thanks.

Joe
- --
Joe Marcus Clarke
FreeBSD GNOME Team	::	gnome at FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD1otib2iPiv4Uz4cRAv6+AKCM7sfg0A+XAjHiiOH8mFih9SB0EwCgkZOw
tMSzMAdcMLaChUH4jY4lPXs=
=FZQi
-----END PGP SIGNATURE-----