Age | Commit message (Collapse) | Author | Files | Lines |
|
Fixed policy for org.freedesktop.Hal.Device.KillSwitch by adding
receive_interface and receive_sender="org.freedesktop.Hal".
|
|
Put the policy rules in alphabetical order.
|
|
Removed second <policy context="default"> block, it makes no
sense to have the same default context two times.
|
|
Removed policy rule for org.freedesktop.Hal.Device.VideoAdapterPM,
there is no such interface in HAL (anymore?).
|
|
|
|
Fixed spec due to path/filename changes with actual PolicyKit.
|
|
Fixed spec for access_control.type due to Policykit changes. Fixed
small typo.
|
|
hal.conf.in: Update dbus permissions to include KillSwitch, which
NetworkManager needs. Taken from Fedora:
http://cvs.fedoraproject.org/viewvc//devel/hal/hal-dbus-perms.patch?view=markup
|
|
Fixed commit ebb0482963494c8733e211dc5ec16253b776a748 to get
make distcheck working again. A user can't run "make distcheck"
because of /lib/udev/rules.d can't be created due to permissions.
This commit change the Makefile and configure to do the same as
the udev package. The path to ${udev_prefix}/lib/udev/rules.d can
get changed via --with-udev-prefix.
|
|
Fixed ACL handling for removable block devices (as CD/DVD). Do not set acl
properties on unpartitioned volumes (bnc#408252), this change the settings
for CD/DVD burn devices and prevent the user from burning CD/DVD's.
|
|
|
|
Fix copy&paste error which assigned the wrong access_control.file for
/dev/drm/card* devices. It previously copied "input.device", but
should be "linux.device_file".
|
|
|
|
|
|
|
|
Added ACL support for scsi_generic scanner devices.
|
|
Fixed serial.port handling for USB serial devices. Since USB devices
can have several ports and since the order of /dev/ttyUSB* depends on
the device order, it make no sense to base serial.port for USB devices
on the number in /dev/ttyUSB*. Here is the port number of the USB
device itself more important to detect/match devices.
Changed the spec description and handling/detection of serial.port for
USB serial devices to use device/port_number info from sysfs. This change
shouldn't affect existing matches in fdi files (as e.g. for modems) as
long as there wheren't more than one USB serial device in the machine as
the entry was generated. I imply this for now with this change.
This change allow us to match e.g. modems also if you put more than one
modem with USB serial ports to a machine. For more see:
https://bugzilla.novell.com/show_bug.cgi?id=458307
|
|
Fixed ACL handling for drm devices. Use linux.device_file instead
of input.device for access_control.file.
|
|
Fix joystick/touchpad/tablet detection. Path contributed via
https://launchpad.net/bugs/284129 by Ari Mustonen.
|
|
Added org.freedesktop.Hal.Device.Leds interface to the spec.
|
|
Updated .gitignore for hald/linux/addons, added hald-addon-leds.
|
|
Added a new singleton addon to handle led devices. The new interface
is called org.freedesktop.Hal.Device.Leds and provide these methodes:
- int SetBrightness (int brightness_value)
- int GetBrightness ()
|
|
Added the leds linux kernel subsystem to HAL. These are the current
properties of led devices:
- leds.device_name (string, mandatory)
- leds.function (string, mandatory)
- leds.colour
|
|
2.6.28 changed linux/serial.h to use __32, which is provided by
linux/types.h. While arguably a kernel bug, working around it by
including it explicitly doesn't hurt.
|
|
This adds support for adding ACLs to removable block devices (such as
USB keys) on insertion. This is useful for allowing users to run mkfs
or fsck on their USB keys.
Please note that the patch does *not* enable it by default, that's up
to distros or individual users (gnome-polkit-authorization), but it
provides a standard flip to configure this behaviour.
|
|
|
|
Fixed ipw addon, use fputs instead of fputc to set the status
to sysfs.
|
|
Added new (not mandatory) killswitch.state property to the killswitch
namespace reflecting the current state of the killswitch as reported
by e.g. the linux kernel.
There are three possible states:
- 0: Radio output (soft) blocked
- 1: Radio output allowed
- 2: Radio output (hard )blocked, non-overrideable via SetPower()
|
|
Added a new singleton addon for the rfkill subsystem to HAL. This
addon (hald-addon-rfkill-killswitch) handles all killswitches
provided by the rfkill linux kernel subsystem.
Note: If your system provides a rfkill device for the Intel
WLAN device(s), you may should build hal-info with
--disable-killswitch-ipw-wlan to prevent trouble.
TODO: Find a way in the fdi-files to prevent trouble with the
ipw killswitch device spawned by via the fdi-files.
|
|
Improved HAL performance for filesystem detection. Call libvolume_id
functions in the volume prober to get the following information only
if we have no udev information about the filesystem:
- volume.fsusage
- volume.fstype
- volume.fsversion
- volume.uuid
- volume.label
HAL now simply use the already in the HotplugEvent stored information
from udev if available, since udev already called libvolume_id to get
these info. With this change HAL needs to probe only CD/DVD media and
maybe fakevolume related volumes.
|
|
This reverts commit 7aca1f3fefefd3c760636aabcff1e25946ab6391.
Reverted the change to prevent trouble with CD/DVD media (because
they are fakevolumes and udev tell us no information about the
filesystem on insert the media).
|
|
Allow uid/gid mount option for ntfs, as reported in
http://bugs.debian.org/427109.
|
|
in https://launchpad.net/bugs/218834 we got a report that some CD-ROMs
are too slow to properly detect everything within the standard 10
seconds hal helper timeout:
[6188]: 22:22:56.009 [D] probe-volume.c:379: Doing probe-volume for
/dev/scd0
[...]
[6182]: 22:22:58.002 [I] addon-storage.c:363: ... device /dev/scd0 is
not locked on HAL
[6188]: 22:23:05.558 [D] probe-volume.c:542: volume.disc.capacity =
2384855040
[...]
[6188]: 22:23:06.406 [E] probe-volume.c:302: Timed out probing
/dev/scd0 - broken device driver?
(NB the timestamps). Since the default 10 seconds seems to be pretty
much arbitrary, I just raised it to 20 for now.
Fixes bz #13009.
|
|
Fixed call of hotplug_queue_now_empty() under linux. Call the
function first if the hotplug queue is really empty and if there
is no hotplug event in progress. Otherwise you get DeviceAdded
events while HAL is still initialising on startup.
|
|
Documented memstick as possible value of storage.bus in the spec.
|
|
Documented memstick and memstick_host namespace in spec.
|
|
Another fix for commit d29ea6b31b67bf540b23dfedfa1b7add4c22bce2:
- info.bus is deprecated, don't add this key
- info.subsystem should get only set in the subsystem specific
code if it differs from the subsystem or in other rare cases
|
|
Fixed commit d29ea6b31b67bf540b23dfedfa1b7add4c22bce2: keep
subsystem handler and related code in alphabetical order.
|
|
This adds basic memory stick support to hal. It's enough to get
automounting up, but it doesn't expose any of the memory stick specific
attributes yet since I'm not sure which of them are especially useful.
|
|
Cleaned up handling of volume filesystem information. Don't call
libvolume_id functions in the volume prober to get the following
information:
- volume.fsusage
- volume.fstype
- volume.fsversion
- volume.uuid
- volume.label
HAL now simply use the already in the HotplugEvent stored information
from udev, since udev already called libvolume_id to get these info.
|
|
Merge commit '315ca276ffdde9a0cba809f67cddf58f258ee1d3'
|
|
Fixed commit 151957477daaf985acdb2d7bda5b4a418c612cf3: don't
call computer_probing_helper_done() twice.
|
|
This allows us to add OLPC specific code in the future. Patch coming up.
|
|
While doing some patches for OLPC, all the OFW firmware strings are not
terminated with \n\0 just with \0.
This means that we get results like OLP when we should be getting
OLPC.
data = OLPC0
index = 01234
len = 4
data[len-1] = C
data = IBMn0
index = 01234
len = 4
data[len-1] = \n
Now, the isspace check checks for \n, so we can remove the explicit \0
termination, and rely on the code three lines down. Removing the
explicit code allows non-newline terminated strings to be got with
hal_util_get_string_from_file().
|
|
HAL has currently a massive problem with Device Mapper devices,
especially on coldplug, and parallel device handling .
Since dm-devices are virtual devices and have no parent we can
never say (when HAL process the hotplug queue) which the related
parent storage device (e.g. /dev/sdb1) is and when it will be
available.
Changed HAL to identify dm-devices on hotplug/coldplug and to
mark them as such in the HotplugEvent with is_dm_device=TRUE.
When the hotplug queue get processed, delay all dm-device as long
as there are still non-dm block devices in the queue to be sure
that all block devices/volumes are available when the Device
Mapper block devices get handled.
|
|
Fixed typo (s/prefered/preferred) and adjusted description of
volume.fstype.alternative.preferred to me more clear.
|
|
Check the acpi video module parameter brightness_switch_enabled via
sysfs to find out of the kernel handles already brightness changes if
a brightness key get pressed.
This works only for the generic 'video' module and only on HAL startup.
If someone change the module settings on runtime without reload the
module the value of brightness_in_hardware can be false. We can live
with this situation, since you should know what you do if you change
module parameter on runtime.
|
|
Fixed md related code to find/set the parent devie in
hotplug_event_begin_add_blockdev().
|
|
Added cciss as possible storage.bus to spec.
|
|
Added support for HP Smart Array CCISS block devices, which are
in recent kernel versions virtual block/storage devices and no
longer pci based (also if the Smart Array controller is a PCI
device).
|