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
PPC_OCP and ppc_sys problem while running kernel2.6 on ML403
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! linyao ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
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
Re: [PATCH] TurboStation support (Properly)
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.
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>;
+ #cpus = <1>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ PowerPC,603e { /* Really 8241 */
+ linux,phandle = <2100>;
+ device_type = "cpu";
+ reg = <0>;
+ clock-frequency = ;/* 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>;
+ 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 = ;
+ 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 = ;
+ interrupts = <5 2>;
+ interrupt-parent = <4400>;
+ };
+
+ [EMAIL PROTECTED] {
+ linux,phandle = <4511>;
+ device_type = "serial";
+ compatible = "ns16550";
+ reg = ;
+ 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 = ;
+ clock-frequency = <7ed6b40>;
+ current-speed = <4b00>; /* 19200 */
+ interrupts = ;
+ interrupt-parent = <4400>;
RE: zImage.elf loads but does not start
Read this http://www.denx.de/wiki/view/DULG/ELDKMountingTargetComponentsViaNFS. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mirek23 Sent: Tuesday, May 08, 2007 2:46 AM To: linuxppc-embedded@ozlabs.org Subject: Re: zImage.elf loads but does not start Thank you Andrei for your hint. I have hard-coded the mac address in the arch/ppc/boot/simple/embed_config.c. Maybe it is not the most elegant solution but it works. Right now I was able to mount the root file system via nfs but it seems to be still somthing missing: [0.00] Kernel command line: console=ttyUL0,9600 root=/dev/nfs rw nfsroot =129.129.130.106:/opt/eldk41/ppc_4xx,tcp macaddr=00:50:c2:46:d8:01 ip=129.129.10 7.50:129.129.130.106:129.129.107.1:255.255.255.0:ml403-mirek:eth0:off panic=1 [0.00] Xilinx INTC #0 at 0x4120 mapped to 0xFDFFF000 [0.00] PID hash table entries: 256 (order: 8, 1024 bytes) [0.000424] Console: colour dummy device 80x25 [0.001483] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.003209] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.034369] Memory: 62720k available (1572k kernel code, 508k data, 96k init, 0k highmem) [0.121167] Mount-cache hash table entries: 512 [0.129517] NET: Registered protocol family 16 [0.166530] NET: Registered protocol family 2 [0.204693] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [0.205867] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [0.206574] TCP bind hash table entries: 2048 (order: 1, 8192 bytes) [0.207009] TCP: Hash tables configured (established 2048 bind 2048) . . . [2.670863] XTemac: using FIFO direct interrupt driven mode. [2.739134] eth%d: XTemac: PHY detected at address 3. [2.802585] eth0: Xilinx TEMAC #0 at 0x8120 mapped to 0xC504, irq=1 [2.886290] eth0: XTemac id 1.0f, block id 5, type 8 [2.947439] mice: PS/2 mouse device common for all mice [3.010300] TCP cubic registered [3.049323] NET: Registered protocol family 1 [3.101718] NET: Registered protocol family 17 [3.661970] eth0: XTemac: Options: 0xb8f2 [7.693861] eth0: XTemac: We renegotiated the speed to: 100 [7.760541] eth0: XTemac: speed set to 100Mb/s [8.830367] IP-Config: Complete: [8.867105] device=eth0, addr=129.129.107.50, mask=255.255.255.0, gw=129.129.107.1, [8.964390] host=ml403-mirek, domain=, nis-domain=(none), [9.034414] bootserver=129.129.130.106, rootserver=129.129.130.106, 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. To satisfy last problem "unable to open an initial console" I have created an entry in the /opt/eldk41/ppc_4xx/dev directory: mknod ttyUL0 c 204 187 ln -s ttyUL0 console I have rebooted the kernel once again and this time kernel has reached the point as listed below.: [8.964390] host=ml403-mirek, domain=, nis-domain=(none), [9.034414] bootserver=129.129.130.106, rootserver=129.129.130.106, 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 I do not know if the console was taken into account or not (the warning has disapeared but I am not able to ping to my board nor telnet to it). Any idea what could be wrong? I use the root file system from eldk4.1: /opt/eldk41/ppc_4xx/etc/inittab: --- id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # UPS connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it. pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" # Run gettys in standard runlevels 3:2345:respawn:/sbin/mingetty --noclear console - The contents of the /opt/eldk41/ppc_4xx/etc/rc3.d/ is as following: K15appWebK80random S12syslog _S30mouse-emulation K70mouse-emulation K90network_S20randomS56xinetd K75netfs S10networkS25netfs S99local -- View this message
Time generation MPC8xx
Anyone knows how the time() function works on Linux on MPC8xx? I don't have an external RTC circuit but I think is emulated. I thought that it used /dev/rtc but it doesn't seem so, furthermore /dev/rtc is really too fast. It gains 5-6 seconds per minute. Any help is appreciated. Bye, Antonio. ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: initramfs on PowerPC
Hi David, I did as you suggested, made a very small initramfs, and it worked! All it contained was a simple "hello world" file plus a /dev/console node. I then tried to increase the size of this small fs by adding a file (dd if=/dev/urandom of=bigfatfile bs=1M count=1) but this then gives a CRC error when I try to boot. I have also tried increasing the default ramdisk size to 16MB but that makes no difference. Are there any limitrations to the size of the initramfs or on the contents of this fs? Any other suggestions? Thanks! Rich On Friday 04 May 2007 20:02, David H. Lynch Jr. wrote: > I tried numerous approaches, I never got anything to work except pointing > CONFIG_INITRAMFS_SOURCE at a directory with my intramfs tree in it. > I am sure other ways work, but I never managed to figure out what I was > doing > wrong. Regardless that has worked well for me. > > When I build I end up with a single file - zImage,.elf that has both my > kernel > and the initramfs tree in it. While there are a number of distro's that > seem to > use initramfs as a separate file - much like initrd, my loader has no > provisions for a 2nd file, and the kernel build process wraps everything > together > which works fine for me. > > I have never seen your "junk in compressed archive" error, and I have > been doing this > for almost 2 years. But I have frequently had decompression errors. > These typically > have been the result of errors in the PPC zlib libraries. I beleive > somewhere between > 2.6.16 and 2.6.18 these libraries got updated, and the PPC version of > the new ones > had problems. Anyway, after 2.6.18 the new ones are good - though somehow > once in a while the broken ones seem to creep into my development tree, > but updating it usually fixes things. > > There also may be a total size issue. I am hazy on the details, but I > beleive if the > size of size of the kernel goes over 3mb that there are CONFIG values that > may need to be changed. I am not sure whether that is compressed size > decompressed size, kernel size, or combined kernel + initramfs size. > > Regardless, one suguestion would be to try with a very minimal initramfs > tree > and add things until it blows up. > > Richard Danter wrote: > > Hi all, > > > > I am having a problem booting a kernel with an initramfs. The kernel > > version is 2.6.14. The target is a ppc 82xx board. > > > > I have tried both generating the cpio.gz file myself (find . | copi -o -H > > newc | gzip > ../initramfs_data.cpio.gz) and pointing initramfs source to > > a root FS directory (using xconfig) and then re-building my kernel. > > > > Usually the error is "junk in compressed archive" though I also see an > > occasional error about padding. > > > > I am using U-Boot to load the kernel image (uImage). > > > > My host is SuSE 10.0 (x86), though I guess that shouldn't make any > > difference (endianism?). > > > > Any thoughts on what I may be doing wrong? > > > > Thanks > > Rich > > ___ > > 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: zImage.elf loads but does not start
Thank you Andrei for your hint. I have hard-coded the mac address in the arch/ppc/boot/simple/embed_config.c. Maybe it is not the most elegant solution but it works. Right now I was able to mount the root file system via nfs but it seems to be still somthing missing: [0.00] Kernel command line: console=ttyUL0,9600 root=/dev/nfs rw nfsroot =129.129.130.106:/opt/eldk41/ppc_4xx,tcp macaddr=00:50:c2:46:d8:01 ip=129.129.10 7.50:129.129.130.106:129.129.107.1:255.255.255.0:ml403-mirek:eth0:off panic=1 [0.00] Xilinx INTC #0 at 0x4120 mapped to 0xFDFFF000 [0.00] PID hash table entries: 256 (order: 8, 1024 bytes) [0.000424] Console: colour dummy device 80x25 [0.001483] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.003209] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.034369] Memory: 62720k available (1572k kernel code, 508k data, 96k init, 0k highmem) [0.121167] Mount-cache hash table entries: 512 [0.129517] NET: Registered protocol family 16 [0.166530] NET: Registered protocol family 2 [0.204693] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [0.205867] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [0.206574] TCP bind hash table entries: 2048 (order: 1, 8192 bytes) [0.207009] TCP: Hash tables configured (established 2048 bind 2048) . . . [2.670863] XTemac: using FIFO direct interrupt driven mode. [2.739134] eth%d: XTemac: PHY detected at address 3. [2.802585] eth0: Xilinx TEMAC #0 at 0x8120 mapped to 0xC504, irq=1 [2.886290] eth0: XTemac id 1.0f, block id 5, type 8 [2.947439] mice: PS/2 mouse device common for all mice [3.010300] TCP cubic registered [3.049323] NET: Registered protocol family 1 [3.101718] NET: Registered protocol family 17 [3.661970] eth0: XTemac: Options: 0xb8f2 [7.693861] eth0: XTemac: We renegotiated the speed to: 100 [7.760541] eth0: XTemac: speed set to 100Mb/s [8.830367] IP-Config: Complete: [8.867105] device=eth0, addr=129.129.107.50, mask=255.255.255.0, gw=129.129.107.1, [8.964390] host=ml403-mirek, domain=, nis-domain=(none), [9.034414] bootserver=129.129.130.106, rootserver=129.129.130.106, 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. To satisfy last problem "unable to open an initial console" I have created an entry in the /opt/eldk41/ppc_4xx/dev directory: mknod ttyUL0 c 204 187 ln -s ttyUL0 console I have rebooted the kernel once again and this time kernel has reached the point as listed below.: [8.964390] host=ml403-mirek, domain=, nis-domain=(none), [9.034414] bootserver=129.129.130.106, rootserver=129.129.130.106, 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 I do not know if the console was taken into account or not (the warning has disapeared but I am not able to ping to my board nor telnet to it). Any idea what could be wrong? I use the root file system from eldk4.1: /opt/eldk41/ppc_4xx/etc/inittab: --- id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # UPS connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it. pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" # Run gettys in standard runlevels 3:2345:respawn:/sbin/mingetty --noclear console - The contents of the /opt/eldk41/ppc_4xx/etc/rc3.d/ is as following: K15appWebK80random S12syslog _S30mouse-emulation K70mouse-emulation K90network_S20randomS56xinetd K75netfs S10networkS25netfs S99local -- View this message in context: http://www.nabble.com/zImage.elf-loads-but-not-starts-tf3607582.html#a10372619 Sent from the linuxppc-embedded mailing list archive at Nabble.com. ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/ma
