On Tue, Sep 06, 2011 at 02:30:07PM +0200, Martin Jansa wrote: > On Sat, Sep 03, 2011 at 12:00:08PM +0200, Yoram bar-haim wrote: > > I meant that it works for me and I can confirm the report about the last > > shr-2.6.39-nodrm in repository. > > my patch did not include 44701728692f6b70c954303db9d8ba20e5701637 (ignore > > unexpected interrupt) and 3e661cec4f3f06a004200d254a2c1a31544b61fa (report > > pressure), so the problem might be one of those, actually I'm working on it > > right now, but without debug board it takes me time... > > I've tried to remove both in oe8, but someone reported it still panics.
sorry for confusion thanks to pespin I've noticed that oe7 was the one with only 1 ts patch and oe8 is without ts patches r2-oe6 was old 2.6.39.1, r3-oe6 was first 2.6.39.4 and had 3 ts patches, r3-oe7 only 1 ts patch r3-oe8 is 2.6.39.4 without ts patches > Now I've reverted all 3 again before someone sends working patch (can > you send yours?) or I'll be at home to test it on device.. > > > BTW, what is the correct way do define local source directory for > > SRC_URI ? it gives me trubles... > > What exactly do you need? You can add patch to SRC_URI and you're all > set. If you meant to use own checkout without unpack/patch tasks from > bitbake then check conf/local-builds.inc for example how to use srctree > gitpkgv classes and for kernel you have to add defconfig to your > checkout. > > Regards, > > > On Saturday, September 03, 2011 09:38:08 AM Martin Jansa wrote: > > > On Thu, Sep 01, 2011 at 07:02:36PM +0300, Yoram bar-haim wrote: > > > > I apllied the same patch locally whith minor modifications to the new > > > > code base, and it works like black magic... > > > > > > What do you mean? Does it work for you but it's black magic or it > > > doesn't work? > > > > > > Because someone reported yesterday that he gets kernel panic as soon as > > > he touches TS and I didn't test it on device yet.. > > > > > > Regards, > > > > > > > On Thursday, September 01, 2011 02:35:04 PM Martin Jansa wrote: > > > > > On Thu, Sep 01, 2011 at 02:10:31PM +0300, Yoram bar-haim wrote: > > > > > > I have it almost done eather, but it's better if you push your > > > > > > patch... > > > > > > > > > > Top 3 patches > > > > > https://gitorious.org/shr/linux/commits/shr-2.6.39-nodrm > > > > > and > > > > > http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=3aec4e > > > > > 8c10 6ed7fb77c94ffcbdad1a66e9f4be85 > > > > > > > > > > but didn't test it in runtime yet :/ > > > > > > > > > > > On Thursday, September 01, 2011 01:49:02 PM Martin Jansa wrote: > > > > > > > On Thu, Sep 01, 2011 at 09:21:48AM +0200, Martin Jansa wrote: > > > > > > > > On Wed, Aug 31, 2011 at 07:12:20PM +0300, Yoram bar-haim wrote: > > > > > > > > > So, does > > > > > > > > > https://gitorious.org/shr/linux/commits/shr-2.6.39-nodrm > > > > > > > > > already includes the openmoko.patch and shr.patch ? > > > > > > > > > can I just pathc onm top of this branch ? > > > > > > > > > > > > > > Btw I have it almost done.. will update to 2.6.39.4 and include 2 > > > > > > > ts patches today. > > > > > > > > > > > > > > > It will be more clear if you read openmoko.patch and shr.patch > > > > > > > > headers or repo description on gitorious: > > > > > > > > > > > > > > > > kernel repositories used in SHR project > > > > > > > > often rebased, so be aware > > > > > > > > > > > > > > > > om-2.6.34-stable is based on Openmoko om-2.6.34 > > > > > > > > (http://git.openmoko.org/?p=kernel.git;a=shortlog;h=refs/heads/om > > > > > > > > -2.6 .34 ) and contains latest stable/longterm upstream patch > > > > > > > > shr-2.6.34-nodrm is rebased on top of om-2.6.34-stable and > > > > > > > > contains common patches which are also usually included in > > > > > > > > qtmoko/debian kernel sources shr-2.6.34 is rebased on top of > > > > > > > > shr-2.6.34-nodrm and contains mostly glamo DRM patches from > > > > > > > > Thomas White > > > > > > > > (http://git.bitwiz.org.uk/?p=kernel.git;a=shortlog;h=refs/heads/g > > > > > > > > drm- 2.6 .34) > > > > > > > > > > > > > > > > The same for 2.6.37, but without DRM patches. > > > > > > > > > > > > > > > > openmoko.patch header: > > > > > > > > All patches from openmoko repository > > > > > > > > http://git.openmoko.org/?p=kernel.git;a=commit;h=164905f9f5843aa9 > > > > > > > > 4b04 eef7 24238c77dc47af0f > > > > > > > > > > > > > > > > So for 2.6.39, we have 2.6.39.1 as latest stable patch (2.6.39 > > > > > > > > release + 2.6.39.1 patch from tarbal) shr/linux:om-2.6.39-stable > > > > > > > > is rebased on top of 2.6.39.1 and used to create openmoko.patch > > > > > > > > http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.39.y. > > > > > > > > git;a =su mmary (git diff linux-2.6.39.y/2.6.39.1 > > > > > > > > > openmoko.patch) > > > > > > > > > > > > > > > > > > > > > > > > shr.patch header: > > > > > > > > All patches from shr kernel repository > > > > > > > > rebased on top of openmoko kernel repository > > > > > > > > > > > > > > > > https://gitorious.org/shr/linux/commits/shr-2.6.39-nodrm > > > > > > > > > > > > > > > > 5 > > > > > > > > 6 35c701e lis302dl: use ABS events rather then REL events > > > > > > > > 7 1d5cd43 input: lis302dl: fix the resume path > > > > > > > > 8 9521296 lis302dl accelerometer driver > > > > > > > > 9 eefe7bf Force GPS power up on resume if it were powered up > > > > > > > > on suspend > > > > > > > > > > > > > > > > 10 fd88443 Fix high power consumption in suspend > > > > > > > > 11 ae31803 wm8753: use snd_soc_jack on neo1973 > > > > > > > > 12 104353d ar6000_delay.patch > > > > > > > > 13 235c131 usbhost.patch > > > > > > > > 14 e342a4d Enable powering off after 8s POWER press > > > > > > > > 15 b9dfb66 glamo-display: fix WSOD for 242 timming > > > > > > > > 16 d952c22 Openmoko resume reason sysfs node ported from > > > > > > > > 2.6.29 > > > > > > > > 17 2d7ec7a nand/s3c2410: add mising badblocksbits value > > > > > > > > 18 2a067d5 glamo-mci: revert changes for Per's patchset > > > > > > > > 19 d9b3bc8 Revert "mmc: add none blocking mmc request > > > > > > > > function" > > > > > > > > 20 a194e92 Revert "mmc: mmc_test: add debugfs file to list all > > > > > > > > tests" 21 8a3a7aa Revert "mmc: mmc_test: add test for none > > > > > > > > blocking transfers" 22 711299a Revert "mmc: add member in mmc > > > > > > > > queue struct to hold request data" 23 101511c Revert "mmc: add > > > > > > > > a block request prepare function" 24 023e4b8 Revert "mmc: move > > > > > > > > error code in mmc_block_issue_rw_rq to a separate function." > > > > > > > > 25 6dd67d8 Revert "mmc: add a second mmc queue request member" > > > > > > > > 26 cc53cf6 Revert "mmc: add handling for two parallel block > > > > > > > > requests in issue_rw_rq" 27 76cc5df Revert "mmc: test: add > > > > > > > > random fault injection in core.c" > > > > > > > > > > > > > > > > And shr/linux:shr-2.6.39-nodrm is reabased on top of > > > > > > > > shr/linux:om-2.6.39-stable and shr.patch is created against > > > > > > > > om-2.6.39-stable (git diff origin/om-2.6.39-stable > shr.patch) > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > > > > > > On Wednesday, August 31, 2011 06:35:53 PM Martin Jansa wrote: > > > > > > > > > > On Wed, Aug 31, 2011 at 5:26 PM, Yoram bar-haim > > > > > > > > > > <[email protected]> > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > On Wednesday, August 31, 2011 05:48:49 PM you wrote: > > > > > > > > > > >> user space > > > > > > > > > > >> (http://atrey.karlin.mff.cuni.cz/~metan/evfilter/) or > > > > > > > > > > >> switching to tslib was one option, but later we were > > > > > > > > > > >> using kernel patch from Gennady Kupava > > > > > > > > > > >> s3c2410_ts: jitter less touchscreen for glamo, version 4 > > > > > > > > > > >> see: > > > > > > > > > > >> https://gitorious.org/shr/linux/commits/shr-2.6.37-nodrm > > > > > > > > > > >> or > > > > > > > > > > >> https://gitorious.org/shr/linux/commit/3f2ddad023c970a1136 > > > > > > > > > > >> f37b c19e 882eba b3 9d5dc directly > > > > > > > > > > > > > > > > > > > > > > This patch seems to only reduce the frequency of event, it > > > > > > > > > > > does not do any filtering or modification of the events. > > > > > > > > > > > > > > > > > > > > Which makes events for evdev usable.. > > > > > > > > > > > > > > > > > > > > BTW: reducing of event frequency == filtering :) > > > > > > > > > > > > > > > > > > > > >> You can try to apply referenced patch to 2.6.39 branch > > > > > > > > > > >> and > > > > > > > > > > >> update it if needed and then test it from > > > > > > > > > > >> meta-smartphone/meta-openmoko/.... Then please send > > > > > > > > > > >> tested > > > > > > > > > > >> patch to shr-devel and I'll apply it to shr-2.6.39-nodrm > > > > > > > > > > >> and meta-smartphone sooner. Thanks! > > > > > > > > > > >> > > > > > > > > > > >> Regards, > > > > > > > > > > > > > > > > > > > > > > I will try to see what can be done,but I'm not sure yet > > > > > > > > > > > what kind of solution should it be... > > _______________________________________________ > > Shr-devel mailing list > > [email protected] > > http://lists.shr-project.org/mailman/listinfo/shr-devel > > -- > Martin 'JaMa' Jansa jabber: [email protected] -- Martin 'JaMa' Jansa jabber: [email protected]
signature.asc
Description: Digital signature
_______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
