Hi Steve,
On Thu, Mar 11, 2010 at 10:26:58PM +0100, Steve Markgraf wrote:
This problem was caused since the apps tried to write
to the C123
display, and the display driver couldn't access I2C properly since
it had been initialized as UWire on the C155 after we introduced
separate images for the boards.
ah, of course.
I have implemented a simple layer for abstracting the
display
drivers on both targets, which you can find in my /pending branch.
I've decided to implement this in a different way (see master branch),
allowing for run-time driver selection. We've been talking about
heading for building only one set of images for the compal phones and
doing runtime detection of E88 / E99 board.
The 'struct display_driver' approach already prepares for this by not
introducing further board-specific compilation differences.
Putting a string on the display now works on both
targets with
display_puts();
same is now true not for current master, at least it works on
my phones.
The latest commit in my branch is adding a chip-select
for the
display which is tested on the C155 and the J100i.
I've cherry-picked that, thanks.
Cheers,
Harald
--
- Harald Welte <laforge(a)gnumonks.org>
http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)