<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hey i have a silly question... <br>I was trying to build the kernel but i am getting this error<br><br><br>+ VERSION=<br>+ '[' -d .git ']'<br>++ git show --pretty=oneline<br>++ head -n1<br>++ cut '-d ' -f1<br>++ cut -b1-16<br>+ HEAD=cfea911c6c57eebd<br>++ git branch<br>++ grep '^*'<br>++ cut '-d ' -f2<br>+ BRANCH=mystable<br>+ VERSION=-mystable_cfea911c6c57eebd<br>+ make -j5 ARCH=arm EXTRAVERSION=-mystable_cfea911c6c57eebd<br>../arm/bin/arm-angstrom-linux-gnueabi-gcc: ../arm/bin/arm-angstrom-linux-gnueabi-gcc: cannot execute binary file<br> CHK include/linux/version.h<br> SYMLINK include/asm-arm/arch -> include/asm-arm/arch-s3c2410<br>make[1]: `include/asm-arm/mach-types.h' is up to date.<br> CHK include/linux/utsrelease.h<br> CC
scripts/mod/empty.o<br>/bin/sh: ../arm/bin/arm-angstrom-linux-gnueabi-gcc: cannot execute binary file<br>make[2]: *** [scripts/mod/empty.o] Error 126<br>make[1]: *** [scripts/mod] Error 2<br>make: *** [scripts] Error 2<br>+ exit 1<br><br>Please help me out with this<br><br><br>--- On <b>Fri, 12/5/08, openmoko-kernel-request@lists.openmoko.org <i><openmoko-kernel-request@lists.openmoko.org></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">From: openmoko-kernel-request@lists.openmoko.org <openmoko-kernel-request@lists.openmoko.org><br>Subject: openmoko-kernel Digest, Vol 85, Issue 17<br>To: openmoko-kernel@lists.openmoko.org<br>Date: Friday, December 5, 2008, 2:27 AM<br><br><pre>Send openmoko-kernel mailing list submissions to<br> openmoko-kernel@lists.openmoko.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br>
http://lists.openmoko.org/mailman/listinfo/openmoko-kernel<br>or, via email, send a message with subject or body 'help' to<br> openmoko-kernel-request@lists.openmoko.org<br><br>You can reach the person managing the list at<br> openmoko-kernel-owner@lists.openmoko.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of openmoko-kernel digest..."<br></pre><pre>Today's Topics:<br><br> 1. Re:[PATCH] looks like cut/paste error (Andy Green)<br> 2. Re:[PATCH] andy-tracking merge breakage (Werner Almesberger)<br> 3. Re:[PATCH] andy-tracking merge breakage (Andy Green)<br> 4. Re:[PATCH] andy-tracking merge breakage (Werner Almesberger)<br> 5. [PATCH] fix-gta03-gsm-module-startup.patch (Andy Green)<br> 6. Re:Openmoko Bug #2115: White Screen of Death (even without<br> suspend) (Openmoko Public Trac)<br> 7. [PATCH] fix-s3c-eint-offset-calc-error.patch (Andy Green)<br> 8. Re:Openmoko Bug #2078:
glamo-mci.0: ****** insanity timeout<br> (Openmoko Public Trac)<br> 9. Re:Openmoko Bug #2078: glamo-mci.0: ****** insanity timeout<br> (Openmoko Public Trac)<br></pre><pre>-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>Somebody in the thread at some point said:<br>| On Thu, Dec 04, 2008 at 08:38:39AM +0000, Andy Green wrote:<br>|> -----BEGIN PGP SIGNED MESSAGE-----<br>|> Hash: SHA1<br>|><br>|> Somebody in the thread at some point said:<br>|> | On Thu, Dec 04, 2008 at 01:40:39PM +0700, Sean McNeil wrote:<br>|> |> The comment leads me to believe there is a cut/paste error on<br>masking<br>|> of<br>|> |> irq.<br>|> |><br>|> |<br>|> | Hi Sean,<br>|> |<br>|> | Yes, I've seen this. I've fixed this along with other minor<br>things I've<br>|> | noticed. The code is not pushed yet.<br>|><br>|> Do you want to take Wener's rtc patch as well then and I will rebase<br>|> when you update
balaji-tracking.<br>|><br>|<br>| Yes, I'll do that.<br>|<br>| Will update soon.<br><br>Great it just reminds me we are breaking new ground now updating<br>pending-tracking for the first time, let's hope that isn't too rough.<br><br>- -Andy<br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.9 (GNU/Linux)<br>Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org<br><br>iEYEARECAAYFAkk3uGoACgkQOjLpvpq7dMq3eACfeNpKjAAtAtNzeiX8y5In34zi<br>GZgAnimGv34d533Le8mDDZxHUhUS4HH+<br>=Kfe2<br>-----END PGP SIGNATURE-----<br><br><br></pre><pre>Andy Green wrote:<br>> Huh, it can be the new s3c pm stuff from Ben... what does it do, just<br>> not come back?<br><br>Yup, just plays dead. No response to AUX, POWER, or alarm.<br>Hardware reset works, so we're at least not powered down.<br><br>> At least there's the chance for git bisect type attack now.<br><br>Yes ! I'm very much looking forward to using that :-)<br><br>However, it seems that this time
it won't help. We still have too<br>many build failures in our tree :-( Well, perhaps I can fix these<br>"transparently" from quilt on top of each commit git-bisect gives<br>me ...<br><br>- Werner<br><br><br></pre><pre>-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>Somebody in the thread at some point said:<br>| Andy Green wrote:<br>|> Huh, it can be the new s3c pm stuff from Ben... what does it do, just<br>|> not come back?<br>|<br>| Yup, just plays dead. No response to AUX, POWER, or alarm.<br>| Hardware reset works, so we're at least not powered down.<br><br>Ha that's funny because that was how the GTA03 resume was acting<br>yesterday. It can be that the issue is in the new s3c pm stuff and is<br>common to GTA02 as well then.<br><br>|> At least there's the chance for git bisect type attack now.<br>|<br>| Yes ! I'm very much looking forward to using that :-)<br>|<br>| However, it seems that this time it won't help. We still have
too<br>| many build failures in our tree :-( Well, perhaps I can fix these<br>| "transparently" from quilt on top of each commit git-bisect gives<br>| me ...<br><br>It's hard now everything lives forever and it takes a long time to<br>switch build config and back again to confirm what's building on GTA03<br>as in this last instance didn't trash GTA02 build. Previously I would<br>just fix it and rewrite the branch like it never existed, now each build<br>problem will always exist in history, along with the fix subsequently.<br><br>- -Andy<br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.9 (GNU/Linux)<br>Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org<br><br>iEYEARECAAYFAkk3wFQACgkQOjLpvpq7dMrxbwCeMqPFLBy+8eFea4lpv3ktBJtM<br>yzUAn1q//102vh/O7znYfQVsRSSrz1g1<br>=S0zZ<br>-----END PGP SIGNATURE-----<br><br><br></pre><pre>Andy Green wrote:<br>> It's hard now everything lives forever and it takes a long time to<br>> switch build
config and back again to confirm what's building on GTA03<br>> as in this last instance didn't trash GTA02 build.<br><br>Hmm, maybe you need a bit more memory and ccache. When everything lives<br>in some cache, git-checkout is almost instantaneous and builds are<br>reasonably fast as well, about one minute for a kernel+modules build.<br><br>> Previously I would<br>> just fix it and rewrite the branch like it never existed, now each build<br>> problem will always exist in history, along with the fix subsequently.<br><br>Perhaps we need a little nazibot that only allows commits that<br>don't break the builds ? :)<br><br>Actually, git-bisect could use a "dunno" option in general.<br>Sometimes, even if the builds are perfect, you hit just some other<br>showstopper that keeps you from probing the problem you're chasing.<br><br>- Werner<br><br><br></pre><pre>Power on is active low for GTA03 GSM module<br><br>Signed-off-by: Andy Green
<andy@openmoko.com><br>---<br><br> arch/arm/mach-s3c6410/om-gta03-features.c | 4 ++--<br> 1 files changed, 2 insertions(+), 2 deletions(-)<br><br>diff --git a/arch/arm/mach-s3c6410/om-gta03-features.c<br>b/arch/arm/mach-s3c6410/om-gta03-features.c<br>index 32ea4a3..b1b8db5 100644<br>--- a/arch/arm/mach-s3c6410/om-gta03-features.c<br>+++ b/arch/arm/mach-s3c6410/om-gta03-features.c<br>@@ -84,7 +84,7 @@ static void om_gta03_features_pwron_set_on(enum feature<br>feature)<br> s3c_gpio_cfgpin(GTA03_GPIO_N_MODEM_RESET, S3C_GPIO_SFN(1));<br> gpio_direction_output(GTA03_GPIO_N_MODEM_RESET, 0);<br> <br>- gpio_direction_output(GTA03_GPIO_MODEN_ON, 1);<br>+ gpio_direction_output(GTA03_GPIO_MODEN_ON, 0);<br> s3c_gpio_setpull(GTA03_GPIO_MODEN_ON, S3C_GPIO_PULL_NONE);<br> s3c_gpio_cfgpin(GTA03_GPIO_MODEN_ON, S3C_GPIO_SFN(1));<br> msleep(1);<br>@@ -117,7 +117,7 @@ static void om_gta03_features_pwron_set_off(enum feature<br>feature)<br> break;<br>
case OM_GTA03_GSM:<br> /* remove power from WLAN / BT module */<br>- gpio_direction_output(GTA03_GPIO_MODEN_ON, 0);<br>+ gpio_direction_output(GTA03_GPIO_MODEN_ON, 1);<br> s3c_gpio_setpull(GTA03_GPIO_MODEN_ON, S3C_GPIO_PULL_NONE);<br> s3c_gpio_cfgpin(GTA03_GPIO_MODEN_ON, S3C_GPIO_SFN(1));<br> break;<br><br><br><br></pre><pre>#2115: White Screen of Death (even without suspend)<br>-----------------------------+----------------------------------------------<br> Reporter: RuiSeabra | Owner: openmoko-kernel <br> <br> Type: defect | Status: new <br> <br> Priority: normal | Milestone: FSO <br> <br>Component: System Software | Version: GTA02v5 <br> <br> Severity: major | Keywords: WSoD white screen death idle<br>fso gta02v5<br> Haspatch: 0
| Blockedby: <br> <br>Estimated: | Patchreview: <br> <br> Blocking: | Reproducible: always <br> <br>-----------------------------+----------------------------------------------<br><br>Comment(by RuiSeabra):<br><br> There's a patch and a test kernel at #1841 which so far looks like it<br> solved this problem for me.<br><br> This (#2115) bug doesn't happen with that kernel. So attached patch would<br> solve many problems in one.<br><br>-- <br>Ticket URL: <https://docs.openmoko.org/trac/ticket/2115#comment:5><br>docs.openmoko.org <http://docs.openmoko.org/trac/><br>openmoko trac<br></pre><pre>There's a bug in calculation of IRQ_EINT_BIT introduced on the test<br>branch for pm changes for s3c by Ben Dooks fixed in this patch.<br><br>There's also a bit of a mystery about how wake gets
to wake EINT<br>set of interrupts, I added a couple of lines that make it work for<br>EINT4+ but not sure what's meant to be there for EINT0-3.<br><br>Still, this gets GTA02 resume working again.<br><br>cc: Ben Dooks <ben-linux@fluff.org><br>Signed-off-by: Andy Green <andy@openmoko.com><br>---<br><br> arch/arm/mach-s3c2410/include/mach/irqs.h | 2 +-<br> arch/arm/plat-s3c24xx/irq-pm.c | 3 +++<br> 2 files changed, 4 insertions(+), 1 deletions(-)<br><br>diff --git a/arch/arm/mach-s3c2410/include/mach/irqs.h<br>b/arch/arm/mach-s3c2410/include/mach/irqs.h<br>index 4a82338..1d0629d 100644<br>--- a/arch/arm/mach-s3c2410/include/mach/irqs.h<br>+++ b/arch/arm/mach-s3c2410/include/mach/irqs.h<br>@@ -84,7 +84,7 @@<br> #define IRQ_EINT22 S3C2410_IRQ(50)<br> #define IRQ_EINT23 S3C2410_IRQ(51)<br> <br>-#define IRQ_EINT_BIT(x) ((x) - (IRQ_EINT4 + 4))<br>+#define IRQ_EINT_BIT(x) ((x) - IRQ_EINT4 + 4)<br> #define IRQ_EINT(x) (((x)
>= 4) ? (IRQ_EINT4 + (x) - 4) : (IRQ_EINT0 +<br>(x)))<br> <br> #define IRQ_LCD_FIFO S3C2410_IRQ(52)<br>diff --git a/arch/arm/plat-s3c24xx/irq-pm.c b/arch/arm/plat-s3c24xx/irq-pm.c<br>index b7acf1a..87bda52 100644<br>--- a/arch/arm/plat-s3c24xx/irq-pm.c<br>+++ b/arch/arm/plat-s3c24xx/irq-pm.c<br>@@ -34,6 +34,9 @@ int s3c_irq_wake(unsigned int irqno, unsigned int state)<br> {<br> unsigned long irqbit = 1 << (irqno - IRQ_EINT0);<br> <br>+ if (irqno >= IRQ_EINT4)<br>+ return s3c_irqext_wake(irqno, state);<br>+<br> if (!(s3c_irqwake_intallow & irqbit))<br> return -ENOENT;<br> <br><br><br><br></pre><pre>#2078: glamo-mci.0: ****** insanity timeout<br>-----------------------------+----------------------------------------------<br> Reporter: Sprite_tm | Owner: openmoko-kernel<br> Type: defect | Status: new <br> Priority: normal | Milestone: <br>Component:
System Software | Version: <br> Severity: normal | Keywords: <br> Haspatch: 0 | Blockedby: <br>Estimated: | Patchreview: <br> Blocking: | Reproducible: <br>-----------------------------+----------------------------------------------<br><br>Comment(by Sprite_tm):<br><br> Something like this?<br><br>-- <br>Ticket URL: <https://docs.openmoko.org/trac/ticket/2078#comment:6><br>docs.openmoko.org <http://docs.openmoko.org/trac/><br>openmoko trac<br></pre><pre>#2078: glamo-mci.0: ****** insanity timeout<br>-----------------------------+----------------------------------------------<br> Reporter: Sprite_tm | Owner: openmoko-kernel<br> Type: defect | Status: new <br> Priority: normal | Milestone:
<br>Component: System Software | Version: <br> Severity: normal | Keywords: <br> Haspatch: 0 | Blockedby: <br>Estimated: | Patchreview: <br> Blocking: | Reproducible: <br>-----------------------------+----------------------------------------------<br><br>Comment(by andy):<br><br> Yes... thanks for reminding me... I modified it a little for style and<br> sent it on stable-tracking<br><br><br>http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=7a55cd6f948a33c4452dd99da39e15efe832f2e2<br><br> because andy-tracking bases off stable-tracking, it inherits it too.<br><br> Thanks for finding the workaround and the patch.<br><br>-- <br>Ticket URL: <https://docs.openmoko.org/trac/ticket/2078#comment:7><br>docs.openmoko.org <http://docs.openmoko.org/trac/><br>openmoko
trac<br></pre><pre>_______________________________________________<br>openmoko-kernel mailing list<br>openmoko-kernel@lists.openmoko.org<br>http://lists.openmoko.org/mailman/listinfo/openmoko-kernel<br></pre></blockquote></td></tr></table><br>