Re: Flash Filesystem
Hi Georg, On Friday 07 September 2007 09:34, schardt wrote: Hi i've some problems using the on board flash memory with linux. i added the support for adm/fujittsu flash in kernel config and add the right parameters for the cfi flash device in physical memory. cat /proc/mtd gives me dev:size erasesize name mtd0: 0040 0001 physmap-flash.0 i added /dev/mtd0 c 90 0 and /dev/mtdblock0 b 31 0 how do i add a partition and filesystem fdisk /dev/mtd0 seems me not to be correct :) There are several ways to definie partitions on an MTD device. Make sure you enable the 'MTD partitioning support' option and have a look at 'RedBoot partition table parsing' and 'Command line partition table parsing': Device Drivers * Memory Technology Device (MTD) support [*] MTD partitioning support RedBoot partition table parsing Command line partition table parsing Another option is to hardcode the partition table in the platform data for the physmap driver. Best regards, -- Laurent Pinchart CSE Semaphore Belgium Chaussée de Bruxelles, 732A B-1410 Waterloo Belgium T +32 (2) 387 42 59 F +32 (2) 387 42 75 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Flash on ep8248e standard motherboards
On Tue, Sep 04, 2007 at 12:08:47PM -0600, Alan Bennett wrote: BDI 2000 Config File: ; initialize - FLASH BR0 OR0 (64 Mbyte) ;*** WM320xf0010100 0xfc001801 WM32 0xf0010104 0xfc0008c2 [FLASH] CHIPTYPEMIRRORX16 CHIPSIZE0x200 BUSWIDTH16 Having just taken delivery of an ep8248e, I'm surprised that the supplied flash config is commented out and erroneous: [FLASH] ;CHIPTYPEAM29F ;Flash type (AM29F | AM29BX8 | AM29BX16 | I28BX8 | I28BX16) ;CHIPSIZE0x20;The size of one flash chip in bytes (e.g. AM29F010 = 0x2) ;BUSWIDTH8 ;The width of the flash memory bus in bits (8 | 16 | 32 | 64) ; Did you start with the Embedded Planet offering, in your current effort to create a usable config? Is MIRRORX16 more than a guess? I've found that my flash chips are spansion GL256N10FFI02, which AFAICT are S29GL256N10FFI02 from AMD, as we used to know them. I wonder if S29M32X16 is a likely guess for CHIPTYPE on the card which has landed in my lap? Maybe the most important question is: Will a wrong algorithm choice let the magic smoke out? Erik (With just one toenail on the road, so far.) ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: [PATCH 1/2] [POWERPC] Add SCC clock support to cpm2_clk_setup()
On Wednesday 11 July 2007 15:17, Laurent Pinchart wrote: cpm2_clk_setup() supports setting FCC clocks only, even though the cpm_clk_target enumeration lists SCC clocks. This patch adds SCC clock support. Any chance this patch (and its 2/2 brother) could be committed ? Best regards, -- Laurent Pinchart CSE Semaphore Belgium Chaussée de Bruxelles, 732A B-1410 Waterloo Belgium T +32 (2) 387 42 59 F +32 (2) 387 42 75 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: [PATCH 1/2] [POWERPC] Add SCC clock support to cpm2_clk_setup()
On Sep 13, 2007, at 8:53 AM, Laurent Pinchart wrote: On Wednesday 11 July 2007 15:17, Laurent Pinchart wrote: cpm2_clk_setup() supports setting FCC clocks only, even though the cpm_clk_target enumeration lists SCC clocks. This patch adds SCC clock support. Any chance this patch (and its 2/2 brother) could be committed ? Have you looked at Scott Wood's cleanup patches. They seem to do some of this. - k ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Flash on ep8248e standard motherboards
Erik Christiansen wrote: On Tue, Sep 04, 2007 at 12:08:47PM -0600, Alan Bennett wrote: BDI 2000 Config File: ; initialize - FLASH BR0 OR0 (64 Mbyte) ;*** WM320xf0010100 0xfc001801 WM32 0xf0010104 0xfc0008c2 [FLASH] CHIPTYPEMIRRORX16 CHIPSIZE0x200 BUSWIDTH16 Having just taken delivery of an ep8248e, I'm surprised that the supplied flash config is commented out and erroneous: [FLASH] ;CHIPTYPEAM29F ;Flash type (AM29F | AM29BX8 | AM29BX16 | I28BX8 | I28BX16) ;CHIPSIZE0x20;The size of one flash chip in bytes (e.g. AM29F010 = 0x2) ;BUSWIDTH8 ;The width of the flash memory bus in bits (8 | 16 | 32 | 64) ; Did you start with the Embedded Planet offering, in your current effort to create a usable config? Is MIRRORX16 more than a guess? I've found that my flash chips are spansion GL256N10FFI02, which AFAICT are S29GL256N10FFI02 from AMD, as we used to know them. I wonder if S29M32X16 is a likely guess for CHIPTYPE on the card which has landed in my lap? MIRRORX16 is the correct type for Spansion GL series NOR flash. AMD spun off their flash business a while ago and renamed it Spansion. If you look on the datasheet you'll see that Spansion calls the GL technology 'MirrorBit', and in all likelihood the device has a 16-bit data bus. The AMD algorithm may work but the MIRRORX16 definitely will. regards, Ben ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Informations about mem and proc environment between bootloader and kernel
Hello Fabien, you should download the U-boot sources from sourceforge.net. There is a README file there where you can read about porting U-boot. The porting to a custom board of U-boot is easier when your cpu is include, like in your case (mpc8xx). Basically you have to create a new entry in board directory. There you have to insert the initialization code for your flash, sdram and other devices. You also have to make a file as the ones in /include/configs/ with your configuration board. It is essential to have correct environment variables when Linux takes the control. If you use the u-boot command bootm in order to boot Linux, the file where U-Boot transfer the control to Linux is /common/cmd_bootm.c. Moreover I would recommend you a book which explains many things regarding porting Linux (and U-boot): Embedded Linux Primer: A practical, real-world approach. Cheers, Raúl Moreno Raúl Moreno Beltrán Telvent Energía, S. A. División de Tecnología. Desarrollo Software Tlfo: 954935670 fabien boucher [EMAIL PROTECTED] fabien boucher Enviado por: [EMAIL PROTECTED] 13/09/2007 16:05 Para: linuxppc-embedded@ozlabs.org cc: Asunto: Informations about mem and proc environment between bootloader and kernel And I need some help for my project (I'm in internship) to port linux on a custom board. This board has been developped by the company where i'm doing the intership and it's based on a MPC875 with RAM and Flash chips and several other devices. Currently the board run with a BSP developped by the company's developpers, the BSP launch Psos. This BSP is able to decompress an image and load it in RAM. I plan to use U-boot to be more able to boot a kernel but as it's not a common board so it's not initialy supported by U-boot. So I have two choices first use the BSP with some changes to adapt it for loading the Linux kernel or using U-boot. I'm looking for informations about the memory and processor environment needed by linux to boot properly for evaluate whether the use of a customize BSP is the easiest way against the port of a new board under U-boot. So if someone know where i can found those informations concerning the step between where the boot program have control of the cpu and where Linux take control. Thank you, Fabien ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Which 2.6 kernel for MPC5200
On 9/12/07, Grant Likely [EMAIL PROTECTED] wrote: On 9/12/07, Jon Smirl [EMAIL PROTECTED] wrote: On 9/12/07, Robert Schwebel [EMAIL PROTECTED] wrote: We have the OSELAS.BSP patch stack for the PCM030 working ontop of Linus' git. It still uses an older version of the Bestcom patches, so if you do some work in that area, please keep me informed about your progress. What is the best way to proceed? I need to be on current git since we are integrating a wireless driver that is tracking current git and the mac80211 work. I have Phytec (pcm030) and Efika hardware but I don't have a 5200lite. Our prototype hardware uses the pcm030 module on a custom baseboard. The best thing for me would be to get a FEC driver merged. That is the largest piece of code that is floating around. Getting that merged would give me a stable base to build future patches on. I'd also like to get support for the pcm030 (minus real-time) merged. That isn't a lot of code once FEC is in the kernel. Domen has posted this driver [RFC PATCH v0.1] net driver: mpc52xx fec. I can work on breaking that up, but I don't have a 5200lite so I will have to port to pcm030. I don't want to start on this if someone else is already doing it. Sylvain's bestcomm patches need be cleaned up and resubmitted before the next merge window opens. AFAIK, the code is pretty much ready, and all the comments have been addressed. All that is required is the final push to tidy the patchset and post to the list one more time. Sylvain said that he was going to get this done last weekend, but I haven't heard back from him yet. I just noticed mail from Paul Mackerras Patches added to powerpc.git for-2.6.24 branch The MPC5200 ones aren't in the list. Sylvain, if you need help, please let me know. I'll happily take on the last bit of tidy work if that's what is needed to be finished before the merge window. (And it needs to be ready *before*, not during if I'm judging the prevailing winds correctly). Cheers, g. -- Jon Smirl [EMAIL PROTECTED] -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 -- Jon Smirl [EMAIL PROTECTED] ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Which 2.6 kernel for MPC5200
On 9/12/07, Domen Puncer [EMAIL PROTECTED] wrote: On 12/09/07 12:16 -0400, Jon Smirl wrote: On 9/12/07, Grant Likely [EMAIL PROTECTED] wrote: On 9/12/07, Jon Smirl [EMAIL PROTECTED] wrote: On 9/12/07, Robert Schwebel [EMAIL PROTECTED] wrote: We have the OSELAS.BSP patch stack for the PCM030 working ontop of Linus' git. It still uses an older version of the Bestcom patches, so if you do some work in that area, please keep me informed about your progress. What is the best way to proceed? I need to be on current git since we are integrating a wireless driver that is tracking current git and the mac80211 work. I have Phytec (pcm030) and Efika hardware but I don't have a 5200lite. Our prototype hardware uses the pcm030 module on a custom baseboard. The best thing for me would be to get a FEC driver merged. That is the largest piece of code that is floating around. Getting that merged would give me a stable base to build future patches on. I'd also like to get support for the pcm030 (minus real-time) merged. That isn't a lot of code once FEC is in the kernel. Domen has posted this driver [RFC PATCH v0.1] net driver: mpc52xx fec. I can work on breaking that up, but I don't have a 5200lite so I will have to port to pcm030. I don't want to start on this if someone else is already doing it. Sylvain's bestcomm patches need be cleaned up and resubmitted before the next merge window opens. AFAIK, the code is pretty much ready, and all the comments have been addressed. All that is required is the final push to tidy the patchset and post to the list one more time. Sylvain said that he was going to get this done last weekend, but I haven't heard back from him yet. Sylvain, if you need help, please let me know. I'll happily take on the last bit of tidy work if that's what is needed to be finished before the merge window. (And it needs to be ready *before*, not during if I'm judging the prevailing winds correctly). Is a version of this patch set that has been rebased to current git available? If I have a starting point I can begin working on the pcm030 support. pcm030 already works, it is just out of tree. I think these patches are latest: http://www.246tnt.com/mpc52xx/dev_full/ Applying them to -git should not be a problem, I don't remember anything tricky, but if you have problems, I can send you patches agains mainline. BTW. I posted FEC patch v2, which will hopefully be merged. I just booted your code successfully on current Linus git with a Phytec pcm030. There is a timeout issue that is probably related to the specific Ethernet PHY chip used on the pcm030. I'm looking into it now. [1.313708] net eth0: attached phy 0 to driver Generic PHY [2.320013] Sending DHCP requests .. timed out! [ 81.968863] IP-Config: Retrying forever (NFS root)... [ 82.477527] net eth0: attached phy 0 to driver Generic PHY [ 83.487809] Sending DHCP requests .6PHY: f0003000:00 - Link is Up - 100/Full [ 86.323795] ., OK [ 88.579802] IP-Config: Got DHCP answer from 192.168.1.200, my address is 192.168.1.5 [ 88.587923] IP-Config: Complete: Domen Cheers, g. -- Jon Smirl [EMAIL PROTECTED] -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 -- Jon Smirl [EMAIL PROTECTED] -- Jon Smirl [EMAIL PROTECTED] ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Patches for 2.6.24 ??
Guys, If you have things you want or think should go into 2.6.24 please speak up now! - k ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Flash on ep8248e standard motherboards
On Thu, Sep 13, 2007 at 10:10:06AM -0400, Ben Warren wrote: MIRRORX16 is the correct type for Spansion GL series NOR flash. AMD spun off their flash business a while ago and renamed it Spansion. If you look on the datasheet you'll see that Spansion calls the GL technology 'MirrorBit', and in all likelihood the device has a 16-bit data bus. The AMD algorithm may work but the MIRRORX16 definitely will. Yes, the Flash Organisation section of the ep8248e manual shows two 16-bit devices. (That's what seemed erroneous in the BDI2000 config file supplied with the card. ;-) Many thanks for putting me on the right track w.r.t. CHIPTYPE. It'll save me trying all the wrong guesses first. Regards, Erik ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
