| Summary: | Remove HAL dependency | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Javier Jardón <jjardon> |
| Component: | Server/Input/Core | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | medium | CC: | jcristau, martin.pitt, peter.hutterer, samuel.thibault, uzytkownik2 |
| Version: | git | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://www.freedesktop.org/wiki/Software/hal | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Javier Jardón
2009-08-22 09:00:50 UTC
Xorg uses HAL on *BSD, Linux, Solaris, and OpenSolaris. udev appears to be Linux only, so would not be a usable replacement. For a future libudev migration, here are some questions and answers that may come up. http://lists.freedesktop.org/archives/devkit-devel/2009-July/000392.html Patch sent to xorg-devel for comments, http://thread.gmane.org/gmane.comp.freedesktop.xorg.devel/2108 Since there is no suitable cross-platform replacement for HAL, we agreed last year that we'd have to return to platform-specific code for replacing HAL's functions, as described on http://www.x.org/wiki/XorgHAL Xorg 1.8 includes the xorg.conf.d replacement for HAL .fdi configuration for all platforms, and the udev implementation of the device discovery/ hotplug notification replacement for Linux platforms. Other platforms still need to implement their platform-specific replacements for the HAL device discovery & hotplug notification functionality. Removing from blocker list - the dependency is optional, and having it for the platforms that haven't yet provided an alternative is not going to stop the release. We still need to work on it, and will probably remove the option someday, but not this release. I'm going to call this one as FIXED, since it only has an obvious replacement on Linux (TTBOMK), where we preferentially use udev anyway. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.