1.1 --- a/README.txt Mon May 28 23:44:25 2018 +0200
1.2 +++ b/README.txt Tue May 29 00:25:45 2018 +0200
1.3 @@ -26,6 +26,22 @@
1.4 configuring and building the software. Building can be done after the steps
1.5 described below.
1.6
1.7 +Configuring this Software
1.8 +-------------------------
1.9 +
1.10 +Some files may need to be adjusted for the device on which the software is to
1.11 +be deployed. A script is provided to check and update them:
1.12 +
1.13 +$LANDFALL/tools/checkconfig.sh
1.14 +
1.15 +(Here, $LANDFALL needs to expand to the location of this distribution.)
1.16 +
1.17 +For example:
1.18 +
1.19 +$LANDFALL/tools/checkconfig.sh qi_lb60
1.20 +
1.21 +This configures the files for the Ben NanoNote.
1.22 +
1.23 Installing this Software
1.24 ------------------------
1.25
1.26 @@ -89,7 +105,6 @@
1.27 input - input event delivery
1.28 keypad - keypad/keyboard scanning
1.29 lcd - LCD and other display peripheral support
1.30 - panel - device-specific panel definitions
1.31 pwm - pulse width modulation support
1.32 spi - serial peripheral interface support
1.33
1.34 @@ -130,7 +145,6 @@
1.35 \-> dev_display_qi_lb60 Display control
1.36 \-> dev_backlight_spi_ili8960 Backlight control
1.37 \-> dev_spi_jz4740 Backlight communication
1.38 - \-> dev_panel_qi_lb60 Panel information
1.39
1.40 And here is how the Letux 400's framebuffer is supported:
1.41
1.42 @@ -138,15 +152,14 @@
1.43 \-> dev_display_letux400 Display control
1.44 \-> dev_backlight_pwm Backlight control
1.45 \-> dev_pwm_jz4730 Backlight communication
1.46 - \-> dev_panel_letux400 Panel information
1.47
1.48 (*) fb-drv links to the same generic JZ4740 LCD controller library in both
1.49 cases
1.50
1.51 Here, the CPM device provides access to the clock and power management
1.52 functionality, the display device provides access to the backlight and is
1.53 -responsible for configuring pins for the display, and the panel device
1.54 -provides information about the screen that the LCD controller needs.
1.55 +responsible for configuring pins for the display. Panel information is
1.56 +provided via a dynamically-loaded library.
1.57
1.58 Potential Improvements
1.59 ----------------------
1.60 @@ -159,9 +172,9 @@
1.61 by libraries. For example, GPIO functionality is currently not exposed via a
1.62 server.
1.63
1.64 -Panel device servers may eventually be replaced by simple resources given that
1.65 -their only job is to provide precomputed data via a capability channel. This
1.66 -could be done using a file bundled with the payload.
1.67 +Panel details are provided by libraries containing the structure definitions
1.68 +required by the LCD device code. These libraries may eventually be replaced by
1.69 +simple resource data files.
1.70
1.71 Framebuffer device servers are not currently used, since fb-drv effectively
1.72 offers the desired functionality together with other things.