Linux 2.4 kernel and tool chain

* Linux 2.4 kernel and tool chain
       [not found] <20060119073110.D31FE80627@linux.omap.com>
@ 2006-01-19  7:59 ` chandrashekhar singh
  2006-01-19  8:13   ` Komal Shah
  0 siblings, 1 reply; 3+ messages in thread
From: chandrashekhar singh @ 2006-01-19  7:59 UTC (permalink / raw)
  To: linux-omap-open-source

Dear All,

I want linux 2.4 kernel for OMAP 2420 and OMAP 730 and its cross tool chain.
I'm unable to find it  with the help of google. so if some  one have it please
send me your link so that i can download it.

BR
chandrashekhar

----- Original Message ----- 
From: <linux-omap-open-source-request@linux.omap.com>
To: <linux-omap-open-source@linux.omap.com>
Sent: Thursday, January 19, 2006 4:31 PM
Subject: Linux-omap-open-source Digest, Vol 21, Issue 36

> Send Linux-omap-open-source mailing list submissions to
> linux-omap-open-source@linux.omap.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> or, via email, send a message with subject or body 'help' to
> linux-omap-open-source-request@linux.omap.com
>
> You can reach the person managing the list at
> linux-omap-open-source-owner@linux.omap.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linux-omap-open-source digest..."
>
>
> Today's Topics:
>
>   1. updated makefile for git tree. (Woodruff, Richard)
>   2. Re: updated makefile for git tree. (Tony Lindgren)
>   3. Oops: 805 [#1] problem using kernel.2.6.10.omap1patch with
>      NFS(RFS) ( &lt;&quot;???&quot;&gt; )
>   4. Oops: 805 [#1] problem using kernel.2.6.10.omap1patch with
>      NFS(RFS) ( ??? )
>   5. Question - Oops: 805 [#1] problem using
>      kernel.2.6.10.omap1patch with NFS(RFS) ( ??? )
>   6. sorry. Subject - Oops: 805 [#1] problem using
>      k2.6.10.omap1patch with NFS(RFS) ( ??? )
>   7. Help me. Oops: 805 [#1]err using kernel.2.6.10.omap1patch
>      with NFS(RFS) (???)
>   8. Re: Help me. Oops: 805 [#1]err using kernel.2.6.10.omap1patch
>      with NFS(RFS) (Tony Lindgren)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 18 Jan 2006 18:24:38 -0600
> From: "Woodruff, Richard" <r-woodruff2@ti.com>
> Subject: updated makefile for git tree.
> To: "Tony Lindgren" <tony@atomide.com>
> Cc: linux-omap-open-source@linux.omap.com
> Message-ID:
> <EA12F909C0431D458B9D18A176BEE4A503EF7360@dlee02.ent.ti.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Tony,
>
> I see you didn't fill in the CROSS_COMPILE when you updated the Makefile
> to 2.6.16-rc1.  Previously you have set it to arm-linux- .
>
> Regards,
> Richard W.
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 18 Jan 2006 16:40:38 -0800
> From: Tony Lindgren <tony@atomide.com>
> Subject: Re: updated makefile for git tree.
> To: "Woodruff, Richard" <r-woodruff2@ti.com>
> Cc: linux-omap-open-source@linux.omap.com
> Message-ID: <20060119004038.GD4425@atomide.com>
> Content-Type: text/plain; charset=us-ascii
>
> * Woodruff, Richard <r-woodruff2@ti.com> [060118 16:25]:
>> Tony,
>>
>> I see you didn't fill in the CROSS_COMPILE when you updated the Makefile
>> to 2.6.16-rc1.  Previously you have set it to arm-linux- .
>
> Thanks, I'll add that back.
>
> Tony
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 19 Jan 2006 15:06:38 +0900 (KST)
> From: " &lt;&quot;???&quot;&gt; " <invain@hanmail.net>
> Subject: Oops: 805 [#1] problem using kernel.2.6.10.omap1patch with
> NFS(RFS)
> To: <linux-omap-open-source@linux.omap.com>
> Message-ID:
> <20060119150638.HM.l000000000524Fd@invain.premium65.hanmail.net>
> Content-Type: text/plain; charset="euc-kr"
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 19 Jan 2006 15:08:23 +0900 (KST)
> From: " ??? " <invain@hanmail.net>
> Subject: Oops: 805 [#1] problem using kernel.2.6.10.omap1patch with
> NFS(RFS)
> To: <linux-omap-open-source@linux.omap.com>
> Message-ID:
> <20060119150823.HM.l000000000524Ff@invain.premium65.hanmail.net>
> Content-Type: text/plain; charset="euc-kr"
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 19 Jan 2006 15:22:21 +0900 (KST)
> From: " ??? " <invain@hanmail.net>
> Subject: Question - Oops: 805 [#1] problem using
> kernel.2.6.10.omap1patch with NFS(RFS)
> To: <linux-omap-open-source@linux.omap.com>
> Message-ID:
> <20060119152221.HM.l000000000524Fh@invain.premium65.hanmail.net>
> Content-Type: text/plain; charset="euc-kr"
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 19 Jan 2006 15:26:46 +0900 (KST)
> From: " ??? " <invain@hanmail.net>
> Subject: sorry. Subject - Oops: 805 [#1] problem using
> k2.6.10.omap1patch with NFS(RFS)
> To: <linux-omap-open-source@linux.omap.com>
> Message-ID:
> <20060119152646.HM.l000000000524Fj@invain.premium65.hanmail.net>
> Content-Type: text/plain; charset="euc-kr"
>
>
>
> ------------------------------
>
> Message: 7
> Date: Thu, 19 Jan 2006 15:32:04 +0900 (KST)
> From: "???" <invain@naver.com>
> Subject: Help me. Oops: 805 [#1]err using kernel.2.6.10.omap1patch
> with NFS(RFS)
> To: <linux-omap-open-source@linux.omap.com>
> Message-ID: <43CF3264.000001.03809@nhn427>
> Content-Type: Text/Plain;  charset="euc-kr"
>
> It seems that my email system  problem. so i changed email address.
>
>
> Subject - Oops: 805 [#1] problem using kernel.2.6.10.omap1patch with NFS(RFS)
> ----------------------------------------- 
>
> I finished compiling and porting ousing kernel.2.6.10 of kernel.org and patch.2.6.10.omap1. But, 
> When I try booting with compiled zImage on omap5912osk board, I meet below error message. For 
> reference, When I use Ramdisk(root file system), kerenl is booted successfully. Only When I use 
> NFS Root file system , error happened like belows. Please. What's reason? . Tell me how to solve 
> this problem.
> (P.S: When I tryed "ping target.board.ip.address" command on host pc(RH9.0), I receviced TTL 
> reply. )
>
> * Test Envirionment.
> -board : TI omap5912.osk board
> -Ethernet : SMC91C94 Ethernet card
> -kernel.org :kernel.2.6.10.tar.gz (www.kernel.org )
> -compiler :montavista _arm_v5
> -omap patch :http://www.muru.com/linux/omap/patches/patch-2.6.10-omap1.bz2
> -Rootfilesystem: NFS Root file system
>
>
> * When I boot kernel.2.6.10.omap1 with nfsroot , I meet "Oops: 805 [#1]:" mesasge like belows. 
> ............... upper omission.....................
> eth0: link up
> IP-Config: Complete:
> device=eth0, addr=192.168.0.10, mask=255.255.255.0, gw=192.168.0.2,
> host=192.168.0.10, domain=, nis-domain=(none),
> bootserver=192.168.0.2, rootserver=192.168.0.2, rootpath= Looking up port of RPC 100003/2 on 
> 192.168.0.2 Looking up port of RPC 100005/1 on 192.168.0.2
> VFS: Mounted root (nfs filesystem).
> Freeing init memory: 104K
> <------------------- Ref: After 10 minutes, Belows message appeared on console. Unable to handle 
> kernel paging request at virtual address c2000000 pgd = c0010000 [c2000000] *pgd=00000000 Internal 
> error: Oops: 805 [#1] Modules linked in:
> CPU: 0
> PC is at .insw_8_lp+0x30/0x44
> LR is at 0x4341
> pc : [] lr : [<00004341>] Not tainted
> sp : c0299e44 ip : 43414341 fp : c0299e98
> r10: c0339000 r9 : c2852000 r8 : 00000000
> r7 : c0339220 r6 : fffffffa r5 : 43414341 r4 : 43414341
> r3 : 43414341 r2 : 7fe11855 r1 : c1fffff4 r0 : c2852008
> Flags: nzCv IRQs on FIQs on Mode SVC_32 Segment user
> Control: 5717F Table: 10010000 DAC: 00000015
> Process init (pid: 1, stack limit = 0xc0298190)
> Stack: (0xc0299e44 to 0xc029a000)
> 9e40: c03f74e0 c2852000 c012de94 c1c230b2 00004030 00000007 00000033
> 9e60: c0339220 c033ea20 000000a0 00000000 c033ea20 00000000 00000000 000000a0
> 9e80: c0299f40 c0299f40 fefbe418 c0299ebc c0299e9c c00232f8 c012dc14 c0210540
> 9ea0: 000000a0 c033ea20 c0299f40 c01d584c c0299edc c0299ec0 c0023454 c00232bc
> 9ec0: 000000a1 00001e00 00000001 c0210570 c0299f08 c0299ee0 c002e7d8 c00233b4
> 9ee0: c0299f74 fefecb00 c0298000 c0028d4c 20000013 c020e740 c0299f40 c0299f3c
> 9f00: c0299f0c c00235dc c002e744 0000001e c0299fb0 c0299f74 fefecb00 ffffffff
> 9f20: c0028d4c 20000013 ffffffff 40127000 c0299fac c0299f40 c00223e0 c002359c
> 9f40: c0013ff8 c0007ff8 00000000 10002401 ffff1000 c0010000 10002001 00000000
> 9f60: c0299fb0 00000000 40127000 c0299fac 00003ff8 c0299f88 c0298000 c0028d4c
> 9f80: 20000013 ffffffff fefecb00 c01d2fa0 ffff1000 60000010 00057177 c0299fec
> 9fa0: 00000000 c0299fb0 c0022718 c0028cd8 00000000 00000001 401282b8 ffff0fff
> 9fc0: 00000000 00000000 401282b8 000012b8 00000000 00000000 40127000 00000000
> 9fe0: beffff3c befffdd8 40049b94 ffff1000 60000010 ffffffff e5903084 e3530001
> Backtrace:
> [] (smc_interrupt+0x0/0x6d0) from [] (__do_irq+0x4c/0x88) [] (__do_irq+0x0/0x88) from [] 
> (do_edge_IRQ+0xb0/0x12c) r8 = C01D584C r7 = C0299F40 r6 = C033EA20 r5 = 000000A0 r4 = C0210540 [] 
> (do_edge_IRQ+0x0/0x12c) from [] (gpio_irq_handler+0xa4/0xb8) r7 = C0210570 r6 = 00000001 r5 = 
> 00001E00 r4 = 000000A1 [] (gpio_irq_handler+0x0/0xb8) from [] (asm_do_IRQ+0x50/0x150) [] 
> (asm_do_IRQ+0x0/0x150) from [] (__irq_svc+0x20/0x80) [] (do_translation_fault+0x0/0xac) from [] 
> (ret_from_exception+0x0/0x10) r8 = C0299FEC r7 = 00057177 r6 = 60000010 r5 = FFFF1000 r4 = 
> C01D2FA0
> Code: e185580c e1d0c0b0 e1d0e0b0 e18cc80e (e8a11038)
> <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
>
> end of Line.
>
>
>
>
> ------------------------------------------------------------------------
> ³×ÀÌ¹ö :: ¶È! ¼Ò¸®³ª°Ô ¹Ù²ï ³×ÀÌ¹ö ¸ÞÀÏÀ» ¸¸³ªº¸¼¼¿ä.
> http://mail.naver.com/
>
> ------------------------------
>
> Message: 8
> Date: Wed, 18 Jan 2006 23:30:41 -0800
> From: Tony Lindgren <tony@atomide.com>
> Subject: Re: Help me. Oops: 805 [#1]err using kernel.2.6.10.omap1patch
> with NFS(RFS)
> To: "???" <invain@naver.com>
> Cc: linux-omap-open-source@linux.omap.com
> Message-ID: <20060119073041.GG4425@atomide.com>
> Content-Type: text/plain; charset=utf-8
>
> * "ìz"ê·¼ì<" <invain@naver.com> [060118 22:37]:
>> It seems that my email system  problem. so i changed email address.
>>
>>
>> Subject - Oops: 805 [#1] problem using kernel.2.6.10.omap1patch with NFS(RFS)
>> ----------------------------------------- 
>>
>> I finished compiling and porting ousing kernel.2.6.10 of kernel.org and patch.2.6.10.omap1. But, 
>> When I try booting with compiled zImage on omap5912osk board, I meet below error message. For 
>> reference, When I use Ramdisk(root file system), kerenl is booted successfully. Only When I use 
>> NFS Root file system , error happened like belows. Please. What's reason? . Tell me how to solve 
>> this problem.
>> (P.S: When I tryed "ping target.board.ip.address" command on host pc(RH9.0), I receviced TTL 
>> reply. )
>>
>> * Test Envirionment.
>> -board : TI omap5912.osk board
>> -Ethernet : SMC91C94 Ethernet card
>> -kernel.org :kernel.2.6.10.tar.gz (www.kernel.org )
>> -compiler :montavista _arm_v5
>> -omap patch :http://www.muru.com/linux/omap/patches/patch-2.6.10-omap1.bz2
>> -Rootfilesystem: NFS Root file system
>>
>>
>> * When I boot kernel.2.6.10.omap1 with nfsroot , I meet "Oops: 805 [#1]:" mesasge like belows. 
>> ............... upper omission.....................
>> eth0: link up
>> IP-Config: Complete:
>> device=eth0, addr=192.168.0.10, mask=255.255.255.0, gw=192.168.0.2,
>> host=192.168.0.10, domain=, nis-domain=(none),
>> bootserver=192.168.0.2, rootserver=192.168.0.2, rootpath= Looking up port of RPC 100003/2 on 
>> 192.168.0.2 Looking up port of RPC 100005/1 on 192.168.0.2
>> VFS: Mounted root (nfs filesystem).
>> Freeing init memory: 104K
>> <------------------- Ref: After 10 minutes, Belows message appeared on console. Unable to handle 
>> kernel paging request at virtual address c2000000 pgd = c0010000 [c2000000] *pgd=00000000 
>> Internal error: Oops: 805 [#1] Modules linked in:
>> CPU: 0
>> PC is at .insw_8_lp+0x30/0x44
>> LR is at 0x4341
>> pc : [] lr : [<00004341>] Not tainted
>> sp : c0299e44 ip : 43414341 fp : c0299e98
>> r10: c0339000 r9 : c2852000 r8 : 00000000
>> r7 : c0339220 r6 : fffffffa r5 : 43414341 r4 : 43414341
>> r3 : 43414341 r2 : 7fe11855 r1 : c1fffff4 r0 : c2852008
>> Flags: nzCv IRQs on FIQs on Mode SVC_32 Segment user
>> Control: 5717F Table: 10010000 DAC: 00000015
>> Process init (pid: 1, stack limit = 0xc0298190)
>> Stack: (0xc0299e44 to 0xc029a000)
>> 9e40: c03f74e0 c2852000 c012de94 c1c230b2 00004030 00000007 00000033
>> 9e60: c0339220 c033ea20 000000a0 00000000 c033ea20 00000000 00000000 000000a0
>> 9e80: c0299f40 c0299f40 fefbe418 c0299ebc c0299e9c c00232f8 c012dc14 c0210540
>> 9ea0: 000000a0 c033ea20 c0299f40 c01d584c c0299edc c0299ec0 c0023454 c00232bc
>> 9ec0: 000000a1 00001e00 00000001 c0210570 c0299f08 c0299ee0 c002e7d8 c00233b4
>> 9ee0: c0299f74 fefecb00 c0298000 c0028d4c 20000013 c020e740 c0299f40 c0299f3c
>> 9f00: c0299f0c c00235dc c002e744 0000001e c0299fb0 c0299f74 fefecb00 ffffffff
>> 9f20: c0028d4c 20000013 ffffffff 40127000 c0299fac c0299f40 c00223e0 c002359c
>> 9f40: c0013ff8 c0007ff8 00000000 10002401 ffff1000 c0010000 10002001 00000000
>> 9f60: c0299fb0 00000000 40127000 c0299fac 00003ff8 c0299f88 c0298000 c0028d4c
>> 9f80: 20000013 ffffffff fefecb00 c01d2fa0 ffff1000 60000010 00057177 c0299fec
>> 9fa0: 00000000 c0299fb0 c0022718 c0028cd8 00000000 00000001 401282b8 ffff0fff
>> 9fc0: 00000000 00000000 401282b8 000012b8 00000000 00000000 40127000 00000000
>> 9fe0: beffff3c befffdd8 40049b94 ffff1000 60000010 ffffffff e5903084 e3530001
>> Backtrace:
>> [] (smc_interrupt+0x0/0x6d0) from [] (__do_irq+0x4c/0x88) [] (__do_irq+0x0/0x88) from [] 
>> (do_edge_IRQ+0xb0/0x12c) r8 = C01D584C r7 = C0299F40 r6 = C033EA20 r5 = 000000A0 r4 = C0210540 [] 
>> (do_edge_IRQ+0x0/0x12c) from [] (gpio_irq_handler+0xa4/0xb8) r7 = C0210570 r6 = 00000001 r5 = 
>> 00001E00 r4 = 000000A1 [] (gpio_irq_handler+0x0/0xb8) from [] (asm_do_IRQ+0x50/0x150) [] 
>> (asm_do_IRQ+0x0/0x150) from [] (__irq_svc+0x20/0x80) [] (do_translation_fault+0x0/0xac) from [] 
>> (ret_from_exception+0x0/0x10) r8 = C0299FEC r7 = 00057177 r6 = 60000010 r5 = FFFF1000 r4 = 
>> C01D2FA0
>> Code: e185580c e1d0c0b0 e1d0e0b0 e18cc80e (e8a11038)
>> <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
>>
>> end of Line.
>
> This sounds like the old wrong-flash-memory-bus-timings problem with
> smc91x. Try a more recent kernel and it should go away.
>
> Tony
>
>
> ------------------------------
>
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
>
> End of Linux-omap-open-source Digest, Vol 21, Issue 36
> ******************************************************
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread