Re: PPC_OCP and ppc_sys problem while running kernel2.6 on ML403
[EMAIL PROTECTED] wrote: Hi, all I met the CONFIG_PPC_OCP related problem while running MontaVista linux based on kernel 2.6.17 on Xilinx ML403.I have been confused with some questions about CONFIG_PPC_OCP and ppc_sys.Any reply from anyone is appreciate. From which version did the kernel.org tree stop using the OCP infrastructure and begin to use the ppc_sys infrastructure?Why did this change occur?what disadvantages dose the OCP infrastructure have? The LSP generated by EDK is still using the OCP infrastructure,so when it overwrites the kernel,mistakes happen.Is there any BSP version using ppc_sys which can solve the OCP problem? Also,the ppc_sys dosen't seem to support Virtex board well because I saw most patches supplied drop both ppc_ocp and ppc_sys.What disadventages dose ppc_sys have?Is patching the only method to solve this problem? Are there any patches supporting 2.6.17? Expect your reply,thanks! I am not sure about versions, but I think OCP has been dropped for mainline Linux Kernel sources for about a year. Even the replacement will be somewhat obsoleted when the Xilinx BSP's move from the arch/ppc tree to the arch/powerpc trees. There is a some significant divergence between the Xilinx EDK approach to supporting Linux and what is in the mainline kernel source. Slowly mainline kernel support for various Xilinx devices is maturing. If your product does not require much support for hardware that is not yet in the mainline sources I would highly recommend using the mainline Kernel source. Currently there is support for the Xilinx ML300 and ML403 (with support for Xilinx PIC, and UartLite) in the distribution kernels. My source (following the distribution source closely) for Pico cards is available on Pico's Web Site, www.picocomputing.com. Grant Likely seems to be the staging point for moving broader Xilinx IP support into the mailine kernel source. Grant maintains a xilinx-dev git tree that is even closer to the source trees from kernel.org that includes deeper support that is in the pipeline. I beleive with the exception of the Xilinx TEMAC, the only EDK component needed is an xparameters.h file for your particular hardware. -- Dave Lynch DLA Systems Software Development:Embedded Linux 717.627.3770 [EMAIL PROTECTED] http://www.dlasys.net fax: 1.253.369.9244Cell: 1.717.587.7774 Over 25 years' experience in platforms, languages, and technologies too numerous to list. Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. Albert Einstein ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: [PATCH] TurboStation support (Properly)
On May 8, 2007, at 4:56 PM, Øyvind Repvik wrote:
On Sunday 06 May 2007 14:46:05 Øyvind Repvik wrote:
Hi,
This patch adds support for the QNAP TurboStation TS-101 and
TS-201 devices.
Of course, it probably helps if my mail client doesn't break the
patch completely.
Comments below.
Out of interesting, what's the difference between the TS-101 and TS-201?
Signed-off-by: Øyvind Repvik [EMAIL PROTECTED]
Signed-off-by: Alessandro Zummo [EMAIL PROTECTED]
--- linux-2.6.21.1/arch/powerpc/boot/dts/qnap-ts101.dts 1970-01-01
01:00:00.0 +0100
+++ linux-2.6.21.1.ts/arch/powerpc/boot/dts/qnap-ts101.dts
2007-05-03 22:44:59.0 +0200
@@ -0,0 +1,166 @@
+/*
+ * Device Tree Souce for QNAP Turbostation 101/201
+ *
+ * Choose CONFIG_TURBOSTATION to build a kernel for turbostation
+ *
+ *
+ * Based on kuroboxHD.dts by G. Liakhovetski
+ *
+ * 2007 (c) Oyvind Repvik [EMAIL PROTECTED]
+ *
+ * This file is licensed under
+ * the terms of the GNU General Public License version 2. This
program
+ * is licensed as is without any warranty of any kind, whether
express
+ * or implied.
+ *
+ * build with: dtc -f -I dts -O dtb -o qnap-ts101.dtb -V 16 qnap-
ts101.dts
+ *
+ *
+ */
+
+/ {
+ linux,phandle = 1000;
+ model = TurboStation TSx01;
+ compatible = turbostation;
+ #address-cells = 1;
+ #size-cells = 1;
+
+ cpus {
+ linux,phandle = 2000;
Can you removal all linux,phandle's and use the new reference syntax.
+ #cpus = 1;
+ #address-cells = 1;
+ #size-cells = 0;
+
+ PowerPC,603e { /* Really 8241 */
+ linux,phandle = 2100;
+ device_type = cpu;
+ reg = 0;
+ clock-frequency = fdad680;/* 266 MHz */
+ timebase-frequency = 1fca055; /* 33.333 MHz */
+ bus-frequency = 0;
+ /* Following required by dtc but not used */
+ i-cache-line-size = 0;
+ d-cache-line-size = 0;
No reason not to set the line-size properly to 20
+ i-cache-size = 4000;
+ d-cache-size = 4000;
+ };
+ };
+
+ /* 64MB @ 0x0 */
+ memory {
+ linux,phandle = 3000;
+ device_type = memory;
+ reg = 0400;
+ };
+
+ [EMAIL PROTECTED] {
+ linux,phandle = 3100;
+ device_type = rom;
+ compatible = direct-mapped;
+ probe-type = CFI;
+ reg = ff00 0100;
+ bank-width = 1;
+ partitions =
+ 0020
+ 0020 00d0
+ 00f0 00040001
+ 00f4 0002
+ 00f6 0004
+ 00fa 0002
+ 00fc 0004
+ ;
+ partition-names = kernel\0rootfs\0uboot1\0uboot1-env\0uboot2
\0uboot2-env\0SysConf;
+ };
+
+
+ soc10x { /* AFAICT need to make soc for 8245's uarts to be
defined */
+ linux,phandle = 4000;
+ #address-cells = 1;
+ #size-cells = 1;
+ #interrupt-cells = 2;
+ device_type = soc;
+ compatible = mpc10x;
+ store-gathering = 0; /* 0 == off, !0 == on */
+ reg = 8000 0010;
+ ranges = 8000 8000 7000/* pci mem space */
+ fc00 fc00 0010/* EUMB */
+ fe00 fe00 00c0/* pci i/o space */
+ fec0 fec0 0030/* pci cfg regs */
+ fef0 fef0 0010; /* pci iack */
+
+ [EMAIL PROTECTED] {
+ linux,phandle = 4300;
+ device_type = i2c;
+ compatible = fsl-i2c;
+ reg = fc003000 1000;
+ interrupts = 5 2;
+ interrupt-parent = 4400;
+ };
+
+ [EMAIL PROTECTED] {
+ linux,phandle = 4511;
+ device_type = serial;
+ compatible = ns16550;
+ reg = fc004500 8;
+ clock-frequency = 7ed6b40;/* 133 MHz */
+ current-speed = 1c200;/* 115200 */
+ interrupts = 9 2;
+ interrupt-parent = 4400;
+ };
+
+ [EMAIL PROTECTED] {
+ linux,phandle = 4512;
+ device_type = serial;
+ compatible = ns16550;
+ reg = fc004600 8;
+
Re: [PATCH] TurboStation support (Properly)
On May 9, 2007, at 9:18 AM, Kumar Gala wrote: On May 8, 2007, at 4:56 PM, Øyvind Repvik wrote: On Sunday 06 May 2007 14:46:05 Øyvind Repvik wrote: Hi, This patch adds support for the QNAP TurboStation TS-101 and TS-201 devices. Of course, it probably helps if my mail client doesn't break the patch completely. Comments below. Out of interesting, what's the difference between the TS-101 and TS-201? Also, can you provide a defconfig. - k ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
RE: zImage.elf loads but does not start
I find this usually happens when /dev/tty, /dev/console or /dev/ttyS0 are not setup properly. That is, they are files instead of nodes. This menas you have mounted the root filesystem and init is running on that root filesystem. Charles -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Craine Sent: Tuesday, May 08, 2007 2:50 PM To: Leonid Cc: linuxppc-embedded@ozlabs.org; Mirek23 Subject: Re: zImage.elf loads but does not start Leonid wrote: rootpath= [9.130834] Looking up port of RPC 13/2 on 129.129.130.106 [9.207363] Looking up port of RPC 15/1 on 129.129.130.106 [9.303794] VFS: Mounted root (nfs filesystem). [9.359316] Freeing unused kernel memory: 96k init [9.422162] Warning: unable to open an initial console. The exact device node this requires is /dev/console c 5 1 That should solve your issue. Cheers, Adrian. ___ 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: MPC832xEMDS: ttyS0 output stops mid boot
Hi, For the record, I've just merged powerpc.git from kernel.org and it has started working now! Clearly this means it was a kernel issue rather than a bootloader issue. Regards, Alex Alex Zeffertt wrote: Hi, Sorry about the cross posting, but I'm not sure which list I should send to I'm trying to boot an up-to-date kernel on my MPC8323E-MDS-PB board, but I the console output stops early on during the kernel boot. I'm running the latest u-boot (git://www.denx.de/git/u-boot-mpc83xx.git) with its default environment. The kernel is built from Paulus' powerpc.git, after checking out tag 2.6.21-rc5. The dtb is build from arch/powerpc/boot/dts/mpc832x_mds.dts with the latest compiler (git://www.jdl.com/software/dtc.git). Has anyone else been here before...? If so I'd appreciate any help you can offer. TIA, Alex ---my ttyS0 output-- = = printenv bootcmd=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr bootdelay=6 baudrate=115200 loads_echo=1 ethaddr=00:04:9f:ef:03:01 eth1addr=00:04:9f:ef:03:02 loadaddr=20 netdev=eth0 consoledev=ttyS0 ramdiskaddr=100 ramdiskfile=ramfs.83xx fdtaddr=40 fdtfile=mpc832xemds.dtb stdin=serial stdout=serial stderr=serial ethact=FSL UEC0 Environment size: 979/8188 bytes = setenv ramdiskfile uRamdisk = setenv fdtfile mpc832x_mds.dtb = setenv bootfile uImage = setenv serverip 10.0.0.107 = setenv ipaddr 10.0.6.65 = run ramboot Using FSL UEC0 device TFTP from server 10.0.0.107; our IP address is 10.0.6.65 Filename 'uRamdisk'. Load address: 0x100 Loading: # # # # # # # # # ### done Bytes transferred = 3296770 (324e02 hex) Using FSL UEC0 device TFTP from server 10.0.0.107; our IP address is 10.0.6.65 Filename 'uImage'. Load address: 0x20 Loading: # # # ## done Bytes transferred = 1212615 (1280c7 hex) Using FSL UEC0 device TFTP from server 10.0.0.107; our IP address is 10.0.6.65 Filename 'mpc832x_mds.dtb'. Load address: 0x40 Loading: ### done Bytes transferred = 12288 (3000 hex) ## Booting image at 0020 ... Image Name: Linux-2.6.21-rc5 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1212551 Bytes = 1.2 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at 0100 ... Image Name: uboot ext2 ramdisk rootfs Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:3296706 Bytes = 3.1 MB Load Address: Entry Point: Verifying Checksum ... OK Booting using flat device tree at 0x40 Loading Ramdisk to 07c87000, end 07fabdc2 ... OK Using MPC832x MDS machine description Linux version 2.6.21-rc5 ([EMAIL PROTECTED]) (gcc version 3.4.3) #2 Thu May 3 16:42:54 BST 2007 Found initrd at 0xc7c87000:0xc7fabdc2 setup_arch: bootmem mpc832x_sys_setup_arch() Found MPC83xx PCI host bridge at 0xe0008500. Firmware bus number: 0-0 arch: exit Zone PFN ranges: DMA 0 -32768 Normal 32768 -32768 early_node_map[1] active PFN ranges 0:0 -32768 Built 1 zonelists. Total pages: 32512 Kernel command line: root=/dev/ram rw console=ttyS0,115200 IPIC (128 IRQ sources) at fddf3700 QEIC (64 IRQ sources) at fddf2080 PID
