* [PATCH 1/3] powerpc: Instrument Hypervisor Calls: merge headers
From: Mike Kravetz @ 2006-07-14 23:39 UTC (permalink / raw)
To: Paul Mackerras
Cc: Arnd Bergmann, Bryan Rosenburg, linuxppc-dev, Nathan Lynch,
Christopher Yeoh
In-Reply-To: <20060714233739.GA11487@monkey.ibm.com>
Move all the Hypervisor call definitions to to a single header file.
--
Signed-off-by: Mike Kravetz <kravetz@us.ibm.com>
diff -Naupr linux-2.6.17.4/drivers/net/ibmveth.h linux-2.6.17.4.work/drivers/net/ibmveth.h
--- linux-2.6.17.4/drivers/net/ibmveth.h 2006-07-06 20:02:28.000000000 +0000
+++ linux-2.6.17.4.work/drivers/net/ibmveth.h 2006-07-14 23:05:37.000000000 +0000
@@ -41,16 +41,6 @@
#define IbmVethMcastRemoveFilter 0x2UL
#define IbmVethMcastClearFilterTable 0x3UL
-/* hcall numbers */
-#define H_VIO_SIGNAL 0x104
-#define H_REGISTER_LOGICAL_LAN 0x114
-#define H_FREE_LOGICAL_LAN 0x118
-#define H_ADD_LOGICAL_LAN_BUFFER 0x11C
-#define H_SEND_LOGICAL_LAN 0x120
-#define H_MULTICAST_CTRL 0x130
-#define H_CHANGE_LOGICAL_LAN_MAC 0x14C
-#define H_FREE_LOGICAL_LAN_BUFFER 0x1D4
-
/* hcall macros */
#define h_register_logical_lan(ua, buflst, rxq, fltlst, mac) \
plpar_hcall_norets(H_REGISTER_LOGICAL_LAN, ua, buflst, rxq, fltlst, mac)
diff -Naupr linux-2.6.17.4/include/asm-powerpc/hvcall.h linux-2.6.17.4.work/include/asm-powerpc/hvcall.h
--- linux-2.6.17.4/include/asm-powerpc/hvcall.h 2006-07-06 20:02:28.000000000 +0000
+++ linux-2.6.17.4.work/include/asm-powerpc/hvcall.h 2006-07-14 23:05:37.000000000 +0000
@@ -155,9 +155,15 @@
#define H_VIO_SIGNAL 0x104
#define H_SEND_CRQ 0x108
#define H_COPY_RDMA 0x110
+#define H_REGISTER_LOGICAL_LAN 0x114
+#define H_FREE_LOGICAL_LAN 0x118
+#define H_ADD_LOGICAL_LAN_BUFFER 0x11C
+#define H_SEND_LOGICAL_LAN 0x120
+#define H_MULTICAST_CTRL 0x130
#define H_SET_XDABR 0x134
#define H_STUFF_TCE 0x138
#define H_PUT_TCE_INDIRECT 0x13C
+#define H_CHANGE_LOGICAL_LAN_MAC 0x14C
#define H_VTERM_PARTNER_INFO 0x150
#define H_REGISTER_VTERM 0x154
#define H_FREE_VTERM 0x158
@@ -187,11 +193,14 @@
#define H_GET_HCA_INFO 0x1B8
#define H_GET_PERF_COUNT 0x1BC
#define H_MANAGE_TRACE 0x1C0
+#define H_FREE_LOGICAL_LAN_BUFFER 0x1D4
#define H_QUERY_INT_STATE 0x1E4
#define H_POLL_PENDING 0x1D8
#define H_JOIN 0x298
#define H_ENABLE_CRQ 0x2B0
+#define MAX_HCALL_OPCODES (H_ENABLE_CRQ >> 2)
+
#ifndef __ASSEMBLY__
/* plpar_hcall() -- Generic call interface using above opcodes
^ permalink raw reply
* [PATCH 0/3] powerpc: Instrument Hypervisor Calls
From: Mike Kravetz @ 2006-07-14 23:37 UTC (permalink / raw)
To: Paul Mackerras
Cc: Arnd Bergmann, Bryan Rosenburg, linuxppc-dev, Nathan Lynch,
Christopher Yeoh
Hi Paul,
Here is an updated version of the patch(es) to instrument hcalls. All
issues from the previous versions have been addressed. Although, I
haven't really discovered an elegant solution to the assembly routine
name juggling.
In addition, there has been some discussion of these patches on IRC.
Some remaining issues/questions are:
- Exactly how much overhead does the statistic gathering introduce?
- What would be the cost of disabling preemption for more accurate statistics?
- What would be the cost of disabling interrupts for more accurate statistics?
- Should we extend this statistic gathering to RTAS calls?
I would like to get this basic code integrated and then start to address
some of these questions. The IBM performance group will help in
benchmarking to determine overhead.
Please note that all code is behind a config option (off by default) with
zero impact unless enabled.
--
Mike
^ permalink raw reply
* Re: Kexec initial registers
From: Benjamin Herrenschmidt @ 2006-07-14 21:08 UTC (permalink / raw)
To: Jimi Xenidis; +Cc: linuxppc-dev
In-Reply-To: <4CE0FC89-084F-42E8-8E3B-8D2C41AC06F2@watson.ibm.com>
On Fri, 2006-07-14 at 12:02 -0400, Jimi Xenidis wrote:
> This is what I have so far:
>
> r3: address of device tree blob
> r4: address that kernel was loaded
> r5: not OF (=0)
Correct and that's all that should be needed
> r13: local_paca address (0?)
You shouldn't have to care about r13 at all, it should be set by the
kernel before it's used. If not, please let us know as that means there
is a bug :)
Ben.
^ permalink raw reply
* Re: some problems on the SystemACE driver.
From: Ming Liu @ 2006-07-14 21:06 UTC (permalink / raw)
To: ammubhai; +Cc: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
Dear Ameet,
Here is the normal log without -d when make zImage. Please check it.
Waiting for your result. Have fun in the weekend. :)
>I appreciate you testing the patch. Don't worry... we will solve it. And
>I am not an expert either... you probably know more than me!
Thanks for your encouraging. Let's do it! Hopefully we can finish it
a.s.a.p. Good luck for us!
Regards
Ming
_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
[-- Attachment #2: log --]
[-- Type: text/plain, Size: 30355 bytes --]
CHK include/linux/version.h
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/split-include
HOSTCC scripts/basic/docproc
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/kxgettext.o
HOSTCC scripts/kconfig/mconf.o
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf -s arch/ppc/Kconfig
#
# using defaults found in .config
#
SPLIT include/linux/autoconf.h -> include/config/*
CC arch/ppc/kernel/asm-offsets.s
GEN include/asm-ppc/asm-offsets.h
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
CC init/main.o
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
CC init/do_mounts.o
LD init/mounts.o
CC init/initramfs.o
CC init/calibrate.o
LD init/built-in.o
HOSTCC usr/gen_init_cpio
GEN usr/initramfs_data.cpio.gz
AS usr/initramfs_data.o
LD usr/built-in.o
AS arch/ppc/kernel/entry.o
CC arch/ppc/kernel/traps.o
CC arch/ppc/kernel/time.o
AS arch/ppc/kernel/misc.o
CC arch/ppc/kernel/setup.o
CC arch/ppc/kernel/ppc_htab.o
CC arch/ppc/kernel/dma-mapping.o
LD arch/ppc/kernel/built-in.o
AS arch/ppc/kernel/head_4xx.o
LDS arch/ppc/kernel/vmlinux.lds
CC arch/powerpc/kernel/semaphore.o
CC arch/powerpc/kernel/cputable.o
CC arch/powerpc/kernel/ptrace.o
CC arch/powerpc/kernel/syscalls.o
CC arch/powerpc/kernel/irq.o
CC arch/powerpc/kernel/align.o
CC arch/powerpc/kernel/signal_32.o
CC arch/powerpc/kernel/pmc.o
CC arch/powerpc/kernel/vdso.o
CC arch/powerpc/kernel/init_task.o
CC arch/powerpc/kernel/process.o
AS arch/powerpc/kernel/systbl.o
CC arch/powerpc/kernel/idle.o
LDS arch/powerpc/kernel/vdso32/vdso32.lds
VDSO32A arch/powerpc/kernel/vdso32/sigtramp.o
VDSO32A arch/powerpc/kernel/vdso32/gettimeofday.o
VDSO32A arch/powerpc/kernel/vdso32/datapage.o
VDSO32A arch/powerpc/kernel/vdso32/cacheflush.o
VDSO32A arch/powerpc/kernel/vdso32/note.o
VDSO32L arch/powerpc/kernel/vdso32/vdso32.so
AS arch/powerpc/kernel/vdso32/vdso32_wrapper.o
LD arch/powerpc/kernel/vdso32/built-in.o
LD arch/powerpc/kernel/built-in.o
LD arch/ppc/platforms/built-in.o
CC arch/ppc/mm/fault.o
CC arch/ppc/mm/init.o
CC arch/ppc/mm/mem_pieces.o
CC arch/ppc/mm/mmu_context.o
CC arch/ppc/mm/pgtable.o
CC arch/ppc/mm/4xx_mmu.o
LD arch/ppc/mm/built-in.o
AS arch/ppc/lib/checksum.o
AS arch/ppc/lib/string.o
CC arch/ppc/lib/strcase.o
AS arch/ppc/lib/div64.o
LD arch/ppc/lib/built-in.o
CC arch/ppc/syslib/xilinx_pic.o
CC arch/ppc/syslib/ppc_sys.o
CC arch/ppc/syslib/ppc4xx_setup.o
LD arch/ppc/syslib/built-in.o
AS arch/powerpc/sysdev/dcr.o
LD arch/powerpc/sysdev/built-in.o
CC arch/powerpc/lib/bitops.o
LD arch/powerpc/lib/built-in.o
CC arch/ppc/platforms/4xx/xilinx_ml403.o
CC arch/ppc/platforms/4xx/virtex.o
LD arch/ppc/platforms/4xx/built-in.o
CC arch/powerpc/math-emu/math.o
arch/powerpc/math-emu/math.c:56: warning: conflicting types for built-in
function 'fabs'
CC arch/powerpc/math-emu/fmr.o
CC arch/powerpc/math-emu/lfd.o
CC arch/powerpc/math-emu/stfd.o
CC arch/powerpc/math-emu/fabs.o
arch/powerpc/math-emu/fabs.c:7: warning: conflicting types for built-in
function 'fabs'
CC arch/powerpc/math-emu/fadd.o
arch/powerpc/math-emu/fadd.c: In function `fadd':
arch/powerpc/math-emu/fadd.c:31: warning: right shift count is negative
arch/powerpc/math-emu/fadd.c:31: warning: left shift count >= width of type
arch/powerpc/math-emu/fadd.c:13: warning: 'R_e' might be used uninitialized
in this function
arch/powerpc/math-emu/fadd.c:13: warning: 'R_f0' might be used uninitialized
in this function
arch/powerpc/math-emu/fadd.c:13: warning: 'R_f1' might be used uninitialized
in this function
CC arch/powerpc/math-emu/fadds.o
arch/powerpc/math-emu/fadds.c: In function `fadds':
arch/powerpc/math-emu/fadds.c:32: warning: right shift count is negative
arch/powerpc/math-emu/fadds.c:32: warning: left shift count >= width of type
arch/powerpc/math-emu/fadds.c:14: warning: 'R_e' might be used uninitialized
in this function
arch/powerpc/math-emu/fadds.c:14: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fadds.c:14: warning: 'R_f1' might be used
uninitialized in this function
CC arch/powerpc/math-emu/fcmpo.o
CC arch/powerpc/math-emu/fcmpu.o
CC arch/powerpc/math-emu/fctiw.o
arch/powerpc/math-emu/fctiw.c: In function `fctiw':
arch/powerpc/math-emu/fctiw.c:15: warning: left shift count >= width of type
arch/powerpc/math-emu/fctiw.c:15: warning: left shift count >= width of type
arch/powerpc/math-emu/fctiw.c:12: warning: 'r' might be used uninitialized
in this function
CC arch/powerpc/math-emu/fctiwz.o
arch/powerpc/math-emu/fctiwz.c: In function `fctiwz':
arch/powerpc/math-emu/fctiwz.c:20: warning: left shift count >= width of
type
arch/powerpc/math-emu/fctiwz.c:20: warning: left shift count >= width of
type
arch/powerpc/math-emu/fctiwz.c:13: warning: 'r' might be used uninitialized
in this function
CC arch/powerpc/math-emu/fdiv.o
arch/powerpc/math-emu/fdiv.c: In function `fdiv':
arch/powerpc/math-emu/fdiv.c:46: warning: left shift count is negative
arch/powerpc/math-emu/fdiv.c:13: warning: 'R_e' might be used uninitialized
in this function
arch/powerpc/math-emu/fdiv.c:13: warning: 'R_f0' might be used uninitialized
in this function
arch/powerpc/math-emu/fdiv.c:13: warning: 'R_f1' might be used uninitialized
in this function
CC arch/powerpc/math-emu/fdivs.o
arch/powerpc/math-emu/fdivs.c: In function `fdivs':
arch/powerpc/math-emu/fdivs.c:48: warning: left shift count is negative
arch/powerpc/math-emu/fdivs.c:14: warning: 'R_e' might be used uninitialized
in this function
arch/powerpc/math-emu/fdivs.c:14: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fdivs.c:14: warning: 'R_f1' might be used
uninitialized in this function
CC arch/powerpc/math-emu/fmadd.o
arch/powerpc/math-emu/fmadd.c: In function `fmadd':
arch/powerpc/math-emu/fmadd.c:36: warning: right shift count is negative
arch/powerpc/math-emu/fmadd.c:36: warning: left shift count >= width of type
arch/powerpc/math-emu/fmadd.c:41: warning: right shift count is negative
arch/powerpc/math-emu/fmadd.c:41: warning: left shift count >= width of type
arch/powerpc/math-emu/fmadd.c:11: warning: 'R_e' might be used uninitialized
in this function
arch/powerpc/math-emu/fmadd.c:11: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fmadd.c:11: warning: 'R_f1' might be used
uninitialized in this function
arch/powerpc/math-emu/fmadd.c:15: warning: 'T_e' might be used uninitialized
in this function
CC arch/powerpc/math-emu/fmadds.o
arch/powerpc/math-emu/fmadds.c: In function `fmadds':
arch/powerpc/math-emu/fmadds.c:37: warning: right shift count is negative
arch/powerpc/math-emu/fmadds.c:37: warning: left shift count >= width of
type
arch/powerpc/math-emu/fmadds.c:42: warning: right shift count is negative
arch/powerpc/math-emu/fmadds.c:42: warning: left shift count >= width of
type
arch/powerpc/math-emu/fmadds.c:12: warning: 'R_e' might be used
uninitialized in this function
arch/powerpc/math-emu/fmadds.c:12: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fmadds.c:12: warning: 'R_f1' might be used
uninitialized in this function
arch/powerpc/math-emu/fmadds.c:16: warning: 'T_e' might be used
uninitialized in this function
CC arch/powerpc/math-emu/fmsub.o
arch/powerpc/math-emu/fmsub.c: In function `fmsub':
arch/powerpc/math-emu/fmsub.c:36: warning: right shift count is negative
arch/powerpc/math-emu/fmsub.c:36: warning: left shift count >= width of type
arch/powerpc/math-emu/fmsub.c:44: warning: right shift count is negative
arch/powerpc/math-emu/fmsub.c:44: warning: left shift count >= width of type
arch/powerpc/math-emu/fmsub.c:11: warning: 'R_e' might be used uninitialized
in this function
arch/powerpc/math-emu/fmsub.c:11: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fmsub.c:11: warning: 'R_f1' might be used
uninitialized in this function
arch/powerpc/math-emu/fmsub.c:15: warning: 'T_e' might be used uninitialized
in this function
CC arch/powerpc/math-emu/fmsubs.o
arch/powerpc/math-emu/fmsubs.c: In function `fmsubs':
arch/powerpc/math-emu/fmsubs.c:37: warning: right shift count is negative
arch/powerpc/math-emu/fmsubs.c:37: warning: left shift count >= width of
type
arch/powerpc/math-emu/fmsubs.c:45: warning: right shift count is negative
arch/powerpc/math-emu/fmsubs.c:45: warning: left shift count >= width of
type
arch/powerpc/math-emu/fmsubs.c:12: warning: 'R_e' might be used
uninitialized in this function
arch/powerpc/math-emu/fmsubs.c:12: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fmsubs.c:12: warning: 'R_f1' might be used
uninitialized in this function
arch/powerpc/math-emu/fmsubs.c:16: warning: 'T_e' might be used
uninitialized in this function
CC arch/powerpc/math-emu/fmul.o
arch/powerpc/math-emu/fmul.c: In function `fmul':
arch/powerpc/math-emu/fmul.c:34: warning: right shift count is negative
arch/powerpc/math-emu/fmul.c:34: warning: left shift count >= width of type
arch/powerpc/math-emu/fmul.c:13: warning: 'R_e' might be used uninitialized
in this function
CC arch/powerpc/math-emu/fmuls.o
arch/powerpc/math-emu/fmuls.c: In function `fmuls':
arch/powerpc/math-emu/fmuls.c:35: warning: right shift count is negative
arch/powerpc/math-emu/fmuls.c:35: warning: left shift count >= width of type
arch/powerpc/math-emu/fmuls.c:14: warning: 'R_e' might be used uninitialized
in this function
CC arch/powerpc/math-emu/fnabs.o
CC arch/powerpc/math-emu/fneg.o
CC arch/powerpc/math-emu/types.o
arch/powerpc/math-emu/types.c: In function `fp_unpack_d':
arch/powerpc/math-emu/types.c:13: warning: left shift count is negative
arch/powerpc/math-emu/types.c: In function `fp_pack_d':
arch/powerpc/math-emu/types.c:28: warning: right shift count is negative
arch/powerpc/math-emu/types.c:28: warning: right shift count is negative
arch/powerpc/math-emu/types.c:28: warning: left shift count is negative
arch/powerpc/math-emu/types.c:28: warning: right shift count is negative
arch/powerpc/math-emu/types.c: In function `fp_pack_ds':
arch/powerpc/math-emu/types.c:41: warning: right shift count is negative
arch/powerpc/math-emu/types.c:45: warning: left shift count is negative
arch/powerpc/math-emu/types.c:46: warning: right shift count is negative
arch/powerpc/math-emu/types.c:46: warning: right shift count is negative
arch/powerpc/math-emu/types.c:46: warning: left shift count is negative
arch/powerpc/math-emu/types.c:46: warning: right shift count is negative
CC arch/powerpc/math-emu/fnmadd.o
arch/powerpc/math-emu/fnmadd.c: In function `fnmadd':
arch/powerpc/math-emu/fnmadd.c:36: warning: right shift count is negative
arch/powerpc/math-emu/fnmadd.c:36: warning: left shift count >= width of
type
arch/powerpc/math-emu/fnmadd.c:41: warning: right shift count is negative
arch/powerpc/math-emu/fnmadd.c:41: warning: left shift count >= width of
type
arch/powerpc/math-emu/fnmadd.c:11: warning: 'R_e' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmadd.c:11: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmadd.c:11: warning: 'R_f1' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmadd.c:15: warning: 'T_e' might be used
uninitialized in this function
CC arch/powerpc/math-emu/fnmadds.o
arch/powerpc/math-emu/fnmadds.c: In function `fnmadds':
arch/powerpc/math-emu/fnmadds.c:37: warning: right shift count is negative
arch/powerpc/math-emu/fnmadds.c:37: warning: left shift count >= width of
type
arch/powerpc/math-emu/fnmadds.c:42: warning: right shift count is negative
arch/powerpc/math-emu/fnmadds.c:42: warning: left shift count >= width of
type
arch/powerpc/math-emu/fnmadds.c:12: warning: 'R_e' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmadds.c:12: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmadds.c:12: warning: 'R_f1' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmadds.c:16: warning: 'T_e' might be used
uninitialized in this function
CC arch/powerpc/math-emu/fnmsub.o
arch/powerpc/math-emu/fnmsub.c: In function `fnmsub':
arch/powerpc/math-emu/fnmsub.c:36: warning: right shift count is negative
arch/powerpc/math-emu/fnmsub.c:36: warning: left shift count >= width of
type
arch/powerpc/math-emu/fnmsub.c:44: warning: right shift count is negative
arch/powerpc/math-emu/fnmsub.c:44: warning: left shift count >= width of
type
arch/powerpc/math-emu/fnmsub.c:11: warning: 'R_e' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmsub.c:11: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmsub.c:11: warning: 'R_f1' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmsub.c:15: warning: 'T_e' might be used
uninitialized in this function
CC arch/powerpc/math-emu/fnmsubs.o
arch/powerpc/math-emu/fnmsubs.c: In function `fnmsubs':
arch/powerpc/math-emu/fnmsubs.c:37: warning: right shift count is negative
arch/powerpc/math-emu/fnmsubs.c:37: warning: left shift count >= width of
type
arch/powerpc/math-emu/fnmsubs.c:45: warning: right shift count is negative
arch/powerpc/math-emu/fnmsubs.c:45: warning: left shift count >= width of
type
arch/powerpc/math-emu/fnmsubs.c:12: warning: 'R_e' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmsubs.c:12: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmsubs.c:12: warning: 'R_f1' might be used
uninitialized in this function
arch/powerpc/math-emu/fnmsubs.c:16: warning: 'T_e' might be used
uninitialized in this function
CC arch/powerpc/math-emu/fres.o
CC arch/powerpc/math-emu/frsp.o
CC arch/powerpc/math-emu/frsqrte.o
CC arch/powerpc/math-emu/fsel.o
CC arch/powerpc/math-emu/lfs.o
arch/powerpc/math-emu/lfs.c: In function `lfs':
arch/powerpc/math-emu/lfs.c:30: warning: left shift count is negative
CC arch/powerpc/math-emu/fsqrt.o
arch/powerpc/math-emu/fsqrt.c: In function `fsqrt':
arch/powerpc/math-emu/fsqrt.c:30: warning: left shift count is negative
arch/powerpc/math-emu/fsqrt.c:30: warning: left shift count is negative
arch/powerpc/math-emu/fsqrt.c:30: warning: left shift count is negative
arch/powerpc/math-emu/fsqrt.c:30: warning: left shift count is negative
arch/powerpc/math-emu/fsqrt.c:30: warning: right shift count is negative
arch/powerpc/math-emu/fsqrt.c:12: warning: 'R_c' might be used uninitialized
in this function
arch/powerpc/math-emu/fsqrt.c:12: warning: 'R_s' might be used uninitialized
in this function
arch/powerpc/math-emu/fsqrt.c:12: warning: 'R_e' might be used uninitialized
in this function
arch/powerpc/math-emu/fsqrt.c:12: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fsqrt.c:12: warning: 'R_f1' might be used
uninitialized in this function
CC arch/powerpc/math-emu/fsqrts.o
arch/powerpc/math-emu/fsqrts.c: In function `fsqrts':
arch/powerpc/math-emu/fsqrts.c:31: warning: left shift count is negative
arch/powerpc/math-emu/fsqrts.c:31: warning: left shift count is negative
arch/powerpc/math-emu/fsqrts.c:31: warning: left shift count is negative
arch/powerpc/math-emu/fsqrts.c:31: warning: left shift count is negative
arch/powerpc/math-emu/fsqrts.c:31: warning: right shift count is negative
arch/powerpc/math-emu/fsqrts.c:13: warning: 'R_c' might be used
uninitialized in this function
arch/powerpc/math-emu/fsqrts.c:13: warning: 'R_s' might be used
uninitialized in this function
arch/powerpc/math-emu/fsqrts.c:13: warning: 'R_e' might be used
uninitialized in this function
arch/powerpc/math-emu/fsqrts.c:13: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fsqrts.c:13: warning: 'R_f1' might be used
uninitialized in this function
CC arch/powerpc/math-emu/fsub.o
arch/powerpc/math-emu/fsub.c: In function `fsub':
arch/powerpc/math-emu/fsub.c:34: warning: right shift count is negative
arch/powerpc/math-emu/fsub.c:34: warning: left shift count >= width of type
arch/powerpc/math-emu/fsub.c:13: warning: 'R_e' might be used uninitialized
in this function
arch/powerpc/math-emu/fsub.c:13: warning: 'R_f0' might be used uninitialized
in this function
arch/powerpc/math-emu/fsub.c:13: warning: 'R_f1' might be used uninitialized
in this function
CC arch/powerpc/math-emu/fsubs.o
arch/powerpc/math-emu/fsubs.c: In function `fsubs':
arch/powerpc/math-emu/fsubs.c:35: warning: right shift count is negative
arch/powerpc/math-emu/fsubs.c:35: warning: left shift count >= width of type
arch/powerpc/math-emu/fsubs.c:14: warning: 'R_e' might be used uninitialized
in this function
arch/powerpc/math-emu/fsubs.c:14: warning: 'R_f0' might be used
uninitialized in this function
arch/powerpc/math-emu/fsubs.c:14: warning: 'R_f1' might be used
uninitialized in this function
CC arch/powerpc/math-emu/mcrfs.o
CC arch/powerpc/math-emu/mffs.o
CC arch/powerpc/math-emu/mtfsb0.o
CC arch/powerpc/math-emu/mtfsb1.o
CC arch/powerpc/math-emu/mtfsf.o
CC arch/powerpc/math-emu/mtfsfi.o
CC arch/powerpc/math-emu/stfiwx.o
CC arch/powerpc/math-emu/stfs.o
arch/powerpc/math-emu/stfs.c: In function `stfs':
arch/powerpc/math-emu/stfs.c:27: warning: right shift count is negative
CC arch/powerpc/math-emu/udivmodti4.o
LD arch/powerpc/math-emu/built-in.o
CC kernel/sched.o
CC kernel/fork.o
CC kernel/exec_domain.o
CC kernel/panic.o
CC kernel/printk.o
CC kernel/profile.o
CC kernel/exit.o
CC kernel/itimer.o
CC kernel/time.o
CC kernel/softirq.o
CC kernel/resource.o
CC kernel/sysctl.o
CC kernel/capability.o
CC kernel/ptrace.o
CC kernel/timer.o
CC kernel/user.o
CC kernel/signal.o
CC kernel/sys.o
CC kernel/kmod.o
CC kernel/workqueue.o
CC kernel/pid.o
CC kernel/rcupdate.o
CC kernel/extable.o
CC kernel/params.o
CC kernel/posix-timers.o
CC kernel/kthread.o
CC kernel/wait.o
CC kernel/kfifo.o
CC kernel/sys_ni.o
CC kernel/posix-cpu-timers.o
CC kernel/mutex.o
CC kernel/hrtimer.o
CC kernel/futex.o
CC kernel/intermodule.o
CC kernel/kallsyms.o
CC kernel/ksysfs.o
CC kernel/softlockup.o
CC kernel/irq/handle.o
CC kernel/irq/manage.o
CC kernel/irq/spurious.o
CC kernel/irq/proc.o
LD kernel/irq/built-in.o
CC kernel/seccomp.o
LD kernel/built-in.o
CC mm/bootmem.o
CC mm/filemap.o
CC mm/mempool.o
CC mm/oom_kill.o
CC mm/fadvise.o
CC mm/page_alloc.o
CC mm/page-writeback.o
CC mm/pdflush.o
CC mm/readahead.o
CC mm/swap.o
CC mm/truncate.o
CC mm/vmscan.o
CC mm/prio_tree.o
CC mm/util.o
CC mm/mmzone.o
CC mm/fremap.o
CC mm/highmem.o
CC mm/madvise.o
CC mm/memory.o
CC mm/mincore.o
CC mm/mlock.o
CC mm/mmap.o
CC mm/mprotect.o
CC mm/mremap.o
CC mm/msync.o
CC mm/rmap.o
CC mm/vmalloc.o
CC mm/page_io.o
CC mm/swap_state.o
CC mm/swapfile.o
CC mm/thrash.o
CC mm/shmem.o
CC mm/slab.o
CC mm/filemap_xip.o
LD mm/built-in.o
CC fs/open.o
CC fs/read_write.o
CC fs/file_table.o
CC fs/buffer.o
CC fs/bio.o
CC fs/super.o
CC fs/block_dev.o
CC fs/char_dev.o
CC fs/stat.o
CC fs/exec.o
CC fs/pipe.o
CC fs/namei.o
CC fs/fcntl.o
CC fs/ioctl.o
CC fs/readdir.o
CC fs/select.o
CC fs/fifo.o
CC fs/locks.o
CC fs/dcache.o
CC fs/inode.o
CC fs/attr.o
CC fs/bad_inode.o
CC fs/file.o
CC fs/filesystems.o
CC fs/namespace.o
CC fs/aio.o
CC fs/seq_file.o
CC fs/xattr.o
CC fs/libfs.o
CC fs/fs-writeback.o
CC fs/mpage.o
CC fs/direct-io.o
CC fs/ioprio.o
CC fs/pnode.o
CC fs/drop_caches.o
CC fs/splice.o
CC fs/sync.o
CC fs/inotify.o
CC fs/eventpoll.o
CC fs/binfmt_script.o
CC fs/binfmt_elf.o
CC fs/mbcache.o
CC fs/posix_acl.o
CC fs/xattr_acl.o
CC fs/dnotify.o
CC fs/autofs/dirhash.o
CC fs/autofs/init.o
CC fs/autofs/inode.o
CC fs/autofs/root.o
CC fs/autofs/symlink.o
CC fs/autofs/waitq.o
LD fs/autofs/autofs.o
LD fs/autofs/built-in.o
CC fs/autofs4/init.o
CC fs/autofs4/inode.o
CC fs/autofs4/root.o
CC fs/autofs4/symlink.o
CC fs/autofs4/waitq.o
CC fs/autofs4/expire.o
LD fs/autofs4/autofs4.o
LD fs/autofs4/built-in.o
CC fs/devpts/inode.o
LD fs/devpts/devpts.o
LD fs/devpts/built-in.o
CC fs/ext2/balloc.o
CC fs/ext2/bitmap.o
CC fs/ext2/dir.o
CC fs/ext2/file.o
CC fs/ext2/fsync.o
CC fs/ext2/ialloc.o
CC fs/ext2/inode.o
CC fs/ext2/ioctl.o
CC fs/ext2/namei.o
CC fs/ext2/super.o
CC fs/ext2/symlink.o
CC fs/ext2/xattr.o
CC fs/ext2/xattr_user.o
CC fs/ext2/xattr_trusted.o
CC fs/ext2/acl.o
CC fs/ext2/xattr_security.o
CC fs/ext2/xip.o
LD fs/ext2/ext2.o
LD fs/ext2/built-in.o
CC fs/nls/nls_base.o
LD fs/nls/built-in.o
CC fs/partitions/check.o
CC fs/partitions/msdos.o
LD fs/partitions/built-in.o
CC fs/proc/mmu.o
CC fs/proc/task_mmu.o
CC fs/proc/inode.o
CC fs/proc/root.o
CC fs/proc/base.o
CC fs/proc/generic.o
CC fs/proc/array.o
CC fs/proc/kmsg.o
CC fs/proc/proc_tty.o
CC fs/proc/proc_misc.o
CC fs/proc/kcore.o
LD fs/proc/proc.o
LD fs/proc/built-in.o
CC fs/ramfs/inode.o
CC fs/ramfs/file-mmu.o
LD fs/ramfs/ramfs.o
LD fs/ramfs/built-in.o
CC fs/sysfs/inode.o
CC fs/sysfs/file.o
CC fs/sysfs/dir.o
CC fs/sysfs/symlink.o
CC fs/sysfs/mount.o
CC fs/sysfs/bin.o
CC fs/sysfs/group.o
LD fs/sysfs/built-in.o
LD fs/built-in.o
CC ipc/util.o
CC ipc/msgutil.o
CC ipc/msg.o
CC ipc/sem.o
CC ipc/shm.o
LD ipc/built-in.o
CC security/commoncap.o
LD security/built-in.o
LD crypto/built-in.o
CC block/elevator.o
CC block/ll_rw_blk.o
CC block/ioctl.o
CC block/genhd.o
CC block/scsi_ioctl.o
CC block/noop-iosched.o
CC block/as-iosched.o
CC block/deadline-iosched.o
CC block/cfq-iosched.o
LD block/built-in.o
CC drivers/base/core.o
CC drivers/base/sys.o
CC drivers/base/bus.o
CC drivers/base/dd.o
CC drivers/base/driver.o
CC drivers/base/class.o
CC drivers/base/platform.o
CC drivers/base/cpu.o
CC drivers/base/firmware.o
CC drivers/base/init.o
CC drivers/base/map.o
CC drivers/base/dmapool.o
CC drivers/base/attribute_container.o
CC drivers/base/transport_class.o
CC drivers/base/power/shutdown.o
LD drivers/base/power/built-in.o
LD drivers/base/built-in.o
CC drivers/block/loop.o
CC drivers/block/xilinx_sysace/adapter.o
drivers/block/xilinx_sysace/adapter.c:221: warning: 'xsysace_restart'
defined but not used
CC drivers/block/xilinx_sysace/xbasic_types.o
CC drivers/block/xilinx_sysace/xsysace.o
CC drivers/block/xilinx_sysace/xsysace_g.o
CC drivers/block/xilinx_sysace/xsysace_intr.o
CC drivers/block/xilinx_sysace/xsysace_l.o
CC drivers/block/xilinx_sysace/xsysace_compactflash.o
CC drivers/block/xilinx_sysace/xsysace_jtagcfg.o
LD drivers/block/xilinx_sysace/xilinx_sysace.o
LD drivers/block/xilinx_sysace/built-in.o
LD drivers/block/built-in.o
LD drivers/cdrom/built-in.o
CC drivers/char/mem.o
CC drivers/char/random.o
CC drivers/char/tty_io.o
CC drivers/char/n_tty.o
CC drivers/char/tty_ioctl.o
CC drivers/char/pty.o
CC drivers/char/misc.o
CC drivers/char/vt_ioctl.o
CC drivers/char/vc_screen.o
CC drivers/char/consolemap.o
CONMK drivers/char/consolemap_deftbl.c
CC drivers/char/consolemap_deftbl.o
CC drivers/char/selection.o
CC drivers/char/keyboard.o
CC drivers/char/vt.o
SHIPPED drivers/char/defkeymap.c
CC drivers/char/defkeymap.o
LD drivers/char/built-in.o
LD drivers/firmware/built-in.o
CC drivers/hwmon/hwmon.o
LD drivers/hwmon/built-in.o
CC drivers/input/input.o
CC drivers/input/mousedev.o
LD drivers/input/built-in.o
CC drivers/input/serio/serio.o
CC drivers/input/serio/i8042.o
CC drivers/input/serio/serport.o
LD drivers/input/serio/built-in.o
LD drivers/media/common/built-in.o
LD drivers/media/built-in.o
LD drivers/mfd/built-in.o
LD drivers/misc/built-in.o
CC drivers/mtd/mtdcore.o
CC drivers/mtd/mtdpart.o
CC drivers/mtd/redboot.o
drivers/mtd/redboot.c: In function `parse_redboot_partitions':
drivers/mtd/redboot.c:103: warning: passing arg 1 of `__swab32s' from
incompatible pointer type
drivers/mtd/redboot.c:104: warning: passing arg 1 of `__swab32s' from
incompatible pointer type
drivers/mtd/redboot.c:105: warning: passing arg 1 of `__swab32s' from
incompatible pointer type
drivers/mtd/redboot.c:106: warning: passing arg 1 of `__swab32s' from
incompatible pointer type
drivers/mtd/redboot.c:107: warning: passing arg 1 of `__swab32s' from
incompatible pointer type
drivers/mtd/redboot.c:108: warning: passing arg 1 of `__swab32s' from
incompatible pointer type
drivers/mtd/redboot.c:109: warning: passing arg 1 of `__swab32s' from
incompatible pointer type
CC drivers/mtd/mtdchar.o
CC drivers/mtd/mtdblock.o
CC drivers/mtd/mtd_blkdevs.o
CC drivers/mtd/chips/chipreg.o
CC drivers/mtd/chips/cfi_probe.o
CC drivers/mtd/chips/cfi_util.o
CC drivers/mtd/chips/cfi_cmdset_0002.o
drivers/mtd/chips/cfi_cmdset_0002.c: In function `cfi_amdstd_init':
drivers/mtd/chips/cfi_cmdset_0002.c:1766: warning: `inter_module_register'
is deprecated (declared at include/linux/module.h:563)
drivers/mtd/chips/cfi_cmdset_0002.c: In function `cfi_amdstd_exit':
drivers/mtd/chips/cfi_cmdset_0002.c:1773: warning: `inter_module_unregister'
is deprecated (declared at include/linux/module.h:564)
CC drivers/mtd/chips/gen_probe.o
LD drivers/mtd/chips/built-in.o
LD drivers/mtd/devices/built-in.o
LD drivers/mtd/maps/built-in.o
LD drivers/mtd/nand/built-in.o
LD drivers/mtd/onenand/built-in.o
LD drivers/mtd/built-in.o
CC drivers/net/Space.o
CC drivers/net/loopback.o
CC drivers/net/xilinx_temac/adapter.o
CC drivers/net/xilinx_temac/xtemac.o
CC drivers/net/xilinx_temac/xtemac_intr.o
CC drivers/net/xilinx_temac/xtemac_intr_sgdma.o
CC drivers/net/xilinx_temac/xtemac_sgdma.o
CC drivers/net/xilinx_temac/xtemac_intr_fifo.o
CC drivers/net/xilinx_temac/xtemac_fifo.o
CC drivers/net/xilinx_temac/xtemac_l.o
CC drivers/net/xilinx_temac/xtemac_control.o
LD drivers/net/xilinx_temac/xilinx_temac.o
LD drivers/net/xilinx_temac/built-in.o
LD drivers/net/built-in.o
CC drivers/serial/serial_core.o
CC drivers/serial/8250.o
CC drivers/serial/8250_early.o
LD drivers/serial/built-in.o
LD drivers/video/backlight/built-in.o
CC drivers/video/console/dummycon.o
LD drivers/video/console/built-in.o
LD drivers/video/built-in.o
CC drivers/xilinx_edk/xilinx_syms.o
CC drivers/xilinx_edk/xbasic_types.o
CC drivers/xilinx_edk/xpacket_fifo_v2_00_a.o
CC drivers/xilinx_edk/xpacket_fifo_l_v2_00_a.o
CC drivers/xilinx_edk/xdmav2.o
CC drivers/xilinx_edk/xdmav2_intr.o
CC drivers/xilinx_edk/xdmav2_sg.o
CC drivers/xilinx_edk/xdmav2_simple.o
LD drivers/xilinx_edk/built-in.o
LD drivers/built-in.o
drivers/xilinx_edk/built-in.o(.sdata+0x0): In function `XAssert':
drivers/xilinx_edk/xbasic_types.c:105: multiple definition of
`XWaitInAssert'
drivers/block/built-in.o(.sdata+0x0):drivers/block/loop.c:91: first defined
here
drivers/xilinx_edk/built-in.o(.sbss+0x4): In function `XAssert':
drivers/xilinx_edk/xbasic_types.c:105: multiple definition of
`XAssertStatus'
drivers/block/built-in.o(.sbss+0x38):drivers/block/loop.c:98: first defined
here
drivers/xilinx_edk/built-in.o(.text+0x44): In function `XAssertSetCallback':
drivers/xilinx_edk/xbasic_types.c:134: multiple definition of
`XAssertSetCallback'
drivers/block/built-in.o(.text+0x24bc):drivers/block/xilinx_sysace/xbasic_types.c:134:
first defined here
drivers/xilinx_edk/built-in.o(.text+0x0): In function `XAssert':
drivers/xilinx_edk/xbasic_types.c:105: multiple definition of `XAssert'
drivers/block/built-in.o(.text+0x2478):drivers/block/xilinx_sysace/xbasic_types.c:105:
first defined here
drivers/xilinx_edk/built-in.o(.text+0x50): In function `XNullHandler':
drivers/xilinx_edk/xbasic_types.c:153: multiple definition of `XNullHandler'
drivers/block/built-in.o(.text+0x24c8):drivers/block/xilinx_sysace/xbasic_types.c:153:
first defined here
make[1]: *** [drivers/built-in.o] Error 1
make: *** [drivers] Error 2
^ permalink raw reply
* Re: [Fwd: Re: [Ilugc] help regarding powerpc and vga card]
From: Benjamin Herrenschmidt @ 2006-07-14 19:20 UTC (permalink / raw)
To: sudheer; +Cc: Sivasankar Chander, linuxppc-embedded
In-Reply-To: <44B77452.1070106@gmail.com>
> >> All PCI VGA cards for use on x86 PCs have a ROMscan
> BIOS
> >> extension on them. This initializes the card after POST -
> basically,
> >> the motherboard BIOS transfers control to the BIOS on the
> >> PCI VGA card, which then initializes itself. If control is
> not
> >> transfered to the VGA BIOS on the card, the VGA controller
> >> stays isolated and will not respond to PCI device
> enumeration,
> >> etc.
> >
> I have a doubt here. How does the processor know that the card
> sitting
> here is a vga card
> and control should be transfered to initialize it. I think it
> can know
> that it is a vga card only by reading the config space .
> And bios is necesary for vga card to work in its normal way.
> Is it
> necesary for bios to be initialised to get detected.
> Please correct me if i am wrong.
You are not wrong (though your mailer sucks). The initial poster seems
to be a bit confused.
All PCI video cards (VGA or not) shall respond to PCI config spaces
normally. They can be enumerated, and if they carry a BIOS image (or any
other firmware support like an Open Firmware F-Code driver), it should
be accessible via the standard PCI expansion ROM BAR.
There is no such thing as "the VGA controller stays isolated" or
whatever sort of crap. However, it is true that the video card needs to
be initialized to be able to actually output anything useful, and
depending on the chip, it's generically a complex procedure involving
setting up all sorts of PLLs, initializing the card's memory controller
and performing the appropriate SDRAM init sequence, initializing the
various external chips like TMDS transmitters on the card etc etc...
That is normally done by the card's firmware which generally sits in the
card's PCI expansion ROM (not always though, it's getting common
nowadays on x86 laptops for example to have the video card's BIOS mixes
with the main BIOS to save a flash chip). The most common type of
firmware is indeed an x86 video BIOS, which can run on non-x86 platforms
through an emulator like x86emu (a common practice, works fairly well
afaik).
Note that what that BIOS does it to poke the card's registers, which are
accessible via the card's normal PCI BARs :) At least most of the time.
Some cards do indeed require some use of the legacy VGA registers for
initialization, which means issuing IO cycles on the bus to fixed VGA
addresses, but that's pretty much irrelevant.
^ permalink raw reply
* Re: [JOB] Senior Embedded Linux Video Engineer
From: Olof Johansson @ 2006-07-14 19:17 UTC (permalink / raw)
To: Tim Bird
Cc: Olof Johansson, Stephen Rothwell, linuxppc-dev, linuxppc-embedded
In-Reply-To: <44B7ECD7.3080807@am.sony.com>
On Fri, Jul 14, 2006 at 12:13:27PM -0700, Tim Bird wrote:
> Olof Johansson wrote:
> > Ick. Why not just create a linuxppc-jobs@ozlabs org instead of hiding it
> > somewhere in the CELF organization...?
>
> Well, it would be either a public list or on CELF's public wiki.
> I'm not sure how this would be "hiding it".
Sorry, I was replying from the viewpoing of a linuxppc-dev reader, not a
linuxppc-embedded reader. I'm willing to say that almost noone of us
visit the CELF pages very often, or at all.
-Olof
^ permalink raw reply
* Re: [JOB] Senior Embedded Linux Video Engineer
From: Segher Boessenkool @ 2006-07-14 19:14 UTC (permalink / raw)
To: bbosch; +Cc: Stephen Rothwell, linuxppc-embedded, linuxppc-dev
In-Reply-To: <17591.43974.871998.267718@waldo.lisle.iphase.com>
> On the other hand, a couple weeks ago, proclus@gnu-darwin.org posted a
> very long, meandering political statement, most of which seemed to
> have very little to do with PowerPC Linux and I didn't notice anyone
> complain on these lists.
I complained on another list -- he sent it _everywhere_.
> (Which is just as well since my objection
> off-list resulted only in a long pointless argument in which it became
> clear that rational debate would get me nowhere.)
Yes indeed.
Segher
^ permalink raw reply
* Re: [JOB] Senior Embedded Linux Video Engineer
From: Tim Bird @ 2006-07-14 19:13 UTC (permalink / raw)
To: Olof Johansson; +Cc: linuxppc-dev, Stephen Rothwell, linuxppc-embedded
In-Reply-To: <20060714180309.GA9121@pb15.lixom.net>
Olof Johansson wrote:
> Ick. Why not just create a linuxppc-jobs@ozlabs org instead of hiding it
> somewhere in the CELF organization...?
Well, it would be either a public list or on CELF's public wiki.
I'm not sure how this would be "hiding it".
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================
^ permalink raw reply
* no "ash" process load
From: morelli.gab @ 2006-07-14 19:02 UTC (permalink / raw)
To: linuxppc-embedded
hi to all
I have a problem when load the kernel-2.6 in my board.
it can't execute the process ash.
how can i set the file "inittab" in way to resolve the problem?
this is the message given back.
mtdblock_release
ok
mtdblock_open
ok
.....
mtdblock: read on "cramfs" at 0x93400, size 0x200
mtdblock: read on "cramfs" at 0x93600, size 0x200
mtdblock: read on "cramfs" at 0x93800, size 0x200
mtdblock: read on "cramfs" at 0x93a00, size 0x200
mtdblock: read on "cramfs" at 0x93c00, size 0x200
mtdblock: read on "cramfs" at 0x93e00, size 0x200
Usage: ash 0123456SsQq=F1BbCcUu
Usage: ash 0123456SsQqAaBbCcUu
Usage: ash 0123456SsQqAaBbCcUu
Usage: ash 0123456SsQqAaBbCcUu
Usage: ash 0123456SsQqAaBbCcUu
Usage: ash 0123456SsQqAaBbCcUu
Usage: ash 0123456SsQqAaBbCcUu
Usage: ash 0123456SsQqAaBbCcUu
...
thanks
^ permalink raw reply
* Re: [JOB] Senior Embedded Linux Video Engineer
From: Frank @ 2006-07-14 18:41 UTC (permalink / raw)
To: Linas Vepstas, Wolfgang Denk
Cc: linuxppc-dev, Stephen Rothwell, linuxppc-embedded
In-Reply-To: <20060714163814.GD11943@austin.ibm.com>
--- Linas Vepstas <linas@austin.ibm.com> wrote:
> On Fri, Jul 14, 2006 at 06:21:00PM +0200, Wolfgang Denk wrote:
> >
> > > Should I post our embedded PPC kernel related work
> openings here?
> >
> > NO!!!
> >
> > This is a technical discussion group. Job offerings,
> commercial ads
> > and all this stuff is off topic here. Please re-read the
> list info at
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded resp.
> -dev
> >
> > It says: "...discussions/patches should pertain to
> software
> > development for the kernel core ppc32 embedded processor
> support and
> > any driver/chip/board support for ppc32 based embedded
> systems."
> >
> > "Software development". This does not allow for job offers,
> ads or
> > other crap.
>
> I respectfully disagree. There may well be people who would
> rather
> work on PowerPC Linux kernels more than any other thing in the
> world,
> and it is entirely appropriate for job openings for PowerPC
> Linux kernel
> programmers to be posted here.
>
> Much as I would like to be, and not for lack of trying,
> indpendently
> wealthy off some dot-com IPO, so that I may code on whatever I
> wished,
> I have, in fact, failed at this, and must stick to actual
> employment
> to feed, cloth and educate my family. I am not alone.
>
> There is a long precedent for this in academic societies, and
> you will
> find job postings in Nature, Science, Physics Today and
> American
> Mathematical Monthly. Frankly, there simply are not so many
> job
> opporunities that we, much like engineers and scientists in
> general,
> can afford to thumb our noses at them.
>
> If you in fact are especially fortunate, then perhaps you
> could
> mentor someone younger: someone who is hot, smart, and fresh
> out of
> college, a good talent, who has contributed good patches, but
> is now
> faced with the need to find rent and beer money. What advice
> can you
> give them, "tough luck Squidward, go work at the Krusty Krab?"
>
> --linas/ozlabs.org/mailman/listinfo/linuxppc-dev
Maybe you should stand on a corner with a sign that says:
"Will code for food"...
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
^ permalink raw reply
* RE: Xilinx hard TEMAC
From: Rick Moleres @ 2006-07-14 18:43 UTC (permalink / raw)
To: dhlii, linuxppc-embedded
David,
<snip>
>=20
> The choice and configuration of the TEMAC was driven by FPGA
> realestate.
>=20
> My perception was that the "Hard" Temac was based on silicon
already
> in the FX (much like the PowerPC) while the "Soft" TEMAC is primarily
> implimented within the FPGA (much like the MicroBlaze).
>=20
> Is that distinction between "soft" and "hard" correct ?
>=20
That is the correct distinction between "soft" and "hard". Just know
that in this case the "soft" TEMAC (whether LL TEMAC or PLB TEMAC) uses
the "hard" TEMAC, and the "hard" TEMAC by itself is not that useful.
> If not is the only significant distinction between the PLB_TEMAC
> supported by the EDK and the LL_TEMAC the bus interface ?
Yes, this is one of the distinctions between LL TEMAC and PLB TEMAC. :-)
> I should not think the difference between different bus
interfaces
> should be radically different in terms of FPGA cells. While
implimenting
> the MAC in the FPGA would likely be expensive in realestate.
> I can try to argue for the PLB_TEMAC - as something that will
have
> Xilinx/MV support and may get incorporated in the standard Kernel - If
> the cost in cells is not substantial.
>=20
I believe LL_TEMAC is smaller than PLB_TEMAC, and so this could be a
tough sell for you if FPGA space is at a premium. When put in a system
with other stuff (e.g., memory controller, etc...) the size gets closer,
but I think GSRD is still smaller. Sorry, I don't have the numbers.
There were improvements to PLB TEMAC in EDK 8.1.2 to address some size
issues, and even more planned down the road to hopefully converge the
two.
>=20
>=20
> > The Linux driver posted for the TEMAC (by MontaVista) is for the
> > PLB_TEMAC. Updates to this driver may also be released with the EDK
> > (e.g., EDK 8.1.2 updated the driver to include checksum offload).
There
> > is a Linux driver for the LL_TEMAC that comes with GSRD, but my
group's
> > efforts go toward the PLB_TEMAC as that is the EDK IP we want to
promote
> > and whose drivers we'd like to see in kernel.org.
> >
> How can I get a copy of the GSRD LL_TEMAC ? Is it a 2.4 or 2.6
driver
> ?
>=20
You should be able to go to http://www.xilinx.com/gsrd to get the GSRD
design, and inside of that design somewhere you'll find a Linux 2.4
driver for the LL TEMAC.
> > By the way, there is no relation to the IBM EMAC.
> >
> These things are worth knowing.
>=20
> The T still means Tri. is there some specific EMAC that was used
as
> a reference for the design or is the TEMAC entirely a Xilinx creation
?
>=20
It's a Xilinx creation as far as I know.
> > Hope that helps,
> > -Rick
> >
^ permalink raw reply
* Re: [JOB] Senior Embedded Linux Video Engineer
From: Geoff Thorpe @ 2006-07-14 18:40 UTC (permalink / raw)
To: Olof Johansson; +Cc: linuxppc-dev, linuxppc-embedded, Stephen Rothwell
In-Reply-To: <20060714180309.GA9121@pb15.lixom.net>
Olof Johansson wrote:
>Personally, I don't mind getting the ads just to know who is growing
>out there and so on, but I don't want them sorted into the folder with
>technical stuff, and I don't want to rely on people tagging the subject
>right.
>
>
In this case, a list moderator was contacted prior to the post. So...
why not just extend the idea and have potential employers[1] provide
their "openings" (erm) to such a moderator who sends a not-too-frequent
digest to the list encapsulating any/all such offerings. That way, the
subject *will* be tagged correctly, the rate of "off-topic" postings is
inherently throttled/coalesced, and anyone who might be remotely
interested will be exposed to such opportunities without having to
actively go searching (ipso facto, those HR types will be less inclined
to carpet-bomb the entire internet for fear that their offerings go
otherwise unnoticed). Hell, if the subject header was appropriately
keyworded - Wolfgang could even procmail it to /dev/null ;-)
[1] this could also cover other commercial/potential-list-abuse subjects
like speaking engagements, survey requests, [tbd]. If it got too big, it
could be replaced with a summary of headings and URLs. Whatever.
Just my first-glance $0.02,
Geoff
^ permalink raw reply
* Kexec initial registers
From: Jimi Xenidis @ 2006-07-14 16:02 UTC (permalink / raw)
To: linuxppc-dev
This is what I have so far:
r3: address of device tree blob
r4: address that kernel was loaded
r5: not OF (=0)
r13: local_paca address (0?)
anything else?
Did I miss the document on this?
-JX
^ permalink raw reply
* Re: how to get individual patches
From: Grant Likely @ 2006-07-14 18:22 UTC (permalink / raw)
To: dhlii; +Cc: linuxppc-embedded
In-Reply-To: <44B7DEC3.1090308@dlasys.net>
On 7/14/06, David H. Lynch Jr. <dhlii@dlasys.net> wrote:
>
> Thank You git bisect has proven to be incredibly interesting.
>
> One question/problem - maybe an incomplete understanding of git.
>
> What I need to do is get to some version of 2.6.16 - as they all work
> for me.
>
> cut in my patches.
>
> And THEN start bisecting while retaining my patches.
>
> Is that going to work or am I going to have to repatch each time ?
AFAIK, yes you will have to repatch every time; I typically write a
little helper script to lessen the pain:
git bisect good|bad # depends on whether it works or not
patch < [patchfile]
compile, test, etc
cg restore -f # Remove the patches
git bisect good|bad # lather, rinse, repeate
>
> Basically can I use git to insert a patch into the middle of its delta
> history and then advance forward from there ?
I don't think so; no automatically; but if you don't commit your
changes then it's easy to drop the change the patch makes.
git-rebase does something similar to what you're trying to do; but
it's complex to use (especially if there are conflicts) and might
conflict w/ the git-bisect tool
>
> It is rapidly becoming obvious that competence with git could have big
> payback.
:)
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
^ permalink raw reply
* Re: how to get individual patches
From: David H. Lynch Jr. @ 2006-07-14 18:13 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <528646bc0606280209m4ce91cb0wc3cab2f2d3aec1a7@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2057 bytes --]
Grant Likely wrote:
> On 6/28/06, David H. Lynch Jr. <dhlii@dlasys.net> wrote:
>
>> The bsp I am working on works with 2.6.16.21 but fails with 2.6.17.
>>
>> How can I find the individual patches that make up the transition
>> from 2.6.16.21 to 2.6.17 ?
>>
>
> Unfortunately, there isn't a direct line between .16.21 and .17 which
> makes it complicated. Does your bsp work with .16? If so; you can
> use the 'git bisect' command to figure out exactly where the
> regression occured.
>
> If it doesn't work on .16; you can do a bisect between .16 and .16.21
> to figure out what patch is missing between .16 and .17.
>
> $ git bisect good v2.6.16
> $ git bisect bad # the head of the tree
> compile, test, etc.
> $ git bisect good|bad # depends on whether it works or not
> compile, test, etc
> $ git bisect good|bad # you get the idea... repeat until it's narrowed down
> $ git log # see where you are in the git tree.
>
>
Thank You git bisect has proven to be incredibly interesting.
One question/problem - maybe an incomplete understanding of git.
What I need to do is get to some version of 2.6.16 - as they all
work for me.
cut in my patches.
And THEN start bisecting while retaining my patches.
Is that going to work or am I going to have to repatch each time ?
Basically can I use git to insert a patch into the middle of its
delta history and then advance forward from there ?
It is rapidly becoming obvious that competence with git could have
big payback.
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 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
[-- Attachment #2: Type: text/html, Size: 2991 bytes --]
^ permalink raw reply
* Re: [JOB] Senior Embedded Linux Video Engineer
From: Olof Johansson @ 2006-07-14 18:03 UTC (permalink / raw)
To: Tim Bird; +Cc: linuxppc-dev, Stephen Rothwell, linuxppc-embedded
In-Reply-To: <44B7D485.3000604@am.sony.com>
On Fri, Jul 14, 2006 at 10:29:41AM -0700, Tim Bird wrote:
> Wolfgang Denk wrote:
> > In message <20060714184305.4d16550a.sfr@canb.auug.org.au> you wrote:
> >> Richard asked the list admins before he sent this message and we decided
> >> it would be OK if he identifed the message in its subject.
> >
> > Hello List Admins,
> >
> > please keep these lists a technical discussion forum with good
> > signal-noise ration. Don't allow people to spam these lists with job
> > offers or other crap.
>
> To lessen the pressure to do this on lists, how about if CELF
> maintains some kind of job board on its wiki, or creates a separate
> list for this? Some member companies (employee seekers) and
> job seekers have asked about this in the past.
>
> I'll discuss this at our AG meeting next week.
Ick. Why not just create a linuxppc-jobs@ozlabs org instead of hiding it
somewhere in the CELF organization, especially since it's not neccessarily
constrained to embedded jobs? That solves the problem for all involved
parties, those who are looking for jobs or want to be in the loop on
what is going on can subscribe, others can keep away.
Stephen, care to create a list?
Personally, I don't mind getting the ads just to know who is growing
out there and so on, but I don't want them sorted into the folder with
technical stuff, and I don't want to rely on people tagging the subject
right.
-Olof
^ permalink raw reply
* Re: [JOB] Senior Embedded Linux Video Engineer
From: Tim Bird @ 2006-07-14 17:29 UTC (permalink / raw)
To: Wolfgang Denk; +Cc: Stephen Rothwell, linuxppc-embedded, linuxppc-dev
In-Reply-To: <20060714112250.CC266352B36@atlas.denx.de>
Wolfgang Denk wrote:
> In message <20060714184305.4d16550a.sfr@canb.auug.org.au> you wrote:
>> Richard asked the list admins before he sent this message and we decided
>> it would be OK if he identifed the message in its subject.
>
> Hello List Admins,
>
> please keep these lists a technical discussion forum with good
> signal-noise ration. Don't allow people to spam these lists with job
> offers or other crap.
To lessen the pressure to do this on lists, how about if CELF
maintains some kind of job board on its wiki, or creates a separate
list for this? Some member companies (employee seekers) and
job seekers have asked about this in the past.
I'll discuss this at our AG meeting next week.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================
^ permalink raw reply
* Re: JTAG PPC info ?
From: David H. Lynch Jr. @ 2006-07-14 17:04 UTC (permalink / raw)
To: bennett78, linuxppc-embedded
In-Reply-To: <1152888198.44b7ad86a50ed@webmail.digis.net>
[-- Attachment #1: Type: text/plain, Size: 3582 bytes --]
bennett78@digis.net wrote:
> Quoting "David H. Lynch Jr." <dhlii@dlasys.net>:
>
>
>> Has anyone not covered by non-disclosure deciphered the JTAG codes
>> for the PowerPC ?
>>
>
> Is this a big secret or just skimpy Freescale documentation?
> Try emailing:
> Ed.Nuckolls@freescale.com
> This effort could help expand projects such as:
> http://sourceforge.net/projects/jtager/
> for us embedded powerpc users!
>
> For myself, right now I can't get much help from Abatron turning
> on a new MPC5200 design. My approach: debugging modified u-boot code
> running out of RAM....lots of machine checks!
>
It is my understanding that certain aspects of JTAG are specific to
the target (chip) for most devices that information is documented.
Some processors treat the JTAG communications to the processor as
proprietary.
Some make the information readily available.
It is my understanding that the interface to the PPC is only
available under NDA from IBM.
My client is building a wholely OpenSource SDK to support developing
for their target.
They have their own pseudo JTAG interface - on the host side it
emulates a JTAG Parallel port in software.
On the target side it is a full hardware JTAG.
They are trying to get a gdbserver working and there is no
OpenSource GdbServer that includes PPC support.
Right now they have a back burner project decyphering the the PPC
interface and are working through it slowly.
> Frank Bennett
> President
> Mathegraphics,LLC
> Fort Collins,CO
> www.mathegraphics.com
> bennett78@digis.net
>
>
>
>>
>> I have a situation using a custom JTAG interface that is looking to
>> impliment host side PPC debugging. JTAG access and manipulation of most
>> all other JTAG devices on the target is working.
>> Right now the problem is deciphering the JTAG commands etc to the
>> PPC itself.
>>
>>
>>
>> Ria Roy wrote:
>>
>>> Hi,
>>>
>>> Does anyone know if Macriagor's mpDemon is capable of debugging the
>>> linux kernel via the JTAG interface.
>>>
>>> Thanks in advance,
>>> Ria
>>>
>>> _______________________________________________
>>> Linuxppc-embedded mailing list
>>> Linuxppc-embedded@ozlabs.org
>>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>
>>>
>> --
>> Dave Lynch DLA Systems
>> Software Development: Embedded Linux
>> 717.627.3770 dhlii@dlasys.net http://www.dlasys.net
>> fax: 1.253.369.9244 Cell: 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
>>
>>
>
>
>
>
> -------------------------------------------------------
> Email sent through Digis Networks http://www.digis.net/
>
>
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 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
[-- Attachment #2: Type: text/html, Size: 5531 bytes --]
^ permalink raw reply
* Re: some problems on the SystemACE driver.
From: Ameet Patil @ 2006-07-14 16:57 UTC (permalink / raw)
To: Ming Liu; +Cc: linuxppc-embedded
In-Reply-To: <BAY110-F126F439AD69BF8F4FFC0E6B26F0@phx.gbl>
Hi Ming,
> I tried the new patches in such a procedure: download the kernel, apply
> the five Temac patches, apply the patch
> linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch, copy and replace
> xparameters_ml403.h and use the one generated by EDK (I don't know if
> this is right. But there is really no modification in your patch for the
> ml403 xparameters file.). Then make menuconfig, make dep and make
> zImage. Still the same problem as former.
Yes! This procedure is correct. But you still get errors? hmmm... The
log file you sent is too long with mostly unnecessary stuffs. A normal
log "make zImage" without verbose output will suffice. Please can you
send me the new log?
> Is there any problem in the sequence according to which I applied the
> patches? Or other problems? But why the problem still happened? If I
> made a wrong operation, please forgive me because I am a novice. That's
> why I would like to describe the procedure as detailed as possible.
I appreciate you testing the patch. Don't worry... we will solve it. And
I am not an expert either... you probably know more than me!
-Ameet
>
>
>
>> From: Ameet Patil <ammubhai@gmail.com>
>> To: Ming Liu <eemingliu@hotmail.com>
>> CC: linuxppc-embedded@ozlabs.org
>> Subject: Re: some problems on the SystemACE driver.
>> Date: Fri, 14 Jul 2006 16:10:54 +0100
>>
>> Ming,
>> Had a look, both patches define the XILINX_OCP functions which is
>> unavoidable really. I have made some changes only so that it works in
>> your scenario. First apply the TEMAC patch and then this one:
>> https://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch
>>
>
>>
>> Also, I have also made some new changes to the SysAce driver patch. New
>> version is here:
>> https://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2.patch
>>
>
>>
>> No, you donot need to apply all the patches found in my patches folder.
>>
>> Let me know what happens? I think it should work....
>>
>> -Ameet
>>
>> Ming Liu wrote:
>> > Dear Ameet,
>> > The attached is the log file to record the error. Please unzip and
>> > search for "XAssert" to go to the end to see the problem. Also, the
>> > .config file is attached. Please rename the file from config into
>> > .config. The linux version is 2.6.17.1. When you compile the kernel,
>> > please remember to export C_INCLUDE_PATH=....../driver/xilinx_edk.
>> > Thanks for your work.
>> >
>> > Regards
>> > Ming
>> >
>> >
>> >> From: Ameet Patil <ammubhai@gmail.com>
>> >> To: Ming Liu <eemingliu@hotmail.com>
>> >> CC: linuxppc-embedded@ozlabs.org
>> >> Subject: Re: some problems on the SystemACE driver.
>> >> Date: Fri, 14 Jul 2006 12:12:36 +0100
>> >>
>> >> Hi Ming,
>> >> Can you send me the entire text output (in a file) of the
> compilation
>> >> process with errors?
>> >>
>> >> -Ameet
>> >>
>> >> Ming Liu wrote:
>> >> > Dear Ameet,
>> >> >
>> >> >> 1. Which TEMAC patch are you using?
>> >> >>
>> >
> (http://source.mvista.com/~ank/paulus-powerpc/20060309/ppc32_xilinx_edk_temac.patch)
>
>
>> >
>> >
>> >> >>
>> >> >
>> >> > There are five patches in the directory 20060309 whose address is
>> > listed
>> >> > above by you. I applied all of them in my system, because without
> any
>> >> > there will be problems.
>> >> >> 2. After applying the patch, is the driver getting compiled
> directly
>> >> >> without having to select it via "make menuconfig"?
>> >> > No. there is an option named "xilinx 10/100/1000 Mbit TEMAC support"
> in
>> >> > the menuconfig. I must select it and then compile the kernel.
>> >> >> 3. I don't see a Makefile in the drivers/net/xilinx_temac/ folder?
>> >> > I have checked. In my kernel, there is the Makefile. I don't know
> why
>> >> > this happened to you.
>> >> >
>> >> > Let me describe the detailed process I did. First, download the
> kernel
>> >> > 2.6.17.1 (or 2.6.16-rc5). Then apply the five patches for Temac.(If
> I
>> >> > use 2.6.17.1, I need to upgrade some files manually. For 2.6.16,
> there
>> >> > is no problem.) And then apply the patch for SystemACE. Also copy
> and
>> >> > replace the xparameters_ml403.h by my own file generated by EDK.
> Then
>> >> > make menuconfig, selecting both Temac and SystemACE and other basic
>> >> > options. Then make dep and make zImage. During this process, I need
> to
>> >> > modify some little problems which are about the inclusion of some
>> > header
>> >> > files, or specify some lib inclusion directories instead. Then that
>> >> > problem appears. There are some main points: 1. configured for ml403
>> >> > board. 2.both Temac and SystemACE are selected. 3. 5 patches for
> Temac
>> >> > and 1 patch for SystemACE. 4. linux version is 2.6.17 or 2.6.16. I
>> >> > really have no idea why this still happens after your modification.
> So
>> > I
>> >> > have to ask you again.
>> >> >> Ofcourse, I can work my way to compile the driver. But is there any
>> > doc.
>> >> >> present explaining this?
>> >> > Sorry that there is no doc to explain this. I just did following the
>> >> > procedure described above. I am totally lost. The strange thing is,
>> > when
>> >> > I select only one of these two drivers, no problem, but if both,
>> > problem.
>> >> > By the way, I noticed that in the address where I get your patch,
> there
>> >> > is also a patch called linuxppc-2.6.17.1-sysace-1.0.patch which is
> much
>> >> > larger than the 1.1 one. I needn't apply the 1.0 one, right?
>> >> > Thanks for your hard work. Hopefully we can solve the problem.
>> >> > Regards
>> >> > Ming
>> >> >
>> >> > _________________________________________________________________
>> >> > 免费下载 MSN Explorer: http://explorer.msn.com/lccn
>> >> >
>> >
>> > _________________________________________________________________
>> > 免费下载 MSN Explorer: http://explorer.msn.com/lccn #
>> > # Automatically generated make config: don't edit
>> > # Linux kernel version: 2.6.17.1
>> > # Fri Jul 14 15:00:57 2006
>> > #
>> > CONFIG_MMU=y
>> > CONFIG_GENERIC_HARDIRQS=y
>> > CONFIG_RWSEM_XCHGADD_ALGORITHM=y
>> > CONFIG_GENERIC_HWEIGHT=y
>> > CONFIG_GENERIC_CALIBRATE_DELAY=y
>> > CONFIG_PPC=y
>> > CONFIG_PPC32=y
>> > CONFIG_GENERIC_NVRAM=y
>> > CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
>> > CONFIG_ARCH_MAY_HAVE_PC_FDC=y
>> >
>> > #
>> > # Code maturity level options
>> > #
>> > CONFIG_EXPERIMENTAL=y
>> > CONFIG_BROKEN_ON_SMP=y
>> > CONFIG_INIT_ENV_ARG_LIMIT=32
>> >
>> > #
>> > # General setup
>> > #
>> > CONFIG_LOCALVERSION=""
>> > CONFIG_LOCALVERSION_AUTO=y
>> > CONFIG_SWAP=y
>> > CONFIG_SYSVIPC=y
>> > # CONFIG_POSIX_MQUEUE is not set
>> > # CONFIG_BSD_PROCESS_ACCT is not set
>> > CONFIG_SYSCTL=y
>> > # CONFIG_AUDIT is not set
>> > # CONFIG_IKCONFIG is not set
>> > # CONFIG_RELAY is not set
>> > CONFIG_INITRAMFS_SOURCE=""
>> > CONFIG_CC_OPTIMIZE_FOR_SIZE=y
>> > # CONFIG_EMBEDDED is not set
>> > CONFIG_KALLSYMS=y
>> > # CONFIG_KALLSYMS_ALL is not set
>> > # CONFIG_KALLSYMS_EXTRA_PASS is not set
>> > CONFIG_HOTPLUG=y
>> > CONFIG_PRINTK=y
>> > CONFIG_BUG=y
>> > CONFIG_ELF_CORE=y
>> > CONFIG_BASE_FULL=y
>> > CONFIG_FUTEX=y
>> > CONFIG_EPOLL=y
>> > CONFIG_SHMEM=y
>> > CONFIG_SLAB=y
>> > # CONFIG_TINY_SHMEM is not set
>> > CONFIG_BASE_SMALL=0
>> > # CONFIG_SLOB is not set
>> > CONFIG_OBSOLETE_INTERMODULE=y
>> >
>> > #
>> > # Loadable module support
>> > #
>> > # CONFIG_MODULES is not set
>> >
>> > #
>> > # Block layer
>> > #
>> > # CONFIG_LBD is not set
>> > # CONFIG_BLK_DEV_IO_TRACE is not set
>> > # CONFIG_LSF is not set
>> >
>> > #
>> > # IO Schedulers
>> > #
>> > CONFIG_IOSCHED_NOOP=y
>> > CONFIG_IOSCHED_AS=y
>> > CONFIG_IOSCHED_DEADLINE=y
>> > CONFIG_IOSCHED_CFQ=y
>> > 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"
>> >
>> > #
>> > # Processor
>> > #
>> > # CONFIG_6xx is not set
>> > CONFIG_40x=y
>> > # CONFIG_44x is not set
>> > # CONFIG_8xx is not set
>> > # CONFIG_E200 is not set
>> > # CONFIG_E500 is not set
>> > CONFIG_MATH_EMULATION=y
>> > # CONFIG_KEXEC is not set
>> > # CONFIG_CPU_FREQ is not set
>> > CONFIG_4xx=y
>> > # CONFIG_WANT_EARLY_SERIAL is not set
>> >
>> > #
>> > # IBM 4xx options
>> > #
>> > # CONFIG_BUBINGA is not set
>> > # CONFIG_CPCI405 is not set
>> > # CONFIG_EP405 is not set
>> > # CONFIG_REDWOOD_5 is not set
>> > # CONFIG_REDWOOD_6 is not set
>> > # CONFIG_SYCAMORE is not set
>> > # CONFIG_WALNUT is not set
>> > # CONFIG_XILINX_ML300 is not set
>> > CONFIG_XILINX_ML403=y
>> > CONFIG_IBM405_ERR77=y
>> > CONFIG_IBM405_ERR51=y
>> > CONFIG_XILINX_VIRTEX_4_FX=y
>> > CONFIG_XILINX_VIRTEX=y
>> > CONFIG_EMBEDDEDBOOT=y
>> > # CONFIG_PPC4xx_DMA is not set
>> > CONFIG_PPC_GEN550=y
>> > CONFIG_UART0_TTYS0=y
>> > # CONFIG_UART0_TTYS1 is not set
>> > CONFIG_NOT_COHERENT_CACHE=y
>> >
>> > #
>> > # Platform options
>> > #
>> > # CONFIG_PC_KEYBOARD is not set
>> > # CONFIG_HIGHMEM is not set
>> > # CONFIG_HZ_100 is not set
>> > CONFIG_HZ_250=y
>> > # CONFIG_HZ_1000 is not set
>> > CONFIG_HZ=250
>> > CONFIG_PREEMPT_NONE=y
>> > # CONFIG_PREEMPT_VOLUNTARY is not set
>> > # CONFIG_PREEMPT is not set
>> > CONFIG_SELECT_MEMORY_MODEL=y
>> > CONFIG_FLATMEM_MANUAL=y
>> > # CONFIG_DISCONTIGMEM_MANUAL is not set
>> > # CONFIG_SPARSEMEM_MANUAL is not set
>> > CONFIG_FLATMEM=y
>> > CONFIG_FLAT_NODE_MEM_MAP=y
>> > # CONFIG_SPARSEMEM_STATIC is not set
>> > CONFIG_SPLIT_PTLOCK_CPUS=4
>> > CONFIG_BINFMT_ELF=y
>> > # CONFIG_BINFMT_MISC is not set
>> > CONFIG_CMDLINE_BOOL=y
>> > CONFIG_CMDLINE="console=ttyS0,9600 root=/dev/xsa3 rw"
>> > # CONFIG_PM is not set
>> > # CONFIG_SOFTWARE_SUSPEND is not set
>> > CONFIG_SECCOMP=y
>> > CONFIG_ISA_DMA_API=y
>> >
>> > #
>> > # Bus options
>> > #
>> > # CONFIG_PPC_I8259 is not set
>> > # CONFIG_PCI is not set
>> > # CONFIG_PCI_DOMAINS is not set
>> >
>> > #
>> > # PCCARD (PCMCIA/CardBus) support
>> > #
>> > # CONFIG_PCCARD is not set
>> >
>> > #
>> > # Advanced setup
>> > #
>> > # CONFIG_ADVANCED_OPTIONS is not set
>> >
>> > #
>> > # Default settings for advanced configuration options are used
>> > #
>> > CONFIG_HIGHMEM_START=0xfe000000
>> > CONFIG_LOWMEM_SIZE=0x30000000
>> > CONFIG_KERNEL_START=0xc0000000
>> > CONFIG_TASK_SIZE=0x80000000
>> > CONFIG_CONSISTENT_START=0xff100000
>> > CONFIG_CONSISTENT_SIZE=0x00200000
>> > CONFIG_BOOT_LOAD=0x00400000
>> >
>> > #
>> > # Networking
>> > #
>> > CONFIG_NET=y
>> >
>> > #
>> > # Networking options
>> > #
>> > # CONFIG_NETDEBUG is not set
>> > # CONFIG_PACKET is not set
>> > CONFIG_UNIX=y
>> > # CONFIG_NET_KEY is not set
>> > CONFIG_INET=y
>> > CONFIG_IP_MULTICAST=y
>> > # CONFIG_IP_ADVANCED_ROUTER is not set
>> > CONFIG_IP_FIB_HASH=y
>> > CONFIG_IP_PNP=y
>> > CONFIG_IP_PNP_DHCP=y
>> > # CONFIG_IP_PNP_BOOTP is not set
>> > # CONFIG_IP_PNP_RARP is not set
>> > # CONFIG_NET_IPIP is not set
>> > # CONFIG_NET_IPGRE is not set
>> > # CONFIG_IP_MROUTE is not set
>> > # CONFIG_ARPD is not set
>> > CONFIG_SYN_COOKIES=y
>> > # CONFIG_INET_AH is not set
>> > # CONFIG_INET_ESP is not set
>> > # CONFIG_INET_IPCOMP is not set
>> > # CONFIG_INET_XFRM_TUNNEL is not set
>> > # CONFIG_INET_TUNNEL is not set
>> > # CONFIG_INET_DIAG is not set
>> > # CONFIG_TCP_CONG_ADVANCED is not set
>> > CONFIG_TCP_CONG_BIC=y
>> > # CONFIG_IPV6 is not set
>> > # CONFIG_INET6_XFRM_TUNNEL is not set
>> > # CONFIG_INET6_TUNNEL is not set
>> > # CONFIG_NETFILTER is not set
>> >
>> > #
>> > # DCCP Configuration (EXPERIMENTAL)
>> > #
>> > # CONFIG_IP_DCCP is not set
>> >
>> > #
>> > # SCTP Configuration (EXPERIMENTAL)
>> > #
>> > # CONFIG_IP_SCTP is not set
>> >
>> > #
>> > # TIPC Configuration (EXPERIMENTAL)
>> > #
>> > # CONFIG_TIPC is not set
>> > # CONFIG_ATM is not set
>> > # CONFIG_BRIDGE is not set
>> > # CONFIG_VLAN_8021Q is not set
>> > # CONFIG_DECNET is not set
>> > # CONFIG_LLC2 is not set
>> > # CONFIG_IPX is not set
>> > # CONFIG_ATALK is not set
>> > # CONFIG_X25 is not set
>> > # CONFIG_LAPB is not set
>> > # CONFIG_NET_DIVERT is not set
>> > # CONFIG_ECONET is not set
>> > # CONFIG_WAN_ROUTER is not set
>> >
>> > #
>> > # QoS and/or fair queueing
>> > #
>> > # CONFIG_NET_SCHED is not set
>> >
>> > #
>> > # Network testing
>> > #
>> > # CONFIG_NET_PKTGEN is not set
>> > # CONFIG_HAMRADIO is not set
>> > # CONFIG_IRDA is not set
>> > # CONFIG_BT is not set
>> > # CONFIG_IEEE80211 is not set
>> >
>> > #
>> > # Device Drivers
>> > #
>> >
>> > #
>> > # Generic Driver Options
>> > #
>> > CONFIG_STANDALONE=y
>> > CONFIG_PREVENT_FIRMWARE_BUILD=y
>> > # CONFIG_FW_LOADER is not set
>> > # CONFIG_DEBUG_DRIVER is not set
>> >
>> > #
>> > # Connector - unified userspace <-> kernelspace linker
>> > #
>> > # CONFIG_CONNECTOR is not set
>> >
>> > #
>> > # Memory Technology Devices (MTD)
>> > #
>> > CONFIG_MTD=y
>> > # CONFIG_MTD_DEBUG is not set
>> > # CONFIG_MTD_CONCAT is not set
>> > CONFIG_MTD_PARTITIONS=y
>> > CONFIG_MTD_REDBOOT_PARTS=y
>> > CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
>> > # CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
>> > # CONFIG_MTD_REDBOOT_PARTS_READONLY is not set
>> > # CONFIG_MTD_CMDLINE_PARTS is not set
>> >
>> > #
>> > # User Modules And Translation Layers
>> > #
>> > CONFIG_MTD_CHAR=y
>> > CONFIG_MTD_BLOCK=y
>> > # CONFIG_FTL is not set
>> > # CONFIG_NFTL is not set
>> > # CONFIG_INFTL is not set
>> > # CONFIG_RFD_FTL is not set
>> >
>> > #
>> > # RAM/ROM/Flash chip drivers
>> > #
>> > CONFIG_MTD_CFI=y
>> > # CONFIG_MTD_JEDECPROBE is not set
>> > CONFIG_MTD_GEN_PROBE=y
>> > # CONFIG_MTD_CFI_ADV_OPTIONS is not set
>> > CONFIG_MTD_MAP_BANK_WIDTH_1=y
>> > CONFIG_MTD_MAP_BANK_WIDTH_2=y
>> > CONFIG_MTD_MAP_BANK_WIDTH_4=y
>> > # CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
>> > # CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
>> > # CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
>> > CONFIG_MTD_CFI_I1=y
>> > CONFIG_MTD_CFI_I2=y
>> > # CONFIG_MTD_CFI_I4 is not set
>> > # CONFIG_MTD_CFI_I8 is not set
>> > # CONFIG_MTD_CFI_INTELEXT is not set
>> > CONFIG_MTD_CFI_AMDSTD=y
>> > # CONFIG_MTD_CFI_STAA is not set
>> > CONFIG_MTD_CFI_UTIL=y
>> > # CONFIG_MTD_RAM is not set
>> > # CONFIG_MTD_ROM is not set
>> > # CONFIG_MTD_ABSENT is not set
>> > # CONFIG_MTD_OBSOLETE_CHIPS is not set
>> >
>> > #
>> > # Mapping drivers for chip access
>> > #
>> > # CONFIG_MTD_COMPLEX_MAPPINGS is not set
>> > # CONFIG_MTD_PHYSMAP is not set
>> > # CONFIG_MTD_PLATRAM is not set
>> >
>> > #
>> > # Self-contained MTD device drivers
>> > #
>> > # CONFIG_MTD_SLRAM is not set
>> > # CONFIG_MTD_PHRAM is not set
>> > # CONFIG_MTD_MTDRAM is not set
>> > # CONFIG_MTD_BLOCK2MTD is not set
>> >
>> > #
>> > # Disk-On-Chip Device Drivers
>> > #
>> > # CONFIG_MTD_DOC2000 is not set
>> > # CONFIG_MTD_DOC2001 is not set
>> > # CONFIG_MTD_DOC2001PLUS is not set
>> >
>> > #
>> > # NAND Flash Device Drivers
>> > #
>> > # CONFIG_MTD_NAND is not set
>> >
>> > #
>> > # OneNAND Flash Device Drivers
>> > #
>> > # CONFIG_MTD_ONENAND is not set
>> >
>> > #
>> > # Parallel port support
>> > #
>> > # CONFIG_PARPORT is not set
>> >
>> > #
>> > # Plug and Play support
>> > #
>> >
>> > #
>> > # Block devices
>> > #
>> > # CONFIG_BLK_DEV_FD is not set
>> > # CONFIG_BLK_DEV_COW_COMMON is not set
>> > CONFIG_BLK_DEV_LOOP=y
>> > # CONFIG_BLK_DEV_CRYPTOLOOP is not set
>> > CONFIG_XILINX_SYSACE=y
>> > # CONFIG_BLK_DEV_NBD is not set
>> > # CONFIG_BLK_DEV_RAM is not set
>> > # CONFIG_BLK_DEV_INITRD is not set
>> > # CONFIG_CDROM_PKTCDVD is not set
>> > # CONFIG_ATA_OVER_ETH is not set
>> >
>> > #
>> > # ATA/ATAPI/MFM/RLL support
>> > #
>> > # CONFIG_IDE is not set
>> >
>> > #
>> > # SCSI device support
>> > #
>> > # CONFIG_RAID_ATTRS is not set
>> > # CONFIG_SCSI is not set
>> >
>> > #
>> > # Multi-device support (RAID and LVM)
>> > #
>> > # CONFIG_MD is not set
>> >
>> > #
>> > # Fusion MPT device support
>> > #
>> > # CONFIG_FUSION is not set
>> >
>> > #
>> > # IEEE 1394 (FireWire) support
>> > #
>> >
>> > #
>> > # I2O device support
>> > #
>> >
>> > #
>> > # Macintosh device drivers
>> > #
>> > # CONFIG_WINDFARM is not set
>> >
>> > #
>> > # Network device support
>> > #
>> > CONFIG_NETDEVICES=y
>> > # CONFIG_DUMMY is not set
>> > # CONFIG_BONDING is not set
>> > # CONFIG_EQUALIZER is not set
>> > # CONFIG_TUN is not set
>> >
>> > #
>> > # PHY device support
>> > #
>> >
>> > #
>> > # Ethernet (10 or 100Mbit)
>> > #
>> > # CONFIG_NET_ETHERNET is not set
>> > # CONFIG_IBM_EMAC is not set
>> >
>> > #
>> > # Ethernet (1000 Mbit)
>> > #
>> > CONFIG_XILINX_TEMAC=y
>> >
>> > #
>> > # Ethernet (10000 Mbit)
>> > #
>> >
>> > #
>> > # Token Ring devices
>> > #
>> >
>> > #
>> > # Wireless LAN (non-hamradio)
>> > #
>> > # CONFIG_NET_RADIO is not set
>> >
>> > #
>> > # Wan interfaces
>> > #
>> > # CONFIG_WAN is not set
>> > # CONFIG_PPP is not set
>> > # CONFIG_SLIP is not set
>> > # CONFIG_SHAPER is not set
>> > # CONFIG_NETCONSOLE is not set
>> > # CONFIG_NETPOLL is not set
>> > # CONFIG_NET_POLL_CONTROLLER is not set
>> >
>> > #
>> > # ISDN subsystem
>> > #
>> > # CONFIG_ISDN is not set
>> >
>> > #
>> > # Telephony Support
>> > #
>> > # CONFIG_PHONE is not set
>> >
>> > #
>> > # Input device support
>> > #
>> > CONFIG_INPUT=y
>> >
>> > #
>> > # Userland interfaces
>> > #
>> > CONFIG_INPUT_MOUSEDEV=y
>> > CONFIG_INPUT_MOUSEDEV_PSAUX=y
>> > CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
>> > CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
>> > # CONFIG_INPUT_JOYDEV is not set
>> > # CONFIG_INPUT_TSDEV is not set
>> > # CONFIG_INPUT_EVDEV is not set
>> > # CONFIG_INPUT_EVBUG is not set
>> >
>> > #
>> > # Input Device Drivers
>> > #
>> > # CONFIG_INPUT_KEYBOARD is not set
>> > # CONFIG_INPUT_MOUSE is not set
>> > # CONFIG_INPUT_JOYSTICK is not set
>> > # CONFIG_INPUT_TOUCHSCREEN is not set
>> > # CONFIG_INPUT_MISC is not set
>> >
>> > #
>> > # Hardware I/O ports
>> > #
>> > CONFIG_SERIO=y
>> > CONFIG_SERIO_I8042=y
>> > CONFIG_SERIO_SERPORT=y
>> > # CONFIG_SERIO_RAW is not set
>> > # CONFIG_GAMEPORT is not set
>> >
>> > #
>> > # Character devices
>> > #
>> > CONFIG_VT=y
>> > CONFIG_VT_CONSOLE=y
>> > CONFIG_HW_CONSOLE=y
>> > # CONFIG_SERIAL_NONSTANDARD is not set
>> >
>> > #
>> > # Serial drivers
>> > #
>> > CONFIG_SERIAL_8250=y
>> > CONFIG_SERIAL_8250_CONSOLE=y
>> > CONFIG_SERIAL_8250_NR_UARTS=4
>> > CONFIG_SERIAL_8250_RUNTIME_UARTS=4
>> > # CONFIG_SERIAL_8250_EXTENDED is not set
>> >
>> > #
>> > # Non-8250 serial port support
>> > #
>> > CONFIG_SERIAL_CORE=y
>> > CONFIG_SERIAL_CORE_CONSOLE=y
>> > CONFIG_UNIX98_PTYS=y
>> > CONFIG_LEGACY_PTYS=y
>> > CONFIG_LEGACY_PTY_COUNT=256
>> >
>> > #
>> > # IPMI
>> > #
>> > # CONFIG_IPMI_HANDLER is not set
>> >
>> > #
>> > # Watchdog Cards
>> > #
>> > # CONFIG_WATCHDOG is not set
>> > # CONFIG_NVRAM is not set
>> > # CONFIG_GEN_RTC is not set
>> > # CONFIG_DTLK is not set
>> > # CONFIG_R3964 is not set
>> >
>> > #
>> > # Ftape, the floppy tape device driver
>> > #
>> > # CONFIG_AGP is not set
>> > # CONFIG_RAW_DRIVER is not set
>> >
>> > #
>> > # TPM devices
>> > #
>> > # CONFIG_TCG_TPM is not set
>> > # CONFIG_TELCLOCK is not set
>> >
>> > #
>> > # I2C support
>> > #
>> > # CONFIG_I2C is not set
>> >
>> > #
>> > # SPI support
>> > #
>> > # CONFIG_SPI is not set
>> > # CONFIG_SPI_MASTER is not set
>> >
>> > #
>> > # Dallas's 1-wire bus
>> > #
>> > # CONFIG_W1 is not set
>> >
>> > #
>> > # Hardware Monitoring support
>> > #
>> > CONFIG_HWMON=y
>> > # CONFIG_HWMON_VID is not set
>> > # CONFIG_SENSORS_F71805F is not set
>> > # CONFIG_HWMON_DEBUG_CHIP is not set
>> >
>> > #
>> > # Misc devices
>> > #
>> >
>> > #
>> > # Multimedia devices
>> > #
>> > # CONFIG_VIDEO_DEV is not set
>> > CONFIG_VIDEO_V4L2=y
>> >
>> > #
>> > # Digital Video Broadcasting Devices
>> > #
>> > # CONFIG_DVB is not set
>> >
>> > #
>> > # Graphics support
>> > #
>> > # CONFIG_FB is not set
>> >
>> > #
>> > # Console display driver support
>> > #
>> > CONFIG_DUMMY_CONSOLE=y
>> >
>> > #
>> > # Sound
>> > #
>> > # CONFIG_SOUND is not set
>> >
>> > #
>> > # USB support
>> > #
>> > # CONFIG_USB_ARCH_HAS_HCD is not set
>> > # CONFIG_USB_ARCH_HAS_OHCI is not set
>> > # CONFIG_USB_ARCH_HAS_EHCI is not set
>> >
>> > #
>> > # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
>> > #
>> >
>> > #
>> > # USB Gadget Support
>> > #
>> > # CONFIG_USB_GADGET is not set
>> >
>> > #
>> > # MMC/SD Card support
>> > #
>> > # CONFIG_MMC is not set
>> >
>> > #
>> > # LED devices
>> > #
>> > # CONFIG_NEW_LEDS is not set
>> >
>> > #
>> > # LED drivers
>> > #
>> >
>> > #
>> > # LED Triggers
>> > #
>> >
>> > #
>> > # InfiniBand support
>> > #
>> >
>> > #
>> > # EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
>> > #
>> >
>> > #
>> > # Real Time Clock
>> > #
>> > # CONFIG_RTC_CLASS is not set
>> > CONFIG_XILINX_EDK=y
>> >
>> > #
>> > # File systems
>> > #
>> > CONFIG_EXT2_FS=y
>> > CONFIG_EXT2_FS_XATTR=y
>> > CONFIG_EXT2_FS_POSIX_ACL=y
>> > CONFIG_EXT2_FS_SECURITY=y
>> > CONFIG_EXT2_FS_XIP=y
>> > CONFIG_FS_XIP=y
>> > # CONFIG_EXT3_FS is not set
>> > CONFIG_FS_MBCACHE=y
>> > # CONFIG_REISERFS_FS is not set
>> > # CONFIG_JFS_FS is not set
>> > CONFIG_FS_POSIX_ACL=y
>> > # CONFIG_XFS_FS is not set
>> > # CONFIG_OCFS2_FS is not set
>> > # CONFIG_MINIX_FS is not set
>> > # CONFIG_ROMFS_FS is not set
>> > CONFIG_INOTIFY=y
>> > # CONFIG_QUOTA is not set
>> > CONFIG_DNOTIFY=y
>> > CONFIG_AUTOFS_FS=y
>> > CONFIG_AUTOFS4_FS=y
>> > # CONFIG_FUSE_FS is not set
>> >
>> > #
>> > # CD-ROM/DVD Filesystems
>> > #
>> > # CONFIG_ISO9660_FS is not set
>> > # CONFIG_UDF_FS is not set
>> >
>> > #
>> > # DOS/FAT/NT Filesystems
>> > #
>> > # CONFIG_MSDOS_FS is not set
>> > # CONFIG_VFAT_FS is not set
>> > # CONFIG_NTFS_FS is not set
>> >
>> > #
>> > # Pseudo filesystems
>> > #
>> > CONFIG_PROC_FS=y
>> > CONFIG_PROC_KCORE=y
>> > CONFIG_SYSFS=y
>> > CONFIG_TMPFS=y
>> > # CONFIG_HUGETLB_PAGE is not set
>> > CONFIG_RAMFS=y
>> > # CONFIG_CONFIGFS_FS is not set
>> >
>> > #
>> > # Miscellaneous filesystems
>> > #
>> > # CONFIG_ADFS_FS is not set
>> > # CONFIG_AFFS_FS is not set
>> > # CONFIG_HFS_FS is not set
>> > # CONFIG_HFSPLUS_FS is not set
>> > # CONFIG_BEFS_FS is not set
>> > # CONFIG_BFS_FS is not set
>> > # CONFIG_EFS_FS is not set
>> > # CONFIG_JFFS_FS is not set
>> > # CONFIG_JFFS2_FS is not set
>> > # CONFIG_CRAMFS is not set
>> > # CONFIG_VXFS_FS is not set
>> > # CONFIG_HPFS_FS is not set
>> > # CONFIG_QNX4FS_FS is not set
>> > # CONFIG_SYSV_FS is not set
>> > # CONFIG_UFS_FS is not set
>> >
>> > #
>> > # Network File Systems
>> > #
>> > # CONFIG_NFS_FS is not set
>> > # CONFIG_NFSD is not set
>> > # CONFIG_SMB_FS is not set
>> > # CONFIG_CIFS is not set
>> > # CONFIG_NCP_FS is not set
>> > # CONFIG_CODA_FS is not set
>> > # CONFIG_AFS_FS is not set
>> > # CONFIG_9P_FS is not set
>> >
>> > #
>> > # Partition Types
>> > #
>> > # CONFIG_PARTITION_ADVANCED is not set
>> > CONFIG_MSDOS_PARTITION=y
>> >
>> > #
>> > # Native Language Support
>> > #
>> > CONFIG_NLS=y
>> > CONFIG_NLS_DEFAULT="iso8859-1"
>> > # CONFIG_NLS_CODEPAGE_437 is not set
>> > # CONFIG_NLS_CODEPAGE_737 is not set
>> > # CONFIG_NLS_CODEPAGE_775 is not set
>> > # CONFIG_NLS_CODEPAGE_850 is not set
>> > # CONFIG_NLS_CODEPAGE_852 is not set
>> > # CONFIG_NLS_CODEPAGE_855 is not set
>> > # CONFIG_NLS_CODEPAGE_857 is not set
>> > # CONFIG_NLS_CODEPAGE_860 is not set
>> > # CONFIG_NLS_CODEPAGE_861 is not set
>> > # CONFIG_NLS_CODEPAGE_862 is not set
>> > # CONFIG_NLS_CODEPAGE_863 is not set
>> > # CONFIG_NLS_CODEPAGE_864 is not set
>> > # CONFIG_NLS_CODEPAGE_865 is not set
>> > # CONFIG_NLS_CODEPAGE_866 is not set
>> > # CONFIG_NLS_CODEPAGE_869 is not set
>> > # CONFIG_NLS_CODEPAGE_936 is not set
>> > # CONFIG_NLS_CODEPAGE_950 is not set
>> > # CONFIG_NLS_CODEPAGE_932 is not set
>> > # CONFIG_NLS_CODEPAGE_949 is not set
>> > # CONFIG_NLS_CODEPAGE_874 is not set
>> > # CONFIG_NLS_ISO8859_8 is not set
>> > # CONFIG_NLS_CODEPAGE_1250 is not set
>> > # CONFIG_NLS_CODEPAGE_1251 is not set
>> > # CONFIG_NLS_ASCII is not set
>> > # CONFIG_NLS_ISO8859_1 is not set
>> > # CONFIG_NLS_ISO8859_2 is not set
>> > # CONFIG_NLS_ISO8859_3 is not set
>> > # CONFIG_NLS_ISO8859_4 is not set
>> > # CONFIG_NLS_ISO8859_5 is not set
>> > # CONFIG_NLS_ISO8859_6 is not set
>> > # CONFIG_NLS_ISO8859_7 is not set
>> > # CONFIG_NLS_ISO8859_9 is not set
>> > # CONFIG_NLS_ISO8859_13 is not set
>> > # CONFIG_NLS_ISO8859_14 is not set
>> > # CONFIG_NLS_ISO8859_15 is not set
>> > # CONFIG_NLS_KOI8_R is not set
>> > # CONFIG_NLS_KOI8_U is not set
>> > # CONFIG_NLS_UTF8 is not set
>> >
>> > #
>> > # IBM 40x options
>> > #
>> >
>> > #
>> > # Library routines
>> > #
>> > # CONFIG_CRC_CCITT is not set
>> > # CONFIG_CRC16 is not set
>> > CONFIG_CRC32=y
>> > # CONFIG_LIBCRC32C is not set
>> > # CONFIG_PROFILING is not set
>> >
>> > #
>> > # Kernel hacking
>> > #
>> > # CONFIG_PRINTK_TIME is not set
>> > # CONFIG_MAGIC_SYSRQ is not set
>> > CONFIG_DEBUG_KERNEL=y
>> > CONFIG_LOG_BUF_SHIFT=14
>> > CONFIG_DETECT_SOFTLOCKUP=y
>> > # CONFIG_SCHEDSTATS is not set
>> > # CONFIG_DEBUG_SLAB is not set
>> > # CONFIG_DEBUG_MUTEXES is not set
>> > # CONFIG_DEBUG_SPINLOCK is not set
>> > # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
>> > # CONFIG_DEBUG_KOBJECT is not set
>> > CONFIG_DEBUG_INFO=y
>> > # CONFIG_DEBUG_FS is not set
>> > # CONFIG_DEBUG_VM is not set
>> > # CONFIG_UNWIND_INFO is not set
>> > CONFIG_FORCED_INLINING=y
>> > # CONFIG_RCU_TORTURE_TEST is not set
>> > # CONFIG_KGDB is not set
>> > # CONFIG_XMON is not set
>> > CONFIG_BDI_SWITCH=y
>> > # CONFIG_SERIAL_TEXT_DEBUG is not set
>> >
>> > #
>> > # Security options
>> > #
>> > # CONFIG_KEYS is not set
>> > # CONFIG_SECURITY is not set
>> >
>> > #
>> > # Cryptographic options
>> > #
>> > # CONFIG_CRYPTO is not set
>> >
>> > #
>> > # Hardware crypto devices
>> > #
>> >
>
> _________________________________________________________________
> 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
>
^ permalink raw reply
* Re: Xilinx hard TEMAC
From: David H. Lynch Jr. @ 2006-07-14 16:54 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <689CB232690D8D4E97DA6C76DA098E6C029DC841@XCO-EXCHVS1.xlnx.xilinx.com>
Rick Moleres wrote:
> David,
>
> I'll see if I can clarify a bit. In Virtex-4, there is a silicon-based
> Hard TEMAC. But in order to get to it (and have things like buffering
> and DMA) you need a soft wrapper - which comes in two flavors. One is
> the LL_TEMAC, which is released as part of the GSRD reference design.
> The other is PLB_TEMAC, which is released in the EDK. The fundamental
> difference between the two (I'm simplifying) is that the LL_TEMAC and
> GSRD system keep data off the PLB bus, using LocalLink point-to-point
> connections between the LL_TEMAC and the memory and DMA controllers.
> The PLB_TEMAC's data path is over the PLB. The LL_TEMAC also supports
> both channels of the Hard TEMAC, whereas the PLB_TEMAC does not (yet).
> Both are comparable in performance. The PLB_TEMAC, as part of the EDK,
> has the official Xilinx support that other EDK IP has, whereas LL_TEMAC
> and GSRD are just a reference design.
>
Thanks, you have clarified things somewhat. I was vaguely aware of
the differences between the locallink and PLB.
Though I still have some confusion.
In my environment FPGA space is precious. The FPGA firmware for
Linux uses the UartLite, and does not include a PIC.
The objective is to leave as much of the FPGA available for
application use as possible. Some current uses of the remaining FPGA
space have included
decryption engines and FFT's. I am not part of the firmware process
- I am just responsible for Linux and any requests I make that require
more FPGA realestate
tend to get stomped on.
The choice and configuration of the TEMAC was driven by FPGA realestate.
My perception was that the "Hard" Temac was based on silicon already
in the FX (much like the PowerPC) while the "Soft" TEMAC is primarily
implimented within the FPGA (much like the MicroBlaze).
Is that distinction between "soft" and "hard" correct ?
If not is the only significant distinction between the PLB_TEMAC
supported by the EDK and the LL_TEMAC the bus interface ?
I should not think the difference between different bus interfaces
should be radically different in terms of FPGA cells. While implimenting
the MAC in the FPGA would likely be expensive in realestate.
I can try to argue for the PLB_TEMAC - as something that will have
Xilinx/MV support and may get incorporated in the standard Kernel - If
the cost in cells is not substantial.
> The Linux driver posted for the TEMAC (by MontaVista) is for the
> PLB_TEMAC. Updates to this driver may also be released with the EDK
> (e.g., EDK 8.1.2 updated the driver to include checksum offload). There
> is a Linux driver for the LL_TEMAC that comes with GSRD, but my group's
> efforts go toward the PLB_TEMAC as that is the EDK IP we want to promote
> and whose drivers we'd like to see in kernel.org.
>
How can I get a copy of the GSRD LL_TEMAC ? Is it a 2.4 or 2.6 driver ?
> By the way, there is no relation to the IBM EMAC.
>
These things are worth knowing.
The T still means Tri. is there some specific EMAC that was used as
a reference for the design or is the TEMAC entirely a Xilinx creation ?
> Hope that helps,
> -Rick
>
>
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 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
^ permalink raw reply
* Re: [PATCH] Add USB to MPC8349 PB platform support
From: Li Yang @ 2006-07-14 16:21 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-dev, linux-usb-devel
In-Reply-To: <B8AB8BA6-500C-43AC-B6E7-A76CA598A429@kernel.crashing.org>
On 7/14/06, Kumar Gala <galak@kernel.crashing.org> wrote:
> Nack, my expectation is this is all setup by the boot loader.
That's a good wish. ;) However, USB is not required by bootloader. So
it is not likely to be initialized there. And if we put it in
bootloader, it will be hard to change the mode(MPH/DR), which requires
a re-burn of bootloader. It's better that we make sure it's correctly
configured here.
>
> - k
>
> On Jul 14, 2006, at 6:52 AM, Li Yang wrote:
>
> > This adds USB platform support to MPC8349 PB. It works with the
> > fsl_usb2_udc driver.
> >
> > Signed-off-by: Li Yang <leoli@freescale.com>
> > ---
^ permalink raw reply
* Re: some problems on the SystemACE driver.
From: Ming Liu @ 2006-07-14 16:38 UTC (permalink / raw)
To: ammubhai; +Cc: linuxppc-embedded
In-Reply-To: <44B7B3FE.7090904@gmail.com>
Dear Ameet,
I am not so clear with your email. First, I have a question about the patch
linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch. I noticed that in this
patch, there are some modifications to the file xparameters_ml300.h. In my
senario, I configure the platform as ml403 and use xparameters_ml403.h
(copy from EDK BSP and rename the file xparameters_ml300.h as
xparameters_ml403.h). Do you mean to modify the ml403 file, right?
Second, after I patch linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch, I
needn't patch linuxppc-2.6.17.1-sysace-1.2.patch any more, right? I
compared the two patch files and found that the only difference between
them is in linuxppc-2.6.17.1-sysace-1.2.patch, there are some modifications
to do with the file "adapter.c.old" while in
linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch there isn't. I don't think
the file "adapter.c.old" has something to do with the kernel compilation.
I tried the new patches in such a procedure: download the kernel, apply the
five Temac patches, apply the patch
linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch, copy and replace
xparameters_ml403.h and use the one generated by EDK (I don't know if this
is right. But there is really no modification in your patch for the ml403
xparameters file.). Then make menuconfig, make dep and make zImage. Still
the same problem as former.
Is there any problem in the sequence according to which I applied the
patches? Or other problems? But why the problem still happened? If I made a
wrong operation, please forgive me because I am a novice. That's why I
would like to describe the procedure as detailed as possible. Also, please
check it again to solve the problem. Thanks for your hard work.
Regards
Ming
>From: Ameet Patil <ammubhai@gmail.com>
>To: Ming Liu <eemingliu@hotmail.com>
>CC: linuxppc-embedded@ozlabs.org
>Subject: Re: some problems on the SystemACE driver.
>Date: Fri, 14 Jul 2006 16:10:54 +0100
>
>Ming,
> Had a look, both patches define the XILINX_OCP functions which is
>unavoidable really. I have made some changes only so that it works in
>your scenario. First apply the TEMAC patch and then this one:
>https://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch
>
>Also, I have also made some new changes to the SysAce driver patch. New
>version is here:
>https://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2.patch
>
>No, you donot need to apply all the patches found in my patches folder.
>
>Let me know what happens? I think it should work....
>
>-Ameet
>
>Ming Liu wrote:
> > Dear Ameet,
> > The attached is the log file to record the error. Please unzip and
> > search for "XAssert" to go to the end to see the problem. Also, the
> > .config file is attached. Please rename the file from config into
> > .config. The linux version is 2.6.17.1. When you compile the kernel,
> > please remember to export C_INCLUDE_PATH=....../driver/xilinx_edk.
> > Thanks for your work.
> >
> > Regards
> > Ming
> >
> >
> >> From: Ameet Patil <ammubhai@gmail.com>
> >> To: Ming Liu <eemingliu@hotmail.com>
> >> CC: linuxppc-embedded@ozlabs.org
> >> Subject: Re: some problems on the SystemACE driver.
> >> Date: Fri, 14 Jul 2006 12:12:36 +0100
> >>
> >> Hi Ming,
> >> Can you send me the entire text output (in a file) of the
compilation
> >> process with errors?
> >>
> >> -Ameet
> >>
> >> Ming Liu wrote:
> >> > Dear Ameet,
> >> >
> >> >> 1. Which TEMAC patch are you using?
> >> >>
> >
(http://source.mvista.com/~ank/paulus-powerpc/20060309/ppc32_xilinx_edk_temac.patch)
> >
> >
> >> >>
> >> >
> >> > There are five patches in the directory 20060309 whose address is
> > listed
> >> > above by you. I applied all of them in my system, because without
any
> >> > there will be problems.
> >> >> 2. After applying the patch, is the driver getting compiled
directly
> >> >> without having to select it via "make menuconfig"?
> >> > No. there is an option named "xilinx 10/100/1000 Mbit TEMAC support"
in
> >> > the menuconfig. I must select it and then compile the kernel.
> >> >> 3. I don't see a Makefile in the drivers/net/xilinx_temac/ folder?
> >> > I have checked. In my kernel, there is the Makefile. I don't know
why
> >> > this happened to you.
> >> >
> >> > Let me describe the detailed process I did. First, download the
kernel
> >> > 2.6.17.1 (or 2.6.16-rc5). Then apply the five patches for Temac.(If
I
> >> > use 2.6.17.1, I need to upgrade some files manually. For 2.6.16,
there
> >> > is no problem.) And then apply the patch for SystemACE. Also copy
and
> >> > replace the xparameters_ml403.h by my own file generated by EDK.
Then
> >> > make menuconfig, selecting both Temac and SystemACE and other basic
> >> > options. Then make dep and make zImage. During this process, I need
to
> >> > modify some little problems which are about the inclusion of some
> > header
> >> > files, or specify some lib inclusion directories instead. Then that
> >> > problem appears. There are some main points: 1. configured for ml403
> >> > board. 2.both Temac and SystemACE are selected. 3. 5 patches for
Temac
> >> > and 1 patch for SystemACE. 4. linux version is 2.6.17 or 2.6.16. I
> >> > really have no idea why this still happens after your modification.
So
> > I
> >> > have to ask you again.
> >> >> Ofcourse, I can work my way to compile the driver. But is there any
> > doc.
> >> >> present explaining this?
> >> > Sorry that there is no doc to explain this. I just did following the
> >> > procedure described above. I am totally lost. The strange thing is,
> > when
> >> > I select only one of these two drivers, no problem, but if both,
> > problem.
> >> > By the way, I noticed that in the address where I get your patch,
there
> >> > is also a patch called linuxppc-2.6.17.1-sysace-1.0.patch which is
much
> >> > larger than the 1.1 one. I needn't apply the 1.0 one, right?
> >> > Thanks for your hard work. Hopefully we can solve the problem.
> >> > Regards
> >> > Ming
> >> >
> >> > _________________________________________________________________
> >> > 免费下载 MSN Explorer: http://explorer.msn.com/lccn
> >> >
> >
> > _________________________________________________________________
> > 免费下载 MSN Explorer: http://explorer.msn.com/lccn #
> > # Automatically generated make config: don't edit
> > # Linux kernel version: 2.6.17.1
> > # Fri Jul 14 15:00:57 2006
> > #
> > CONFIG_MMU=y
> > CONFIG_GENERIC_HARDIRQS=y
> > CONFIG_RWSEM_XCHGADD_ALGORITHM=y
> > CONFIG_GENERIC_HWEIGHT=y
> > CONFIG_GENERIC_CALIBRATE_DELAY=y
> > CONFIG_PPC=y
> > CONFIG_PPC32=y
> > CONFIG_GENERIC_NVRAM=y
> > CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
> > CONFIG_ARCH_MAY_HAVE_PC_FDC=y
> >
> > #
> > # Code maturity level options
> > #
> > CONFIG_EXPERIMENTAL=y
> > CONFIG_BROKEN_ON_SMP=y
> > CONFIG_INIT_ENV_ARG_LIMIT=32
> >
> > #
> > # General setup
> > #
> > CONFIG_LOCALVERSION=""
> > CONFIG_LOCALVERSION_AUTO=y
> > CONFIG_SWAP=y
> > CONFIG_SYSVIPC=y
> > # CONFIG_POSIX_MQUEUE is not set
> > # CONFIG_BSD_PROCESS_ACCT is not set
> > CONFIG_SYSCTL=y
> > # CONFIG_AUDIT is not set
> > # CONFIG_IKCONFIG is not set
> > # CONFIG_RELAY is not set
> > CONFIG_INITRAMFS_SOURCE=""
> > CONFIG_CC_OPTIMIZE_FOR_SIZE=y
> > # CONFIG_EMBEDDED is not set
> > CONFIG_KALLSYMS=y
> > # CONFIG_KALLSYMS_ALL is not set
> > # CONFIG_KALLSYMS_EXTRA_PASS is not set
> > CONFIG_HOTPLUG=y
> > CONFIG_PRINTK=y
> > CONFIG_BUG=y
> > CONFIG_ELF_CORE=y
> > CONFIG_BASE_FULL=y
> > CONFIG_FUTEX=y
> > CONFIG_EPOLL=y
> > CONFIG_SHMEM=y
> > CONFIG_SLAB=y
> > # CONFIG_TINY_SHMEM is not set
> > CONFIG_BASE_SMALL=0
> > # CONFIG_SLOB is not set
> > CONFIG_OBSOLETE_INTERMODULE=y
> >
> > #
> > # Loadable module support
> > #
> > # CONFIG_MODULES is not set
> >
> > #
> > # Block layer
> > #
> > # CONFIG_LBD is not set
> > # CONFIG_BLK_DEV_IO_TRACE is not set
> > # CONFIG_LSF is not set
> >
> > #
> > # IO Schedulers
> > #
> > CONFIG_IOSCHED_NOOP=y
> > CONFIG_IOSCHED_AS=y
> > CONFIG_IOSCHED_DEADLINE=y
> > CONFIG_IOSCHED_CFQ=y
> > 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"
> >
> > #
> > # Processor
> > #
> > # CONFIG_6xx is not set
> > CONFIG_40x=y
> > # CONFIG_44x is not set
> > # CONFIG_8xx is not set
> > # CONFIG_E200 is not set
> > # CONFIG_E500 is not set
> > CONFIG_MATH_EMULATION=y
> > # CONFIG_KEXEC is not set
> > # CONFIG_CPU_FREQ is not set
> > CONFIG_4xx=y
> > # CONFIG_WANT_EARLY_SERIAL is not set
> >
> > #
> > # IBM 4xx options
> > #
> > # CONFIG_BUBINGA is not set
> > # CONFIG_CPCI405 is not set
> > # CONFIG_EP405 is not set
> > # CONFIG_REDWOOD_5 is not set
> > # CONFIG_REDWOOD_6 is not set
> > # CONFIG_SYCAMORE is not set
> > # CONFIG_WALNUT is not set
> > # CONFIG_XILINX_ML300 is not set
> > CONFIG_XILINX_ML403=y
> > CONFIG_IBM405_ERR77=y
> > CONFIG_IBM405_ERR51=y
> > CONFIG_XILINX_VIRTEX_4_FX=y
> > CONFIG_XILINX_VIRTEX=y
> > CONFIG_EMBEDDEDBOOT=y
> > # CONFIG_PPC4xx_DMA is not set
> > CONFIG_PPC_GEN550=y
> > CONFIG_UART0_TTYS0=y
> > # CONFIG_UART0_TTYS1 is not set
> > CONFIG_NOT_COHERENT_CACHE=y
> >
> > #
> > # Platform options
> > #
> > # CONFIG_PC_KEYBOARD is not set
> > # CONFIG_HIGHMEM is not set
> > # CONFIG_HZ_100 is not set
> > CONFIG_HZ_250=y
> > # CONFIG_HZ_1000 is not set
> > CONFIG_HZ=250
> > CONFIG_PREEMPT_NONE=y
> > # CONFIG_PREEMPT_VOLUNTARY is not set
> > # CONFIG_PREEMPT is not set
> > CONFIG_SELECT_MEMORY_MODEL=y
> > CONFIG_FLATMEM_MANUAL=y
> > # CONFIG_DISCONTIGMEM_MANUAL is not set
> > # CONFIG_SPARSEMEM_MANUAL is not set
> > CONFIG_FLATMEM=y
> > CONFIG_FLAT_NODE_MEM_MAP=y
> > # CONFIG_SPARSEMEM_STATIC is not set
> > CONFIG_SPLIT_PTLOCK_CPUS=4
> > CONFIG_BINFMT_ELF=y
> > # CONFIG_BINFMT_MISC is not set
> > CONFIG_CMDLINE_BOOL=y
> > CONFIG_CMDLINE="console=ttyS0,9600 root=/dev/xsa3 rw"
> > # CONFIG_PM is not set
> > # CONFIG_SOFTWARE_SUSPEND is not set
> > CONFIG_SECCOMP=y
> > CONFIG_ISA_DMA_API=y
> >
> > #
> > # Bus options
> > #
> > # CONFIG_PPC_I8259 is not set
> > # CONFIG_PCI is not set
> > # CONFIG_PCI_DOMAINS is not set
> >
> > #
> > # PCCARD (PCMCIA/CardBus) support
> > #
> > # CONFIG_PCCARD is not set
> >
> > #
> > # Advanced setup
> > #
> > # CONFIG_ADVANCED_OPTIONS is not set
> >
> > #
> > # Default settings for advanced configuration options are used
> > #
> > CONFIG_HIGHMEM_START=0xfe000000
> > CONFIG_LOWMEM_SIZE=0x30000000
> > CONFIG_KERNEL_START=0xc0000000
> > CONFIG_TASK_SIZE=0x80000000
> > CONFIG_CONSISTENT_START=0xff100000
> > CONFIG_CONSISTENT_SIZE=0x00200000
> > CONFIG_BOOT_LOAD=0x00400000
> >
> > #
> > # Networking
> > #
> > CONFIG_NET=y
> >
> > #
> > # Networking options
> > #
> > # CONFIG_NETDEBUG is not set
> > # CONFIG_PACKET is not set
> > CONFIG_UNIX=y
> > # CONFIG_NET_KEY is not set
> > CONFIG_INET=y
> > CONFIG_IP_MULTICAST=y
> > # CONFIG_IP_ADVANCED_ROUTER is not set
> > CONFIG_IP_FIB_HASH=y
> > CONFIG_IP_PNP=y
> > CONFIG_IP_PNP_DHCP=y
> > # CONFIG_IP_PNP_BOOTP is not set
> > # CONFIG_IP_PNP_RARP is not set
> > # CONFIG_NET_IPIP is not set
> > # CONFIG_NET_IPGRE is not set
> > # CONFIG_IP_MROUTE is not set
> > # CONFIG_ARPD is not set
> > CONFIG_SYN_COOKIES=y
> > # CONFIG_INET_AH is not set
> > # CONFIG_INET_ESP is not set
> > # CONFIG_INET_IPCOMP is not set
> > # CONFIG_INET_XFRM_TUNNEL is not set
> > # CONFIG_INET_TUNNEL is not set
> > # CONFIG_INET_DIAG is not set
> > # CONFIG_TCP_CONG_ADVANCED is not set
> > CONFIG_TCP_CONG_BIC=y
> > # CONFIG_IPV6 is not set
> > # CONFIG_INET6_XFRM_TUNNEL is not set
> > # CONFIG_INET6_TUNNEL is not set
> > # CONFIG_NETFILTER is not set
> >
> > #
> > # DCCP Configuration (EXPERIMENTAL)
> > #
> > # CONFIG_IP_DCCP is not set
> >
> > #
> > # SCTP Configuration (EXPERIMENTAL)
> > #
> > # CONFIG_IP_SCTP is not set
> >
> > #
> > # TIPC Configuration (EXPERIMENTAL)
> > #
> > # CONFIG_TIPC is not set
> > # CONFIG_ATM is not set
> > # CONFIG_BRIDGE is not set
> > # CONFIG_VLAN_8021Q is not set
> > # CONFIG_DECNET is not set
> > # CONFIG_LLC2 is not set
> > # CONFIG_IPX is not set
> > # CONFIG_ATALK is not set
> > # CONFIG_X25 is not set
> > # CONFIG_LAPB is not set
> > # CONFIG_NET_DIVERT is not set
> > # CONFIG_ECONET is not set
> > # CONFIG_WAN_ROUTER is not set
> >
> > #
> > # QoS and/or fair queueing
> > #
> > # CONFIG_NET_SCHED is not set
> >
> > #
> > # Network testing
> > #
> > # CONFIG_NET_PKTGEN is not set
> > # CONFIG_HAMRADIO is not set
> > # CONFIG_IRDA is not set
> > # CONFIG_BT is not set
> > # CONFIG_IEEE80211 is not set
> >
> > #
> > # Device Drivers
> > #
> >
> > #
> > # Generic Driver Options
> > #
> > CONFIG_STANDALONE=y
> > CONFIG_PREVENT_FIRMWARE_BUILD=y
> > # CONFIG_FW_LOADER is not set
> > # CONFIG_DEBUG_DRIVER is not set
> >
> > #
> > # Connector - unified userspace <-> kernelspace linker
> > #
> > # CONFIG_CONNECTOR is not set
> >
> > #
> > # Memory Technology Devices (MTD)
> > #
> > CONFIG_MTD=y
> > # CONFIG_MTD_DEBUG is not set
> > # CONFIG_MTD_CONCAT is not set
> > CONFIG_MTD_PARTITIONS=y
> > CONFIG_MTD_REDBOOT_PARTS=y
> > CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
> > # CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
> > # CONFIG_MTD_REDBOOT_PARTS_READONLY is not set
> > # CONFIG_MTD_CMDLINE_PARTS is not set
> >
> > #
> > # User Modules And Translation Layers
> > #
> > CONFIG_MTD_CHAR=y
> > CONFIG_MTD_BLOCK=y
> > # CONFIG_FTL is not set
> > # CONFIG_NFTL is not set
> > # CONFIG_INFTL is not set
> > # CONFIG_RFD_FTL is not set
> >
> > #
> > # RAM/ROM/Flash chip drivers
> > #
> > CONFIG_MTD_CFI=y
> > # CONFIG_MTD_JEDECPROBE is not set
> > CONFIG_MTD_GEN_PROBE=y
> > # CONFIG_MTD_CFI_ADV_OPTIONS is not set
> > CONFIG_MTD_MAP_BANK_WIDTH_1=y
> > CONFIG_MTD_MAP_BANK_WIDTH_2=y
> > CONFIG_MTD_MAP_BANK_WIDTH_4=y
> > # CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
> > # CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
> > # CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
> > CONFIG_MTD_CFI_I1=y
> > CONFIG_MTD_CFI_I2=y
> > # CONFIG_MTD_CFI_I4 is not set
> > # CONFIG_MTD_CFI_I8 is not set
> > # CONFIG_MTD_CFI_INTELEXT is not set
> > CONFIG_MTD_CFI_AMDSTD=y
> > # CONFIG_MTD_CFI_STAA is not set
> > CONFIG_MTD_CFI_UTIL=y
> > # CONFIG_MTD_RAM is not set
> > # CONFIG_MTD_ROM is not set
> > # CONFIG_MTD_ABSENT is not set
> > # CONFIG_MTD_OBSOLETE_CHIPS is not set
> >
> > #
> > # Mapping drivers for chip access
> > #
> > # CONFIG_MTD_COMPLEX_MAPPINGS is not set
> > # CONFIG_MTD_PHYSMAP is not set
> > # CONFIG_MTD_PLATRAM is not set
> >
> > #
> > # Self-contained MTD device drivers
> > #
> > # CONFIG_MTD_SLRAM is not set
> > # CONFIG_MTD_PHRAM is not set
> > # CONFIG_MTD_MTDRAM is not set
> > # CONFIG_MTD_BLOCK2MTD is not set
> >
> > #
> > # Disk-On-Chip Device Drivers
> > #
> > # CONFIG_MTD_DOC2000 is not set
> > # CONFIG_MTD_DOC2001 is not set
> > # CONFIG_MTD_DOC2001PLUS is not set
> >
> > #
> > # NAND Flash Device Drivers
> > #
> > # CONFIG_MTD_NAND is not set
> >
> > #
> > # OneNAND Flash Device Drivers
> > #
> > # CONFIG_MTD_ONENAND is not set
> >
> > #
> > # Parallel port support
> > #
> > # CONFIG_PARPORT is not set
> >
> > #
> > # Plug and Play support
> > #
> >
> > #
> > # Block devices
> > #
> > # CONFIG_BLK_DEV_FD is not set
> > # CONFIG_BLK_DEV_COW_COMMON is not set
> > CONFIG_BLK_DEV_LOOP=y
> > # CONFIG_BLK_DEV_CRYPTOLOOP is not set
> > CONFIG_XILINX_SYSACE=y
> > # CONFIG_BLK_DEV_NBD is not set
> > # CONFIG_BLK_DEV_RAM is not set
> > # CONFIG_BLK_DEV_INITRD is not set
> > # CONFIG_CDROM_PKTCDVD is not set
> > # CONFIG_ATA_OVER_ETH is not set
> >
> > #
> > # ATA/ATAPI/MFM/RLL support
> > #
> > # CONFIG_IDE is not set
> >
> > #
> > # SCSI device support
> > #
> > # CONFIG_RAID_ATTRS is not set
> > # CONFIG_SCSI is not set
> >
> > #
> > # Multi-device support (RAID and LVM)
> > #
> > # CONFIG_MD is not set
> >
> > #
> > # Fusion MPT device support
> > #
> > # CONFIG_FUSION is not set
> >
> > #
> > # IEEE 1394 (FireWire) support
> > #
> >
> > #
> > # I2O device support
> > #
> >
> > #
> > # Macintosh device drivers
> > #
> > # CONFIG_WINDFARM is not set
> >
> > #
> > # Network device support
> > #
> > CONFIG_NETDEVICES=y
> > # CONFIG_DUMMY is not set
> > # CONFIG_BONDING is not set
> > # CONFIG_EQUALIZER is not set
> > # CONFIG_TUN is not set
> >
> > #
> > # PHY device support
> > #
> >
> > #
> > # Ethernet (10 or 100Mbit)
> > #
> > # CONFIG_NET_ETHERNET is not set
> > # CONFIG_IBM_EMAC is not set
> >
> > #
> > # Ethernet (1000 Mbit)
> > #
> > CONFIG_XILINX_TEMAC=y
> >
> > #
> > # Ethernet (10000 Mbit)
> > #
> >
> > #
> > # Token Ring devices
> > #
> >
> > #
> > # Wireless LAN (non-hamradio)
> > #
> > # CONFIG_NET_RADIO is not set
> >
> > #
> > # Wan interfaces
> > #
> > # CONFIG_WAN is not set
> > # CONFIG_PPP is not set
> > # CONFIG_SLIP is not set
> > # CONFIG_SHAPER is not set
> > # CONFIG_NETCONSOLE is not set
> > # CONFIG_NETPOLL is not set
> > # CONFIG_NET_POLL_CONTROLLER is not set
> >
> > #
> > # ISDN subsystem
> > #
> > # CONFIG_ISDN is not set
> >
> > #
> > # Telephony Support
> > #
> > # CONFIG_PHONE is not set
> >
> > #
> > # Input device support
> > #
> > CONFIG_INPUT=y
> >
> > #
> > # Userland interfaces
> > #
> > CONFIG_INPUT_MOUSEDEV=y
> > CONFIG_INPUT_MOUSEDEV_PSAUX=y
> > CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
> > CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
> > # CONFIG_INPUT_JOYDEV is not set
> > # CONFIG_INPUT_TSDEV is not set
> > # CONFIG_INPUT_EVDEV is not set
> > # CONFIG_INPUT_EVBUG is not set
> >
> > #
> > # Input Device Drivers
> > #
> > # CONFIG_INPUT_KEYBOARD is not set
> > # CONFIG_INPUT_MOUSE is not set
> > # CONFIG_INPUT_JOYSTICK is not set
> > # CONFIG_INPUT_TOUCHSCREEN is not set
> > # CONFIG_INPUT_MISC is not set
> >
> > #
> > # Hardware I/O ports
> > #
> > CONFIG_SERIO=y
> > CONFIG_SERIO_I8042=y
> > CONFIG_SERIO_SERPORT=y
> > # CONFIG_SERIO_RAW is not set
> > # CONFIG_GAMEPORT is not set
> >
> > #
> > # Character devices
> > #
> > CONFIG_VT=y
> > CONFIG_VT_CONSOLE=y
> > CONFIG_HW_CONSOLE=y
> > # CONFIG_SERIAL_NONSTANDARD is not set
> >
> > #
> > # Serial drivers
> > #
> > CONFIG_SERIAL_8250=y
> > CONFIG_SERIAL_8250_CONSOLE=y
> > CONFIG_SERIAL_8250_NR_UARTS=4
> > CONFIG_SERIAL_8250_RUNTIME_UARTS=4
> > # CONFIG_SERIAL_8250_EXTENDED is not set
> >
> > #
> > # Non-8250 serial port support
> > #
> > CONFIG_SERIAL_CORE=y
> > CONFIG_SERIAL_CORE_CONSOLE=y
> > CONFIG_UNIX98_PTYS=y
> > CONFIG_LEGACY_PTYS=y
> > CONFIG_LEGACY_PTY_COUNT=256
> >
> > #
> > # IPMI
> > #
> > # CONFIG_IPMI_HANDLER is not set
> >
> > #
> > # Watchdog Cards
> > #
> > # CONFIG_WATCHDOG is not set
> > # CONFIG_NVRAM is not set
> > # CONFIG_GEN_RTC is not set
> > # CONFIG_DTLK is not set
> > # CONFIG_R3964 is not set
> >
> > #
> > # Ftape, the floppy tape device driver
> > #
> > # CONFIG_AGP is not set
> > # CONFIG_RAW_DRIVER is not set
> >
> > #
> > # TPM devices
> > #
> > # CONFIG_TCG_TPM is not set
> > # CONFIG_TELCLOCK is not set
> >
> > #
> > # I2C support
> > #
> > # CONFIG_I2C is not set
> >
> > #
> > # SPI support
> > #
> > # CONFIG_SPI is not set
> > # CONFIG_SPI_MASTER is not set
> >
> > #
> > # Dallas's 1-wire bus
> > #
> > # CONFIG_W1 is not set
> >
> > #
> > # Hardware Monitoring support
> > #
> > CONFIG_HWMON=y
> > # CONFIG_HWMON_VID is not set
> > # CONFIG_SENSORS_F71805F is not set
> > # CONFIG_HWMON_DEBUG_CHIP is not set
> >
> > #
> > # Misc devices
> > #
> >
> > #
> > # Multimedia devices
> > #
> > # CONFIG_VIDEO_DEV is not set
> > CONFIG_VIDEO_V4L2=y
> >
> > #
> > # Digital Video Broadcasting Devices
> > #
> > # CONFIG_DVB is not set
> >
> > #
> > # Graphics support
> > #
> > # CONFIG_FB is not set
> >
> > #
> > # Console display driver support
> > #
> > CONFIG_DUMMY_CONSOLE=y
> >
> > #
> > # Sound
> > #
> > # CONFIG_SOUND is not set
> >
> > #
> > # USB support
> > #
> > # CONFIG_USB_ARCH_HAS_HCD is not set
> > # CONFIG_USB_ARCH_HAS_OHCI is not set
> > # CONFIG_USB_ARCH_HAS_EHCI is not set
> >
> > #
> > # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
> > #
> >
> > #
> > # USB Gadget Support
> > #
> > # CONFIG_USB_GADGET is not set
> >
> > #
> > # MMC/SD Card support
> > #
> > # CONFIG_MMC is not set
> >
> > #
> > # LED devices
> > #
> > # CONFIG_NEW_LEDS is not set
> >
> > #
> > # LED drivers
> > #
> >
> > #
> > # LED Triggers
> > #
> >
> > #
> > # InfiniBand support
> > #
> >
> > #
> > # EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
> > #
> >
> > #
> > # Real Time Clock
> > #
> > # CONFIG_RTC_CLASS is not set
> > CONFIG_XILINX_EDK=y
> >
> > #
> > # File systems
> > #
> > CONFIG_EXT2_FS=y
> > CONFIG_EXT2_FS_XATTR=y
> > CONFIG_EXT2_FS_POSIX_ACL=y
> > CONFIG_EXT2_FS_SECURITY=y
> > CONFIG_EXT2_FS_XIP=y
> > CONFIG_FS_XIP=y
> > # CONFIG_EXT3_FS is not set
> > CONFIG_FS_MBCACHE=y
> > # CONFIG_REISERFS_FS is not set
> > # CONFIG_JFS_FS is not set
> > CONFIG_FS_POSIX_ACL=y
> > # CONFIG_XFS_FS is not set
> > # CONFIG_OCFS2_FS is not set
> > # CONFIG_MINIX_FS is not set
> > # CONFIG_ROMFS_FS is not set
> > CONFIG_INOTIFY=y
> > # CONFIG_QUOTA is not set
> > CONFIG_DNOTIFY=y
> > CONFIG_AUTOFS_FS=y
> > CONFIG_AUTOFS4_FS=y
> > # CONFIG_FUSE_FS is not set
> >
> > #
> > # CD-ROM/DVD Filesystems
> > #
> > # CONFIG_ISO9660_FS is not set
> > # CONFIG_UDF_FS is not set
> >
> > #
> > # DOS/FAT/NT Filesystems
> > #
> > # CONFIG_MSDOS_FS is not set
> > # CONFIG_VFAT_FS is not set
> > # CONFIG_NTFS_FS is not set
> >
> > #
> > # Pseudo filesystems
> > #
> > CONFIG_PROC_FS=y
> > CONFIG_PROC_KCORE=y
> > CONFIG_SYSFS=y
> > CONFIG_TMPFS=y
> > # CONFIG_HUGETLB_PAGE is not set
> > CONFIG_RAMFS=y
> > # CONFIG_CONFIGFS_FS is not set
> >
> > #
> > # Miscellaneous filesystems
> > #
> > # CONFIG_ADFS_FS is not set
> > # CONFIG_AFFS_FS is not set
> > # CONFIG_HFS_FS is not set
> > # CONFIG_HFSPLUS_FS is not set
> > # CONFIG_BEFS_FS is not set
> > # CONFIG_BFS_FS is not set
> > # CONFIG_EFS_FS is not set
> > # CONFIG_JFFS_FS is not set
> > # CONFIG_JFFS2_FS is not set
> > # CONFIG_CRAMFS is not set
> > # CONFIG_VXFS_FS is not set
> > # CONFIG_HPFS_FS is not set
> > # CONFIG_QNX4FS_FS is not set
> > # CONFIG_SYSV_FS is not set
> > # CONFIG_UFS_FS is not set
> >
> > #
> > # Network File Systems
> > #
> > # CONFIG_NFS_FS is not set
> > # CONFIG_NFSD is not set
> > # CONFIG_SMB_FS is not set
> > # CONFIG_CIFS is not set
> > # CONFIG_NCP_FS is not set
> > # CONFIG_CODA_FS is not set
> > # CONFIG_AFS_FS is not set
> > # CONFIG_9P_FS is not set
> >
> > #
> > # Partition Types
> > #
> > # CONFIG_PARTITION_ADVANCED is not set
> > CONFIG_MSDOS_PARTITION=y
> >
> > #
> > # Native Language Support
> > #
> > CONFIG_NLS=y
> > CONFIG_NLS_DEFAULT="iso8859-1"
> > # CONFIG_NLS_CODEPAGE_437 is not set
> > # CONFIG_NLS_CODEPAGE_737 is not set
> > # CONFIG_NLS_CODEPAGE_775 is not set
> > # CONFIG_NLS_CODEPAGE_850 is not set
> > # CONFIG_NLS_CODEPAGE_852 is not set
> > # CONFIG_NLS_CODEPAGE_855 is not set
> > # CONFIG_NLS_CODEPAGE_857 is not set
> > # CONFIG_NLS_CODEPAGE_860 is not set
> > # CONFIG_NLS_CODEPAGE_861 is not set
> > # CONFIG_NLS_CODEPAGE_862 is not set
> > # CONFIG_NLS_CODEPAGE_863 is not set
> > # CONFIG_NLS_CODEPAGE_864 is not set
> > # CONFIG_NLS_CODEPAGE_865 is not set
> > # CONFIG_NLS_CODEPAGE_866 is not set
> > # CONFIG_NLS_CODEPAGE_869 is not set
> > # CONFIG_NLS_CODEPAGE_936 is not set
> > # CONFIG_NLS_CODEPAGE_950 is not set
> > # CONFIG_NLS_CODEPAGE_932 is not set
> > # CONFIG_NLS_CODEPAGE_949 is not set
> > # CONFIG_NLS_CODEPAGE_874 is not set
> > # CONFIG_NLS_ISO8859_8 is not set
> > # CONFIG_NLS_CODEPAGE_1250 is not set
> > # CONFIG_NLS_CODEPAGE_1251 is not set
> > # CONFIG_NLS_ASCII is not set
> > # CONFIG_NLS_ISO8859_1 is not set
> > # CONFIG_NLS_ISO8859_2 is not set
> > # CONFIG_NLS_ISO8859_3 is not set
> > # CONFIG_NLS_ISO8859_4 is not set
> > # CONFIG_NLS_ISO8859_5 is not set
> > # CONFIG_NLS_ISO8859_6 is not set
> > # CONFIG_NLS_ISO8859_7 is not set
> > # CONFIG_NLS_ISO8859_9 is not set
> > # CONFIG_NLS_ISO8859_13 is not set
> > # CONFIG_NLS_ISO8859_14 is not set
> > # CONFIG_NLS_ISO8859_15 is not set
> > # CONFIG_NLS_KOI8_R is not set
> > # CONFIG_NLS_KOI8_U is not set
> > # CONFIG_NLS_UTF8 is not set
> >
> > #
> > # IBM 40x options
> > #
> >
> > #
> > # Library routines
> > #
> > # CONFIG_CRC_CCITT is not set
> > # CONFIG_CRC16 is not set
> > CONFIG_CRC32=y
> > # CONFIG_LIBCRC32C is not set
> > # CONFIG_PROFILING is not set
> >
> > #
> > # Kernel hacking
> > #
> > # CONFIG_PRINTK_TIME is not set
> > # CONFIG_MAGIC_SYSRQ is not set
> > CONFIG_DEBUG_KERNEL=y
> > CONFIG_LOG_BUF_SHIFT=14
> > CONFIG_DETECT_SOFTLOCKUP=y
> > # CONFIG_SCHEDSTATS is not set
> > # CONFIG_DEBUG_SLAB is not set
> > # CONFIG_DEBUG_MUTEXES is not set
> > # CONFIG_DEBUG_SPINLOCK is not set
> > # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
> > # CONFIG_DEBUG_KOBJECT is not set
> > CONFIG_DEBUG_INFO=y
> > # CONFIG_DEBUG_FS is not set
> > # CONFIG_DEBUG_VM is not set
> > # CONFIG_UNWIND_INFO is not set
> > CONFIG_FORCED_INLINING=y
> > # CONFIG_RCU_TORTURE_TEST is not set
> > # CONFIG_KGDB is not set
> > # CONFIG_XMON is not set
> > CONFIG_BDI_SWITCH=y
> > # CONFIG_SERIAL_TEXT_DEBUG is not set
> >
> > #
> > # Security options
> > #
> > # CONFIG_KEYS is not set
> > # CONFIG_SECURITY is not set
> >
> > #
> > # Cryptographic options
> > #
> > # CONFIG_CRYPTO is not set
> >
> > #
> > # Hardware crypto devices
> > #
> >
_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
^ permalink raw reply
* Re: [JOB] Senior Embedded Linux Video Engineer
From: Linas Vepstas @ 2006-07-14 16:38 UTC (permalink / raw)
To: Wolfgang Denk; +Cc: linuxppc-dev, linuxppc-embedded, Stephen Rothwell
In-Reply-To: <20060714162100.E027F352681@atlas.denx.de>
On Fri, Jul 14, 2006 at 06:21:00PM +0200, Wolfgang Denk wrote:
>
> > Should I post our embedded PPC kernel related work openings here?
>
> NO!!!
>
> This is a technical discussion group. Job offerings, commercial ads
> and all this stuff is off topic here. Please re-read the list info at
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded resp. -dev
>
> It says: "...discussions/patches should pertain to software
> development for the kernel core ppc32 embedded processor support and
> any driver/chip/board support for ppc32 based embedded systems."
>
> "Software development". This does not allow for job offers, ads or
> other crap.
I respectfully disagree. There may well be people who would rather
work on PowerPC Linux kernels more than any other thing in the world,
and it is entirely appropriate for job openings for PowerPC Linux kernel
programmers to be posted here.
Much as I would like to be, and not for lack of trying, indpendently
wealthy off some dot-com IPO, so that I may code on whatever I wished,
I have, in fact, failed at this, and must stick to actual employment
to feed, cloth and educate my family. I am not alone.
There is a long precedent for this in academic societies, and you will
find job postings in Nature, Science, Physics Today and American
Mathematical Monthly. Frankly, there simply are not so many job
opporunities that we, much like engineers and scientists in general,
can afford to thumb our noses at them.
If you in fact are especially fortunate, then perhaps you could
mentor someone younger: someone who is hot, smart, and fresh out of
college, a good talent, who has contributed good patches, but is now
faced with the need to find rent and beer money. What advice can you
give them, "tough luck Squidward, go work at the Krusty Krab?"
--linas
^ permalink raw reply
* Re: [JOB] Senior Embedded Linux Video Engineer
From: Wolfgang Denk @ 2006-07-14 16:21 UTC (permalink / raw)
To: bbosch; +Cc: linuxppc-dev, Stephen Rothwell, linuxppc-embedded
In-Reply-To: <17591.43974.871998.267718@waldo.lisle.iphase.com>
In message <17591.43974.871998.267718@waldo.lisle.iphase.com> you wrote:
>
> Should I post our embedded PPC kernel related work openings here?
NO!!!
This is a technical discussion group. Job offerings, commercial ads
and all this stuff is off topic here. Please re-read the list info at
https://ozlabs.org/mailman/listinfo/linuxppc-embedded resp. -dev
It says: "...discussions/patches should pertain to software
development for the kernel core ppc32 embedded processor support and
any driver/chip/board support for ppc32 based embedded systems."
"Software development". This does not allow for job offers, ads or
other crap.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The first thing we do is kill all the lawyers.
(Shakespeare. II Henry VI, Act IV, scene ii)
^ permalink raw reply
* Re: JTAG PPC info ?
From: bennett78 @ 2006-07-14 14:43 UTC (permalink / raw)
To: dhlii, David H. Lynch Jr.; +Cc: linuxppc-embedded
In-Reply-To: <44B6DD86.5080804@dlasys.net>
Quoting "David H. Lynch Jr." <dhlii@dlasys.net>:
> Has anyone not covered by non-disclosure deciphered the JTAG codes
> for the PowerPC ?
Is this a big secret or just skimpy Freescale documentation?
Try emailing:
Ed.Nuckolls@freescale.com
This effort could help expand projects such as:
http://sourceforge.net/projects/jtager/
for us embedded powerpc users!
For myself, right now I can't get much help from Abatron turning
on a new MPC5200 design. My approach: debugging modified u-boot code
running out of RAM....lots of machine checks!
Frank Bennett
President
Mathegraphics,LLC
Fort Collins,CO
www.mathegraphics.com
bennett78@digis.net
>
> I have a situation using a custom JTAG interface that is looking to
> impliment host side PPC debugging. JTAG access and manipulation of most
> all other JTAG devices on the target is working.
> Right now the problem is deciphering the JTAG commands etc to the
> PPC itself.
>
>
>
> Ria Roy wrote:
> > Hi,
> >
> > Does anyone know if Macriagor's mpDemon is capable of debugging the
> > linux kernel via the JTAG interface.
> >
> > Thanks in advance,
> > Ria
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
>
>
> --
> Dave Lynch DLA Systems
> Software Development: Embedded Linux
> 717.627.3770 dhlii@dlasys.net http://www.dlasys.net
> fax: 1.253.369.9244 Cell: 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
>
-------------------------------------------------------
Email sent through Digis Networks http://www.digis.net/
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox