PCI driver on EB8347
RajanI have written PCI driver which works fine along with MPC8347 and two PCI Rajan card connected in a single PCI bus. When I try to communicate same PCI card Rajan using PCI bridge ( PCI2050B ), Linux does detect PCI card on Secondary bus Rajan but same driver doesn't work PCI interrupt for secondary bus set up properly? RajanDo I need to enable support for second PCI host controller at kernel level to Rajanmake it work? Or I need to do something else ? I tried compiling PPC-linux kernel Rajan after enabling CONFIG_85xx_PCI2 kernel doesn't compile it gives me error while Rajancompiling arch/ppc/syslib/ppc83xx_setup.c Kernel version I'm using is 2.6.13. Why you enable CONFIG_85xx_PCI2 in kernel? It is for 85xx, but you are using 8347 processor. snip Dave
Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs
On Aug 10, 2006, at 6:18 AM, Prashant Yendigeri wrote: Hi, The gianfar driver of 2.6.12 and 2.4.20 give different outputs on the same PPC 8540 board. What could be the reason ? Output on 2.4.20 : /root # ifconfig eth0 172.28.8.254 up eth0: PHY is Marvell 88E1011S (1410c62) eth0: Auto-negotiation done eth0: Half Duplex eth0: Speed 10BT eth0: Link is up Output on 2.6.12 / # ifconfig eth0 172.28.8.254 up eth0: PHY is Generic MII () It looks like your 2.6.12 kernel isn't handling the PHY correctly. I'd recommend upgrading to something newer which has the phylib (can't remember which 2.6 that went into). - kumar
[RFC] consolidated libdt proposal
On Aug 10, 2006, at 1:55 PM, Mark A. Greer wrote: On Thu, Aug 10, 2006 at 11:51:30AM -0500, Milton Miller wrote: On Tue Aug 8 2006 01:04:08 PM CDT, Mark A. Greer wrote: If we're going to allow cmdline editing in the bootwrapper, we would need to extend the size of a property. ... We already have replace the command line merged (it's why my patches don't apply). That's different. ... Yes, but it still requires changing the size or inserting a property, which is the real requirement we were discussing. Yes, editing at command line would require an input function. milton
how to apply a PowerPC patch to linux 2.4 kernel and port to memec board with vertex II pro FPGA?
hi all, im new to porting of Linux to PowerPC . Could anyone let me know 1) the procedure of how to Port a linux OS to PowerPC for a VirtexII Pro memec board?? whats are the steps that i need to follow? 2) where can i find the power-pc patch for linux 2.4 kernel? Thanks and Regards, Ujwal -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060811/3fe4d776/attachment.htm
XUPV2P, which kernel 2.6. device drivers are available?
And so it came to pass, that on Mon, 07 Aug 2006 17:03:22 +0100 Ameet Patil ammubhai at gmail.com wrote as thus: Hi Benjamin, I had ported the ENET driver but it was a bit buggy. Could you send me your driver patch so I can test it? Hi, I have put all necessary files into an archive. I have implemented the driver into a patched version of the 2.6.18-rc3 kernel, so I thought it would be the best to provide all modified files in an archive (also, I am not familiar with generating patches and stuff... ;-). Please feel free to provide a real patch. Ok, here we go: http://www.dt.e-technik.uni-dortmund.de/mitarbeiter/heyne/xilinx/xilinx_emac_26.zip Be warned: This driver probably can be considered as BadHack(TM) - It's the first one I am providing to the public. So if you have any suggestions for improving it, please tell me. TODO (As far as I can tell): - Make it a real platform device - Make use of the XILINX_EDK config of the TEMAC driver patch (Btw.: Will this be officially integrated into the kernel?). Any feedback will be appreciated... Best regards -- Benjamin Heyne
PCI driver on EB8347
I'm using polling mechanism and not interrupts in my driver. Although I'm not using polling I see strange behavior When I do lspci -v I don't see any interrupts being allocated to PCI device behind PCI bridge But when I use same card directly on primary bus I do see interrupt being allocated to PCI device. Any advise why IRQ's being not allocated in case its attached to PCI bridge ? Do I need to take care of any extra configuration in case of PCI card is attached to PCI bridge ? Yaa you are correct I shouldn't use CONFIG_85xx_PCI2 Thanks, -Rajan From: Liu Dave-r63238 [mailto:[EMAIL PROTECTED] Sent: Thu 8/10/2006 10:40 PM To: rajan rai; Gala Kumar K.-galak Cc: linuxppc-embedded at ozlabs.org Subject: RE: PCI driver on EB8347 RajanI have written PCI driver which works fine along with MPC8347 and two PCI Rajan card connected in a single PCI bus. When I try to communicate same PCI card Rajan using PCI bridge ( PCI2050B ), Linux does detect PCI card on Secondary bus Rajan but same driver doesn't work PCI interrupt for secondary bus set up properly? RajanDo I need to enable support for second PCI host controller at kernel level to Rajanmake it work? Or I need to do something else ? I tried compiling PPC-linux kernel Rajan after enabling CONFIG_85xx_PCI2 kernel doesn't compile it gives me error while Rajancompiling arch/ppc/syslib/ppc83xx_setup.c Kernel version I'm using is 2.6.13. Why you enable CONFIG_85xx_PCI2 in kernel? It is for 85xx, but you are using 8347 processor. snip Dave -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060811/8adf09d2/attachment.htm
SystemAce Driver.
Hi Sudheer, Frank has already answered your questions. If you have any problems with the SysAce patch... do let me know. I have written a small tutorial here if it helps... http://linux.get2knowmore.com -Ameet sudheer wrote: Hello Ameet Patil I am looking for linux kernel source 2.6.16 with system ace controller support. I downloaded the linux-2.6.16 and linux-2.6.17-1 source from kernel.org but could not find any files related to system ace controller ( No xilinx_sysace directory in drivers/block/) . I have checked penguinppc.org also but could not get it. Can you please send to me the link where i could download the linuxppc-2.6.16 source with system ace support. Thanks Regards Sudheer Ameet Patil wrote: Hi Raja, I have ported the Xilinx System ACE driver to 2.6 kernel. Find the latest one here: http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2.patch NOTE: this patch wouldn't work if you are using the TEMAC driver. In which case use the -after-TEMAC patch found in the patches folder above. Check the following discussions (threads) for more details: 1. Xilinx SystemACE driver for 2.6 2. Xilinx BSP for linux 2.6 3. Kernel hangs after Now booting the kernel. cheers, -Ameet Raja Chidambaram wrote: Hi all, We are working on customized board with amcc 440SPe processor xilinx System Ace controller. The System Ace controller is connected to compact flash driver. We use u-boot 1.2 as bootloader linux kernel 2.6.16-2. On the process the u-boot is able to detect compact flash through Xilinx SystemAce controller able to load the kernel image into compact flash.But when the linux boot's up it not able to detect the System Ace controller or compact flash. Note:we need to have the root file system in compact flash. Is their any drivers available for SystemAce controller on linux 2.6,if their how to get it.please help me in this with regards raja __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
mpc8xx usb controller on linux 2.6
Hello, I am using linux 2.6.18 on a MPC875, which runs on a custom board. Some changes to the official kernel allow me to get the mpc8xx internal usb host controller working and access an usb stick successfully. I just used Brad Parkers 2.4 patch, ported it to linux 2.6 and merged it with the cpm2usb project. Until now it just worked for my board. Maybe any skilled programmer would like to test the patch also on his own board, fix some bugs and give me some confidence that the patch is somehow stable so that it once can be added to official linux source tree. I would appreciate that and try to help to get it working. You can find the patch at http://wwwcip.informatik.uni-erlangen.de/~sijoange/ Because of a bug in the m8xx USB CPM (read m8xx errata) you must feed a 1khz signal out and feed it at the DREQ pin in again on your board. Then you have to patch the kernel, configure linux to use the m8xx usb sof patch and the m8xx usb host controller, startup the compiled linux, fix some bugs, give me some feedback. Regards, Josef
SystemAce Driver.
Hi Ameet, Firstly, thanks for the mail. I am able to compile the linux-2.6.16 and got the ace support files with the patch. While compiling got some errors with xparameters, but am rectify them. I need to wait for the hardware to test the source. Thanks Regards Sudheer Ameet Patil wrote: Hi Sudheer, Frank has already answered your questions. If you have any problems with the SysAce patch... do let me know. I have written a small tutorial here if it helps... http://linux.get2knowmore.com -Ameet sudheer wrote: Hello Ameet Patil I am looking for linux kernel source 2.6.16 with system ace controller support. I downloaded the linux-2.6.16 and linux-2.6.17-1 source from kernel.org but could not find any files related to system ace controller ( No xilinx_sysace directory in drivers/block/) . I have checked penguinppc.org also but could not get it. Can you please send to me the link where i could download the linuxppc-2.6.16 source with system ace support. Thanks Regards Sudheer Ameet Patil wrote: Hi Raja, I have ported the Xilinx System ACE driver to 2.6 kernel. Find the latest one here: http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2.patch NOTE: this patch wouldn't work if you are using the TEMAC driver. In which case use the -after-TEMAC patch found in the patches folder above. Check the following discussions (threads) for more details: 1. Xilinx SystemACE driver for 2.6 2. Xilinx BSP for linux 2.6 3. Kernel hangs after Now booting the kernel. cheers, -Ameet Raja Chidambaram wrote: Hi all, We are working on customized board with amcc 440SPe processor xilinx System Ace controller. The System Ace controller is connected to compact flash driver. We use u-boot 1.2 as bootloader linux kernel 2.6.16-2. On the process the u-boot is able to detect compact flash through Xilinx SystemAce controller able to load the kernel image into compact flash.But when the linux boot's up it not able to detect the System Ace controller or compact flash. Note:we need to have the root file system in compact flash. Is their any drivers available for SystemAce controller on linux 2.6,if their how to get it.please help me in this with regards raja __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs
On Aug 11, 2006, at 6:21 AM, Prashant Yendigeri wrote: Hi, Downloaded 2.6.16.26 and booted up and got this : / # ifconfig eth0 172.28.8.254 up [ 34.034596] 0:00 not found [ 34.037330] eth0: Could not attach to PHY [ 34.041809] 0:00 not found SIOCSIFFLAGS: No[ 34.044526] eth0: Could not attach to PHY such device SIOCSIFFLAGS: No such device I had enabled all the PHY devices in .config and also tried only with Marvell phy enabled. Are you doing this on a custom board? If so what is the PHY address for the Marvell phy you are using? - k Kernel boot messages : [2.296555] Gianfar MII Bus: probed [2.301789] eth0: Gianfar Ethernet Controller Version 1.2, 00:01:af:07:9b:8a [2.309039] eth0: Running with NAPI disabled [2.313307] eth0: 64/64 RX/TX BD ring size [2.318498] eth1: Gianfar Ethernet Controller Version 1.2, 00:00:00:00:72:6f [2.325738] eth1: Running with NAPI disabled [2.330006] eth1: 64/64 RX/TX BD ring size [2.335198] eth2: Gianfar Ethernet Controller Version 1.2, 6f: 74:3d:2f:64:65 [2.342377] eth2: Running with NAPI disabled [2.346662] eth2: 64/64 RX/TX BD ring size [2.351586] Marvell 88E1101: Registered new driver [2.357010] Davicom DM9161E: Registered new driver [2.362443] Davicom DM9131: Registered new driver [2.367775] Cicada Cis8204: Registered new driver [2.373136] LXT970: Registered new driver [2.377794] LXT971: Registered new driver [2.382461] QS6612: Registered new driver Regards, Prashant Kumar Gala galak at kernel.crashing.org 08/11/2006 09:40 AM To Prashant Yendigeri Prashant.Yendigeri at lntinfotech.com cc linuxppc-embedded at ozlabs.org Subject Re: Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs On Aug 10, 2006, at 6:18 AM, Prashant Yendigeri wrote: Hi, The gianfar driver of 2.6.12 and 2.4.20 give different outputs on the same PPC 8540 board. What could be the reason ? Output on 2.4.20 : /root # ifconfig eth0 172.28.8.254 up eth0: PHY is Marvell 88E1011S (1410c62) eth0: Auto-negotiation done eth0: Half Duplex eth0: Speed 10BT eth0: Link is up Output on 2.6.12 / # ifconfig eth0 172.28.8.254 up eth0: PHY is Generic MII () It looks like your 2.6.12 kernel isn't handling the PHY correctly. I'd recommend upgrading to something newer which has the phylib (can't remember which 2.6 that went into). - kumar __ __
PCI driver on EB8347
On Aug 11, 2006, at 4:15 AM, rajan rai wrote: I'm using polling mechanism and not interrupts in my driver. Although I'm not using polling I see strange behavior When I do lspci -v I don't see any interrupts being allocated to PCI device behind PCI bridge But when I use same card directly on primary bus I do see interrupt being allocated to PCI device. Any advise why IRQ's being not allocated in case its attached to PCI bridge ? Do I need to take care of any extra configuration in case of PCI card is attached to PCI bridge ? You need to make sure that the pci_map_irq/mpc83xx_map_irq function handles the right swizziling for the P2P bridge for your setup. If you are just connected directly its pretty straight forward. However IRQ assignment behind the bridge can be very board specific and so you need to make sure that the code is doing the right think for you. What ever strangeness do you see from lspci? - k
Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs
Hi, This is a standard board designed by GDA technologies Inc. (www.gdatech.com) and eth on 2.4.20 works very much. U-Boot messages : U-Boot 1.1.0(pq3-20040423-r1) (May 5 2006 - 08:56:54) Freescale PowerPC Core: E500, Version: 2.0, (0x80200020) System: 8540, Version: 2.0, (0x80300020) Clocks: CPU: 660 MHz, CCB: 264 MHz, DDR: 132 MHz, LBC: 66 MHz L1 D-cache 32KB, L1 I-cache 32KB enabled. Board: Freescale EVAL8540 Board CPU: 660 MHz CCB: 264 MHz DDR: 132 MHz LBC: 66 MHz L1 D-cache 32KB, L1 I-cache 32KB enabled. I2C: ready DRAM: 256 MB FLASH: 8 MB L2 cache enabled: 256KB In:serial Out: serial Err: serial Net: Freescale ENET0: PHY is Marvell 88E1011S (1410c62) Freescale ENET1: PHY is Marvell 88E1011S (1410c62) Freescale ENET2: PHY is Intel LXT971A (1378e2) Freescale ENET0, Freescale ENET1, Freescale ENET2 Hit any key to stop autoboot: 0 MPC8540EVAL= -prashant Kumar Gala galak at kernel.crashing.org Sent by: linuxppc-embedded-bounces+prashant.yendigeri=lntinfotech.com at ozlabs.org 08/11/2006 06:07 PM To Prashant Yendigeri Prashant.Yendigeri at lntinfotech.com cc linuxppc-embedded at ozlabs.org Subject Re: Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs On Aug 11, 2006, at 6:21 AM, Prashant Yendigeri wrote: Hi, Downloaded 2.6.16.26 and booted up and got this : / # ifconfig eth0 172.28.8.254 up [ 34.034596] 0:00 not found [ 34.037330] eth0: Could not attach to PHY [ 34.041809] 0:00 not found SIOCSIFFLAGS: No[ 34.044526] eth0: Could not attach to PHY such device SIOCSIFFLAGS: No such device I had enabled all the PHY devices in .config and also tried only with Marvell phy enabled. Are you doing this on a custom board? If so what is the PHY address for the Marvell phy you are using? - k Kernel boot messages : [2.296555] Gianfar MII Bus: probed [2.301789] eth0: Gianfar Ethernet Controller Version 1.2, 00:01:af:07:9b:8a [2.309039] eth0: Running with NAPI disabled [2.313307] eth0: 64/64 RX/TX BD ring size [2.318498] eth1: Gianfar Ethernet Controller Version 1.2, 00:00:00:00:72:6f [2.325738] eth1: Running with NAPI disabled [2.330006] eth1: 64/64 RX/TX BD ring size [2.335198] eth2: Gianfar Ethernet Controller Version 1.2, 6f: 74:3d:2f:64:65 [2.342377] eth2: Running with NAPI disabled [2.346662] eth2: 64/64 RX/TX BD ring size [2.351586] Marvell 88E1101: Registered new driver [2.357010] Davicom DM9161E: Registered new driver [2.362443] Davicom DM9131: Registered new driver [2.367775] Cicada Cis8204: Registered new driver [2.373136] LXT970: Registered new driver [2.377794] LXT971: Registered new driver [2.382461] QS6612: Registered new driver Regards, Prashant Kumar Gala galak at kernel.crashing.org 08/11/2006 09:40 AM To Prashant Yendigeri Prashant.Yendigeri at lntinfotech.com cc linuxppc-embedded at ozlabs.org Subject Re: Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs On Aug 10, 2006, at 6:18 AM, Prashant Yendigeri wrote: Hi, The gianfar driver of 2.6.12 and 2.4.20 give different outputs on the same PPC 8540 board. What could be the reason ? Output on 2.4.20 : /root # ifconfig eth0 172.28.8.254 up eth0: PHY is Marvell 88E1011S (1410c62) eth0: Auto-negotiation done eth0: Half Duplex eth0: Speed 10BT eth0: Link is up Output on 2.6.12 / # ifconfig eth0 172.28.8.254 up eth0: PHY is Generic MII () It looks like your 2.6.12 kernel isn't handling the PHY correctly. I'd recommend upgrading to something newer which has the phylib (can't remember which 2.6 that went into). - kumar __ __ ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded __ __ -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060811/9aa6acdc/attachment.htm
MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006
Hi Jeffrey, I got one more question. Is it enough to jumper the MPC8548 to an endpoint device? Or is some additional code required (like your U-Boot commands) to make a MPC8548 work as an EP. Up to now I was assuming there is a certain EEPROM that contains a sufficient PCIe EP configuration. Thanks, Florian
PCI DMA_MR Problem
I got a problem when I set the pci dmamr for MPC8250 for DMA PCI transfering data on linux kernel 2.6.17. When I set the values for the pci_dmamr registers, then print the register values back, some bits can not be set. Did anybody know what are the problem, or I have to set other stuff. Thanks. The code like this: volatile cpm2_map_t *immap = cpm2_immr; immap-im_pci.pci_dmamr0 = 0x0042b00c; immap-im_pci.pci_dmamr1 = 0x0042b00c; immap-im_pci.pci_dmamr2 = 0x0042b00c; immap-im_pci.pci_dmamr3 = 0x0042b00c; printk(DMA0 MR = 0x%08x\n, immap-im_pci.pci_dmamr0); printk(DMA1 MR (0x%08x) = 0x%08x\n, immap-im_pci.pci_dmamr1); printk(DMA2 MR (0x%08x) = 0x%08x\n, immap-im_pci.pci_dmamr2); printk(DMA3 MR (0x%08x) = 0x%08x\n, immap-im_pci.pci_dmamr3); The results are following: DMA0 MR (0xf0010500) = 0x0040b000 DMA1 MR (0xf0010580) = 0x0040b000 DMA2 MR (0xf0010600) = 0x0040b000 DMA3 MR (0xf0010680) = 0x0040b000 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs
On Fri, 2006-08-11 at 18:13 +0530, Prashant Yendigeri wrote: Hi, This is a standard board designed by GDA technologies Inc. (www.gdatech.com) and eth on 2.4.20 works very much. I used a 8540 GDA board once upon a time and all I needed to do was to change the PHY address. Lookat your 2.4 source and determine what the correct value is and double check. -Matthew
Realtime preemption patch on PPC
On Thursday 10 August 2006 18:04, Ben Weintraub wrote: Howdy, I'm wondering if anyone has had success getting Ingo Molnar's realtime preemption patch (the one here: http://people.redhat.com/mingo/realtime-preempt/ ) working on the ppc arch. I have gotten them to work with MPC7448 boards, but it has hardware floating point, so no math-emu problems. Anyhow, when I boot on an MPC8555 with my hack, I get an endless stream of: BUG: sleeping function called from invalid context init(1) at arch/powerpc/math-emu/math.c:226 in_atomic():0 [], irqs_disabled():1 Call Trace: [A0BB3E90] [A000934C] show_stack+0x48/0x194 (unreliable) [A0BB3EC0] [A001B7DC] __might_sleep+0xe8/0xf4 [A0BB3EE0] [A00136C0] do_mathemu+0x30/0x8c8 [A0BB3F00] [A00036AC] program_check_exception+0x1ac/0x514 [A0BB3F40] [A0002A08] ret_from_except_full+0x0/0x4c Line 226 in arch/powerpc/math-emu/math.c is part of the do_mathemu() function, and contains a call to get_user(), which calls __might_sleep(), causing this problem.
U-boot on ML403
Ming Liu wrote: Dear Frank, I know you are using U-boot on ML403 now. So can you say something about how to configure U-boot as ML403 board? I noticed that in U-boot 1.1.4, there is only ML300 supported. So if I want to configure the board as ML403 and some other customed options(e.g. no EEPROM), what shall I do? Thanks for your help. Regards Ming Ming, I received an updated version of the Xilinx xapp542 directly from Xilinx. We had to sign a non-disclosure agreement before they would send it to me. This update provided the necessary pieces to allow XPS to generate a U-Boot BSP and a modified U-Boot tree with support for additional mlXXX boards. I would recommend contacting Xilinx for this. Sorry I can't be of greater assistance. Frank
U-boot on ML403
Ming Liu wrote: Dear Frank, So you mean, you built your ML403 system with U-Boot supported according to the updated version of xapp542, right? There are NOT some patches open to everyone to include ML403 support into the U-Boot tree, right? If both answers for the two questions are yes, then I have to contact Xilinx to ask for help. Anyway, thanks for your information and reply. Regards Ming Ming, There may be public patches available, but I don't know where to obtain them. I used the patches from Xilinx. Frank
U-boot on ML403
Dear Frank, OK then. I have tried to find the patch. But I failed. So maybe it's better to contact Xilinx. Thanks for your help anyway. Regards Ming From: Frank D Lombardo lombardo at mdivac.com To: Ming Liu eemingliu at hotmail.com CC: linuxppc-embedded at ozlabs.org Subject: Re: U-boot on ML403 Date: Fri, 11 Aug 2006 11:39:59 -0400 Ming Liu wrote: Dear Frank, So you mean, you built your ML403 system with U-Boot supported according to the updated version of xapp542, right? There are NOT some patches open to everyone to include ML403 support into the U-Boot tree, right? If both answers for the two questions are yes, then I have to contact Xilinx to ask for help. Anyway, thanks for your information and reply. Regards Ming Ming, There may be public patches available, but I don't know where to obtain them. I used the patches from Xilinx. Frank _ ?? MSN Messenger: http://messenger.msn.com/cn
[RFC] Adding MTD to device tree
Hello. Here's the proposal for the representation of the MTD (optionally having some partitions) in the device tree, along with the sample code that parses the MTD node and hands the necessary information to the 'physmap' driver using the 'platform_device' method. The representation was fitted to the current Linux MTD driver model, so it doesn't bear any information on the chip models or the flash interflace, letting the MTD probing code figure all that out (this part might need some changes I suspect). To me, however, this method seems too limiting: we have to look thru the device tree for each particular kind MTDs (assuming that there could be different ones that 'physmap' can't drive) and register each of them its own way. If we teach 'physmap' to register on the 'of_platform_device' bus, we may look up the device tree for *any* MTD nodes somewhere in arch/powerpc/ tree, register them all, and leave it up to the particular driver to claim them and get the information the driver needs from their node's properties. That would require introducing another MTD partition pasrsing module (so the code that parses the partitions in this patch will move into the separate module under drivers/mtd/). Opinions on what way should be taken and what needs to be added from both PowerPC and MTD communities are very welcome. WBR, Sergei Signed-off-by: Sergei Shtylyov sshtylyov at ru.mvista.com -- next part -- An embedded and charset-unspecified text was scrubbed... Name: OF-physmap-device.patch Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060811/ebf70715/attachment.txt
how to apply a PowerPC patch to linux 2.4 kernel and port to memec board with vertex II pro FPGA?
Hi Ujwal, Linux has support for Xilinx Virtex II Pro FPGA with PPC405. I am sure you can compile for your specific board (MEMEC). Long time back I had come across a doc. related to Linux on MEMEC. Try googling for it... may be its still there. The key is to configure (or set the defines of) the Linux BSP parameters that are specific to your board! cheers, -Ameet Ujwal wrote: hi amit, which are the common development/evaluation boards does this PowerPC work ??? can i use the MEMEC design board with Virtex II Pro FPGA and run the crosscompiled image of linux for powerpc on this board? pls reply as im right now bowled out . Thanks, Ujwal On 8/11/06, *Ameet Patil* ammubhai at gmail.com mailto:ammubhai at gmail.com wrote: Ujwal, Have a look at: http://splish.ee.byu.edu/projects/LinuxFPGA/configuring.htm http://www.crhc.uiuc.edu/IMPACT/gsrc/hardwarelab/docs/kernel-HOWTO.html http://linux.get2knowmore.com/ U might get some idea. -Ameet Ujwal wrote: hi all, im new to porting of Linux to PowerPC . Could anyone let me know 1) the procedure of how to Port a linux OS to PowerPC for a VirtexII Pro memec board?? whats are the steps that i need to follow? 2) where can i find the power-pc patch for linux 2.4 kernel? Thanks and Regards, Ujwal ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org mailto:Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : differentoutputs
Why there are three TSEC on the MPC8540?? Dai -Original Message- From: linuxppc-embedded-bounces+dai.haruki=freescale.com at ozlabs.org [mailto:linuxppc-embedded-bounces+dai.haruki=freescale.com at ozl abs.org] On Behalf Of Kumar Gala Sent: Friday, August 11, 2006 7:38 AM To: Prashant Yendigeri Cc: linuxppc-embedded at ozlabs.org Subject: Re: Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : differentoutputs On Aug 11, 2006, at 6:21 AM, Prashant Yendigeri wrote: Hi, Downloaded 2.6.16.26 and booted up and got this : / # ifconfig eth0 172.28.8.254 up [ 34.034596] 0:00 not found [ 34.037330] eth0: Could not attach to PHY [ 34.041809] 0:00 not found SIOCSIFFLAGS: No[ 34.044526] eth0: Could not attach to PHY such device SIOCSIFFLAGS: No such device I had enabled all the PHY devices in .config and also tried only with Marvell phy enabled. Are you doing this on a custom board? If so what is the PHY address for the Marvell phy you are using? - k Kernel boot messages : [2.296555] Gianfar MII Bus: probed [2.301789] eth0: Gianfar Ethernet Controller Version 1.2, 00:01:af:07:9b:8a [2.309039] eth0: Running with NAPI disabled [2.313307] eth0: 64/64 RX/TX BD ring size [2.318498] eth1: Gianfar Ethernet Controller Version 1.2, 00:00:00:00:72:6f [2.325738] eth1: Running with NAPI disabled [2.330006] eth1: 64/64 RX/TX BD ring size [2.335198] eth2: Gianfar Ethernet Controller Version 1.2, 6f: 74:3d:2f:64:65 [2.342377] eth2: Running with NAPI disabled [2.346662] eth2: 64/64 RX/TX BD ring size [2.351586] Marvell 88E1101: Registered new driver [2.357010] Davicom DM9161E: Registered new driver [2.362443] Davicom DM9131: Registered new driver [2.367775] Cicada Cis8204: Registered new driver [2.373136] LXT970: Registered new driver [2.377794] LXT971: Registered new driver [2.382461] QS6612: Registered new driver Regards, Prashant Kumar Gala galak at kernel.crashing.org 08/11/2006 09:40 AM To Prashant Yendigeri Prashant.Yendigeri at lntinfotech.com cc linuxppc-embedded at ozlabs.org Subject Re: Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs On Aug 10, 2006, at 6:18 AM, Prashant Yendigeri wrote: Hi, The gianfar driver of 2.6.12 and 2.4.20 give different outputs on the same PPC 8540 board. What could be the reason ? Output on 2.4.20 : /root # ifconfig eth0 172.28.8.254 up eth0: PHY is Marvell 88E1011S (1410c62) eth0: Auto-negotiation done eth0: Half Duplex eth0: Speed 10BT eth0: Link is up Output on 2.6.12 / # ifconfig eth0 172.28.8.254 up eth0: PHY is Generic MII () It looks like your 2.6.12 kernel isn't handling the PHY correctly. I'd recommend upgrading to something newer which has the phylib (can't remember which 2.6 that went into). - kumar __ __ ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : differentoutputs
On Fri, Aug 11, 2006 at 11:08:59AM -0700, Haruki Dai-r35557 wrote: Why there are three TSEC on the MPC8540?? There aren't. There are two TSECs and one FEC on the MPC8540. gianfar drives them all (all the non-CPM enets, that is). -Matt
[RFC] consolidated libdt proposal
On Tue, 2006-08-08 at 14:12, Matthew McClintock wrote: This is a patch to u-boot with the changes. * Patch to modify ft_build.c to update flat device trees in place Patch by Matthew McClintock 26-June-2006 Signed-off-by: Matthew McClintock msm at freescale.com Also FYI, I have assembled all Matt's 85xx related U-Boot patches, along with the corresponding 86xx updates, into the u-boot-86xx.git tree on: http://jdl.com/git_repos/ This U-Boot separates out the DTS files, but allows the DTB to be downloaded. It can then update it and hand it off to either an 85xx or 86xx linux kernel. I use these commands, roughly: # build U-boot and Linux as usual $ dtc -f -V 0x10 -I dts -O dtb \ linux-2.6-86xx/arch/powerpc/boot/dts/mpc8641_hpcn.dts \ mpc8641_hpcn.dtb In U-boot now: tftp 100 loeliger/uImage.8641 tftp 90 loeliger/mpc8641_hpcn.dtb bootm 100 - 90 Enjoy, jdl
MTD Flash Howto ?
On Fri, 2006-08-04 at 10:20 -0400, Ned W. Rhodes wrote: The book Building Embedded Linux Systems has a good section on the use of flash file systems. When you boot, you will see something like this, depending on the type of flash driver you have. Make sure you have defined your mtd map in kernel/drivers/mtd/map. JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc. JFS: nTxBlock = 965, nTxLock = 7720 Is JFFS2 required to mount MTD devices? Everything seems to be set up correctly here: S29GL512N MirrorBit Flash: probing 16-bit flash bus S29GL512N MirrorBit Flash: Found 1 x16 devices at 0x0 in 16-bit bank Amd/Fujitsu Extended Query Table at 0x0040 S29GL512N MirrorBit Flash: CFI does not contain boot bank location. Assuming top. number of CFI chips: 1 cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness. Creating 2 MTD partitions on S29GL512N MirrorBit Flash: 0x-0x02a0 : Raw Area ftl_cs: FTL header not found. 0x02a0-0x02b8 : User FS ftl_cs: FTL header not found. blkmtd: version $Revision: 1.24 $ blkmtd: error: missing `device' name cat /proc/mtd: dev:size erasesize name mtd0: 02a0 0002 Raw Area mtd1: 0018 0002 User FS cat /proc/partitions: major minor #blocks name 31 0 43008 mtdblock0 31 1 1536 mtdblock1 ~ # ls -al /dev/mtdblock[01] brw-r--r--1 root 0 31, 0 Aug 11 14:27 /dev/mtdblock0 brw-r--r--1 root 0 31, 1 Aug 11 14:27 /dev/mtdblock1 As you can see the major and minor numbers are correct, but I cannot mount the MTD partitions: ~ # mount -t minix /dev/mtdblock1 foo mount: Mounting /dev/mtdblock1 on /foo failed: No such device What am I doing wrong? Lee
[RFC] Adding MTD to device tree
On Fri, 2006-08-11 at 23:10 +0200, Arnd Bergmann wrote: On Friday 11 August 2006 17:31, Sergei Shtylyov wrote: + h) MTD nodes + + Memory Technology Devices are flash, ROM, and similar chips, often used + for solid state file systems on embedded devices. + + Required properties: + +- device_type : has to be mtd +- compatible : Should be the name of the MTD driver. Currently, this is + most likely to be physmap. +- reg : Offset and length of the register set for the device. I would prefer to call them something different in the device tree. The name 'mtd' is very specific to Linux, but the device tree is a more generic concept. Agreed here. I understand that the booting-without-of.txt file is by definition Linux specific as well, but we should be prepared for making parts of it a OS independent binding at the point where we put the same device nodes into actual OF implementations that able to boot different operating systems. I would prefer a naming that has Required properties: - device_type : one of nand-flash, nor-flash, or rom. There are more than just those kinds of MTDs. There's dataflash, AG-AND, NVRAM, ioremappable DRAM, etc. I'd prefer it to just be called flash. See more below. - model : an identifier for the actual controller chip used. Meaning what exactly? Lots of NOR flash doesn't have a controller. - compatible : Should be the name of the MTD driver. For type rom, this is most likely physmap. This I agree with, but Sergei already had this. And since you're specifying the name of the MTD driver, that typically already knows what type of chip it's talking to. For example, physmap will probe for CFI, JEDEC, and ROM devices already. It can't do NAND flash, so you'd have to specify the name of a NAND driver, such as ndfc.c and that only deals with NAND flash. josh
