Difference between revisions of "TODO"
(→TODO list) |
|||
| Line 1: | Line 1: | ||
| − | + | = TODO list = | |
Some project ideas | Some project ideas | ||
| − | == | + | == Add support for wifi and bluetooth == |
| − | + | Add support for most used USB wifi and bluetooth USB keys. | |
| + | == Bluetooth remote control == | ||
| − | + | Add a remote control via bluetooth and wifi. | |
| − | + | == Make more human-readable flash.log == | |
| − | + | The flash.log in the nfs share more human-readable. Maybe add some more info inside. | |
| − | |||
| − | |||
| − | |||
| − | + | == PHP interface for reflashing camera(s) == | |
| − | + | PHP web interface to reflash one or multiple cameras with ktest, brows the log for each of them and why not run some tests like get an JPEG image and check if the image is "normal". The interface should allow to configure all ktest params individually per camera. | |
| − | == | + | == The streamer == |
| − | + | === Audio === | |
| − | + | Implement audio from alsa source synced with video. | |
| − | === | + | === Subtitles === |
| − | + | Implement subtitles what can be redden or not by the client. Subtitles should be able to handle info from EXIF and any user defined data. | |
| + | |||
| + | === Write to disk === | ||
| + | |||
| + | Implement an option to stream to the network and/or to the hard drive / CF. | ||
| + | |||
| + | == Exif == | ||
| + | |||
| + | Add fields for geo-location (GPS), orientation of the camera and some user defined data. The camera model should also include sensor type and model. | ||
| + | |||
| + | == Make a block diagram of the boot process == | ||
| + | |||
| + | It is needed for new devs and to be able to have an overview of the process and be able to enhance it. | ||
| + | |||
| + | == Better usage of busybox == | ||
| + | |||
| + | Enable cool and useful staff from busybox as for example passwd, cfdisk, minicom, ... | ||
| + | (Please post a list to this section for discussion before doing what) | ||
| + | |||
| + | == Hardware Test Software == | ||
| + | |||
| + | Hmm... will be described later. | ||
| + | |||
| + | == Do some magic to be able to pass params to the kernel over reboot == | ||
| + | |||
| + | Implement a way to pass params to the next booted kernel. This can be done in 2 different ways: | ||
| + | |||
| + | * passing kernel params truth RAM | ||
| + | * using KEXEC kernel function | ||
| + | * simulate the green button pressure at boot time (to boot in flashing mode) | ||
| + | * after flashing the camera from network boot erase the bit saying what the green button was pressed | ||
| + | |||
| + | == Green button == | ||
| + | |||
| + | The green button on the back of the camera can be used in different ways: | ||
| + | |||
| + | * at power up to put the CPU in flashing mode | ||
| + | * 1-2 seconds after power up and hold for ~8 seconds to boot the camera with squashfs and tmpfs instead of jffs. When a special script can be used to relink safe files from sqauashfs to jffs. (cf [http://wiki.elphel.com/index.php?title=TODO&action=submit#Change_the_structure_of_the_boot_process]) | ||
| + | * something else user configurable after init 5 | ||
| + | |||
| + | == Init levels == | ||
| + | |||
| + | Implement init levels, init 3 should have only GNU/Linux with telnetd, everything camera specific should run from init 5. The default level will be 5, but ktest should be able to pass init=3 to the kernel. | ||
| + | |||
| + | == Ktest == | ||
| + | |||
| + | === Rename ktest === | ||
| + | Ktest should be renamed to something else resuming it's function. | ||
| + | |||
| + | === Better output === | ||
| + | Some more output should be added to ktest to make it more verbose and user-friendly. | ||
| + | |||
| + | === New function === | ||
| + | Add new function and param to read & copy partitions from the flash to NFS for debuging. | ||
| + | |||
| + | == Ethernet leds == | ||
| + | |||
| + | Hack in to the ehternet driver to make a better usage of leds. For example during flash with pressed button boot with orange led ON, blink orange while booting the kernel, blink with the green led while copying from NFS to flash and green ON when completely flashed and ready to be rebooted. While normal operation leds can be used in a more nice way when now. | ||
| + | |||
| + | == Change the structure of the boot process == | ||
| + | |||
| + | I like how partitions are organized in OpenWRT. The root partition should be read only squashfs. The same root partition should be used to boot from flash or from ktest. Then a read/write flash or tmpfs partition can be mounted, squashfs remounted to a new directory. And files from / linked to the /squashfs directory. | ||
| + | |||
| + | During the flash process files from squashfs will be symlinked to the tmpfs and to the flash r/w partition. | ||
| + | |||
| + | Like what we always have a clean squashfs, links from the r/w jffs partition can be removed and replaced by real files with different content. We can also implement a function for the green button to erase the files from the r/w partition and relink them to /squashfs. It's a simple way to get back to a known point without reflashing the camera. | ||
Revision as of 17:00, 17 August 2007
Contents
- 1 TODO list
- 1.1 Add support for wifi and bluetooth
- 1.2 Bluetooth remote control
- 1.3 Make more human-readable flash.log
- 1.4 PHP interface for reflashing camera(s)
- 1.5 The streamer
- 1.6 Exif
- 1.7 Make a block diagram of the boot process
- 1.8 Better usage of busybox
- 1.9 Hardware Test Software
- 1.10 Do some magic to be able to pass params to the kernel over reboot
- 1.11 Green button
- 1.12 Init levels
- 1.13 Ktest
- 1.14 Ethernet leds
- 1.15 Change the structure of the boot process
TODO list
Some project ideas
Add support for wifi and bluetooth
Add support for most used USB wifi and bluetooth USB keys.
Bluetooth remote control
Add a remote control via bluetooth and wifi.
Make more human-readable flash.log
The flash.log in the nfs share more human-readable. Maybe add some more info inside.
PHP interface for reflashing camera(s)
PHP web interface to reflash one or multiple cameras with ktest, brows the log for each of them and why not run some tests like get an JPEG image and check if the image is "normal". The interface should allow to configure all ktest params individually per camera.
The streamer
Audio
Implement audio from alsa source synced with video.
Subtitles
Implement subtitles what can be redden or not by the client. Subtitles should be able to handle info from EXIF and any user defined data.
Write to disk
Implement an option to stream to the network and/or to the hard drive / CF.
Exif
Add fields for geo-location (GPS), orientation of the camera and some user defined data. The camera model should also include sensor type and model.
Make a block diagram of the boot process
It is needed for new devs and to be able to have an overview of the process and be able to enhance it.
Better usage of busybox
Enable cool and useful staff from busybox as for example passwd, cfdisk, minicom, ... (Please post a list to this section for discussion before doing what)
Hardware Test Software
Hmm... will be described later.
Do some magic to be able to pass params to the kernel over reboot
Implement a way to pass params to the next booted kernel. This can be done in 2 different ways:
- passing kernel params truth RAM
- using KEXEC kernel function
- simulate the green button pressure at boot time (to boot in flashing mode)
- after flashing the camera from network boot erase the bit saying what the green button was pressed
Green button
The green button on the back of the camera can be used in different ways:
- at power up to put the CPU in flashing mode
- 1-2 seconds after power up and hold for ~8 seconds to boot the camera with squashfs and tmpfs instead of jffs. When a special script can be used to relink safe files from sqauashfs to jffs. (cf [1])
- something else user configurable after init 5
Init levels
Implement init levels, init 3 should have only GNU/Linux with telnetd, everything camera specific should run from init 5. The default level will be 5, but ktest should be able to pass init=3 to the kernel.
Ktest
Rename ktest
Ktest should be renamed to something else resuming it's function.
Better output
Some more output should be added to ktest to make it more verbose and user-friendly.
New function
Add new function and param to read & copy partitions from the flash to NFS for debuging.
Ethernet leds
Hack in to the ehternet driver to make a better usage of leds. For example during flash with pressed button boot with orange led ON, blink orange while booting the kernel, blink with the green led while copying from NFS to flash and green ON when completely flashed and ready to be rebooted. While normal operation leds can be used in a more nice way when now.
Change the structure of the boot process
I like how partitions are organized in OpenWRT. The root partition should be read only squashfs. The same root partition should be used to boot from flash or from ktest. Then a read/write flash or tmpfs partition can be mounted, squashfs remounted to a new directory. And files from / linked to the /squashfs directory.
During the flash process files from squashfs will be symlinked to the tmpfs and to the flash r/w partition.
Like what we always have a clean squashfs, links from the r/w jffs partition can be removed and replaced by real files with different content. We can also implement a function for the green button to erase the files from the r/w partition and relink them to /squashfs. It's a simple way to get back to a known point without reflashing the camera.
