Kaixo! Li Mon, Jun 17, 2013 at 06:40:54PM +0200, Lennart Poettering scrijha:
> If firmware loading is a one-time thing you need to execute when the > device is plugged in, and is relatively quick to execute there is no > need to involve a systemd service and you can simply run this from a > udev rule directly. Well, the problem is the loader is a user space program (it seems attemps to integrate a loader in the linux kernel have been rejected) that uses the "hci0" (or hci1 or watever) interface to upload the firmware. And I find it more elegant to have systemd call the loader, as then there is a single place where it is called (a single file to edit if the loader program is moved, renamed or its command line options change); plus it has the extra bonus of being able to use systemctl status and journalctl to see if the firmware upload went correctly or not. that being said, if udev is the place to go, it's fine too; but then udev is missing an important feature: it should expose the bdaddr of a bluetooth device in it's normal form (eg: 00:02:72:32:DE:FB ) Should I switch to another mailing-list for further udev ? Thanks -- Ki ça vos våye bén, Pablo Saratxaga http://chanae.walon.org/pablo/ PGP Key available, key ID: 0xD9B85466
pgp_l4aAgvgYn.pgp
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
