Re: further touchscreen / keyboard issues in the newest cvs version

Hi Paul,

So I got everything working! It turns out that the
CONFIG_KEYBOARD_ASIC3 option conflicts with the keyboard modules, but
only when the touchscreen is loaded as well. I did as you suggested and
compiled from cvs HEAD. I found that with the above mentioned option
set to "y" and the CONFIG_TOUCHSCREEN_ADS7846_SSP set to "y" then the
keyboard would not work. If I disabled the TOUCHSCREEN option the
keyboard would work, but the touchscreen would not (obviously :-) ).
But if I disabled the KEYBOARD_ASIC3 option than both would work.

Sorry about the rootdelay option question. Somehow I missed that as it
was going through the mailing list. I should have checked the archives.

Anyway everything seems to be working now, I'm going to start testing
the powerstuff, and write to internal flash. Any particular tests you
would like conducted? I don't use this as my main pda yet although now
that power seems to be working pretty well I'm serously considering it.

Thanks,
Daniel Steen

Paul Sokolovsky wrote:

>Hello Daniel,
>
>Sunday, February 11, 2007, 2:56:18 AM, you wrote:
>
>
>
>>Hi Paul,
>>
>>
>
>
>
>>I am using the latest haret off of the handhelds page for haret
>>(0.4.7). When I compile a kernel, and try to get it to boot I get the
>>little haret window ( Haret: booting linux) the bar fills to the end,
>>and then I get a green bar and a pink bar across the middle of the
>>screen and the screen slowly fades out.
>>
>>
>
> Well, according to last questions in FAQ section on
>http://www.handhelds.org/moin/moin.cgi/HaRET , that would mean that
>there was some issues on "preload" phase (except that it seems that
>preloader just overwrites FB with the code, so I don't really see blue
>lien either ;-) ). I myself didn't hit such case for quite some time
>(with known working kernel, of course), even though I have to admit
>that once in a while (1 of 20) I still get USB busted with haret load.
>
> Anyway, if you say that it is resolved now, it might be indeed some
>inconsistent CVS state, like partial update or update between commits.
>
>[]
>
>
>
Received on Sun Feb 11 2007 - 10:33:49 EST