Linux on Virtex4
Hi, I am also operating Linux by Avnet V4FX12MM of a MPMC2+GSRD design. However, V4FX and a PHY chips get very hot, and this design may malfunction and may output oops. Therefore, like an attached photo, my V4FX12MM applies a heat sink and FAN, and is operating them. Is it stabilizing and operating by your design? Best Regards, Yoshio Kashiwagi - Nissin Systems Hi Rick, I saw on linuxppc-embedded at ozlabs.org that you are trying to port (or better you did) monta vista linux to Avnet's V4FX Mini-Module. I will try to deal with the same thing. My design is basically the same: all features of MM incorporated in CoreConnect style architecture. I also tried with Multi Port Memory Controller (MPMC2) and ported (memory works, but for LAN I still need phy datasheet) the Gigabit System Reference Design (GSRD2) to Mini-Module. By using the MPMC2 memory core you can connect PPC directly to memory using two PLBs (data and instruction separated). This way you might solve the CPU cache errata. The problem with MPMC2 is that it consumes A LOT of BRAM and logic. I tried to build a full featured system, but V4FX12 lacks logic for the purpose. Is there a way that you can help me with running MV linux on my system? Cheers, Ales Gorkic ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded -- next part -- A non-text attachment was scrubbed... Name: V4FX12MM.jpg Type: image/jpeg Size: 30745 bytes Desc: not available Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060713/942ee0d6/attachment.jpg
Problem in PCI resource allocation with MPC8245
Hi, I have a Freescale MPC8245 machine running Montavista Linux (kernel 2.4.20). There are two devices connected to the PCI bus: a USB host controller (VIA VT6212L) and a single-chip network switch (Broadcom BCM5650). Now BCM5650 is working but VT6212L is not. I tried to modify the PCI code but met some problems. Here are the PCI information and boot message: Bus 0, device 0, devfn 0 (id 1057-0006, headertype 0x00) region 0: mask 0x0008, now at 0x region 0: type mem, size 0 (0MB) region 1: mask 0xf000, now at 0x region 1: type mem, size 4096 (4KB) region 2: mask 0x0008, now at 0x region 2: type mem, size 0 (0MB) Bus 0, device 16, devfn 0 (id 14e4-5650, headertype 0x00) -- BCM5650 region 0: mask 0x0004, now at 0xbfff region 0: type mem, size 65536 (64KB) region 1: mask 0x00ff, now at 0x region 1: type I/O, size 65284 (65284B) Bus 0, device 17, devfn 0 (id 1106-3038, headertype 0x00) -- VT6212L (UHCI 1) region 4: mask 0xffe1, now at 0x00bfffe0 region 4: type I/O, size 32 (32B) Bus 0, device 17, devfn 1 (id 1106-3038, headertype 0x00) -- VT6212L (UHCI 2) region 4: mask 0xffe1, now at 0x00bfffc0 region 4: type I/O, size 32 (32B) Bus 0, device 17, devfn 2 (id 1106-3104, headertype 0x00) -- VT6212L (EHCI) region 0: mask 0xff00, now at 0xbffeff00 region 0: type mem, size 256 (256B) -- PCI: Probing PCI hardware PCI:00:00.0 Resource 0 [-] is unassigned PCI:00:00.0 Resource 1 [-0fff] is unassigned PCI:00:00.0 Resource 2 [-] is unassigned PCI: bridge rsrc 0..bf (100), parent c0179de4 PCI: bridge rsrc 8000..fcff (200), parent c0179e00 PCI:00:10.0: Resource 0: bfff-bfff (f=204) -- BCM5650 PCI:00:11.0: Resource 4: 00bfffe0-00bf (f=101)-- VT6212L (UHCI 1) PCI:00:11.1: Resource 4: 00bfffc0-00bfffdf (f=101) -- VT6212L (UHCI 2) PCI:00:11.2: Resource 0: bffeff00-bffe (f=200) -- VT6212L (EHCI) -- It seems no problem with the allocated resource regions for VT6212L, but I got Timeout message printed by USB driver. So, I modify the function mpc10x_bridge_set_resources in arch/ppc/kernel/mpc10x_common.c: case MPC10X_MEM_MAP_B: pci_init_resource(hose-io_resource, 0x, 0x, /* original value: 0x00bf, */ IORESOURCE_IO, PCI host bridge); -- and the defination of MPC10X_MAPB_PCI_IO_END in include/asm/mpc10x.h: #define MPC10X_MAPB_PCI_IO_END (0x0001 - 1)/* original value: (0x00c0 - 1) */ -- After modification, the USB 1.x driver (UHCI) is working, and EHCI is still not working. BUT I don't know why the UHCI works if I do the above modification? The PCI information after modification is shown below: Bus 0, device 17, function 0: Class 0c03: PCI device 1106:3038 (rev 97). IRQ 1. Master Capable. Latency=128. I/O at 0xffe0 [0x]. -- I/O change to 0xffe0 Bus 0, device 17, function 1: Class 0c03: PCI device 1106:3038 (rev 97). IRQ 1. Master Capable. Latency=128. I/O at 0xffc0 [0xffdf].-- I/O change to 0xffc0 Bus 0, device 17, function 2: Class 0c03: PCI device 1106:3104 (rev 99). IRQ 1. Master Capable. Latency=128. Non-prefetchable 32 bit memory at 0xbffeff00 [0xbffe]. -- I do the modification for the PCI memory configuration similar to the modification for PCI I/O configuration: [arch/ppc/kernel/mpc10x_common.c] case MPC10X_MEM_MAP_B: ... snipped pci_init_resource (hose-mem_resources[0], 0x, /* original value: 0x8000, */ 0x000f, /* original value: 0xfcff, */ IORESOURCE_MEM, PCI host bridge); -- [include/asm/mpc10x.h] #define MPC10X_MAPB_ISA_MEM_BASE0x /* original value: 0x8000 */ ... snipped #define MPC10X_MAPB_PCI_MEM_START 0x /* original value: 0x8000 */ #define MPC10X_MAPB_PCI_MEM_END(0x0010 - 1) /* original value: (0xC000 - 1) */ -- Surprisingly, after this modification, the USB2.0 driver (EHCI) can work. BUT, the BCM5650 driver failed... Here are the PCI information and boot message: Bus 0, device 16, function 0: Class 0280: PCI device 14e4:5650 (rev 17). Master Capable. Latency=128. Non-prefetchable 64 bit memory at 0xf [0xf]. -- BCM5650 PCI memory address change to 0xf Bus 0, device 17, function 0: Class 0c03: PCI device 1106:3038
help regarding powerpc and vga card
Hello All I am working on a powerpc board. I have placed the board on a PCI backplane and connected a PCI VGA card to the same. PCI enumuration from u-boot does not detect my VGA card whereas it detects other cards like ethernet in the same slot. The VGA card details are as follows. Vendor ID=0x1002 Device ID= 0x4752 Name: ATI Technologies Inc Rage XL The VGA card is universal compatible. It is working with X86 PC. In my target system , I have tested adding the vendor id and and device id in the u-boot/include/pci_ids.h and declared the pci_device_id structure in a new header file. uboot/include/vga_ragexl.h . Even then card is not getting detected. Anyone please help me if i am missing anything. Thanks Regards Sudheer.A -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060713/9716a0b1/attachment.htm
Macraigor mpDemon
Hi, Does anyone know if Macriagor's mpDemon is capable of debugging the linux kernel via the JTAG interface. Thanks in advance, Ria
some problems on the SystemACE driver.
Dear Ameet, Have you seen the response I sent to you last night? The content is that there is still the same problem in the newly updated patch for SystemACE. I forgot to CC a copy to the maillist so I don't know if you have received it. I don't mean to push you. :) Any progress on the patch? If yes, please tell me a.s.a.p. and I am anxious for testing it. Regards Ming From: Ameet Patil ammubhai at gmail.com To: Ming Liu eemingliu at hotmail.com CC: akonovalov at ru.mvista.com, linuxppc-embedded at ozlabs.org Subject: Re: some problems on the SystemACE driver. Date: Wed, 12 Jul 2006 19:22:08 +0100 Hi Ming, Thanks for testing the driver patch! The errors you get when compiling both - SysAce and TEMAC are reasonable. My ignorance or call it me being lazy. I recollect now... I was also working on the Xilinx Ethernet driver and forgot to cleanup that code before creating the patch for the SysAce driver. Thus, it so happens that code for the ethernet driver in my patch also gets compiled along with the TEMAC. I have deleted the unnecessary code files and updated the patch (name changed). Find the new one here: https://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.1.patch Let me know if it works for you now? -Ameet Ming Liu wrote: Dear Ameet (and Andrei), I have tested the new patch for SystemACE driver. With respect to the single SystemACE driver, it works well. I can boot my linux in ML403 board. (I tried both 2.6.16-rc5 and 2.6.17.1 versions) So first congratulations and thanks for your hard work! However, when I tried to implemented Temac (with and without SystemACE. TWO conditions.), some errors happened. Here is the compilation information: CC init/do_mounts.o LD init/mounts.o CC init/initramfs.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o(.sdata+0x2c): multiple definition of `XWaitInAssert' arch/ppc/platforms/4xx/built-in.o(.sdata+0x0): first defined here drivers/built-in.o(.text+0x3e480): In function `XPacketFifoV200a_WriteDre': : multiple definition of `XPacketFifoV200a_WriteDre' arch/ppc/platforms/4xx/built-in.o(.text+0x1b14): first defined here drivers/built-in.o(.text+0x3e158): In function `XPacketFifoV200a_SelfTest': : multiple definition of `XPacketFifoV200a_SelfTest' arch/ppc/platforms/4xx/built-in.o(.text+0x17ec): first defined here drivers/built-in.o(.sbss+0x18c): multiple definition of `XAssertStatus' arch/ppc/platforms/4xx/built-in.o(.sbss+0x8): first defined here drivers/built-in.o(.text+0x3e798): In function `XPacketFifoV200a_L0Write': : multiple definition of `XPacketFifoV200a_L0Write' arch/ppc/platforms/4xx/built-in.o(.text+0x1e2c): first defined here drivers/built-in.o(.text+0x3e280): In function `XPacketFifoV200a_Read': : multiple definition of `XPacketFifoV200a_Read' arch/ppc/platforms/4xx/built-in.o(.text+0x1914): first defined here drivers/built-in.o(.text+0x3e55c): In function `XPacketFifoV200a_L0Read': : multiple definition of `XPacketFifoV200a_L0Read' arch/ppc/platforms/4xx/built-in.o(.text+0x1bf0): first defined here drivers/built-in.o(.text+0x3e380): In function `XPacketFifoV200a_Write': : multiple definition of `XPacketFifoV200a_Write' arch/ppc/platforms/4xx/built-in.o(.text+0x1a14): first defined here drivers/built-in.o(.text+0x3e0cc): In function `XAssertSetCallback': : multiple definition of `XAssertSetCallback' arch/ppc/platforms/4xx/built-in.o(.text+0x44): first defined here drivers/built-in.o(.text+0x3e9fc): In function `XPacketFifoV200a_L0WriteDre': : multiple definition of `XPacketFifoV200a_L0WriteDre' arch/ppc/platforms/4xx/built-in.o(.text+0x2090): first defined here drivers/built-in.o(.text+0x3e0dc): In function `XPacketFifoV200a_Initialize': : multiple definition of `XPacketFifoV200a_Initialize' arch/ppc/platforms/4xx/built-in.o(.text+0x1770): first defined here drivers/built-in.o(.text+0x3e088): In function `XAssert': : multiple definition of `XAssert' arch/ppc/platforms/4xx/built-in.o(.text+0x0): first defined here drivers/built-in.o(.text+0x3e0d8): In function `XNullHandler': : multiple definition of `XNullHandler' arch/ppc/platforms/4xx/built-in.o(.text+0x50): first defined here make: *** [.tmp_vmlinux1] Error 1 It looks like that your patch affect some symbols which are used by Temac. (When I use the old patch for SystemACE, there is no problem like this if I only choose Temac. ) So let's find out the problem together. Also, I don't know if this is a problem from SystemACE or Temac , I would like to invite Andrei to look at this altogether. If any suggestion, please feel free to announce. Thanks for both your help. Regards Ming From: Ameet Patil ammubhai at gmail.com To: Ming Liu eemingliu at hotmail.com CC: linuxppc-embedded at ozlabs.org Subject: Re: some problems on the SystemACE driver. Date: Wed, 12 Jul 2006 10:54:13
cpm_uart_port_map not initialised before serial console setup
Hi everybody, while trying to use SCC1 as a serial console, I found a bug in the cpm_uart driver. The cpm_uart_port_map table is initialised by cpm_uart_count() which is called in cpm_uart_init() at module_init() time. cpm_uart_console_setup(), called at console_initcall() time, accesses cpm_uart_port_map, leading to a crash when using any serial port except SMC1 as the serial console. I attached a very simple patch to fix the problem, but it might be subject to race conditions. Could anyone familiar with the cpm_uart driver have a look at it ? Best regards, Laurent Pinchart -- next part -- A non-text attachment was scrubbed... Name: cpm_uart.patch Type: text/x-diff Size: 403 bytes Desc: not available Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060713/a4ed8093/attachment.patch
Linux on Virtex4
Ales, H... No, I've not done anything with the Avnet MM board. I may have responded to somebody who was working with that board on this list. We work a lot with PLB TEMAC and MV Linux, but do very little with GSRD (it's a reference design that's not officially supported through the EDK). On the surface, I don't think I can help much here, but feel free to directly send me a more detailed email and maybe I can point you to someone who can help. -Rick -Original Message- From: linuxppc-embedded-bounces+moleres=xilinx.com at ozlabs.org [mailto:[EMAIL PROTECTED] On Behalf Of Ale? Gorkic Sent: Wednesday, July 12, 2006 7:13 AM To: linuxppc-embedded at ozlabs.org Subject: re:Linux on Virtex4 Hi Rick, I saw on linuxppc-embedded at ozlabs.org that you are trying to port (or better you did) monta vista linux to Avnet's V4FX Mini-Module. I will try to deal with the same thing. My design is basically the same: all features of MM incorporated in CoreConnect style architecture. I also tried with Multi Port Memory Controller (MPMC2) and ported (memory works, but for LAN I still need phy datasheet) the Gigabit System Reference Design (GSRD2) to Mini-Module. By using the MPMC2 memory core you can connect PPC directly to memory using two PLBs (data and instruction separated). This way you might solve the CPU cache errata. The problem with MPMC2 is that it consumes A LOT of BRAM and logic. I tried to build a full featured system, but V4FX12 lacks logic for the purpose. Is there a way that you can help me with running MV linux on my system? Cheers, Ales Gorkic ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
some problems on the SystemACE driver.
Hi Ming, Instead of bouncing emails to and forth, lets do all at one place: 1. Which TEMAC patch are you using? (http://source.mvista.com/~ank/paulus-powerpc/20060309/ppc32_xilinx_edk_temac.patch) 2. After applying the patch, is the driver getting compiled directly without having to select it via make menuconfig? 3. I don't see a Makefile in the drivers/net/xilinx_temac/ folder? Ofcourse, I can work my way to compile the driver. But is there any doc. present explaining this? -Ameet Ming Liu wrote: Dear Ameet, Unfortunately, I tried the new patch and the same problem happened. Here is the information: CC drivers/xilinx_edk/xdmav2_simple.o LD drivers/xilinx_edk/built-in.o LD drivers/built-in.o drivers/xilinx_edk/built-in.o(.sdata+0x0): In function `XAssert': drivers/xilinx_edk/xbasic_types.c:105: multiple definition of `XWaitInAssert' drivers/block/built-in.o(.sdata+0x4):drivers/block/rd.c:103: first defined here drivers/xilinx_edk/built-in.o(.sbss+0x4): In function `XAssert': drivers/xilinx_edk/xbasic_types.c:105: multiple definition of `XAssertStatus' drivers/block/built-in.o(.sbss+0x3c):include/asm-generic/bitops/non-atomic.h:108 : first defined here drivers/xilinx_edk/built-in.o(.text+0x44): In function `XAssertSetCallback': drivers/xilinx_edk/xbasic_types.c:134: multiple definition of `XAssertSetCallbac k' drivers/block/built-in.o(.text+0x38d0):drivers/block/xilinx_sysace/xbasic_types. c:117: first defined here drivers/xilinx_edk/built-in.o(.text+0x0): In function `XAssert': drivers/xilinx_edk/xbasic_types.c:105: multiple definition of `XAssert' drivers/block/built-in.o(.text+0x388c):drivers/block/xilinx_sysace/xbasic_types. c:87: first defined here drivers/xilinx_edk/built-in.o(.text+0x50): In function `XNullHandler': drivers/xilinx_edk/xbasic_types.c:153: multiple definition of `XNullHandler' drivers/block/built-in.o(.text+0x38dc):drivers/block/xilinx_sysace/xbasic_types. c:136: first defined here make[1]: *** [drivers/built-in.o] Error 1 make: *** [drivers] Error 2 This time I only tried on linux 2.6.17.1 version. Please check again and modify it. Thank you. Regards Ming From: Ameet Patil ammubhai at gmail.com To: Ming Liu eemingliu at hotmail.com CC: akonovalov at ru.mvista.com, linuxppc-embedded at ozlabs.org Subject: Re: some problems on the SystemACE driver. Date: Wed, 12 Jul 2006 19:22:08 +0100 Hi Ming, Thanks for testing the driver patch! The errors you get when compiling both - SysAce and TEMAC are reasonable. My ignorance or call it me being lazy. I recollect now... I was also working on the Xilinx Ethernet driver and forgot to cleanup that code before creating the patch for the SysAce driver. Thus, it so happens that code for the ethernet driver in my patch also gets compiled along with the TEMAC. I have deleted the unnecessary code files and updated the patch (name changed). Find the new one here: https://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.1.patch Let me know if it works for you now? -Ameet Ming Liu wrote: Dear Ameet (and Andrei), I have tested the new patch for SystemACE driver. With respect to the single SystemACE driver, it works well. I can boot my linux in ML403 board. (I tried both 2.6.16-rc5 and 2.6.17.1 versions) So first congratulations and thanks for your hard work! However, when I tried to implemented Temac (with and without SystemACE. TWO conditions.), some errors happened. Here is the compilation information: CC init/do_mounts.o LD init/mounts.o CC init/initramfs.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o(.sdata+0x2c): multiple definition of `XWaitInAssert' arch/ppc/platforms/4xx/built-in.o(.sdata+0x0): first defined here drivers/built-in.o(.text+0x3e480): In function `XPacketFifoV200a_WriteDre': : multiple definition of `XPacketFifoV200a_WriteDre' arch/ppc/platforms/4xx/built-in.o(.text+0x1b14): first defined here drivers/built-in.o(.text+0x3e158): In function `XPacketFifoV200a_SelfTest': : multiple definition of `XPacketFifoV200a_SelfTest' arch/ppc/platforms/4xx/built-in.o(.text+0x17ec): first defined here drivers/built-in.o(.sbss+0x18c): multiple definition of `XAssertStatus' arch/ppc/platforms/4xx/built-in.o(.sbss+0x8): first defined here drivers/built-in.o(.text+0x3e798): In function `XPacketFifoV200a_L0Write': : multiple definition of `XPacketFifoV200a_L0Write' arch/ppc/platforms/4xx/built-in.o(.text+0x1e2c): first defined here drivers/built-in.o(.text+0x3e280): In function `XPacketFifoV200a_Read': : multiple definition of `XPacketFifoV200a_Read' arch/ppc/platforms/4xx/built-in.o(.text+0x1914): first defined here drivers/built-in.o(.text+0x3e55c): In function `XPacketFifoV200a_L0Read': : multiple definition of `XPacketFifoV200a_L0Read'
cpm_uart_port_map not initialised before serial console setup
On Thu, 13 Jul 2006 16:55:35 +0200 Laurent Pinchart laurent.pinchart at tbox.biz wrote: Hi everybody, while trying to use SCC1 as a serial console, I found a bug in the cpm_uart driver. The cpm_uart_port_map table is initialised by cpm_uart_count() which is called in cpm_uart_init() at module_init() time. cpm_uart_console_setup(), called at console_initcall() time, accesses cpm_uart_port_map, leading to a crash when using any serial port except SMC1 as the serial console. I attached a very simple patch to fix the problem, but it might be subject to race conditions. Could anyone familiar with the cpm_uart driver have a look at it ? Ugh, you're right. But I think we need to finally get rid of the stupid count/port_map creation based on #ifdefs. I'll have a look at it immediately as time permits -- Sincerely, Vitaly
Knowing kernel module load address (insmod hasn't -m)
Hi all, where can be read at which memory address a module was loaded. I use the bb insmod that doesn't provide -m option. Bye, Antonio.
[JOB] Senior Embedded Linux Video Engineer
Senior Embedded Linux Video Engineer Responsible for the technical leadership in design and development of embedded OS features for Cisco's next generation Audio/Video application which will change the entire video conferencing industry. Please check out these links for an overview of the project: http://www.humanproductivitylab.com/archive_blogs/2006/03/26/ciscos_channel_partners_should_1.php http://www.msnbc.msn.com/id/11768174/site/newsweek/ Requirements: ?Strong technical skills with an emphasis on Embedded Linux, Operating System interfaces, and Platform Software and Services. ?5-7 years of embedded C programming. ?4 years Linux experience with at least 2 years embedded Linux. ?Linux expertise on PowerPC architecture. ?Experience in Linux internals such as file systems, device drivers, network interfaces. ?Thorough understanding of Linux utilities such as system logging and run time options. ?Experience in building BSP packaging ?Familiar with gcc/gdb toolchain ?Excellent written and verbal communication skills ?Permanent US work authorization or transferable H1b with a minimum of two years remaining eligibility. Desired Skills/Experience: ?Experience in providing Technical and team leadership ?Experience in GPL compliance ?Build systems, tool chain, executable/library structures and makefile ?Background in a startup or dynamic working environment ?Strong understanding of operating system Kernel internals ?Experience with writing/debugging BSP's for Linux ?Background in VoIP Audio/Video systems Typically requires MSEE/CS combined with 5-7 years of related experience, or BSEE/CS combined with 7-10+ yrs related experience. Opportunity is in San Jose, CA. (Relocation assistance is not available) If interested, please respond with a copy of your resume and the best numbers and times for a follow-up phone conversation. Thank you, Richard Davenport Recruiter Cisco Recruiting Team (888) 329-3480 or (501) 351-7396 richarddavenport at spherion.com
Knowing kernel module load address (insmod hasn't -m)
cat /proc/modules If you want more detailed information about a module (locations of .text, .data, .bss etc), enable CONFIG_KALLSYMS in your kernel and you'll see lots of goodness in the /sys/module/YOUR MODULE/sections directory. Do yourself a favor and browse http://lwn.net/Articles/driver-porting/ where Jon Corbet has written a really good series of articles about modules and device drivers in the 2.6 kernel. cheers, Ben On Thu, 2006-07-13 at 22:38 +0200, Antonio Di Bacco wrote: Hi all, where can be read at which memory address a module was loaded. I use the bb insmod that doesn't provide -m option. Bye, Antonio. ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
