Re: Configuring Freecale ucc_geth without a PHY
Kim Phillips wrote: On Tue, 29 Jan 2008 11:08:43 -0600 Steven Hein [EMAIL PROTECTED] wrote: Hi all, I have a custom board with an MPC8358 (our board is based off of the MPC8360E-MDS development board) that has its eth's directly connected (GMII) to a Broadcom network switch part on the same board, with no PHYs between them. We've have been using a 2.6.16.18 kernel (from TimeSys) up until now, and I hacked in some crude support for no-phy configs forced to 100Mbit and 1Gbit speeds. Now I'm moving to 2.6.22 (with 8360 the patches from bitshrine.org), and I'm trying to understand how I should do this with device trees, the new PHY infrastructure, etc. Has anyone else needed this support? Does anyone have any suggestions as to how to tackle it? check out the fixed-link property and associated code. This implementation came about after 2.6.22 though (it's commit-ish v2.6.23-10096-ga21e282). Kim Thanks for the pointer Kim! Using the fixed-link property code already in the tree, and adding the glue in ucc_geth.c to use it (modeled after the code in gianfar fix-link support in fsl_soc.c), I was able to get this working with me 8360 board. Is there a document anywhere that describes how to submit patches for the powerpc kernel?Or do I just create the patch (I'm learning about git right now...) again the paulus/powerpc.git tree, and send it to this list? Thanks, Steve -- Steve Hein ([EMAIL PROTECTED]) Engineering Diagnostics/Software Silicon Graphics, Inc. 1168 Industrial Blvd. Phone: (715) 726-8410 Chippewa Falls, WI 54729 Fax: (715) 726-6715 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Configuring Freecale ucc_geth without a PHY
Steven Hein wrote: Is there a document anywhere that describes how to submit patches for the powerpc kernel?Or do I just create the patch (I'm learning about git right now...) again the paulus/powerpc.git tree, and send it to this list? Correct. Don't just lean toward git, actually use it. And paulus/powerpc.git is the right basis. Send it to the [EMAIL PROTECTED] list, not here. jdl ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Kernel oops in MPC8568MDS BSP
Hello, I am using MPC8568MDS BSP on my board, which has same memory map as MPC8568MDS board has. However I have kernel oops at free_bootmem_with_active_regions() within do_init_bootmem(). Any idea on this issue? Thanks, Mike bootm 0x100 0x200 0x40 ## Booting image at 0100 ... Image Name: Linux-2.6.23 Created: 2008-01-31 18:52:45 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1370100 Bytes = 1.3 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at 0200 ... Image Name: uboot ext2 ramdisk rootfs Created: 2007-11-26 2:28:38 UTC Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:4001113 Bytes = 3.8 MB Load Address: Entry Point: Verifying Checksum ... OK Booting using flat device tree at 0x40 Loading Ramdisk to 1fb6e000, end 1ff3ed59 ... OK Using MPC85xx MDS machine description Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb Linux version 2.6.23 () (gcc version 4.1.2) #3 Thu Jan 31 13:52:40 EST 2008 Found initrd at 0xdfb6e000:0xdff3ed59 console [udbg0] enabled Kernel BUG at c0296a68 [verbose debug info unavailable] Oops: Exception in kernel mode, sig: 5 [#1] MPC85xx MDS Modules linked in: NIP: c0296a68 LR: c0298100 CTR: 1c00 REGS: c02c7ec0 TRAP: 0700 Not tainted (2.6.23) MSR: 00021000 ME CR: 24002028 XER: 2000 TASK = c02ac5e0[0] 'swapper' THREAD: c02c6000 GPR00: 0001 c02c7f70 c02ac5e0 c02daa2c 0001e401 2000 0356 GPR08: 0001 25e9 25e9 24002022 6000 1ffbd400 007fff00 GPR16: 1ffb9824 0004 1fffc830 0080 007ffeb0 003d0d59 GPR24: 1ff3fe50 1140 c02b c02a5320 0002 Call Trace: [c02c7f90] [c0291144] [c02c7fb0] [c028f250] [c02c7fc0] [c028681c] [c02c7ff0] [c388] Instruction dump: 5489e8fa 7d30 7d295a14 7d604828 7d6a0078 7d40492d 40a2fff4 7c095839 38840001 4182000c 4200ffd0 4e800020 0fe0 4800 3d20c02b 7c601b78 Kernel panic - not syncing: Attempted to kill the idle task! ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Reminder: removal of arch/ppc
On Fri, Jan 25, 2008 at 10:55:25AM -0600, Kumar Gala wrote: Just a reminder that the plan is to remove arch/ppc this summer (June 2008). The following boards still existing over in arch/ppc. Some of them have been ported over to arch/powerpc. If you care about one of these boards and its not ported speak up (it helps if you have access to the board). Also, if you know a given board is free to die of bitrot let us know so we know not to worry about it: I guess I'm just not a nice guy but I say let them die. No need to worry. The code really isn't going anywhere -- git-checkout v2.6.pick your favorite version and its back. /me's $0.02. Mark ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Reminder: removal of arch/ppc
On Jan 31, 2008, at 4:54 PM, Mark A. Greer wrote: On Fri, Jan 25, 2008 at 10:55:25AM -0600, Kumar Gala wrote: Just a reminder that the plan is to remove arch/ppc this summer (June 2008). The following boards still existing over in arch/ppc. Some of them have been ported over to arch/powerpc. If you care about one of these boards and its not ported speak up (it helps if you have access to the board). Also, if you know a given board is free to die of bitrot let us know so we know not to worry about it: I guess I'm just not a nice guy but I say let them die. No need to worry. The code really isn't going anywhere -- git-checkout v2.6.pick your favorite version and its back. /me's $0.02. this is where I poke you about the sandpoint port ;) - k ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded