hal/doc TODO,1.28,1.29
David Zeuthen
david at freedesktop.org
Sun Jul 18 10:23:18 PDT 2004
Update of /cvs/hal/hal/doc
In directory pdx:/tmp/cvs-serv14805/doc
Modified Files:
TODO
Log Message:
2004-07-18 David Zeuthen <david at fubar.dk>
* doc/TODO: updated; changed the
http://freedesktop.org/cgi-bin/viewcvs.cgi/hal/hal/doc/TODO
page on fd.o Wiki to point to doc/TODO on HEAD.
Index: TODO
===================================================================
RCS file: /cvs/hal/hal/doc/TODO,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -d -r1.28 -r1.29
--- TODO 4 Jul 2004 21:57:53 -0000 1.28
+++ TODO 18 Jul 2004 17:23:16 -0000 1.29
@@ -1,84 +1,172 @@
CVSID:$Id$
-This document is the TODO list for the HAL project. Feel free to add/remove
-entries if you get an idea or implement one of these.
+This document is the TODO list for the HAL project. Feel free to
+add/remove entries if you get an idea or implement one of these. If
+you want to work on one of these you might want to send a patch for
+that updates this file to reflect it.
- - Add support for removal of class devices - we should probably remove
- the properties merged and send out a d-bus signal; see comments in
- hald/linux/osspec.c:remove_class_device(). This can now easily be tested
- with modprobe and rmmod on the sg kernel module
+============================================================================
+* CD Burning problems (davidz is working on this)
+============================================================================
- - Persistent device store
- Device should be persistent (e.g. saved in a file) so i) we don't need
- to check fdi files each and every time we start up; and ii) device
- properties are persistent across time
+hald should use O_EXCL when polling the CD drive. Bastien Nocera
+(magicdev maintainer) confirms that magicdev uses this and this fixes
+the burning problems.
- - How this should be implemented should probably be discussed on the
- mailing list; one way is to use a binary format (performance), another
- way is to use a human-readable file (maybe even, ugh, xml). I personally
- opt the the binary format
+============================================================================
+* Multi-function USB devices (davidz is working on this)
+============================================================================
- - There should be a commandline tool for the administrator to easily
- purge the database
+Here's one
- - We still need to scan all devices at startup; most of the logic is
- already implemented but it's a bit tricky to figure out.
+ http://www.pc-netto.dk/templates/product.asp?productguid=133%2D09
- - Support for more bus-devices and class-devices
+this one got one USB interface for the PS/2 keyboard and one USB
+interface for the PS/2 mouse. Here's another one
- - Testing framework; probably only feasible for non-os specific code, e.g.
- the whole device and device store framework
+ http://www.superwarehouse.com/HP_PSC_2175/Q3068A/p/286911
- - Support for more filesystem sniffing and volume label extraction
- (see hald/linux/block_class_device.c:detect_fs). Only cdfs and udf
- seems to be missing
+that got a many USB interfaces for printing, scanning, media reader
+etc. We need a better way of representing such devices; if possible
+in a way that doesn't change already written .fdi files
- - Caching in libhal; the API is ready for it. Remember you cannot use
- glib or other dependencies; we can only depend on libc and dbus!
+============================================================================
+* Input devices
+============================================================================
- - Property access control and per-user properties
- Non-root users should only have read-access to the devices except
- in properties where the key starts with 'user.'. Also properties
- starting with 'user.' should be per-user (and per-box, e.g. don't
- save them in a dotfile or dotdirectory in the users homedir; see TODO
- item for persistent device store)
+We should somehow expose the protocol used; e.g. for input.device we
+should have input.protocol=Linux|PS2 etc.
- - Support for signed fdi files
- One way to implement this is using an existing PKI framework.
- There should be an easy way to sign an .fdi file e.g. a hal-sign-fdi
- tool. There should also be a directory where vendors can easily
- drop the public key.
- Also, we should probably consider emitting a dbus-signal or setting
- a property so desktop environments can figure display an appropriate
- dialog with the .fdi file is unsigned. Probably needs discussion on the
- mailling list.
+============================================================================
+* More property types
+============================================================================
- - Callouts are currently called in order, so if a callout hangs then
- no others will be called. There should be a timeout which kills the
- callout after a certain period of time. (5 seconds? 10? 15?)
+The gstreamer guys expressed desire for some more property types; here's
+some ideas
- - Don't remove a device before all the children are removed
+ - lists; should by of ANY type; info.capabilities should probably be
+ a list of strings
- - Clean shutdown
- The daemon should listen for SIGTERM, SIGQUIT and SIGINT and shut
- itself down cleanly. This includes removing all devices from the GDL
- so that callouts can clean up any state on disk.
+ - ranges, e.g. [3.4;43.2[, [2.0;3.0]
- - There needs to be a way to match on capabilities in the FDI files.
- It'd also be nice if there were author/maintainer info in there.
+============================================================================
+* Root HalDevice representing system
+============================================================================
-Issues with Linux kernel 2.6.*:
+The CITY OF LOST DEVICES HalDevice should be renamed to Computer and
+contain information about the system such as the kernel version, X.org
+version etc.
- - The ide%d, parent of IDE devices, are no under /sys/bus or /sys/class.
- In HAL we call it ide_host
- - 16-bit PCMCIA devices (e.g. not CardBus) is not in sysfs
- - It would be nice if the kernel could poll for media by itself; right
- now we poll for media in hald/linux/block_class_device.c:detect_media
+============================================================================
+============================================================================
+ NEW MAJOR RELEASE, UPDATE SPEC
+============================================================================
+============================================================================
- - The ide_cs driver for PCMCIA card readers has a bug where it removes
- and inserts the block device when we do a simple readonly open on the
- top block device (to poll for media)
+
+============================================================================
+* Locking of devices
+============================================================================
+
+It should be possible to acquire (advisory) locks on devices, for
+discussion see this thread
+
+ http://freedesktop.org/pipermail/hal/2004-July/000579.html
+
+============================================================================
+* Removal of class devices
+============================================================================
+
+Add support for removal of class devices - we should probably remove
+the properties merged and send out a d-bus signal; see comments in
+hald/linux/osspec.c:remove_class_device(). This can now easily be
+tested with modprobe and rmmod on the sg kernel module
+
+
+============================================================================
+* .fdi file enhancements
+============================================================================
+
+There needs to be a way to match on capabilities in the FDI files.
+It'd also be nice if there were author/maintainer info in there.
+
+One way to implement this is using an existing PKI framework. There
+should be an easy way to sign an .fdi file e.g. a hal-sign-fdi
+tool. There should also be a directory where vendors can easily drop
+the public key.
+
+Also, we should probably consider emitting a dbus-signal or setting a
+property so desktop environments can figure display an appropriate
+dialog with the .fdi file is unsigned. Probably needs discussion on
+the mailing list.
+
+============================================================================
+* Persistent device store
+============================================================================
+
+Kay Sievers have implemented parts of it, see
+
+ http://freedesktop.org/pipermail/hal/2004-June/000388.html
+
+for details and discussion. This mail also covers things like clean
+shutdown
+
+
+============================================================================
+* Power management
+============================================================================
+
+There is already some discussion here
+
+ http://freedesktop.org/pipermail/hal/2004-July/000544.html
+
+about abstracting both ACPI and pmud.
+
+============================================================================
+* Support for more bus-devices and class-devices
+============================================================================
+
+Some low hanging fruit might be video4linux stuff
+
+============================================================================
+* Testing
+============================================================================
+
+Testing framework; probably only feasible for non-os specific code,
+e.g. the whole callout, device and device store framework
+
+============================================================================
+* Caching in libhal
+============================================================================
+
+Caching in libhal; the API is ready for it. Remember you cannot use
+glib or other dependencies; we can only depend on libc and dbus!
+
+
+============================================================================
+* Property access control and per-user properties
+============================================================================
+
+Non-root users should only have read-access to the devices except in
+properties where the key starts with 'user.'. Also properties starting
+with 'user.' should be per-user (and per-box, e.g. don't save them in
+a dotfile or dotdirectory in the users homedir; see TODO item for
+persistent device store)
+
+============================================================================
+* Callouts
+============================================================================
+
+Callouts are currently called in order, so if a callout hangs then no
+others will be called. There should be a timeout which kills the
+callout after a certain period of time. (5 seconds? 10? 15?)
+
+============================================================================
+* Device Removal
+============================================================================
+
+We shouldn't remove a device before all the children are removed
More information about the hal-commit
mailing list