| Summary: | small tools needed for firmware loader for broadcom usb devices | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Pablo Saratxaga <pablo> |
| Component: | New RPM package request | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | pablo |
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
systemd service file to load firmware, to be triggered by udev
udev rules to call brcm_patchram_plus_usb trough systemd |
||
|
Description
Pablo Saratxaga
2013-06-11 09:34:48 CEST
Created attachment 4128 [details]
systemd service file to load firmware, to be triggered by udev
first try at a systemd service unit that will call brcm_patchram_plus_usb
maybe it should call a script instead of the firmware loader directly? (to allow actions in case firmware is not ther, for example).
FIXME: I use fixed value "hci0"; that should be changed as if more than one bluetooth adapter is present it may be "hci1", etc; but I have no idea how to get the actual value.CC:
(none) =>
pablo Created attachment 4129 [details] udev rules to call brcm_patchram_plus_usb trough systemd udev rules file to call the systemd service to load firmware trough brcm_patchram_plus_usb. I use RUN+=... as I'm not able to make TAG+="systemd" work (on MGA3). list of matching devices taken from: https://bbs.archlinux.org/viewtopic.php?pid=1038550#p1038550 I only have 0a5c:21e8 to test Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |