Re: [ANN] Introducing new "test" branch in powerpc.git tree
On Wed, Feb 04, 2009 at 09:20:04PM -0700, Grant Likely wrote: > what to do with it. The only difference is that mine isn't usually > public. If people want to see it, then I push it out, but otherwise I > just wait until I've got a real pull request. I'd like to see that tree public, so I can check anytime if you already have picked up a patch or if it has been overlooked... Regards, Wolfram -- Pengutronix e.K. | Wolfram Sang| Industrial Linux Solutions | http://www.pengutronix.de/ | signature.asc Description: Digital signature ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Calling wait_event_interruptible_timeout() in I2C wait functions
On Wed, Feb 04, 2009 at 12:00:52PM -0800, Mike Ditto wrote: > Timur Tabi wrote: > > However, it appears that this is not common behavior for I2C driver. In > > fact, only these six drivers ever call wait_event_interruptible_timeout(): > > i2c-cpm.c > I don't know about the others, but in i2c-cpm.c the use of interruptible > wait seems incorrect. Maybe it could be made correct, but as is, it > does not correctly clean up the hardware state or return a useful > value when interrupted by a signal. It's not clear what to do, anyway - This is exactly the problem for users that caused Timur to run into this - further up the stack we're trying to do cleanup that involves writing via I2C but the I2C writes error out due to the signal. > handling (one second delay in the unlikely worst case for i2c-cpm). Ditto for the Freescale PowerPC I2C driver. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
2.6.29-rc3-git7 build break : drivers/serial/cpm_uart/
2.6.29-rc3-git7 randconfig build breaks with following error CC drivers/serial/cpm_uart/cpm_uart_core.o drivers/serial/cpm_uart/cpm_uart_core.c: In function cpm_put_poll_char: drivers/serial/cpm_uart/cpm_uart_core.c:992: error: implicit declaration of function cpm_uart_early_write make[3]: *** [drivers/serial/cpm_uart/cpm_uart_core.o] Error 1 make[2]: *** [drivers/serial/cpm_uart] Error 2 make[1]: *** [drivers/serial] Error 2 make: *** [drivers] Error 2 Couldn't find implementation for cpm_uart_early_write. Config file is attached. Thanks -Sachin -- - Sachin Sant IBM Linux Technology Center India Systems and Technology Labs Bangalore, India - # # Automatically generated make config: don't edit # Linux kernel version: 2.6.29-rc3-git7 # Thu Feb 5 17:21:59 2009 # # CONFIG_PPC64 is not set # # Processor support # CONFIG_6xx=y # CONFIG_PPC_85xx is not set # CONFIG_PPC_8xx is not set # CONFIG_40x is not set # CONFIG_44x is not set # CONFIG_E200 is not set CONFIG_PPC_FPU=y # CONFIG_FSL_EMB_PERFMON is not set CONFIG_ALTIVEC=y CONFIG_PPC_STD_MMU=y CONFIG_PPC_STD_MMU_32=y # CONFIG_PPC_MM_SLICES is not set # CONFIG_SMP is not set CONFIG_NOT_COHERENT_CACHE=y CONFIG_PPC32=y CONFIG_WORD_SIZE=32 # CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set CONFIG_MMU=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_HARDIRQS=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set CONFIG_IRQ_PER_CPU=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_ILOG2_U32=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_GPIO=y # CONFIG_ARCH_NO_VIRT_TO_BUS is not set CONFIG_PPC=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_NVRAM=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_PPC_OF=y CONFIG_OF=y CONFIG_PPC_UDBG_16550=y # CONFIG_GENERIC_TBSYNC is not set CONFIG_AUDIT_ARCH=y CONFIG_DEFAULT_UIMAGE=y CONFIG_REDBOOT=y CONFIG_HIBERNATE_32=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_PPC_DCR_NATIVE is not set # CONFIG_PPC_DCR_MMIO is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_TASKSTATS=y # CONFIG_TASK_DELAY_ACCT is not set # CONFIG_TASK_XACCT is not set # CONFIG_AUDIT is not set # # RCU Subsystem # CONFIG_CLASSIC_RCU=y # CONFIG_TREE_RCU is not set # CONFIG_PREEMPT_RCU is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_PREEMPT_RCU_TRACE is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=17 CONFIG_GROUP_SCHED=y # CONFIG_FAIR_GROUP_SCHED is not set CONFIG_RT_GROUP_SCHED=y CONFIG_USER_SCHED=y # CONFIG_CGROUP_SCHED is not set CONFIG_CGROUPS=y CONFIG_CGROUP_DEBUG=y CONFIG_CGROUP_NS=y CONFIG_CGROUP_FREEZER=y # CONFIG_CGROUP_DEVICE is not set # CONFIG_CGROUP_CPUACCT is not set CONFIG_RESOURCE_COUNTERS=y # CONFIG_CGROUP_MEM_RES_CTLR is not set CONFIG_RELAY=y CONFIG_NAMESPACES=y # CONFIG_UTS_NS is not set CONFIG_IPC_NS=y # CONFIG_USER_NS is not set CONFIG_PID_NS=y # CONFIG_NET_NS is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_EXTRA_PASS=y CONFIG_HOTPLUG=y # CONFIG_PRINTK is not set # CONFIG_BUG is not set CONFIG_ELF_CORE=y # CONFIG_COMPAT_BRK is not set # CONFIG_BASE_FULL is not set CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y # CONFIG_SIGNALFD is not set # CONFIG_TIMERFD is not set CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set # CONFIG_PROFILING is not set CONFIG_TRACEPOINTS=y CONFIG_MARKERS=y CONFIG_HAVE_OPROFILE=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_CLK=y # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=1 # CONFIG_MODULES is not set CONFIG_BLOCK=y CONFIG_LBD=y CONFIG_BLK_DEV_BSG=y # CONFIG_BLK_DEV_INTEGRITY is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y # CONFIG_IOSCHED_DEADLINE is not set # CONFIG_IOSCHED_CFQ is not set CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="anticipatory" CONFIG_FREEZER=y CONFIG_PPC_MSI_BITMAP=y # # Platform support # CONFIG_PPC_MULTIPLATFORM=y CONFIG_CLASSIC32=y # CONFIG_PPC_CHRP is not set CONFIG_PPC_MPC512x=y CONFIG_PPC_M
ndfc driver on Kilauea board
Hi, I'm trying to enable Linux ndfc driver on Kilauea (ppc405ex) board rev 1.2 running u-boot v2009.01 and linux-2.6.29-rc3. I've enabled NDFC in kernel config and updated kilauea.dts as described in Documentation/powerpc/dts-bindings/4xx/ndfc.txt NDFC chip select is 1, so it matches the example in ndfc.txt However driver probe routine is not called by the kernel, and NAND is not identified. What am I missing ? The same driver (backported) works for me on custom 460EX board with u-boot-1.3.4 and linux-2.6.28 Thanks a lot in advance. Felix. -- View this message in context: http://www.nabble.com/ndfc-driver-on-Kilauea-board-tp21851244p21851244.html Sent from the linuxppc-dev mailing list archive at Nabble.com. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
next 2009 Feb 5 build break:arch/powerpc/kernel/built-in.o
Hi Stephen, Next 20090205 build fails with following error: ld: arch/powerpc/kernel/built-in.o section .text exceeds stub group size ld: arch/powerpc/kernel/head_64.o section .text exceeds stub group size arch/powerpc/kernel/built-in.o: In function `.of_pci_phb_probe': of_platform.c:(.devinit.text+0x104): undefined reference to `.pcibios_claim_one_bus' arch/powerpc/platforms/built-in.o: In function `.pcibios_add_pci_devices': (.text+0x9158): undefined reference to `.pcibios_finish_adding_to_bus' arch/powerpc/platforms/built-in.o: In function `.remove_phb_dynamic': (.text+0x93a8): undefined reference to `.pcibios_unmap_io_space' arch/powerpc/platforms/built-in.o: In function `.init_phb_dynamic': (.devinit.text+0x3d8): undefined reference to `.pcibios_finish_adding_to_bus' make: *** [.tmp_vmlinux1] Error 1 Config file attached. Thanks -Sachin -- - Sachin Sant IBM Linux Technology Center India Systems and Technology Labs Bangalore, India - # # Automatically generated make config: don't edit # Linux kernel version: 2.6.29-rc3 # Thu Feb 5 07:14:39 2009 # CONFIG_PPC64=y # # Processor support # CONFIG_POWER4_ONLY=y CONFIG_POWER4=y # CONFIG_TUNE_CELL is not set CONFIG_PPC_FPU=y CONFIG_ALTIVEC=y # CONFIG_VSX is not set CONFIG_PPC_STD_MMU=y CONFIG_PPC_STD_MMU_64=y CONFIG_PPC_MM_SLICES=y CONFIG_VIRT_CPU_ACCOUNTING=y CONFIG_SMP=y CONFIG_NR_CPUS=32 CONFIG_64BIT=y CONFIG_WORD_SIZE=64 CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_MMU=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_HARDIRQS=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_IRQ_PER_CPU=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_ILOG2_U32=y CONFIG_ARCH_HAS_ILOG2_U64=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_GPIO=y CONFIG_ARCH_NO_VIRT_TO_BUS=y CONFIG_PPC=y CONFIG_EARLY_PRINTK=y CONFIG_COMPAT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_PPC_OF=y CONFIG_OF=y CONFIG_PPC_UDBG_16550=y CONFIG_GENERIC_TBSYNC=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_DEFAULT_UIMAGE is not set # CONFIG_PPC_DCR_NATIVE is not set CONFIG_PPC_DCR_MMIO=y CONFIG_PPC_DCR=y CONFIG_PPC_OF_PLATFORM_PCI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # # CONFIG_EXPERIMENTAL is not set CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set # CONFIG_SWAP is not set CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # CONFIG_TASKSTATS is not set CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_TREE=y # # RCU Subsystem # CONFIG_CLASSIC_RCU=y # CONFIG_TREE_RCU is not set # CONFIG_PREEMPT_RCU is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_PREEMPT_RCU_TRACE is not set CONFIG_IKCONFIG=y # CONFIG_IKCONFIG_PROC is not set CONFIG_LOG_BUF_SHIFT=17 CONFIG_CGROUPS=y CONFIG_CGROUP_DEBUG=y CONFIG_CGROUP_NS=y CONFIG_CGROUP_FREEZER=y CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y # CONFIG_CGROUP_CPUACCT is not set # CONFIG_RESOURCE_COUNTERS is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=y CONFIG_RELAY=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_EXTRA_PASS=y # CONFIG_HOTPLUG is not set # CONFIG_PRINTK is not set CONFIG_BUG=y # CONFIG_ELF_CORE is not set CONFIG_PCSPKR_PLATFORM=y CONFIG_COMPAT_BRK=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y # CONFIG_TIMERFD is not set # CONFIG_EVENTFD is not set # CONFIG_SHMEM is not set CONFIG_AIO=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y # CONFIG_SLAB is not set # CONFIG_SLUB is not set CONFIG_SLQB=y # CONFIG_SLOB is not set # CONFIG_PROFILING is not set CONFIG_HAVE_OPROFILE=y CONFIG_KPROBES=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_HAVE_SYSCALL_WRAPPERS=y CONFIG_KRETPROBES=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_USE_GENERIC_SMP_HELPERS=y # CONFIG_SLOW_WORK is not set # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_FORCE_LOAD=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODVERSIONS is not set CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLOCK_COMPAT=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADL
[RFC] Error handling in *_add/find_bridges()
Hi! I have a minor question about the error handling in the various *_add/find_bridges functions, which are used to detect and initialize PHBs. AFAIK all of them return an error code that is never checked in the platform setup code (e.g. when there is no memory for the pci_controller struct). Shouldn't the kernel panic (BUG();), when it can't initialize the PHB for whatever reason and the platform depends on a working PCI bus? Thanks! regards, Gerhard -- Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [ANN] Introducing new "test" branch in powerpc.git tree
On Thu, Feb 05, 2009 at 03:01:33PM +1100, Benjamin Herrenschmidt wrote: >Hoy ! > >So I've been annoyed for some time by the way we do our preparation for >the next merge window. The "next" branch is defined as not being rebased >ever (well, as much as possible), which makes it impossible to just >stash things early in there and rebase if needed, which is a useful >exercise in the weeks leading to the merge window to be able to test >patches, fix them, etc... while keeping a good idea of what's planned to >go in. > >Thus I've created a "test" branch. I'll push it out later today with >various things pending. For pulls from sub-maintainers, I'll probably >merge into "next" quickly (ie. a day or two after hitting "test" just >enough time to find gross problems). That will allow me to be more >pro-active also at pulling things off the mailing list and sticking them >there even if some cosmetic changes have been requested to the patch as >I will have no issue rebasing it when the new patch comes in. I like this. So we have: test -> testing stuff next -> stuff that's been tested and is queued up for the next release merge -> fixes for the currently being worked on release Which begs the question of what master is for. So far, it's just been a mirror of next from what I can tell. Maybe it should just track Linus' tree? josh ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: ndfc driver on Kilauea board
Felix Radensky wrote:
>
> Hi,
>
> I'm trying to enable Linux ndfc driver on Kilauea (ppc405ex) board rev 1.2
> running
> u-boot v2009.01 and linux-2.6.29-rc3. I've enabled NDFC in kernel config
> and
> updated kilauea.dts as described in
> Documentation/powerpc/dts-bindings/4xx/ndfc.txt
> NDFC chip select is 1, so it matches the example in ndfc.txt
> However driver probe routine is not called by the kernel, and NAND is not
> identified. What am I missing ? The same driver (backported) works for me
> on custom 460EX board with u-boot-1.3.4 and linux-2.6.28
>
> Thanks a lot in advance.
>
> Felix.
>
U-boot on Kilauea ships with the following definitions:
fdt_addr=0xfc1e
net_nfs_fdt=tftp 20 ${bootfile};tftp ${fdt_addr} ${fdt_file};run nfsargs
addip addtty;bootm 20 - ${fdt_addr}
I was running net_nfs_fdt to download kernel and fdt from network, but in
reality
fdt stored on flash was used, which has no ndfc definitions. Now that I'm
using
a proper ftd, NAND is properly identified.
Sorry for the noise.
Felix.
--
View this message in context:
http://www.nabble.com/ndfc-driver-on-Kilauea-board-tp21851244p21852712.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Calling wait_event_interruptible_timeout() in I2C wait functions
On Thu, Feb 5, 2009 at 5:51 AM, Mark Brown wrote: > This is exactly the problem for users that caused Timur to run into this > - further up the stack we're trying to do cleanup that involves writing > via I2C but the I2C writes error out due to the signal. Well, there's not much discussion on this issue, so I'm going to make the change to an uninterruptible wait and see if it fixes my problem. If so, I'll post a patch for i2c-mpc.c and see how far I get. -- Timur Tabi Linux kernel developer at Freescale ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH 2/3] powerpc: Make it possible to safely select CONFIG_FRAME_POINTER
On Thu, Feb 05, 2009 at 04:30:23AM +0300, Anton Vorontsov wrote: [...] > > > > > Remove -fno-omit-frame-pointer flag from CFLAGS. > > > > > Remove -fno-omit-frame-pointer workarounds. > > > > > > > > But what about -pg -requires -fno-omit-frame-pointer ? > > > > > > I don't think it requires -fno-omit-frame-pointer. It is just > > > incompatible with -fomit-frame-pointer. > > > > From a quick test, you seem to be right. > > > > Now the question of course is whether -pg will internally trigger > > the bug for which we need the workaround tho... > > According to http://marc.info/?l=linux-kernel&m=121958694215835&w=4 > just removing -fno-omit-frame-pointer solved the problem. > > But I'll double check that on the actual hardware. Confirmed. Just -pg doesn't cause any ill effects (for the test I built kernel on a ppc32 board). While simply adding -fno-omit-frame-pointer caused this during bootup: ... Waiting for /dev to be fully populated... Unable to handle kernel paging request for data at address 0x0901 Faulting instruction address: 0xc00d9a4c Oops: Kernel access of bad area, sig: 11 [#1] MPC837x RDB Modules linked in: NIP: c00d9a4c LR: c00d9a34 CTR: c015ac7c REGS: cf197cd0 TRAP: 0300 Not tainted (2.6.29-rc3-45527-g727839a-dirty) MSR: 9032 CR: 44084228 XER: 2000 DAR: 0901, DSISR: 2200 TASK = cfa42a80[1140] 'udevd' THREAD: cf196000 GPR00: f000 cf197d80 cfa42a80 cf4213f0 c058e678 0003 cf42145a 7f7f7f7f GPR08: 012c c058 cf197d80 84084228 1002414c cf197e9c c058e7b4 GPR16: c058e678 fff4 c05b cf197dc0 cf197db8 cf197dc8 GPR24: c00e4e30 24084222 0001 0901 cf197e98 cf4213f0 cf197d80 NIP [c00d9a4c] do_lookup+0x7c/0xf8 LR [c00d9a34] do_lookup+0x64/0xf8 Call Trace: [cf197d80] [c00d9a34] do_lookup+0x64/0xf8 (unreliable) [cf197db0] [c00db73c] __link_path_walk+0x180/0xdc4 [cf197e30] [c00dc3d8] path_walk+0x58/0xe0 [cf197e60] [c00dc55c] do_path_lookup+0x8c/0x164 [cf197e90] [c00dd260] user_path_at+0x64/0xac [cf197f00] [c00d3760] sys_readlinkat+0x40/0xb4 [cf197f30] [c00d380c] sys_readlink+0x38/0x50 [cf197f40] [c0018040] ret_from_syscall+0x0/0x38 --- Exception: c01 at 0xfed4754 LR = 0x10006280 Instruction dump: 8009 2f80 419e0028 7fa4eb78 7c0903a6 4e800421 7c7b1b79 40810040 3800f000 7fc3f378 7f9e0040 419d0018 <935c> 7f83e378 93dc0004 4bfffcd1 ---[ end trace 4815c47675962320 ]--- FWIW, gcc version 4.2.0. -- Anton Vorontsov email: cbouatmai...@gmail.com irc://irc.freenode.net/bd2 ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [ANN] Introducing new "test" branch in powerpc.git tree
On Thu, Feb 5, 2009 at 2:45 AM, Wolfram Sang wrote: > On Wed, Feb 04, 2009 at 09:20:04PM -0700, Grant Likely wrote: > >> what to do with it. The only difference is that mine isn't usually >> public. If people want to see it, then I push it out, but otherwise I >> just wait until I've got a real pull request. > > I'd like to see that tree public, so I can check anytime if you already > have picked up a patch or if it has been overlooked... Sure, I can push it out. It will be a little haphazard though. I maintain it using stacked git, so not all the things that I have in the stack are actually applied at any given time, but I will try to keep it up to date as I pick things up. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [ANN] Introducing new "test" branch in powerpc.git tree
> Sure, I can push it out. It will be a little haphazard though. I > maintain it using stacked git, so not all the things that I have in > the stack are actually applied at any given time, but I will try to > keep it up to date as I pick things up. Cool, thanks, this will do! -- Pengutronix e.K. | Wolfram Sang| Industrial Linux Solutions | http://www.pengutronix.de/ | signature.asc Description: Digital signature ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH 1/3] powerpc: bare minimum checkpoint/restart implementation
Quoting Benjamin Herrenschmidt (b...@kernel.crashing.org): > On Wed, 2009-02-04 at 18:44 -0500, Oren Laadan wrote: > > * Anything that is decided at compiled time should probably go to the arch- > > dependent header. > > > > * Anything that can change at boot time (e.g., for x86 that would include > > the capabilities of the FPU), or even run time (is there any ?) should > > be described to the letter (in fine print) in 'struct cr_hdr_cpu' and > > friends. > > I think we should avoid compile time completely. > > We mostly try to have kernels running on everything anyway, and there's > no reason not to be able to move a snapshot to a different CPU if it's > not using a feature of the CPU that is different. Absolutely, but the accepted way to handle that so far is that if you want to run an "incompatible" checkpoint image on a new cpu, a userspace program will rewrite the image to be correct for the target cpu. But what you list below seems more usable than trying to encapsulate that info in some hokey version number system. > Nathan, what about you start the structure with a 64 bit bitmask that > indicates what "records" are present followed by concatenated records ? > > IE. The "main" state (pt_regs) wouldn't change, but then, you could have > a list of things: > > - FPRs > - old style VSX > - VSRs > - Freescale SPE state > - DABR > - BookE IAC/DACs > - tbd... > > Then, when resuming a snapshot, we can use some bit masks trickery > indicating the validity on a given target. IE. If CPU has no VSX and > original program uses VSX then you can't resume. But if CPU has VSR you > can.. etc... We can keep it trivial at fist, especting the same > features, and try to be smart later. > > Ben. > ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: MPC5200 PCI Issues
On Thu, Feb 5, 2009 at 12:06 AM, Tobias Knutsson
wrote:
> When enabling the debug-printouts, it came to me that I forgot to
> mention something kind of important. Using the standard mpc52xx_pci.c,
> even the memory resources are mapped to zero.
>
> After disabling this code block, the memory regions are mapped out
> fine (but still no IO):
Reenable this code, enable debug in arch/powerpc/kernel/pci-common.c,
and post the results.
When this code is disabled then you're just getting the leftovers from
U-Boot's scan of the PCI bus. For MPC5200 support Linux does its own
scan and its own allocation of memory/IO address space and this code
is needed to make sure that happens.
g.
>
> static void
> mpc52xx_pci_fixup_resources(struct pci_dev *dev)
> {
>int i;
>
>pr_debug("mpc52xx_pci_fixup_resources() %.4x:%.4x\n",
> dev->vendor, dev->device);
>
>/* We don't rely on boot loader for PCI and resets all
> devices */
>for (i = 0; i < DEVICE_COUNT_RESOURCE; i++) {
>struct resource *res = &dev->resource[i];
>if (res->end > res->start) {/* Only valid resources */
>res->end -= res->start;
>res->start = 0;
>res->flags |= IORESOURCE_UNSET;
>}
>}
>
> What is the purpose of this code? Since all resources are reset here,
> where are they inteded to be re-allocated?
>
> Here is the bootlog with the aforementioned code enabled:
>
>
> reading cuImage.lite5200b
>
> 1833699 bytes read
> ## Booting kernel from Legacy Image at 00201400 ...
> Image Name: Linux-2.6.28
> Created: 2009-02-05 6:54:20 UTC
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size:1833635 Bytes = 1.7 MB
> Load Address: 0040
> Entry Point: 004005a0
> Verifying Checksum ... OK
> Uncompressing Kernel Image ... OK
> [0.00] Using lite5200 machine description
> [0.00] Linux version 2.6.28 (tknuts...@ztn-ubuntu) (gcc
> version 4.3.2 (Sourcery G++ Lite 4.3-50) ) #66 Thu Feb 5 07:51:46 CET
> 2009
> [0.00] Adding MPC52xx PCI host bridge /p...@fd00
> [0.00] PCI host bridge /p...@fd00 (primary) ranges:
> [0.00] MEM 0x5000..0x5fff ->
> 0x5000
> [0.00] IO 0x6000..0x60ff ->
> 0x
> [0.00] mpc52xx_pci_setup(hose=c03ec000, pci_regs=fdffad00)
> [0.00] mem_resource[0] = {.start=5000, .end=5fff, .flags=200}
> [0.00] .io_resource={.start=0,.end=ff,.flags=100}
> .io_base_phys=0x6000
> [0.00] Zone PFN ranges:
> [0.00] DMA 0x -> 0x4000
> [0.00] Normal 0x4000 -> 0x4000
> [0.00] Movable zone start PFN for each node
> [0.00] early_node_map[1] active PFN ranges
> [0.00] 0: 0x -> 0x4000
> [0.00] Built 1 zonelists in Zone order, mobility grouping on.
> Total pages: 16256
> [0.00] Kernel command line: console=ttyPSC0,115200 root=/dev/sda2 rw
> [0.00] MPC52xx PIC is up and running!
> [0.00] PID hash table entries: 256 (order: 8, 1024 bytes)
> [0.00] clocksource: timebase mult[7d0] shift[22] registered
> [0.000263] console [ttyPSC0] enabled
> [0.121690] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
> [0.129012] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
> [0.147433] Memory: 60844k/65536k available (3704k kernel code,
> 4624k reserved, 156k data, 117k bss, 180k init)
> [0.157672] SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0,
> CPUs=1, Nodes=1
> [0.165373] Calibrating delay loop... 63.87 BogoMIPS (lpj=127744)
> [0.236265] Mount-cache hash table entries: 512
> [0.245719] net_namespace: 288 bytes
> [0.250237] NET: Registered protocol family 16
> [0.284887] PCI: Probing PCI hardware
> [0.289670] mpc52xx_pci_fixup_resources() 1057:5809
> [0.294799] PCI::00:17.0 Resource 0
> 5040-507f [21208] fixup...
> [0.303180] PCI::00:17.05040-507f
> [0.309998] PCI::00:17.0 Resource 1
> 5080-50ff [20200] fixup...
> [0.318262] PCI::00:17.05080-50ff
> [0.325062] PCI::00:17.0 Resource 2
> 6000-600f [20101] fixup...
> [0.26] PCI::00:17.06000-600f
> [0.340124] mpc52xx_pci_fixup_resources() 104c:9065
> [0.345242] PCI::00:18.0 Resource 0
> 5100-513f [21208] fixup...
> [0.353519] PCI::00:18.05100-513f
> [0.360319] PCI::00:18.0 Resource 1
> 5180-51ff [20200] fixup...
> [0.368583] PCI::00:18.05180-51ff
FSL eSDHC bindings update
On Thu, Jan 22, 2009 at 01:15:01PM -0600, Kumar Gala wrote: > On Jan 21, 2009, at 8:00 PM, Anton Vorontsov wrote: >> This patch adds a new driver: sdhci-of. The driver is similar to >> the sdhci-pci, it contains common probe code, and controller-specific >> ops and quirks. >> >> So far there are only Freescale eSDHC ops and quirks. >> >> Signed-off-by: Anton Vorontsov >> --- >> drivers/mmc/host/Kconfig| 10 ++ >> drivers/mmc/host/Makefile |1 + >> drivers/mmc/host/sdhci-of.c | 274 ++ >> + >> 3 files changed, 285 insertions(+), 0 deletions(-) >> create mode 100644 drivers/mmc/host/sdhci-of.c > > Still griping about lack of OF binding docs for this. Here they're. I'm assuming that MPC8536 is the first chip in 85xx family with eSDHC. Thanks, -- Anton Vorontsov email: cbouatmai...@gmail.com irc://irc.freenode.net/bd2 ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
[PATCH 1/3] powerpc: Document FSL eSDHC bindings
This patch documents OF bindings for the Freescale Enhanced Secure
Digital Host Controller.
Signed-off-by: Anton Vorontsov
---
Documentation/powerpc/dts-bindings/fsl/esdhc.txt | 24 ++
1 files changed, 24 insertions(+), 0 deletions(-)
create mode 100644 Documentation/powerpc/dts-bindings/fsl/esdhc.txt
diff --git a/Documentation/powerpc/dts-bindings/fsl/esdhc.txt
b/Documentation/powerpc/dts-bindings/fsl/esdhc.txt
new file mode 100644
index 000..6008465
--- /dev/null
+++ b/Documentation/powerpc/dts-bindings/fsl/esdhc.txt
@@ -0,0 +1,24 @@
+* Freescale Enhanced Secure Digital Host Controller (eSDHC)
+
+The Enhanced Secure Digital Host Controller provides an interface
+for MMC, SD, and SDIO types of memory cards.
+
+Required properties:
+ - compatible : should be
+"fsl,-esdhc", "fsl,mpc8379-esdhc" for MPC83xx processors.
+"fsl,-esdhc", "fsl,mpc8536-esdhc" for MPC85xx processors.
+ - reg : should contain eSDHC registers location and length.
+ - interrupts : should contain eSDHC interrupt.
+ - interrupt-parent : interrupt source phandle.
+ - clock-frequency : specifies eSDHC base clock frequency.
+
+Example:
+
+sd...@2e000 {
+ compatible = "fsl,mpc8378-esdhc", "fsl,mpc8379-esdhc";
+ reg = <0x2e000 0x1000>;
+ interrupts = <42 0x8>;
+ interrupt-parent = <&ipic>;
+ /* Filled in by U-Boot */
+ clock-frequency = <0>;
+};
--
1.5.6.5
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
[PATCH 2/3] powerpc/83xx: Convert existing sdhc nodes to new bindings
- sdhc node renamed to sdhci ("sdhc" name is confusing since SDHC is
used to name Secure Digital High Capacity cards, while SDHCI is an
interface).
- Get rid of "fsl,esdhc" compatible entry, it's replaced by the
"fsl,-esdhc" scheme;
- Get rid of `model' property.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/boot/dts/mpc8377_mds.dts |7 ---
arch/powerpc/boot/dts/mpc8378_mds.dts |7 ---
arch/powerpc/boot/dts/mpc8379_mds.dts |7 ---
3 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/boot/dts/mpc8377_mds.dts
b/arch/powerpc/boot/dts/mpc8377_mds.dts
index a519e85..3e3ec8f 100644
--- a/arch/powerpc/boot/dts/mpc8377_mds.dts
+++ b/arch/powerpc/boot/dts/mpc8377_mds.dts
@@ -313,12 +313,13 @@
fsl,descriptor-types-mask = <0x3ab0ebf>;
};
- s...@2e000 {
- model = "eSDHC";
- compatible = "fsl,esdhc";
+ sd...@2e000 {
+ compatible = "fsl,mpc8377-esdhc", "fsl,mpc8379-esdhc";
reg = <0x2e000 0x1000>;
interrupts = <42 0x8>;
interrupt-parent = <&ipic>;
+ /* Filled in by U-Boot */
+ clock-frequency = <0>;
};
s...@18000 {
diff --git a/arch/powerpc/boot/dts/mpc8378_mds.dts
b/arch/powerpc/boot/dts/mpc8378_mds.dts
index 6bbee49..c3b212c 100644
--- a/arch/powerpc/boot/dts/mpc8378_mds.dts
+++ b/arch/powerpc/boot/dts/mpc8378_mds.dts
@@ -313,12 +313,13 @@
fsl,descriptor-types-mask = <0x3ab0ebf>;
};
- s...@2e000 {
- model = "eSDHC";
- compatible = "fsl,esdhc";
+ sd...@2e000 {
+ compatible = "fsl,mpc8378-esdhc", "fsl,mpc8379-esdhc";
reg = <0x2e000 0x1000>;
interrupts = <42 0x8>;
interrupt-parent = <&ipic>;
+ /* Filled in by U-Boot */
+ clock-frequency = <0>;
};
/* IPIC
diff --git a/arch/powerpc/boot/dts/mpc8379_mds.dts
b/arch/powerpc/boot/dts/mpc8379_mds.dts
index acf06c4..1b61cda 100644
--- a/arch/powerpc/boot/dts/mpc8379_mds.dts
+++ b/arch/powerpc/boot/dts/mpc8379_mds.dts
@@ -310,12 +310,13 @@
fsl,descriptor-types-mask = <0x3ab0ebf>;
};
- s...@2e000 {
- model = "eSDHC";
- compatible = "fsl,esdhc";
+ sd...@2e000 {
+ compatible = "fsl,mpc8379-esdhc";
reg = <0x2e000 0x1000>;
interrupts = <42 0x8>;
interrupt-parent = <&ipic>;
+ /* Filled in by U-Boot */
+ clock-frequency = <0>;
};
s...@18000 {
--
1.5.6.5
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
[PATCH 3/3] powerpc/83xx: Add FSL eSDHC support for MPC837x-RDB boards
Simply add appropriate sdhci nodes.
Note that U-Boot should configure pin multiplexing for eSDHC prior
to Linux could use it. U-Boot should also fill-in the clock-frequency
property (eSDHC clock depends on board-specific SCCR[ESDHCCM] bits).
Signed-off-by: Anton Vorontsov
---
arch/powerpc/boot/dts/mpc8377_rdb.dts |9 +
arch/powerpc/boot/dts/mpc8378_rdb.dts |9 +
arch/powerpc/boot/dts/mpc8379_rdb.dts |9 +
3 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/boot/dts/mpc8377_rdb.dts
b/arch/powerpc/boot/dts/mpc8377_rdb.dts
index b4ab3d0..6f4d614 100644
--- a/arch/powerpc/boot/dts/mpc8377_rdb.dts
+++ b/arch/powerpc/boot/dts/mpc8377_rdb.dts
@@ -291,6 +291,15 @@
fsl,descriptor-types-mask = <0x3ab0ebf>;
};
+ sd...@2e000 {
+ compatible = "fsl,mpc8377-esdhc", "fsl,mpc8379-esdhc";
+ reg = <0x2e000 0x1000>;
+ interrupts = <42 0x8>;
+ interrupt-parent = <&ipic>;
+ /* Filled in by U-Boot */
+ clock-frequency = <0>;
+ };
+
s...@18000 {
compatible = "fsl,mpc8377-sata", "fsl,pq-sata";
reg = <0x18000 0x1000>;
diff --git a/arch/powerpc/boot/dts/mpc8378_rdb.dts
b/arch/powerpc/boot/dts/mpc8378_rdb.dts
index 1b05fb0..6457ef1 100644
--- a/arch/powerpc/boot/dts/mpc8378_rdb.dts
+++ b/arch/powerpc/boot/dts/mpc8378_rdb.dts
@@ -289,6 +289,15 @@
fsl,descriptor-types-mask = <0x3ab0ebf>;
};
+ sd...@2e000 {
+ compatible = "fsl,mpc8378-esdhc", "fsl,mpc8379-esdhc";
+ reg = <0x2e000 0x1000>;
+ interrupts = <42 0x8>;
+ interrupt-parent = <&ipic>;
+ /* Filled in by U-Boot */
+ clock-frequency = <0>;
+ };
+
/* IPIC
* interrupts cell =
* sense values match linux IORESOURCE_IRQ_* defines:
diff --git a/arch/powerpc/boot/dts/mpc8379_rdb.dts
b/arch/powerpc/boot/dts/mpc8379_rdb.dts
index 72cdc3c..203fff2 100644
--- a/arch/powerpc/boot/dts/mpc8379_rdb.dts
+++ b/arch/powerpc/boot/dts/mpc8379_rdb.dts
@@ -288,6 +288,15 @@
fsl,descriptor-types-mask = <0x3ab0ebf>;
};
+ sd...@2e000 {
+ compatible = "fsl,mpc8379-esdhc";
+ reg = <0x2e000 0x1000>;
+ interrupts = <42 0x8>;
+ interrupt-parent = <&ipic>;
+ /* Filled in by U-Boot */
+ clock-frequency = <0>;
+ };
+
s...@18000 {
compatible = "fsl,mpc8379-sata", "fsl,pq-sata";
reg = <0x18000 0x1000>;
--
1.5.6.5
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH] AMCC Crypto4xx Device Driver v6
Hi Herbert, Thanks for apply the patch. Somehow the new directory driver/crypto/amcc is missing from the tree. I can see everything else in the tree except the driver source code. Do you want me to submit a new patch, or you can fix it with the V6 patch. Thanks James On Thu, 2009-02-05 at 16:18 +1100, Herbert Xu wrote: > On Wed, Jan 28, 2009 at 02:53:05PM -0800, James Hsiao wrote: > > This patch adds support for AMCC ppc4xx security device driver. This is the > > initial release that includes the driver framework with AES and SHA1 > > algorithms > > support. > > The remaining algorithms will be released in the near future. > > > > Signed-off-by: James Hsiao > > Patch applied. Thanks James! ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: MPC5200 PCI Issues
Hi,
That is exactly what the bootlog shows. Debug output on in both
mpc52xx_pci.c and in pci-common.c. And the discussed code section
enabled.
Hälsningar / Regards
Tobias Knutsson
On 5 feb 2009, at 17.44, Grant Likely wrote:
On Thu, Feb 5, 2009 at 12:06 AM, Tobias Knutsson
wrote:
When enabling the debug-printouts, it came to me that I forgot to
mention something kind of important. Using the standard
mpc52xx_pci.c,
even the memory resources are mapped to zero.
After disabling this code block, the memory regions are mapped out
fine (but still no IO):
Reenable this code, enable debug in arch/powerpc/kernel/pci-common.c,
and post the results.
When this code is disabled then you're just getting the leftovers from
U-Boot's scan of the PCI bus. For MPC5200 support Linux does its own
scan and its own allocation of memory/IO address space and this code
is needed to make sure that happens.
g.
static void
mpc52xx_pci_fixup_resources(struct pci_dev *dev)
{
int i;
pr_debug("mpc52xx_pci_fixup_resources() %.4x:%.4x\n",
dev->vendor, dev->device);
/* We don't rely on boot loader for PCI and resets all
devices */
for (i = 0; i < DEVICE_COUNT_RESOURCE; i++) {
struct resource *res = &dev->resource[i];
if (res->end > res->start) {/* Only valid
resources */
res->end -= res->start;
res->start = 0;
res->flags |= IORESOURCE_UNSET;
}
}
What is the purpose of this code? Since all resources are reset here,
where are they inteded to be re-allocated?
Here is the bootlog with the aforementioned code enabled:
reading cuImage.lite5200b
1833699 bytes read
## Booting kernel from Legacy Image at 00201400 ...
Image Name: Linux-2.6.28
Created: 2009-02-05 6:54:20 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size:1833635 Bytes = 1.7 MB
Load Address: 0040
Entry Point: 004005a0
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
[0.00] Using lite5200 machine description
[0.00] Linux version 2.6.28 (tknuts...@ztn-ubuntu) (gcc
version 4.3.2 (Sourcery G++ Lite 4.3-50) ) #66 Thu Feb 5 07:51:46 CET
2009
[0.00] Adding MPC52xx PCI host bridge /p...@fd00
[0.00] PCI host bridge /p...@fd00 (primary) ranges:
[0.00] MEM 0x5000..0x5fff ->
0x5000
[0.00] IO 0x6000..0x60ff ->
0x
[0.00] mpc52xx_pci_setup(hose=c03ec000, pci_regs=fdffad00)
[0.00] mem_resource[0] =
{.start=5000, .end=5fff, .flags=200}
[0.00] .io_resource={.start=0,.end=ff,.flags=100}
.io_base_phys=0x6000
[0.00] Zone PFN ranges:
[0.00] DMA 0x -> 0x4000
[0.00] Normal 0x4000 -> 0x4000
[0.00] Movable zone start PFN for each node
[0.00] early_node_map[1] active PFN ranges
[0.00] 0: 0x -> 0x4000
[0.00] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 16256
[0.00] Kernel command line: console=ttyPSC0,115200 root=/
dev/sda2 rw
[0.00] MPC52xx PIC is up and running!
[0.00] PID hash table entries: 256 (order: 8, 1024 bytes)
[0.00] clocksource: timebase mult[7d0] shift[22]
registered
[0.000263] console [ttyPSC0] enabled
[0.121690] Dentry cache hash table entries: 8192 (order: 3,
32768 bytes)
[0.129012] Inode-cache hash table entries: 4096 (order: 2,
16384 bytes)
[0.147433] Memory: 60844k/65536k available (3704k kernel code,
4624k reserved, 156k data, 117k bss, 180k init)
[0.157672] SLUB: Genslabs=12, HWalign=32, Order=0-3,
MinObjects=0,
CPUs=1, Nodes=1
[0.165373] Calibrating delay loop... 63.87 BogoMIPS (lpj=127744)
[0.236265] Mount-cache hash table entries: 512
[0.245719] net_namespace: 288 bytes
[0.250237] NET: Registered protocol family 16
[0.284887] PCI: Probing PCI hardware
[0.289670] mpc52xx_pci_fixup_resources() 1057:5809
[0.294799] PCI::00:17.0 Resource 0
5040-507f [21208] fixup...
[0.303180] PCI::00:17.0
5040-507f
[0.309998] PCI::00:17.0 Resource 1
5080-50ff [20200] fixup...
[0.318262] PCI::00:17.0
5080-50ff
[0.325062] PCI::00:17.0 Resource 2
6000-600f [20101] fixup...
[0.26] PCI::00:17.0
6000-600f
[0.340124] mpc52xx_pci_fixup_resources() 104c:9065
[0.345242] PCI::00:18.0 Resource 0
5100-513f [21208] fixup...
[0.353519] PCI::00:18.0
5100-513f
[0.360319] PCI::00:18.0 Resource 1
5180-51ff [20200] fixup...
[0.3
[PATCH 1/2] powerpc/83xx: Fix missing #{address,size}-cells in mpc8313erdb.dts
commit b31a1d8b41513b96e9c7ec2f68c5734cef0b26a4 ("gianfar: Convert
gianfar to an of_platform_driver") introduced a child node for
the ether...@25000 controller, but no address and size cells
specifiers were added, and that makes dtc unhappy:
DTC: dts->dtb on file "arch/powerpc/boot/dts/mpc8313erdb.dts"
Warning (reg_format): "reg" property in
/soc8...@e000/ether...@25000/m...@25520 has invalid length (8 bytes)
(#address-cells == 2, #size-cells == 1)
Warning (avoid_default_addr_size): Relying on default #address-cells value for
/soc8...@e000/ether...@25000/m...@25520
Warning (avoid_default_addr_size): Relying on default #size-cells value for
/soc8...@e000/ether...@25000/m...@25520
Signed-off-by: Anton Vorontsov
---
arch/powerpc/boot/dts/mpc8313erdb.dts |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/boot/dts/mpc8313erdb.dts
b/arch/powerpc/boot/dts/mpc8313erdb.dts
index 909a89c..3f84cd0 100644
--- a/arch/powerpc/boot/dts/mpc8313erdb.dts
+++ b/arch/powerpc/boot/dts/mpc8313erdb.dts
@@ -219,6 +219,8 @@
};
enet1: ether...@25000 {
+ #address-cells = <1>;
+ #size-cells = <1>;
cell-index = <1>;
device_type = "network";
model = "eTSEC";
--
1.5.6.5
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
[PATCH 2/2] powerpc/83xx: Fix TSEC0 workability on MPC8313E-RDB boards
TSEC0 is connected to Vitesse 7385 5-port switch. The switch
isn't connected to any mdio bus, the link to the switch is fixed
to Full-duplex 1000 Mb/s (no pause).
This patch fixes following failure during bootup:
m...@24520:01 not found
eth0: Could not attach to PHY
IP-Config: Failed to open eth0
Signed-off-by: Anton Vorontsov
---
arch/powerpc/boot/dts/mpc8313erdb.dts |9 ++---
arch/powerpc/configs/83xx/mpc8313_rdb_defconfig |2 +-
2 files changed, 3 insertions(+), 8 deletions(-)
diff --git a/arch/powerpc/boot/dts/mpc8313erdb.dts
b/arch/powerpc/boot/dts/mpc8313erdb.dts
index 3f84cd0..3ebf7ec 100644
--- a/arch/powerpc/boot/dts/mpc8313erdb.dts
+++ b/arch/powerpc/boot/dts/mpc8313erdb.dts
@@ -191,7 +191,8 @@
interrupts = <37 0x8 36 0x8 35 0x8>;
interrupt-parent = <&ipic>;
tbi-handle = < &tbi0 >;
- phy-handle = < &phy1 >;
+ /* Vitesse 7385 isn't on the MDIO bus */
+ fixed-link = <1 1 1000 0 0>;
fsl,magic-packet;
m...@24520 {
@@ -199,12 +200,6 @@
#size-cells = <0>;
compatible = "fsl,gianfar-mdio";
reg = <0x24520 0x20>;
- phy1: ethernet-...@1 {
- interrupt-parent = <&ipic>;
- interrupts = <19 0x8>;
- reg = <0x1>;
- device_type = "ethernet-phy";
- };
phy4: ethernet-...@4 {
interrupt-parent = <&ipic>;
interrupts = <20 0x8>;
diff --git a/arch/powerpc/configs/83xx/mpc8313_rdb_defconfig
b/arch/powerpc/configs/83xx/mpc8313_rdb_defconfig
index 9e47ae9..409d017 100644
--- a/arch/powerpc/configs/83xx/mpc8313_rdb_defconfig
+++ b/arch/powerpc/configs/83xx/mpc8313_rdb_defconfig
@@ -651,7 +651,7 @@ CONFIG_CICADA_PHY=y
# CONFIG_NATIONAL_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_LSI_ET1011C_PHY is not set
-# CONFIG_FIXED_PHY is not set
+CONFIG_FIXED_PHY=y
# CONFIG_MDIO_BITBANG is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
--
1.5.6.5
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [ANN] Introducing new "test" branch in powerpc.git tree
> Which begs the question of what master is for. So far, it's just been > a mirror of next from what I can tell. Maybe it should just track > Linus' tree? I've been wondering myself what to do with it ... I may just leave it to track linus indeed. Or maybe just delete it. Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [ANN] Introducing new "test" branch in powerpc.git tree
On Fri, Feb 06, 2009 at 07:56:22AM +1100, Benjamin Herrenschmidt wrote: > >> Which begs the question of what master is for. So far, it's just been >> a mirror of next from what I can tell. Maybe it should just track >> Linus' tree? > >I've been wondering myself what to do with it ... I may just leave it to >track linus indeed. Or maybe just delete it. I don't think you can delete it without hosing people who try to clone it. josh ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH 1/3] powerpc: bare minimum checkpoint/restart implementation
> Absolutely, but the accepted way to handle that so far is that if > you want to run an "incompatible" checkpoint image on a new cpu, > a userspace program will rewrite the image to be correct for the target > cpu. That doesn't sound nice and definitely not something we want to do on PowerPC. There are lots of reasons for that including the fact that the actual feature set may depend on what the FW enabled which itself can depend on the kernel version .. or not, etc etc... I'd rather keep all that logic in the kernel to be honest. > But what you list below seems more usable than trying to encapsulate > that info in some hokey version number system. There are things however that I can't expose and for which we can't do much about. IE. The kernel exposes some features to userspace, such as the PowerPC ISA level supported, the presence of some optional instructions, etc... We don't know whether the user space program is using that stuff though... ie, we could get into situations where userspace is trying to use, let's say, 44x MAC instructions, and thus that program will fail to resume on some other processor, and we have no way to know about it from the kernel. But I'll leave that problem for later... Maybe we should implement some way, using personalities or something similar, to run programs so that they see a limited set of CPU features, for people who explicitely want them to be migrateable.. a bit similar to what our Hypervisor does if you want a partition to be migrateable between different processors, it only advertises the common subset of functionality. Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH] AMCC Crypto4xx Device Driver v6
On Thu, Feb 05, 2009 at 11:47:48AM -0800, James Hsiao wrote:
>
> Thanks for apply the patch.
> Somehow the new directory driver/crypto/amcc is missing from the tree.
> I can see everything else in the tree except the driver source code.
> Do you want me to submit a new patch, or you can fix it with the V6
> patch.
I'll fix it up.
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~}
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH] AMCC Crypto4xx Device Driver v6
Thanks allot! James On Fri, 2009-02-06 at 08:30 +1100, Herbert Xu wrote: > On Thu, Feb 05, 2009 at 11:47:48AM -0800, James Hsiao wrote: > > > > Thanks for apply the patch. > > Somehow the new directory driver/crypto/amcc is missing from the tree. > > I can see everything else in the tree except the driver source code. > > Do you want me to submit a new patch, or you can fix it with the V6 > > patch. > > I'll fix it up. > > Thanks, ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
[PATCH 1/1 v4] AMCC PPC 460SX redwood SoC platform initial framework
From: Madhulika Madishetty
This patch contains initial framework for the AMCC Redwood board.
Signed-off-by: Madhulika Madishetty
Signed-off-by: Tirumala Marri
Signed-off-by: Feng Kan
Signed-off-by: Vidhyananth Venkatasamy
Signed-off-by: Preetesh Parekh
Acked-by: Loc Ho
Acked-by: Feng Kan
---
arch/powerpc/boot/dts/redwood.dts | 244 ++
arch/powerpc/configs/44x/redwood_defconfig | 1176
arch/powerpc/kernel/cpu_setup_44x.S|1 +
arch/powerpc/kernel/cputable.c | 14 +
arch/powerpc/platforms/44x/Kconfig | 19 +
arch/powerpc/platforms/44x/ppc44x_simple.c |1 +
6 files changed, 1455 insertions(+), 0 deletions(-)
create mode 100644 arch/powerpc/boot/dts/redwood.dts
create mode 100644 arch/powerpc/configs/44x/redwood_defconfig
diff --git a/arch/powerpc/boot/dts/redwood.dts
b/arch/powerpc/boot/dts/redwood.dts
new file mode 100644
index 000..ad402c4
--- /dev/null
+++ b/arch/powerpc/boot/dts/redwood.dts
@@ -0,0 +1,244 @@
+/*
+ * Device Tree Source for AMCC Redwood(460SX)
+ *
+ * Copyright 2008 AMCC
+ *
+ * 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.
+ */
+
+/dts-v1/;
+
+/ {
+ #address-cells = <2>;
+ #size-cells = <1>;
+ model = "amcc,redwood";
+ compatible = "amcc,redwood";
+ dcr-parent = <&{/cpus/c...@0}>;
+
+ aliases {
+ ethernet0 = &EMAC0;
+ serial0 = &UART0;
+ };
+
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ c...@0 {
+ device_type = "cpu";
+ model = "PowerPC,460SX";
+ reg = <0x>;
+ clock-frequency = <0>; /* Filled in by U-Boot */
+ timebase-frequency = <0>; /* Filled in by U-Boot */
+ i-cache-line-size = <32>;
+ d-cache-line-size = <32>;
+ i-cache-size = <32768>;
+ d-cache-size = <32768>;
+ dcr-controller;
+ dcr-access-method = "native";
+ };
+ };
+
+ memory {
+ device_type = "memory";
+ reg = <0x 0x 0x>; /* Filled in by
U-Boot */
+ };
+
+ UIC0: interrupt-controller0 {
+ compatible = "ibm,uic-460sx","ibm,uic";
+ interrupt-controller;
+ cell-index = <0>;
+ dcr-reg = <0x0c0 0x009>;
+ #address-cells = <0>;
+ #size-cells = <0>;
+ #interrupt-cells = <2>;
+ };
+
+ UIC1: interrupt-controller1 {
+ compatible = "ibm,uic-460sx","ibm,uic";
+ interrupt-controller;
+ cell-index = <1>;
+ dcr-reg = <0x0d0 0x009>;
+ #address-cells = <0>;
+ #size-cells = <0>;
+ #interrupt-cells = <2>;
+ interrupts = <0x1e 0x4 0x1f 0x4>; /* cascade */
+ interrupt-parent = <&UIC0>;
+ };
+
+ UIC2: interrupt-controller2 {
+ compatible = "ibm,uic-460sx","ibm,uic";
+ interrupt-controller;
+ cell-index = <2>;
+ dcr-reg = <0x0e0 0x009>;
+ #address-cells = <0>;
+ #size-cells = <0>;
+ #interrupt-cells = <2>;
+ interrupts = <0xa 0x4 0xb 0x4>; /* cascade */
+ interrupt-parent = <&UIC0>;
+ };
+
+ UIC3: interrupt-controller3 {
+ compatible = "ibm,uic-460sx","ibm,uic";
+ interrupt-controller;
+ cell-index = <3>;
+ dcr-reg = <0x0f0 0x009>;
+ #address-cells = <0>;
+ #size-cells = <0>;
+ #interrupt-cells = <2>;
+ interrupts = <0x10 0x4 0x11 0x4>; /* cascade */
+ interrupt-parent = <&UIC0>;
+ };
+
+ SDR0: sdr {
+ compatible = "ibm,sdr-460sx";
+ dcr-reg = <0x00e 0x002>;
+ };
+
+ CPR0: cpr {
+ compatible = "ibm,cpr-460sx";
+ dcr-reg = <0x00c 0x002>;
+ };
+
+ plb {
+ compatible = "ibm,plb-460sx", "ibm,plb4";
+ #address-cells = <2>;
+ #size-cells = <1>;
+ ranges;
+ clock-frequency = <0>; /* Filled in by U-Boot */
+
+ SDRAM0: sdram {
+ compatible = "ibm,sdram-460sx", "ibm,sdram-405gp";
+ dcr-reg = <0x010 0x002>;
+ };
+
+ MAL0: mcmal {
+ compatible = "ibm,mcmal-460sx", "ibm,mcmal2";
+ dcr-reg = <0x180 0x62>;
+ num-tx-chans = <4>;
+ num-
linux2.6.23-rc2 enable APU for ppc405
Anybody can help? Thanks a lot! Hi, I am now using impulse c and xilinx virtex4 ml403 board to do a project. And I want to run the application through APU in the linux environment. So I need to enable the apu for the linux 2.6.23-rc kernel. Then use cross compiler(crosstool-0.43) to make zImage. Does anybody have patch for linux 2.6 to enable apu/fpu? Or any guide for this? I am a new guy in this field, hope can get help! Thanks very much! Best regards, Li Jun ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Html attachments
Hi all, I have reconfigured the list to hold any emails with html attachments for moderator approval. So if you don't want your mail to be delayed, do not post html mail to this list. Thanks. -- Cheers, Stephen Rothwells...@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ pgpTgs56mcyNW.pgp Description: PGP signature ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Build breakage for CONFIG_PM but no CONFIG_SUSPEND
I noticed this doing some randconfig testing (.config below). I have
CONFIG_PM but no CONFIG_SUSPEND. Bug is against mainline.
arch/powerpc/sysdev/built-in.o: In function `ipic_suspend':
ipic.c:(.text+0x6b34): undefined reference to `fsl_deep_sleep'
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [sub-make] Error 2
Looks like #ifdef CONFIG_PM in arch/powerpc/sysdev/ipic.c should be
CONFIG_SUSPEND. d49747bdfb2ddebea24d1580da55b79d093d48a9 introduced
this.
Maybe this fixes it?
Fix build when we have CONFIG_PM but no CONFIG_SUSPEND.
Signed-off-by: Michael Neuling
---
arch/powerpc/sysdev/ipic.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/sysdev/ipic.c b/arch/powerpc/sysdev/ipic.c
index 88a983e..9a89cd3 100644
--- a/arch/powerpc/sysdev/ipic.c
+++ b/arch/powerpc/sysdev/ipic.c
@@ -890,7 +890,7 @@ unsigned int ipic_get_irq(void)
return irq_linear_revmap(primary_ipic->irqhost, irq);
}
-#ifdef CONFIG_PM
+#ifdef CONFIG_SUSPEND
static struct {
u32 sicfr;
u32 siprr[2];
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.29-rc3
# Fri Feb 6 10:32:48 2009
#
# CONFIG_PPC64 is not set
#
# Processor support
#
CONFIG_6xx=y
# CONFIG_PPC_85xx is not set
# CONFIG_PPC_8xx is not set
# CONFIG_40x is not set
# CONFIG_44x is not set
# CONFIG_E200 is not set
CONFIG_PPC_FPU=y
# CONFIG_FSL_EMB_PERFMON is not set
CONFIG_ALTIVEC=y
CONFIG_PPC_STD_MMU=y
CONFIG_PPC_STD_MMU_32=y
# CONFIG_PPC_MM_SLICES is not set
CONFIG_SMP=y
CONFIG_NR_CPUS=4
CONFIG_NOT_COHERENT_CACHE=y
CONFIG_PPC32=y
CONFIG_WORD_SIZE=32
# CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set
CONFIG_MMU=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_HARDIRQS=y
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
CONFIG_IRQ_PER_CPU=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_ILOG2_U32=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_GPIO=y
# CONFIG_ARCH_NO_VIRT_TO_BUS is not set
CONFIG_PPC=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_NVRAM=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_PPC_OF=y
CONFIG_OF=y
CONFIG_PPC_UDBG_16550=y
CONFIG_GENERIC_TBSYNC=y
CONFIG_AUDIT_ARCH=y
CONFIG_GENERIC_BUG=y
CONFIG_DEFAULT_UIMAGE=y
CONFIG_REDBOOT=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_PPC_DCR_NATIVE is not set
# CONFIG_PPC_DCR_MMIO is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
# CONFIG_SYSVIPC is not set
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
# CONFIG_TASK_DELAY_ACCT is not set
CONFIG_TASK_XACCT=y
# CONFIG_TASK_IO_ACCOUNTING is not set
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_TREE=y
#
# RCU Subsystem
#
CONFIG_CLASSIC_RCU=y
# CONFIG_TREE_RCU is not set
# CONFIG_PREEMPT_RCU is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_PREEMPT_RCU_TRACE is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=17
# CONFIG_GROUP_SCHED is not set
# CONFIG_CGROUPS is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_EMBEDDED=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
# CONFIG_PRINTK is not set
CONFIG_BUG=y
# CONFIG_ELF_CORE is not set
# CONFIG_PCSPKR_PLATFORM is not set
CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
# CONFIG_FUTEX is not set
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
# CONFIG_SIGNALFD is not set
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
# CONFIG_SLAB is not set
# CONFIG_SLUB is not set
CONFIG_SLQB=y
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
CONFIG_TRACEPOINTS=y
CONFIG_MARKERS=y
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_HAVE_CLK=y
CONFIG_SLOW_WORK=y
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_STOP_MACHINE=y
# CONFIG_BLOCK is not set
# CONFIG_FREEZER is not set
CONFIG_PPC_MSI_BITMAP=y
#
# Platform support
#
CONFIG_PPC_MULTIPLATFORM=y
CONFIG_CLASSIC32=y
CONFIG_PPC_CHRP=y
CONFIG_PPC_MPC512x=y
CONFIG_PPC_MPC5121=y
CONFIG_MPC5121_ADS=y
CONFIG_M
ftrace compile error with 32 bit PPC with mainline
I get the following compile error with ftrace with mainline with the attached config (made with randconfig) /home/mikey/src/linux-2.6-ozlabs/arch/powerpc/kernel/ftrace.c: In function ‘__ftrace_make_call’: /home/mikey/src/linux-2.6-ozlabs/arch/powerpc/kernel/ftrace.c:443: error: dereferencing pointer to incomplete type /home/mikey/src/linux-2.6-ozlabs/arch/powerpc/kernel/ftrace.c:443: error: dereferencing pointer to incomplete type /home/mikey/src/linux-2.6-ozlabs/arch/powerpc/kernel/ftrace.c:443: error: dereferencing pointer to incomplete type /home/mikey/src/linux-2.6-ozlabs/arch/powerpc/kernel/ftrace.c:450: error: dereferencing pointer to incomplete type Mikey # # Automatically generated make config: don't edit # Linux kernel version: 2.6.29-rc3 # Fri Feb 6 11:53:28 2009 # # CONFIG_PPC64 is not set # # Processor support # CONFIG_6xx=y # CONFIG_PPC_85xx is not set # CONFIG_PPC_8xx is not set # CONFIG_40x is not set # CONFIG_44x is not set # CONFIG_E200 is not set CONFIG_PPC_FPU=y CONFIG_FSL_EMB_PERFMON=y # CONFIG_ALTIVEC is not set CONFIG_PPC_STD_MMU=y CONFIG_PPC_STD_MMU_32=y # CONFIG_PPC_MM_SLICES is not set # CONFIG_SMP is not set CONFIG_NOT_COHERENT_CACHE=y CONFIG_PPC32=y CONFIG_WORD_SIZE=32 # CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set CONFIG_MMU=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_HARDIRQS=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set CONFIG_IRQ_PER_CPU=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_ILOG2_U32=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_GPIO=y # CONFIG_ARCH_NO_VIRT_TO_BUS is not set CONFIG_PPC=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_NVRAM=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_PPC_OF=y CONFIG_OF=y CONFIG_PPC_UDBG_16550=y # CONFIG_GENERIC_TBSYNC is not set CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y CONFIG_DEFAULT_UIMAGE=y CONFIG_REDBOOT=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_PPC_DCR_NATIVE is not set # CONFIG_PPC_DCR_MMIO is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y # CONFIG_SYSVIPC is not set CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # # RCU Subsystem # CONFIG_CLASSIC_RCU=y # CONFIG_TREE_RCU is not set # CONFIG_PREEMPT_RCU is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_PREEMPT_RCU_TRACE is not set CONFIG_IKCONFIG=y # CONFIG_IKCONFIG_PROC is not set CONFIG_LOG_BUF_SHIFT=17 CONFIG_GROUP_SCHED=y # CONFIG_FAIR_GROUP_SCHED is not set CONFIG_RT_GROUP_SCHED=y CONFIG_USER_SCHED=y # CONFIG_CGROUP_SCHED is not set CONFIG_CGROUPS=y CONFIG_CGROUP_DEBUG=y CONFIG_CGROUP_NS=y CONFIG_CGROUP_FREEZER=y # CONFIG_CGROUP_DEVICE is not set CONFIG_CGROUP_CPUACCT=y # CONFIG_RESOURCE_COUNTERS is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=y CONFIG_RELAY=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set # CONFIG_HOTPLUG is not set # CONFIG_PRINTK is not set CONFIG_BUG=y # CONFIG_ELF_CORE is not set # CONFIG_PCSPKR_PLATFORM is not set CONFIG_COMPAT_BRK=y # CONFIG_BASE_FULL is not set # CONFIG_FUTEX is not set CONFIG_ANON_INODES=y # CONFIG_EPOLL is not set CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y # CONFIG_SHMEM is not set CONFIG_AIO=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y CONFIG_MARKERS=y # CONFIG_OPROFILE is not set CONFIG_HAVE_OPROFILE=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_CLK=y # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_BASE_SMALL=1 # CONFIG_MODULES is not set # CONFIG_BLOCK is not set CONFIG_FREEZER=y CONFIG_PPC_MSI_BITMAP=y # # Platform support # CONFIG_PPC_MULTIPLATFORM=y CONFIG_CLASSIC32=y CONFIG_PPC_CHRP=y CONFIG_PPC_MPC512x=y CONFIG_PPC_MPC5121=y CONFIG_MPC5121_ADS=y CONFIG_MPC5121_GENERIC=y CONFIG_PPC_MPC52xx=y # CONFIG_PPC_MPC5200_SIMPLE is not set CONFIG_PPC_EFIKA=y # CONFIG_PPC_LITE5200 is not set CONFIG_PPC_MPC5200_BUGFIX=y CONFIG_PPC_MPC5200_GPIO=y # CONFIG_PPC_PMAC is not set # CONFIG_PPC_CELL is not set # CONFIG_PPC_CELL_NATIVE is not set # CONFIG_PPC_82xx is not set # CONFIG_PQ2ADS is not set CONFIG_PPC_83xx=y CONFIG_MPC831x_RDB=y # CONFIG_MPC832x_MDS is not set # CONFIG_MPC832x_RDB is not set CONFIG_MPC834x_MDS=y # CONFIG_MPC834x_ITX is not set CONFIG_MPC836x_MDS=y # CONFIG_MPC83
Re: ftrace compile error with 32 bit PPC with mainline
On Fri, 2009-02-06 at 13:37 +1100, Michael Neuling wrote: > # CONFIG_MODULES is not set Those are module references. I never tested with modules turned off. I'll write up a patch tonight. Thanks, -- Steve ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: FSL eSDHC bindings update
On Feb 5, 2009, at 1:04 PM, Anton Vorontsov wrote: On Thu, Jan 22, 2009 at 01:15:01PM -0600, Kumar Gala wrote: On Jan 21, 2009, at 8:00 PM, Anton Vorontsov wrote: This patch adds a new driver: sdhci-of. The driver is similar to the sdhci-pci, it contains common probe code, and controller- specific ops and quirks. So far there are only Freescale eSDHC ops and quirks. Signed-off-by: Anton Vorontsov --- drivers/mmc/host/Kconfig| 10 ++ drivers/mmc/host/Makefile |1 + drivers/mmc/host/sdhci-of.c | 274 ++ + 3 files changed, 285 insertions(+), 0 deletions(-) create mode 100644 drivers/mmc/host/sdhci-of.c Still griping about lack of OF binding docs for this. Here they're. I'm assuming that MPC8536 is the first chip in 85xx family with eSDHC. thanks. MPC8536 is the first. Do we need a u-boot patch for clock- frequency on 85xx? - k ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH 1/2] ftrace, powerpc: replace debug macro with proper pr_deug
[ forgot to add linuxppc ]
On Fri, 6 Feb 2009, Steven Rostedt wrote:
> From: Steven Rostedt
>
> Impact: cleanup
>
> The PowerPC ftrace code uses a hacked up DEBUGP macro for prints.
> This patch converts it to the standard pr_debug.
>
> Signed-off-by: Steven Rostedt
> ---
> arch/powerpc/kernel/ftrace.c | 26 ++
> 1 files changed, 10 insertions(+), 16 deletions(-)
>
> diff --git a/arch/powerpc/kernel/ftrace.c b/arch/powerpc/kernel/ftrace.c
> index 5355244..a913f91 100644
> --- a/arch/powerpc/kernel/ftrace.c
> +++ b/arch/powerpc/kernel/ftrace.c
> @@ -20,12 +20,6 @@
> #include
> #include
>
> -#if 0
> -#define DEBUGP printk
> -#else
> -#define DEBUGP(fmt , ...)do { } while (0)
> -#endif
> -
> static unsigned int ftrace_nop = PPC_NOP_INSTR;
>
> #ifdef CONFIG_PPC32
> @@ -175,7 +169,7 @@ __ftrace_make_nop(struct module *mod,
>* 0xe8, 0x4c, 0x00, 0x28,ld r2,40(r12)
>*/
>
> - DEBUGP("ip:%lx jumps to %lx r2: %lx", ip, tramp, mod->arch.toc);
> + pr_debug("ip:%lx jumps to %lx r2: %lx", ip, tramp, mod->arch.toc);
>
> /* Find where the trampoline jumps to */
> if (probe_kernel_read(jmp, (void *)tramp, sizeof(jmp))) {
> @@ -183,7 +177,7 @@ __ftrace_make_nop(struct module *mod,
> return -EFAULT;
> }
>
> - DEBUGP(" %08x %08x", jmp[0], jmp[1]);
> + pr_debug(" %08x %08x", jmp[0], jmp[1]);
>
> /* verify that this is what we expect it to be */
> if (((jmp[0] & 0x) != 0x3d82) ||
> @@ -198,18 +192,18 @@ __ftrace_make_nop(struct module *mod,
> offset = (unsigned)((unsigned short)jmp[0]) << 16 |
> (unsigned)((unsigned short)jmp[1]);
>
> - DEBUGP(" %x ", offset);
> + pr_debug(" %x ", offset);
>
> /* get the address this jumps too */
> tramp = mod->arch.toc + offset + 32;
> - DEBUGP("toc: %lx", tramp);
> + pr_debug("toc: %lx", tramp);
>
> if (probe_kernel_read(jmp, (void *)tramp, 8)) {
> printk(KERN_ERR "Failed to read %lx\n", tramp);
> return -EFAULT;
> }
>
> - DEBUGP(" %08x %08x\n", jmp[0], jmp[1]);
> + pr_debug(" %08x %08x\n", jmp[0], jmp[1]);
>
> ptr = ((unsigned long)jmp[0] << 32) + jmp[1];
>
> @@ -286,7 +280,7 @@ __ftrace_make_nop(struct module *mod,
>* 0x4e, 0x80, 0x04, 0x20 bctr
>*/
>
> - DEBUGP("ip:%lx jumps to %lx", ip, tramp);
> + pr_debug("ip:%lx jumps to %lx", ip, tramp);
>
> /* Find where the trampoline jumps to */
> if (probe_kernel_read(jmp, (void *)tramp, sizeof(jmp))) {
> @@ -294,7 +288,7 @@ __ftrace_make_nop(struct module *mod,
> return -EFAULT;
> }
>
> - DEBUGP(" %08x %08x ", jmp[0], jmp[1]);
> + pr_debug(" %08x %08x ", jmp[0], jmp[1]);
>
> /* verify that this is what we expect it to be */
> if (((jmp[0] & 0x) != 0x3d60) ||
> @@ -310,7 +304,7 @@ __ftrace_make_nop(struct module *mod,
> if (tramp & 0x8000)
> tramp -= 0x1;
>
> - DEBUGP(" %x ", tramp);
> + pr_debug(" %x ", tramp);
>
> if (tramp != addr) {
> printk(KERN_ERR
> @@ -413,7 +407,7 @@ __ftrace_make_call(struct dyn_ftrace *rec, unsigned long
> addr)
> /* ld r2,40(r1) */
> op[1] = 0xe8410028;
>
> - DEBUGP("write to %lx\n", rec->ip);
> + pr_debug("write to %lx\n", rec->ip);
>
> if (probe_kernel_write((void *)ip, op, MCOUNT_INSN_SIZE * 2))
> return -EPERM;
> @@ -453,7 +447,7 @@ __ftrace_make_call(struct dyn_ftrace *rec, unsigned long
> addr)
> return -EINVAL;
> }
>
> - DEBUGP("write to %lx\n", rec->ip);
> + pr_debug("write to %lx\n", rec->ip);
>
> if (probe_kernel_write((void *)ip, &op, MCOUNT_INSN_SIZE))
> return -EPERM;
> --
> 1.5.6.5
>
> --
>
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH 2/2] powerpc, ftrace: fix compile error when modules not configured
[ forgot to add linuxppc ]
On Fri, 6 Feb 2009, Steven Rostedt wrote:
> From: Steven Rostedt
>
> Michael Neuling reported a compile bug when dynamic ftrace was
> configured in and modules were not. This was due to the ftrace
> code referencing module specific structures.
>
> Reported-by: Michael Neuling
> Signed-off-by: Steven Rostedt
> ---
> arch/powerpc/kernel/ftrace.c | 16 +++-
> 1 files changed, 15 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/kernel/ftrace.c b/arch/powerpc/kernel/ftrace.c
> index a913f91..88c641d 100644
> --- a/arch/powerpc/kernel/ftrace.c
> +++ b/arch/powerpc/kernel/ftrace.c
> @@ -113,6 +113,8 @@ static int test_24bit_addr(unsigned long ip, unsigned
> long addr)
> return create_branch((unsigned int *)ip, addr, 0);
> }
>
> +#ifdef CONFIG_MODULES
> +
> static int is_bl_op(unsigned int op)
> {
> return (op & 0xfc03) == 0x4801;
> @@ -323,6 +325,7 @@ __ftrace_make_nop(struct module *mod,
> return 0;
> }
> #endif /* PPC64 */
> +#endif /* CONFIG_MODULES */
>
> int ftrace_make_nop(struct module *mod,
> struct dyn_ftrace *rec, unsigned long addr)
> @@ -342,6 +345,7 @@ int ftrace_make_nop(struct module *mod,
> return ftrace_modify_code(ip, old, new);
> }
>
> +#ifdef CONFIG_MODULES
> /*
>* Out of range jumps are called from modules.
>* We should either already have a pointer to the module
> @@ -366,9 +370,13 @@ int ftrace_make_nop(struct module *mod,
> mod = rec->arch.mod;
>
> return __ftrace_make_nop(mod, rec, addr);
> -
> +#else
> + /* We should not get here without modules */
> + return -EINVAL;
> +#endif /* CONFIG_MODULES */
> }
>
> +#ifdef CONFIG_MODULES
> #ifdef CONFIG_PPC64
> static int
> __ftrace_make_call(struct dyn_ftrace *rec, unsigned long addr)
> @@ -457,6 +465,7 @@ __ftrace_make_call(struct dyn_ftrace *rec, unsigned long
> addr)
> return 0;
> }
> #endif /* CONFIG_PPC64 */
> +#endif /* CONFIG_MODULES */
>
> int ftrace_make_call(struct dyn_ftrace *rec, unsigned long addr)
> {
> @@ -475,6 +484,7 @@ int ftrace_make_call(struct dyn_ftrace *rec, unsigned
> long addr)
> return ftrace_modify_code(ip, old, new);
> }
>
> +#ifdef CONFIG_MODULES
> /*
>* Out of range jumps are called from modules.
>* Being that we are converting from nop, it had better
> @@ -486,6 +496,10 @@ int ftrace_make_call(struct dyn_ftrace *rec, unsigned
> long addr)
> }
>
> return __ftrace_make_call(rec, addr);
> +#else
> + /* We should not get here without modules */
> + return -EINVAL;
> +#endif /* CONFIG_MODULES */
> }
>
> int ftrace_update_ftrace_func(ftrace_func_t func)
> --
> 1.5.6.5
>
> --
>
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH 2/2] powerpc, ftrace: fix compile error when modules not configured
In message <20090206060527.369616...@goodmis.org> you wrote:
> From: Steven Rostedt
>
> Michael Neuling reported a compile bug when dynamic ftrace was
> configured in and modules were not. This was due to the ftrace
> code referencing module specific structures.
>
> Reported-by: Michael Neuling
> Signed-off-by: Steven Rostedt
Steve,
Thanks, fixes the error I was seeing.
As an aside, is there anyway we can merge some of the code in
arch/powerpc/kernel/ftrace.c between 32 and 64bit? There seems to be a
lot of repeated code in there with only minor changes.
Mikey
> ---
> arch/powerpc/kernel/ftrace.c | 16 +++-
> 1 files changed, 15 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/kernel/ftrace.c b/arch/powerpc/kernel/ftrace.c
> index a913f91..88c641d 100644
> --- a/arch/powerpc/kernel/ftrace.c
> +++ b/arch/powerpc/kernel/ftrace.c
> @@ -113,6 +113,8 @@ static int test_24bit_addr(unsigned long ip, unsigned lon
g addr)
> return create_branch((unsigned int *)ip, addr, 0);
> }
>
> +#ifdef CONFIG_MODULES
> +
> static int is_bl_op(unsigned int op)
> {
> return (op & 0xfc03) == 0x4801;
> @@ -323,6 +325,7 @@ __ftrace_make_nop(struct module *mod,
> return 0;
> }
> #endif /* PPC64 */
> +#endif /* CONFIG_MODULES */
>
> int ftrace_make_nop(struct module *mod,
> struct dyn_ftrace *rec, unsigned long addr)
> @@ -342,6 +345,7 @@ int ftrace_make_nop(struct module *mod,
> return ftrace_modify_code(ip, old, new);
> }
>
> +#ifdef CONFIG_MODULES
> /*
>* Out of range jumps are called from modules.
>* We should either already have a pointer to the module
> @@ -366,9 +370,13 @@ int ftrace_make_nop(struct module *mod,
> mod = rec->arch.mod;
>
> return __ftrace_make_nop(mod, rec, addr);
> -
> +#else
> + /* We should not get here without modules */
> + return -EINVAL;
> +#endif /* CONFIG_MODULES */
> }
>
> +#ifdef CONFIG_MODULES
> #ifdef CONFIG_PPC64
> static int
> __ftrace_make_call(struct dyn_ftrace *rec, unsigned long addr)
> @@ -457,6 +465,7 @@ __ftrace_make_call(struct dyn_ftrace *rec, unsigned long
addr)
> return 0;
> }
> #endif /* CONFIG_PPC64 */
> +#endif /* CONFIG_MODULES */
>
> int ftrace_make_call(struct dyn_ftrace *rec, unsigned long addr)
> {
> @@ -475,6 +484,7 @@ int ftrace_make_call(struct dyn_ftrace *rec, unsigned lon
g addr)
> return ftrace_modify_code(ip, old, new);
> }
>
> +#ifdef CONFIG_MODULES
> /*
>* Out of range jumps are called from modules.
>* Being that we are converting from nop, it had better
> @@ -486,6 +496,10 @@ int ftrace_make_call(struct dyn_ftrace *rec, unsigned lo
ng addr)
> }
>
> return __ftrace_make_call(rec, addr);
> +#else
> + /* We should not get here without modules */
> + return -EINVAL;
> +#endif /* CONFIG_MODULES */
> }
>
> int ftrace_update_ftrace_func(ftrace_func_t func)
> --
> 1.5.6.5
>
> --
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH 2/2] powerpc, ftrace: fix compile error when modules not configured
On Fri, 2009-02-06 at 17:23 +1100, Michael Neuling wrote: > In message <20090206060527.369616...@goodmis.org> you wrote: > > From: Steven Rostedt > > > > Michael Neuling reported a compile bug when dynamic ftrace was > > configured in and modules were not. This was due to the ftrace > > code referencing module specific structures. > > > > Reported-by: Michael Neuling > > Signed-off-by: Steven Rostedt > > Steve, > > Thanks, fixes the error I was seeing. Cool. > > As an aside, is there anyway we can merge some of the code in > arch/powerpc/kernel/ftrace.c between 32 and 64bit? There seems to be a > lot of repeated code in there with only minor changes. It looks similar, but there's enough differences that I would like to keep them separate. The code is complex enough and has a lot of subtle differences between the two archs. -- Steve ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
MPC5121e, MBX driver, pvr.ko ...
Hi all, I have a custom board with a MPC5121e (rev 1.5) on it. It is the latest git kernel from denx ads5121 head with our BSP mixed in. I decided to try out Application Note AN3793 from Freescale (3D Graphics on the ADS512101 Board Using OpenGL ES). I started trying to load the provided (binary!) kernel modules into our kernel, but I am geeting errors inserting the modules using insmod: 'clcdc.ko' complains about not being able to register de device major number, and 'dbgdrv.ko' oopses with a BUG() in percpu_modfree()! This function should never be called in a non-SMP kernel, so I suspect there are some important differences between the kernel I have and the one the binary-only drivers where built against :-( In another approach I managed to load the provided kernel binary (which is built for the ADS512101 evaluation board) on our platform, by tweaking our device-tree until it booted without crashing. In the end I was able to load all the modules and run the OpenGL-ES demo programs. I can't believe this is the intended way of doing this, so I'd like to know if there is someone else who has managed to get the MBX running OpenGL-ES on a custom board with a custom build of the kernel. Note: the kernel version number is still the same: 2.6.24.6, only difference AFAIK is some minor unrelated patches to drivers for other MPC5121 SoC devices, and probably some different configuration options. Apparently this is enough to break binary compatibility for the drivers :-( Any hint is appreciated... Best regards, -- David Jander Protonic Holland. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
