ioremap() fails for 64 MB
I think 64MB limitation of ioremap() is due to the kernel's page size. When compiling kernel, it has an option to choose the memory page size which is default 64MB. To use memory greater than 64MB, there is two methods. One is to make the kernel's page size larger as Phil Nitschke said. Another is to modify ioremap() a little bit --- just make it use another file for mmap while larger than 64MB. Since the central concept of linux is file-based, I think more files are not harmful that only waste a little bit inode structure. And it is much more feasible that one can choose to use file in memory or harddisk or mounted device harddisk/memory ... ... -Original Message- From: [EMAIL PROTECTED] [mailto:linuxppc-embedded-bounces+vows_siu=yahoo.com.hk at ozlabs.org] On Behalf Of Phil Nitschke Sent: Wednesday, August 23, 2006 6:01 PM To: Matt Porter Cc: linuxppc-embedded at ozlabs.org Subject: Re: ioremap() fails for 64 MB On Tue, 2006-08-22 at 09:22 -0500, Matt Porter wrote: On Tue, Aug 22, 2006 at 05:11:09PM +0930, Phil Nitschke wrote: Hi all, I have 2 GB memory on a 7448 processor, and want to reserve a huge chunk of it at boot-time, then ioremap() it into the kernel space inside a device driver. So far I've succeeded with 64 MB, but can't go any higher, as mm/vmalloc.c tells me: allocation failed: out of vmalloc space - use vmalloc=size to increase size. So I tried adding a vmalloc line to the kernel command line as follows: Kernel cmd line: root=/dev/nfs rw mem=1920M vmalloc=1024M nfsroot=... Yeah, that suggestion is bogus. That option can't help with getting more vmalloc space in this case. So the vmalloc=size argument has made no difference. What do I need to do to make this work? Go to the Advanced setup menu. There's a number of options to provide fine-grained control of the PPC kernel virtual address space. SNIP Thanks Matt (and others) for your suggestions. Matt has given me the answers I was looking for. Since my (2 GB) memory is within the (4 GB) addressable by a 32-bit processor, why do I need high memory at all? Are there performance implications on this platform from having a non optimal low/high ratio? That said, why don't you just use alloc_bootmem() to reserve memory for your driver at boot time? I avoided this simply because I wanted to load/unload my driver (during development), and alloc_bootmem() seemed better suited to drivers compiled into the kernel. But I'll look again at this idea if further problems arise with the approach above. Thanks again, -- Phil ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.5/425 - Release Date: 2006/8/22 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.5/426 - Release Date: 2006/8/23
Artesyn PM/PPC 750 U-Boot/Linux support? Datasheet?
You can find nearly all the power pc datasheet from IBM (ibm.com) own web site. I think the most important feature of this 750 series ppc is its capability to run 4 instructions per cycle and have built-in FPU. -Original Message- From: [EMAIL PROTECTED] [mailto:linuxppc-embedded-bounces+vows_siu=yahoo.com.hk at ozlabs.org] On Behalf Of mahesh.roy at wipro.com Sent: Tuesday, August 22, 2006 10:16 PM To: linuxppc-embedded at ozlabs.org Subject: Artesyn PM/PPC 750 U-Boot/Linux support? Datasheet? hi man i saw ur mail and wanted the datasheet of ppc 750 board. so if u can kindly mail it me i ll be grateful to u. Mahesh Roy Designation :Project Engineer Extn : 74162 Direct: 0484-3054162 Mobile : +91-9895572846 (8:30 am to 9:00 pm) (MON to FRI) The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.4/424 - Release Date: 2006/8/21 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.4/424 - Release Date: 2006/8/21 -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060823/ab6d1eff/attachment.htm -- next part -- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 4389 bytes Desc: not available Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060823/ab6d1eff/attachment.jpeg -- next part -- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7830 bytes Desc: not available Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060823/ab6d1eff/attachment.gif
ML40X, ppc 405 crash
So can u access your NFS mapped partition? If you can access every FILEs on the partition, running updatedb ought to index the NFS partition also. Then ?locate fixdep? is just to find the local indexed database and display the matched result --- I just don?t understand the problem. Please state more what have you done in order to let us help you. -Original Message- From: [EMAIL PROTECTED] [mailto:linuxppc-embedded-bounces+vows_siu=yahoo.com.hk at ozlabs.org] On Behalf Of Wade Maxfield Sent: Tuesday, August 22, 2006 5:34 AM To: ppc Subject: ML40X, ppc 405 crash I was running NFS on ML40X. I did a updatedb and then immediately, locate fixdep I got the following crash root at ml403:/home/moduletest# updatedb locate fixdep eth0: Could not transmit buffer. eth0: Could not transmit buffer. eth0: Could not transmit buffer. Oops: kernel access of bad area, sig: 11 [#1] PREEMPT NIP: C01D0F74 LR: C01D0910 SP: C28B1930 REGS: c28b1880 TRAP: 0300Not tainted MSR: 00029030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 DAR: 0004, DSISR: 0080 TASK = c0b034c0[5097] 'frcode' THREAD: c28b Last syscall: 234 GPR00: C28B1930 C0B034C0 C35E3200 C03CC380 C276E810 05E8 C3CE8880 GPR08: 0002 C3CE890C 33003599 10018E04 100C3208 C02DCE08 GPR16: C00DB1CC C02DCE08 0002 000A C28B1DF8 C02E C02A C3A30940 GPR24: C3A30940 C35E3200 C3CE8880 C03A8800 NIP [c01d0f74] pfifo_fast_dequeue+0x40/0x74 LR [c01d0910] qdisc_restart+0x30/0x2b4 Call trace: [c01c1e94] dev_queue_xmit+0x264/0x318 [c01dd8dc] ip_finish_output+0x140/0x2cc [c01dddb0] ip_queue_xmit+0x348/0x53c [c01ef628] tcp_transmit_skb+0x324/0x7f8 [c01f05fc] tcp_write_xmit+0x14c/0x31c [c01ed360] __tcp_data_snd_check+0xc8/0xfc [c01ed9a4] tcp_rcv_established+0x2c0/0x8ac [c01f7250] tcp_v4_do_rcv+0x184/0x374 [c01f7d9c] tcp_v4_rcv+0x95c/0xa4c [c01da000] ip_local_deliver+0x120/0x298 [c01da86c] ip_rcv+0x400/0x508 [c01c2614] netif_receive_skb+0x24c/0x2fc [c01c276c] process_backlog+0xa8/0x1a0 [c01c2908] net_rx_action+0xa4/0x1cc [c001bef4] ___do_softirq+0x7c/0x114 Kernel panic - not syncing: Aiee, killing interrupt handler! 0Rebooting in 180 seconds.. - Here is the kernel build and boot information. (I use the demo compact flash disk image shipped with the ml403 as an intermediate. I've not yet been able to get a small enough build to fit on 412 meg using your tools.) Linux version 2.6.10_mvl401-ml40x (HYPERLINK mailto:root at localhost.localdomainroot at localhost.localdomain) (gcc version 3.4.3 (MontaV ista 3.4.3-25.0.107.0601076 2006-07-21)) #1 Fri Aug 18 14:43:45 CDT 2006 Xilinx ML40x Reference System (Virtex-4 FX) Port by MontaVista Software, Inc. (HYPERLINK mailto:source at mvista.comsource at mvista.com) Built 1 zonelists Kernel command line: console=ttyS0,115200 ip=on root=/dev/xsysace2 rw Xilinx INTC #0 at 0xD1000FC0 mapped to 0xFDFFEFC0 PID hash table entries: 512 (order: 9, 8192 bytes) hr_time_init: arch_to_nsec = 6990506, nsec_to_arch = 1288490158 Console: colour dummy device 80x25 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 61824k available (2244k kernel code, 640k data, 140k init, 0k highmem) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) spawn_desched_task() desched cpu_callback 3/ ksoftirqd started up. desched cpu_callback 2/ desched thread 0 started up. NET: Registered protocol family 16 Registering platform device 'xilinx_emac.0'. Parent at platform Registering platform device 'xilinx_fb.0'. Parent at platform Registering platform device 'xilinx_sysace.0'. Parent at platform Registering platform device 'xilinx_iic.0'. Parent at platform Registering platform device 'xilinx_gpio.0'. Parent at platform Registering platform device 'xilinx_gpio.1'. Parent at platform Registering platform device 'xilinx_gpio.2'. Parent at platform Registering platform device 'xilinx_ps2.0'. Parent at platform Registering platform device 'xilinx_ps2.1'. Parent at platform Installing knfsd (copyright (C) 1996 HYPERLINK mailto:okir at monad.swb.deokir at monad.swb.de). Console: switching to colour frame buffer device 80x30 xgpio #0 at 0x9000 mapped to 0xC505C000 xgpio #1 at 0x90001000 mapped to 0xC505E000 xgpio #2 at 0x90002000 mapped to 0xC506 xilinx_ps2 #0 at 0xA900 mapped to 0xC5062000 xilinx_ps2 #1 at 0xA9001000 mapped to 0xC5064000 Serial: 8250/16550 driver $Revision: 1.90 $ 5 ports, IRQ sharing disabled Registering platform device 'serial8250'. Parent at platform ttyS0 at MMIO 0x0 (irq = 9) is a 16450 io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 8192K
