From: Marc H. <mhu...@lo...> - 2008-03-31 15:17:37
|
Steve, Its working for me too in 302, but didn't changes recently in tslib (beating the driver into submission) require task-base rebuild and reflashing uImage as well as rootfs for things to work? At least that's what I did and its happy. Marc > -----Original Message----- > From: gum...@li... [mailto:gumstix-users- > bo...@li...] On Behalf Of Steve Sakoman > Sent: Monday, March 31, 2008 10:33 AM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] Touchscreen Stops Working > > Keith, > > I just tested the 302 pre-built basic-image with > verdex/consoleLCD16/netwifimicroSD and everything works. > > If you are still having problems, could you try flashing with the > pre-built image? > > Steve > > > On Sun, Mar 30, 2008 at 8:00 PM, Keith Howell <kc...@kc...> wrote: > > > > I re-flashed my verdex to the 302 build files and now my touchscreen > doesn't > > work any more. > > > > >From dmesg :- > > > > <6>tsc2003_i2c_detect: probing address 0x48 > > <3>i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free > > <3>i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free > > <3>i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free > > <3>i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free > > <3>i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free > > <3>i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free > > <4>i2c: error: exhausted retries > > <4>i2c: msg_num: 1 msg_idx: 0 msg_ptr: 0 > > <4>i2c: ICR: 000007e9 ISR: 00000004 > > <4>i2c: log: > > <6>I2C: i2c-0: PXA I2C adapter > > <6>tsc2003 i2c touch screen controller > > <6>Bill Gatliff <bgat at billgatliff.com > > <6>Nicholas Chen <nchen at cs.umd.edu> > > <6>tsc2003_i2c_detect: probing address 0x48 > > <4>i2c: error: timeout > > <4>i2c: msg_num: 1 msg_idx: 0 msg_ptr: 1 > > <4>i2c: ICR: 000017ee ISR: 00000005 > > <4>i2c: log: [00000045:000017e8] [00000085:000017ee] > > <6>I2C: i2c-1: PXA I2C adapter > > <6>i2c /dev entries driver > > > > My touchscreen was working before the reflash but now there is no entry > in the > > /dev tree for it. Also the evdev module is not listed in lsmod anymore. > > > > I guess this is related to the change made in the kernel module. Should > I > > stick with 302 or roll back to a previous revision? If rolling back is > the > > answer, what version was the driver prior to the fix? > > > > -- > > Keith Howell > > > > > > ----------------------------------------------------------------------- > -- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketpla > ce > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketpla > ce > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |