* Re: [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers
From: Mike Kravetz @ 2006-06-15 14:58 UTC (permalink / raw)
To: Arnd Bergmann
Cc: Bryan Rosenburg, linuxppc-dev, Nathan Lynch, Paul Mackerras,
Christopher Yeoh
In-Reply-To: <200606151309.40360.arnd@arndb.de>
On Thu, Jun 15, 2006 at 01:09:39PM +0200, Arnd Bergmann wrote:
> On Thursday 15 June 2006 01:52, Mike Kravetz wrote:
> > I'm really wondering what would be the best way to make these stats
> > available to userspace. As mentioned, putting them into sysfs would
> > violate the one value/one file rule. The use of /proc is discouraged.
> > debugfs was mentioned, but I have never used it. Noticed that debugfs
> > was enabled in the default config (at least for pseries). Looks like
> > that would be the best alternative. Agree?
>
> Debugfs sounds good. If you use one file per hcall, it's probably as
> easy as
But does debugfs have the same one value/one file rule? Thought I could
dump all the data in a single debugfs file.
--
Mike
^ permalink raw reply
* cramfs and crontab timestamp
From: hubert.loewenguth @ 2006-06-15 15:25 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]
hi to the community
I'm not sure here is the good place for my question because it's not
related to the ppc architecture, but i try.
Here is my problem I don't understand:
I have an embended linux 2.4.20 on a 8260 ppc with a cramfs root
file-system I use since 1 year.
Everything works fine.
During the init process, the content of the /etc directory is copy in a
tmpfs file system and then then a tmpfs file-system is mounted on /etc
and fill with the old content.
(thanks to that, I can replace after some files in the /etc by other
specific files store in a little jffs part of the flash with the
customer specific configurations /etc configuration files).
Recently, I've decided to add cron to this platform and something very
strange appear.
My /etc/crontab file is very simple:
-----------------------------------------------
SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=""
HOME=/
#test of cron
* * * * * root echo date >>/tmp/essai
-----------------------------------------------
everything works fine when I boot on a nfs file-system.
But nothing is done (/tmp/essai not created) if I boot on the cramfs
file-system.
And what is the only difference beetwen the two startup:........ the
timestamp of the /etc/crontab (1/1/1970 for crontab coming from the cramfs)
So I try something after having boot on cramfs:
echo "#toto">>/etc/crontab
And ones I have done this, the cron process start to work correctly,
creating and editing the /tmp/essai.
I know that cron verify if the /etc/crontab has changed every mn, so I
think this is the reason it works after, but why does it not see the
first crontab file ?
It's juste like the 1/1/1970 timestamp of /etc/crontab make him
invisible by cron.
Does anyone having an idea or having already encounter this kind of
problem ?
I have find nothing on the web about this or a similar problem.
Thanks for any help
[-- Attachment #2: hubert.loewenguth.vcf --]
[-- Type: text/x-vcard, Size: 285 bytes --]
begin:vcard
fn:Hubert Loewenguth
n:Loewenguth;Hubert
org:Thales Broadcast & Multimedia
adr:;;1 rue de l'hautil;Conflans Ste Honorine;;78700;France
email;internet:hubert.loewenguth@thales-bm.com
title:Software Engineer
tel;work:01-34-90-37-56
x-mozilla-html:TRUE
version:2.1
end:vcard
^ permalink raw reply
* RE: Linuxppc-embedded Digest, Vol 22, Issue 32
From: MZ Majid Khan-amm117 @ 2006-06-15 15:38 UTC (permalink / raw)
To: linuxppc-embedded
Hi Phil.
could you please send me the below Patch file.
Thanks.
Majid
------------------------------------------------------------------------
--------------
Hi guys,
I've written a DMA controller driver for the Marvell Discovery series
(particularly the MV64360, MV64460). It is still a work-in-progress and
comes with many caveats, but I'm happy to share it should anyone be
interested. Some of the caveats include:
- does not support scatter-gather operations yet
- quite limited testing has been performed to date
The 50 kb, 5000 line patch is usually applied to a 2.6.16 kernel which
has already been patched for use with Artesyn boards, particularly the
PmPPC7448, and affects the following files:
linux-2.6.16/arch/ppc/Kconfig
linux-2.6.16/arch/ppc/configs/pmppc744x_defconfig
linux-2.6.16/arch/ppc/platforms/pmppc7447.c
linux-2.6.16/arch/ppc/syslib/Makefile
linux-2.6.16/arch/ppc/syslib/mv64x60.c
linux-2.6.16/arch/ppc/syslib/mv64x6x_dma.c
linux-2.6.16/include/asm-ppc/mv64x60.h
linux-2.6.16/include/asm-ppc/mv64x60_defs.h
linux-2.6.16/include/asm-ppc/mv64x6x_dma.h
linux-2.6.16/include/linux/mv643xx.h
=20
Please let me know if there is anyone would like me to post this patch,
and in what form I should do this.
--=20
Phil
------------------------------------------------------------------------
--------
Previous message: Init dies with unhandled signal 4=20
Next message: help with inittab=20
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]=20
------------------------------------------------------------------------
--------
More information about the Linuxppc-embedded mailing list=20
-----Original Message-----
From:
linuxppc-embedded-bounces+majid.khanmohammedzai=3Dmotorola.com@ozlabs.org=
[mailto:linuxppc-embedded-bounces+majid.khanmohammedzai=3Dmotorola.com@oz=
l
abs.org] On Behalf Of linuxppc-embedded-request@ozlabs.org
Sent: Thursday, June 15, 2006 5:38 PM
To: linuxppc-embedded@ozlabs.org
Subject: Linuxppc-embedded Digest, Vol 22, Issue 32
Send Linuxppc-embedded mailing list submissions to
linuxppc-embedded@ozlabs.org
To subscribe or unsubscribe via the World Wide Web, visit
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
or, via email, send a message with subject or body 'help' to
linuxppc-embedded-request@ozlabs.org
You can reach the person managing the list at
linuxppc-embedded-owner@ozlabs.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of Linuxppc-embedded digest..."
Today's Topics:
1. xilinx ml403 with 2.6 Kernel (Karl Pr?fer)
2. Binding FCC interfaces to device names in reverse order
(Laurent Pinchart)
3. Re: xilinx ml403 with 2.6 Kernel (Karl Pr?fer)
----------------------------------------------------------------------
Message: 1
Date: Thu, 15 Jun 2006 12:20:55 +0200
From: "Karl Pr?fer" <heiguga@gmx.net>
Subject: xilinx ml403 with 2.6 Kernel
To: linuxppc-embedded@ozlabs.org
Message-ID: <20060615102055.39970@gmx.net>
Content-Type: text/plain; charset=3D"iso-8859-1"
Hallo!
I am not perfect in english, so please forgice me my mistakes...
I am trying to get the 2.6 kernel running on my ml403 board...
1. I downloaded paulus tree:
cg-clone
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
myprojectdir
2. I copied my Xilinx BSP in the kernel dir cp -ra <BSPDIR>/*
<KERNELDIR>/
3. I configured the Makefile to use my crosscompiler and the ppc Arch.
I have built a crosstoolchain for a 2.4.26 kernel in past (with
crosstool 0.42).
I know that this toolchain works with a 2.4 kernel...
Can i use this toolchain to compile the 2.6 kernel??
Why do i need a kernel(some headers) to build the croostoolchain??
4. Then I configured the kernel:
#
# Automatically generated make config: don't edit # Linux kernel
version: 2.6.17-rc5 # Wed Jun 14 10:02:22 2006 # CONFIG_MMU=3Dy
CONFIG_GENERIC_HARDIRQS=3Dy CONFIG_RWSEM_XCHGADD_ALGORITHM=3Dy
CONFIG_GENERIC_HWEIGHT=3Dy CONFIG_GENERIC_CALIBRATE_DELAY=3Dy =
CONFIG_PPC=3Dy
CONFIG_PPC32=3Dy CONFIG_GENERIC_NVRAM=3Dy =
CONFIG_GENERIC_FIND_NEXT_BIT=3Dy
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=3Dy
CONFIG_ARCH_MAY_HAVE_PC_FDC=3Dy
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=3Dy
CONFIG_BROKEN_ON_SMP=3Dy
CONFIG_INIT_ENV_ARG_LIMIT=3D32
#
# General setup
#
CONFIG_LOCALVERSION=3D""
# CONFIG_LOCALVERSION_AUTO is not set
# CONFIG_SWAP is not set
CONFIG_SYSVIPC=3Dy
CONFIG_POSIX_MQUEUE=3Dy
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=3Dy
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
# CONFIG_RELAY is not set
CONFIG_INITRAMFS_SOURCE=3D""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set # CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=3Dy # CONFIG_KALLSYMS_ALL is not set #
CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=3Dy =
CONFIG_PRINTK=3Dy
CONFIG_BUG=3Dy CONFIG_ELF_CORE=3Dy CONFIG_BASE_FULL=3Dy CONFIG_FUTEX=3Dy
CONFIG_EPOLL=3Dy CONFIG_SHMEM=3Dy CONFIG_SLAB=3Dy # CONFIG_TINY_SHMEM is =
not
set CONFIG_BASE_SMALL=3D0 # CONFIG_SLOB is not set
#
# Loadable module support
#
CONFIG_MODULES=3Dy
CONFIG_MODULE_UNLOAD=3Dy
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=3Dy
# CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=3Dy
#
# 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=3Dy
CONFIG_IOSCHED_AS=3Dy
CONFIG_IOSCHED_DEADLINE=3Dy
CONFIG_IOSCHED_CFQ=3Dy
CONFIG_DEFAULT_AS=3Dy
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED=3D"anticipatory"
#
# Processor
#
# CONFIG_6xx is not set
CONFIG_40x=3Dy
# CONFIG_44x is not set
# CONFIG_8xx is not set
# CONFIG_E200 is not set
# CONFIG_E500 is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_KEXEC is not set
# CONFIG_CPU_FREQ is not set
CONFIG_4xx=3Dy
# 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=3Dy
CONFIG_IBM405_ERR77=3Dy
CONFIG_IBM405_ERR51=3Dy
CONFIG_XILINX_VIRTEX_4_FX=3Dy
CONFIG_XILINX_VIRTEX=3Dy
CONFIG_EMBEDDEDBOOT=3Dy
# CONFIG_PPC4xx_DMA is not set
CONFIG_PPC_GEN550=3Dy
CONFIG_UART0_TTYS0=3Dy
# CONFIG_UART0_TTYS1 is not set
CONFIG_NOT_COHERENT_CACHE=3Dy
#
# Platform options
#
# CONFIG_PC_KEYBOARD is not set
# CONFIG_HIGHMEM is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=3Dy
# CONFIG_HZ_1000 is not set
CONFIG_HZ=3D250
CONFIG_PREEMPT_NONE=3Dy
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_SELECT_MEMORY_MODEL=3Dy
CONFIG_FLATMEM_MANUAL=3Dy
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=3Dy
CONFIG_FLAT_NODE_MEM_MAP=3Dy
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=3D4
CONFIG_BINFMT_ELF=3Dy
# CONFIG_BINFMT_MISC is not set
CONFIG_CMDLINE_BOOL=3Dy
CONFIG_CMDLINE=3D"console=3DttyS0,9600 ip=3Doff =
root=3D/dev/xsysace/disc0/part3
rw"
# CONFIG_PM is not set
# CONFIG_SOFTWARE_SUSPEND is not set
CONFIG_SECCOMP=3Dy
CONFIG_ISA_DMA_API=3Dy
#
# 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=3D0xfe000000 CONFIG_LOWMEM_SIZE=3D0x30000000
CONFIG_KERNEL_START=3D0xc0000000 CONFIG_TASK_SIZE=3D0x80000000
CONFIG_CONSISTENT_START=3D0xff100000
CONFIG_CONSISTENT_SIZE=3D0x00200000
CONFIG_BOOT_LOAD=3D0x00400000
#
# Networking
#
CONFIG_NET=3Dy
#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=3Dy
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=3Dy
CONFIG_XFRM=3Dy
# CONFIG_XFRM_USER is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=3Dy
CONFIG_IP_MULTICAST=3Dy
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=3Dy
CONFIG_IP_PNP=3Dy
CONFIG_IP_PNP_DHCP=3Dy
CONFIG_IP_PNP_BOOTP=3Dy
# 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=3Dy
CONFIG_INET_AH=3Dy
CONFIG_INET_ESP=3Dy
CONFIG_INET_IPCOMP=3Dy
CONFIG_INET_XFRM_TUNNEL=3Dy
CONFIG_INET_TUNNEL=3Dy
CONFIG_INET_DIAG=3Dy
CONFIG_INET_TCP_DIAG=3Dy
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=3Dy
# 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=3Dy
CONFIG_PREVENT_FIRMWARE_BUILD=3Dy
# 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 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 is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=3Dy
CONFIG_BLK_DEV_RAM_COUNT=3D16
CONFIG_BLK_DEV_RAM_SIZE=3D4096
# 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=3Dy
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# PHY device support
#
# CONFIG_PHYLIB is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=3Dy
# CONFIG_MII is not set
# CONFIG_IBM_EMAC is not set
#
# Ethernet (1000 Mbit)
#
#
# 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=3Dy
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=3Dy
CONFIG_INPUT_MOUSEDEV_PSAUX=3Dy
CONFIG_INPUT_MOUSEDEV_SCREEN_X=3D1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=3D768
# 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=3Dy
CONFIG_KEYBOARD_ATKBD=3Dy
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=3Dy
# CONFIG_INPUT_UINPUT is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=3Dy
CONFIG_SERIO_I8042=3Dy
CONFIG_SERIO_SERPORT=3Dy
CONFIG_SERIO_LIBPS2=3Dy
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=3Dy
CONFIG_VT_CONSOLE=3Dy
CONFIG_HW_CONSOLE=3Dy
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=3Dy
CONFIG_SERIAL_8250_CONSOLE=3Dy
CONFIG_SERIAL_8250_NR_UARTS=3D4
CONFIG_SERIAL_8250_RUNTIME_UARTS=3D4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=3Dy
CONFIG_SERIAL_CORE_CONSOLE=3Dy
CONFIG_UNIX98_PTYS=3Dy
CONFIG_LEGACY_PTYS=3Dy
CONFIG_LEGACY_PTY_COUNT=3D256
#
# 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 is not set
# CONFIG_HWMON_VID is not set
#
# Misc devices
#
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
CONFIG_VIDEO_V4L2=3Dy
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
# CONFIG_FB is not set
#
# Console display driver support
#
CONFIG_DUMMY_CONSOLE=3Dy
#
# 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
#
# File systems
#
CONFIG_EXT2_FS=3Dy
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=3Dy
CONFIG_EXT3_FS_XATTR=3Dy
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=3Dy
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=3Dy
CONFIG_REISERFS_FS=3Dy
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# 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=3Dy
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=3Dy
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# 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_FAT_FS=3Dy
CONFIG_MSDOS_FS=3Dy
CONFIG_VFAT_FS=3Dy
CONFIG_FAT_DEFAULT_CODEPAGE=3D437
CONFIG_FAT_DEFAULT_IOCHARSET=3D"iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=3Dy
# CONFIG_PROC_KCORE is not set
CONFIG_SYSFS=3Dy
CONFIG_TMPFS=3Dy
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=3Dy
# 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_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=3Dy
CONFIG_NFS_V3=3Dy
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=3Dy
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
# CONFIG_ROOT_NFS is not set
CONFIG_LOCKD=3Dy
CONFIG_LOCKD_V4=3Dy
CONFIG_EXPORTFS=3Dy
CONFIG_NFS_COMMON=3Dy
CONFIG_SUNRPC=3Dy
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 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=3Dy
#
# Native Language Support
#
CONFIG_NLS=3Dy
CONFIG_NLS_DEFAULT=3D"iso8859-1"
CONFIG_NLS_CODEPAGE_437=3Dm
# 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=3Dm
# 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 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=3Dy
CONFIG_ZLIB_DEFLATE=3Dy
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_MAGIC_SYSRQ=3Dy
CONFIG_DEBUG_KERNEL=3Dy
CONFIG_LOG_BUF_SHIFT=3D14
CONFIG_DETECT_SOFTLOCKUP=3Dy
# 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 is not set # CONFIG_DEBUG_FS is not set #
CONFIG_DEBUG_VM is not set CONFIG_FORCED_INLINING=3Dy #
CONFIG_RCU_TORTURE_TEST is not set # CONFIG_KGDB is not set #
CONFIG_XMON is not set # CONFIG_BDI_SWITCH is not set #
CONFIG_SERIAL_TEXT_DEBUG is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=3Dy
CONFIG_CRYPTO_HMAC=3Dy
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=3Dy
CONFIG_CRYPTO_SHA1=3Dy
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_DES=3Dy
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
CONFIG_CRYPTO_DEFLATE=3Dy
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_TEST is not set
#
# Hardware crypto devices
#
5. I tried to compile the kernel:
make clean bzImage modules
and get this error:
# Temporary hack until we have migrated to asm-powerpc
CLEAN /home/freaked/WORK/ppc_kernel_2_6_paulus
CLEAN arch/ppc/kernel
CLEAN init
CLEAN usr
CLEAN .tmp_versions
CLEAN .tmp_gas_check
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/genksyms/genksyms.o
HOSTCC scripts/genksyms/lex.o
HOSTCC scripts/genksyms/parse.o
HOSTLD scripts/genksyms/genksyms
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
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
CC init/do_mounts_rd.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/ppc_ksyms.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
arch/powerpc/kernel/signal_32.c: In function `handle_rt_signal':
arch/powerpc/kernel/signal_32.c:763: error: request for member
`vdso_base' in something not a structure or union
arch/powerpc/kernel/signal_32.c:766: error: request for member
`vdso_base' in something not a structure or union
arch/powerpc/kernel/signal_32.c: In function `handle_signal':
arch/powerpc/kernel/signal_32.c:1037: error: request for member
`vdso_base' in something not a structure or union
arch/powerpc/kernel/signal_32.c:1040: error: request for member
`vdso_base' in something not a structure or union
make[1]: *** [arch/powerpc/kernel/signal_32.o] Fehler 1
make: *** [arch/powerpc/kernel] Fehler 2
Could someone please help me to interprete this error??
Could someone send me an working .config file for the kernel?
I would be more then happy when someone could help me!!
Thanks in advanced!!
greetings Robert Zach
heiguga@gmx.net
--=20
Echte DSL-Flatrate dauerhaft f?r 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl
------------------------------
Message: 2
Date: Thu, 15 Jun 2006 13:59:02 +0200
From: Laurent Pinchart <laurent.pinchart@tbox.biz>
Subject: Binding FCC interfaces to device names in reverse order
To: linuxppc-embedded@ozlabs.org
Message-ID: <200606151359.02966.laurent.pinchart@tbox.biz>
Content-Type: text/plain; charset=3D"us-ascii"
Hello,
I'm trying to change the order in which the MPC8248 FCC devices are
bound to network interface names.
The current behaviour is to handle FCC1, FCC2 and FCC3 in that order.
FCC1 is thus mapped to eth0 and FCC2 to eth1 (FCC3 is unused in my
design).
For some reason I'd like to map FCC2 to eth0 and FCC1 to eth1. Interface
names are allocated as devices are registered, so I thought I could
change the detection order by modifying the ppc_sys_platform_devices
array:
ppc_sys_platform_devices[MPC82xx_CPM_FCC1].id =3D 2;
ppc_sys_platform_devices[MPC82xx_CPM_FCC2].id =3D 1;
FCC devices detection is indeed reversed, and FCC2 is mapped to eth0.
Plugging a cable into the FCC2 socket prints a message referencing eth0,
and ifconfig confirms that eth0 is running.
Unfortunately, that's where things stop working. I can't ping FCC1 or
FCC2, no data is received by the kernel.
Does anyone know why changing the device ids breaks the fs_enet driver ?
Laurent Pinchart
------------------------------
Message: 3
Date: Thu, 15 Jun 2006 14:07:36 +0200
From: "Karl Pr?fer" <heiguga@gmx.net>
Subject: Re: xilinx ml403 with 2.6 Kernel
To: linuxppc-embedded@ozlabs.org
Message-ID: <20060615120736.40000@gmx.net>
Content-Type: text/plain; charset=3D"iso-8859-1"
Hello again!
I had a little mistake in my first mail.
I have copied the whole BSP...
Now i have tried to copy only the xparameters_ml403.h in
arch/ppc/platforms/4xx/xparameters/ but get the same error!!
I would be more then happy when somebody could help me.
nice greetings Robert
-------- Original-Nachricht --------
Datum: Thu, 15 Jun 2006 12:20:55 +0200
Von: "Karl Pr?fer" <heiguga@gmx.net>
An: linuxppc-embedded@ozlabs.org
Betreff: xilinx ml403 with 2.6 Kernel
> Hallo!
>=20
> I am not perfect in english, so please forgice me my mistakes...
>=20
> I am trying to get the 2.6 kernel running on my ml403 board...
>=20
> 1. I downloaded paulus tree:
> cg-clone=20
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
> myprojectdir
>=20
>=20
> 2. I copied my Xilinx BSP in the kernel dir cp -ra <BSPDIR>/*=20
> <KERNELDIR>/
>=20
>=20
> 3. I configured the Makefile to use my crosscompiler and the ppc Arch.
> I have built a crosstoolchain for a 2.4.26 kernel in past (with =20
> crosstool 0.42).
> I know that this toolchain works with a 2.4 kernel...
>=20
> Can i use this toolchain to compile the 2.6 kernel??
> Why do i need a kernel(some headers) to build the croostoolchain??
>=20
>=20
> 4. Then I configured the kernel:
> #
> # Automatically generated make config: don't edit # Linux kernel=20
> version: 2.6.17-rc5 # Wed Jun 14 10:02:22 2006 # CONFIG_MMU=3Dy=20
> CONFIG_GENERIC_HARDIRQS=3Dy CONFIG_RWSEM_XCHGADD_ALGORITHM=3Dy=20
> CONFIG_GENERIC_HWEIGHT=3Dy CONFIG_GENERIC_CALIBRATE_DELAY=3Dy =
CONFIG_PPC=3Dy
> CONFIG_PPC32=3Dy CONFIG_GENERIC_NVRAM=3Dy =
CONFIG_GENERIC_FIND_NEXT_BIT=3Dy=20
> CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=3Dy
> CONFIG_ARCH_MAY_HAVE_PC_FDC=3Dy
>=20
> #
> # Code maturity level options
> #
> CONFIG_EXPERIMENTAL=3Dy
> CONFIG_BROKEN_ON_SMP=3Dy
> CONFIG_INIT_ENV_ARG_LIMIT=3D32
>=20
> #
> # General setup
> #
> CONFIG_LOCALVERSION=3D""
> # CONFIG_LOCALVERSION_AUTO is not set
> # CONFIG_SWAP is not set
> CONFIG_SYSVIPC=3Dy
> CONFIG_POSIX_MQUEUE=3Dy
> # CONFIG_BSD_PROCESS_ACCT is not set
> CONFIG_SYSCTL=3Dy
> # CONFIG_AUDIT is not set
> # CONFIG_IKCONFIG is not set
> # CONFIG_RELAY is not set
> CONFIG_INITRAMFS_SOURCE=3D""
> # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set # CONFIG_EMBEDDED is not set=20
> CONFIG_KALLSYMS=3Dy # CONFIG_KALLSYMS_ALL is not set #=20
> CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=3Dy =
CONFIG_PRINTK=3Dy
> CONFIG_BUG=3Dy CONFIG_ELF_CORE=3Dy CONFIG_BASE_FULL=3Dy =
CONFIG_FUTEX=3Dy=20
> CONFIG_EPOLL=3Dy CONFIG_SHMEM=3Dy CONFIG_SLAB=3Dy # CONFIG_TINY_SHMEM =
is not
> set CONFIG_BASE_SMALL=3D0 # CONFIG_SLOB is not set
>=20
> #
> # Loadable module support
> #
> CONFIG_MODULES=3Dy
> CONFIG_MODULE_UNLOAD=3Dy
> # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_MODVERSIONS=3Dy #=20
> CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=3Dy
>=20
> #
> # Block layer
> #
> # CONFIG_LBD is not set
> # CONFIG_BLK_DEV_IO_TRACE is not set
> # CONFIG_LSF is not set
>=20
> #
> # IO Schedulers
> #
> CONFIG_IOSCHED_NOOP=3Dy
> CONFIG_IOSCHED_AS=3Dy
> CONFIG_IOSCHED_DEADLINE=3Dy
> CONFIG_IOSCHED_CFQ=3Dy
> CONFIG_DEFAULT_AS=3Dy
> # CONFIG_DEFAULT_DEADLINE is not set
> # CONFIG_DEFAULT_CFQ is not set
> # CONFIG_DEFAULT_NOOP is not set
> CONFIG_DEFAULT_IOSCHED=3D"anticipatory"
>=20
> #
> # Processor
> #
> # CONFIG_6xx is not set
> CONFIG_40x=3Dy
> # CONFIG_44x is not set
> # CONFIG_8xx is not set
> # CONFIG_E200 is not set
> # CONFIG_E500 is not set
> # CONFIG_MATH_EMULATION is not set
> # CONFIG_KEXEC is not set
> # CONFIG_CPU_FREQ is not set
> CONFIG_4xx=3Dy
> # CONFIG_WANT_EARLY_SERIAL is not set
>=20
> #
> # 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=3Dy
> CONFIG_IBM405_ERR77=3Dy
> CONFIG_IBM405_ERR51=3Dy
> CONFIG_XILINX_VIRTEX_4_FX=3Dy
> CONFIG_XILINX_VIRTEX=3Dy
> CONFIG_EMBEDDEDBOOT=3Dy
> # CONFIG_PPC4xx_DMA is not set
> CONFIG_PPC_GEN550=3Dy
> CONFIG_UART0_TTYS0=3Dy
> # CONFIG_UART0_TTYS1 is not set
> CONFIG_NOT_COHERENT_CACHE=3Dy
>=20
> #
> # Platform options
> #
> # CONFIG_PC_KEYBOARD is not set
> # CONFIG_HIGHMEM is not set
> # CONFIG_HZ_100 is not set
> CONFIG_HZ_250=3Dy
> # CONFIG_HZ_1000 is not set
> CONFIG_HZ=3D250
> CONFIG_PREEMPT_NONE=3Dy
> # CONFIG_PREEMPT_VOLUNTARY is not set
> # CONFIG_PREEMPT is not set
> CONFIG_SELECT_MEMORY_MODEL=3Dy
> CONFIG_FLATMEM_MANUAL=3Dy
> # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is=20
> not set CONFIG_FLATMEM=3Dy CONFIG_FLAT_NODE_MEM_MAP=3Dy #=20
> CONFIG_SPARSEMEM_STATIC is not set
> CONFIG_SPLIT_PTLOCK_CPUS=3D4
> CONFIG_BINFMT_ELF=3Dy
> # CONFIG_BINFMT_MISC is not set
> CONFIG_CMDLINE_BOOL=3Dy
> CONFIG_CMDLINE=3D"console=3DttyS0,9600 ip=3Doff=20
> root=3D/dev/xsysace/disc0/part3 rw"
> # CONFIG_PM is not set
> # CONFIG_SOFTWARE_SUSPEND is not set
> CONFIG_SECCOMP=3Dy
> CONFIG_ISA_DMA_API=3Dy
>=20
> #
> # Bus options
> #
> # CONFIG_PPC_I8259 is not set
> # CONFIG_PCI is not set
> # CONFIG_PCI_DOMAINS is not set
>=20
> #
> # PCCARD (PCMCIA/CardBus) support
> #
> # CONFIG_PCCARD is not set
>=20
> #
> # Advanced setup
> #
> # CONFIG_ADVANCED_OPTIONS is not set
>=20
> #
> # Default settings for advanced configuration options are used #=20
> CONFIG_HIGHMEM_START=3D0xfe000000 CONFIG_LOWMEM_SIZE=3D0x30000000=20
> CONFIG_KERNEL_START=3D0xc0000000 CONFIG_TASK_SIZE=3D0x80000000=20
> CONFIG_CONSISTENT_START=3D0xff100000
> CONFIG_CONSISTENT_SIZE=3D0x00200000
> CONFIG_BOOT_LOAD=3D0x00400000
>=20
> #
> # Networking
> #
> CONFIG_NET=3Dy
>=20
> #
> # Networking options
> #
> # CONFIG_NETDEBUG is not set
> CONFIG_PACKET=3Dy
> # CONFIG_PACKET_MMAP is not set
> CONFIG_UNIX=3Dy
> CONFIG_XFRM=3Dy
> # CONFIG_XFRM_USER is not set
> # CONFIG_NET_KEY is not set
> CONFIG_INET=3Dy
> CONFIG_IP_MULTICAST=3Dy
> # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=3Dy=20
> CONFIG_IP_PNP=3Dy CONFIG_IP_PNP_DHCP=3Dy CONFIG_IP_PNP_BOOTP=3Dy #=20
> CONFIG_IP_PNP_RARP is not set # CONFIG_NET_IPIP is not set #=20
> CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set #=20
> CONFIG_ARPD is not set CONFIG_SYN_COOKIES=3Dy CONFIG_INET_AH=3Dy=20
> CONFIG_INET_ESP=3Dy CONFIG_INET_IPCOMP=3Dy CONFIG_INET_XFRM_TUNNEL=3Dy =
> CONFIG_INET_TUNNEL=3Dy CONFIG_INET_DIAG=3Dy CONFIG_INET_TCP_DIAG=3Dy # =
> CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_BIC=3Dy #=20
> CONFIG_IPV6 is not set # CONFIG_INET6_XFRM_TUNNEL is not set #=20
> CONFIG_INET6_TUNNEL is not set # CONFIG_NETFILTER is not set
>=20
> #
> # DCCP Configuration (EXPERIMENTAL)
> #
> # CONFIG_IP_DCCP is not set
>=20
> #
> # SCTP Configuration (EXPERIMENTAL)
> #
> # CONFIG_IP_SCTP is not set
>=20
> #
> # 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
>=20
> #
> # QoS and/or fair queueing
> #
> # CONFIG_NET_SCHED is not set
>=20
> #
> # 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
>=20
> #
> # Device Drivers
> #
>=20
> #
> # Generic Driver Options
> #
> CONFIG_STANDALONE=3Dy
> CONFIG_PREVENT_FIRMWARE_BUILD=3Dy
> # CONFIG_FW_LOADER is not set
> # CONFIG_DEBUG_DRIVER is not set
>=20
> #
> # Connector - unified userspace <-> kernelspace linker # #=20
> CONFIG_CONNECTOR is not set
>=20
> #
> # Memory Technology Devices (MTD)
> #
> # CONFIG_MTD is not set
>=20
> #
> # Parallel port support
> #
> # CONFIG_PARPORT is not set
>=20
> #
> # Plug and Play support
> #
>=20
> #
> # Block devices
> #
> # CONFIG_BLK_DEV_FD is not set
> # CONFIG_BLK_DEV_COW_COMMON is not set # CONFIG_BLK_DEV_LOOP is not=20
> set # CONFIG_BLK_DEV_NBD is not set CONFIG_BLK_DEV_RAM=3Dy
> CONFIG_BLK_DEV_RAM_COUNT=3D16
> CONFIG_BLK_DEV_RAM_SIZE=3D4096
> # CONFIG_BLK_DEV_INITRD is not set
> # CONFIG_CDROM_PKTCDVD is not set
> # CONFIG_ATA_OVER_ETH is not set
>=20
> #
> # ATA/ATAPI/MFM/RLL support
> #
> # CONFIG_IDE is not set
>=20
> #
> # SCSI device support
> #
> # CONFIG_RAID_ATTRS is not set
> # CONFIG_SCSI is not set
>=20
> #
> # Multi-device support (RAID and LVM)
> #
> # CONFIG_MD is not set
>=20
> #
> # Fusion MPT device support
> #
> # CONFIG_FUSION is not set
>=20
> #
> # IEEE 1394 (FireWire) support
> #
>=20
> #
> # I2O device support
> #
>=20
> #
> # Macintosh device drivers
> #
> # CONFIG_WINDFARM is not set
>=20
> #
> # Network device support
> #
> CONFIG_NETDEVICES=3Dy
> # CONFIG_DUMMY is not set
> # CONFIG_BONDING is not set
> # CONFIG_EQUALIZER is not set
> # CONFIG_TUN is not set
>=20
> #
> # PHY device support
> #
> # CONFIG_PHYLIB is not set
>=20
> #
> # Ethernet (10 or 100Mbit)
> #
> CONFIG_NET_ETHERNET=3Dy
> # CONFIG_MII is not set
> # CONFIG_IBM_EMAC is not set
>=20
> #
> # Ethernet (1000 Mbit)
> #
>=20
> #
> # Ethernet (10000 Mbit)
> #
>=20
> #
> # Token Ring devices
> #
>=20
> #
> # Wireless LAN (non-hamradio)
> #
> # CONFIG_NET_RADIO is not set
>=20
> #
> # 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
>=20
> #
> # ISDN subsystem
> #
> # CONFIG_ISDN is not set
>=20
> #
> # Telephony Support
> #
> # CONFIG_PHONE is not set
>=20
> #
> # Input device support
> #
> CONFIG_INPUT=3Dy
>=20
> #
> # Userland interfaces
> #
> CONFIG_INPUT_MOUSEDEV=3Dy
> CONFIG_INPUT_MOUSEDEV_PSAUX=3Dy
> CONFIG_INPUT_MOUSEDEV_SCREEN_X=3D1024
> CONFIG_INPUT_MOUSEDEV_SCREEN_Y=3D768
> # CONFIG_INPUT_JOYDEV is not set
> # CONFIG_INPUT_TSDEV is not set
> # CONFIG_INPUT_EVDEV is not set
> # CONFIG_INPUT_EVBUG is not set
>=20
> #
> # Input Device Drivers
> #
> CONFIG_INPUT_KEYBOARD=3Dy
> CONFIG_KEYBOARD_ATKBD=3Dy
> # CONFIG_KEYBOARD_SUNKBD is not set
> # CONFIG_KEYBOARD_LKKBD is not set
> # CONFIG_KEYBOARD_XTKBD is not set
> # CONFIG_KEYBOARD_NEWTON is not set
> # CONFIG_INPUT_MOUSE is not set
> # CONFIG_INPUT_JOYSTICK is not set
> # CONFIG_INPUT_TOUCHSCREEN is not set
> CONFIG_INPUT_MISC=3Dy
> # CONFIG_INPUT_UINPUT is not set
>=20
> #
> # Hardware I/O ports
> #
> CONFIG_SERIO=3Dy
> CONFIG_SERIO_I8042=3Dy
> CONFIG_SERIO_SERPORT=3Dy
> CONFIG_SERIO_LIBPS2=3Dy
> # CONFIG_SERIO_RAW is not set
> # CONFIG_GAMEPORT is not set
>=20
> #
> # Character devices
> #
> CONFIG_VT=3Dy
> CONFIG_VT_CONSOLE=3Dy
> CONFIG_HW_CONSOLE=3Dy
> # CONFIG_SERIAL_NONSTANDARD is not set
>=20
> #
> # Serial drivers
> #
> CONFIG_SERIAL_8250=3Dy
> CONFIG_SERIAL_8250_CONSOLE=3Dy
> CONFIG_SERIAL_8250_NR_UARTS=3D4
> CONFIG_SERIAL_8250_RUNTIME_UARTS=3D4
> # CONFIG_SERIAL_8250_EXTENDED is not set
>=20
> #
> # Non-8250 serial port support
> #
> CONFIG_SERIAL_CORE=3Dy
> CONFIG_SERIAL_CORE_CONSOLE=3Dy
> CONFIG_UNIX98_PTYS=3Dy
> CONFIG_LEGACY_PTYS=3Dy
> CONFIG_LEGACY_PTY_COUNT=3D256
>=20
> #
> # IPMI
> #
> # CONFIG_IPMI_HANDLER is not set
>=20
> #
> # 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
>=20
> #
> # Ftape, the floppy tape device driver # # CONFIG_AGP is not set #=20
> CONFIG_RAW_DRIVER is not set
>=20
> #
> # TPM devices
> #
> # CONFIG_TCG_TPM is not set
> # CONFIG_TELCLOCK is not set
>=20
> #
> # I2C support
> #
> # CONFIG_I2C is not set
>=20
> #
> # SPI support
> #
> # CONFIG_SPI is not set
> # CONFIG_SPI_MASTER is not set
>=20
> #
> # Dallas's 1-wire bus
> #
> # CONFIG_W1 is not set
>=20
> #
> # Hardware Monitoring support
> #
> # CONFIG_HWMON is not set
> # CONFIG_HWMON_VID is not set
>=20
> #
> # Misc devices
> #
>=20
> #
> # Multimedia devices
> #
> # CONFIG_VIDEO_DEV is not set
> CONFIG_VIDEO_V4L2=3Dy
>=20
> #
> # Digital Video Broadcasting Devices
> #
> # CONFIG_DVB is not set
>=20
> #
> # Graphics support
> #
> # CONFIG_FB is not set
>=20
> #
> # Console display driver support
> #
> CONFIG_DUMMY_CONSOLE=3Dy
>=20
> #
> # Sound
> #
> # CONFIG_SOUND is not set
>=20
> #
> # 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
>=20
> #
> # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
> #
>=20
> #
> # USB Gadget Support
> #
> # CONFIG_USB_GADGET is not set
>=20
> #
> # MMC/SD Card support
> #
> # CONFIG_MMC is not set
>=20
> #
> # LED devices
> #
> # CONFIG_NEW_LEDS is not set
>=20
> #
> # LED drivers
> #
>=20
> #
> # LED Triggers
> #
>=20
> #
> # InfiniBand support
> #
>=20
> #
> # EDAC - error detection and reporting (RAS) (EXPERIMENTAL) #
>=20
> #
> # Real Time Clock
> #
> # CONFIG_RTC_CLASS is not set
>=20
> #
> # File systems
> #
> CONFIG_EXT2_FS=3Dy
> # CONFIG_EXT2_FS_XATTR is not set
> # CONFIG_EXT2_FS_XIP is not set
> CONFIG_EXT3_FS=3Dy
> CONFIG_EXT3_FS_XATTR=3Dy
> # CONFIG_EXT3_FS_POSIX_ACL is not set
> # CONFIG_EXT3_FS_SECURITY is not set
> CONFIG_JBD=3Dy
> # CONFIG_JBD_DEBUG is not set
> CONFIG_FS_MBCACHE=3Dy
> CONFIG_REISERFS_FS=3Dy
> # CONFIG_REISERFS_CHECK is not set
> # CONFIG_REISERFS_PROC_INFO is not set # CONFIG_REISERFS_FS_XATTR is=20
> not set # CONFIG_JFS_FS is not set # CONFIG_FS_POSIX_ACL is not set #=20
> CONFIG_XFS_FS is not set # CONFIG_OCFS2_FS is not set #=20
> CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set=20
> CONFIG_INOTIFY=3Dy # CONFIG_QUOTA is not set CONFIG_DNOTIFY=3Dy #=20
> CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set #=20
> CONFIG_FUSE_FS is not set
>=20
> #
> # CD-ROM/DVD Filesystems
> #
> # CONFIG_ISO9660_FS is not set
> # CONFIG_UDF_FS is not set
>=20
> #
> # DOS/FAT/NT Filesystems
> #
> CONFIG_FAT_FS=3Dy
> CONFIG_MSDOS_FS=3Dy
> CONFIG_VFAT_FS=3Dy
> CONFIG_FAT_DEFAULT_CODEPAGE=3D437
> CONFIG_FAT_DEFAULT_IOCHARSET=3D"iso8859-1"
> # CONFIG_NTFS_FS is not set
>=20
> #
> # Pseudo filesystems
> #
> CONFIG_PROC_FS=3Dy
> # CONFIG_PROC_KCORE is not set
> CONFIG_SYSFS=3Dy
> CONFIG_TMPFS=3Dy
> # CONFIG_HUGETLB_PAGE is not set
> CONFIG_RAMFS=3Dy
> # CONFIG_CONFIGFS_FS is not set
>=20
> #
> # 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_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
>=20
> #
> # Network File Systems
> #
> CONFIG_NFS_FS=3Dy
> CONFIG_NFS_V3=3Dy
> # CONFIG_NFS_V3_ACL is not set
> # CONFIG_NFS_V4 is not set
> # CONFIG_NFS_DIRECTIO is not set
> CONFIG_NFSD=3Dy
> # CONFIG_NFSD_V3 is not set
> # CONFIG_NFSD_TCP is not set
> # CONFIG_ROOT_NFS is not set
> CONFIG_LOCKD=3Dy
> CONFIG_LOCKD_V4=3Dy
> CONFIG_EXPORTFS=3Dy
> CONFIG_NFS_COMMON=3Dy
> CONFIG_SUNRPC=3Dy
> # CONFIG_RPCSEC_GSS_KRB5 is not set
> # CONFIG_RPCSEC_GSS_SPKM3 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
>=20
> #
> # Partition Types
> #
> # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=3Dy
>=20
> #
> # Native Language Support
> #
> CONFIG_NLS=3Dy
> CONFIG_NLS_DEFAULT=3D"iso8859-1"
> CONFIG_NLS_CODEPAGE_437=3Dm
> # 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=3Dm
> # 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
>=20
> #
> # IBM 40x options
> #
>=20
> #
> # Library routines
> #
> # CONFIG_CRC_CCITT is not set
> # CONFIG_CRC16 is not set
> # CONFIG_CRC32 is not set
> # CONFIG_LIBCRC32C is not set
> CONFIG_ZLIB_INFLATE=3Dy
> CONFIG_ZLIB_DEFLATE=3Dy
> # CONFIG_PROFILING is not set
>=20
> #
> # Kernel hacking
> #
> # CONFIG_PRINTK_TIME is not set
> CONFIG_MAGIC_SYSRQ=3Dy
> CONFIG_DEBUG_KERNEL=3Dy
> CONFIG_LOG_BUF_SHIFT=3D14
> CONFIG_DETECT_SOFTLOCKUP=3Dy
> # 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 is not set # CONFIG_DEBUG_FS is not set #=20
> CONFIG_DEBUG_VM is not set CONFIG_FORCED_INLINING=3Dy #=20
> CONFIG_RCU_TORTURE_TEST is not set # CONFIG_KGDB is not set #=20
> CONFIG_XMON is not set # CONFIG_BDI_SWITCH is not set #=20
> CONFIG_SERIAL_TEXT_DEBUG is not set
>=20
> #
> # Security options
> #
> # CONFIG_KEYS is not set
> # CONFIG_SECURITY is not set
>=20
> #
> # Cryptographic options
> #
> CONFIG_CRYPTO=3Dy
> CONFIG_CRYPTO_HMAC=3Dy
> # CONFIG_CRYPTO_NULL is not set
> # CONFIG_CRYPTO_MD4 is not set
> CONFIG_CRYPTO_MD5=3Dy
> CONFIG_CRYPTO_SHA1=3Dy
> # CONFIG_CRYPTO_SHA256 is not set
> # CONFIG_CRYPTO_SHA512 is not set
> # CONFIG_CRYPTO_WP512 is not set
> # CONFIG_CRYPTO_TGR192 is not set
> CONFIG_CRYPTO_DES=3Dy
> # CONFIG_CRYPTO_BLOWFISH is not set
> # CONFIG_CRYPTO_TWOFISH is not set
> # CONFIG_CRYPTO_SERPENT is not set
> # CONFIG_CRYPTO_AES is not set
> # CONFIG_CRYPTO_CAST5 is not set
> # CONFIG_CRYPTO_CAST6 is not set
> # CONFIG_CRYPTO_TEA is not set
> # CONFIG_CRYPTO_ARC4 is not set
> # CONFIG_CRYPTO_KHAZAD is not set
> # CONFIG_CRYPTO_ANUBIS is not set
> CONFIG_CRYPTO_DEFLATE=3Dy
> # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not=20
> set # CONFIG_CRYPTO_TEST is not set
>=20
> #
> # Hardware crypto devices
> #
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> 5. I tried to compile the kernel:
> make clean bzImage modules
>=20
> and get this error:
> # Temporary hack until we have migrated to asm-powerpc
> CLEAN /home/freaked/WORK/ppc_kernel_2_6_paulus
> CLEAN arch/ppc/kernel
> CLEAN init
> CLEAN usr
> CLEAN .tmp_versions
> CLEAN .tmp_gas_check
> 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=20
> .config #
> SPLIT include/linux/autoconf.h -> include/config/*
> CC arch/ppc/kernel/asm-offsets.s
> GEN include/asm-ppc/asm-offsets.h
> HOSTCC scripts/genksyms/genksyms.o
> HOSTCC scripts/genksyms/lex.o
> HOSTCC scripts/genksyms/parse.o
> HOSTLD scripts/genksyms/genksyms
> CC scripts/mod/empty.o
> HOSTCC scripts/mod/mk_elfconfig
> MKELF scripts/mod/elfconfig.h
> HOSTCC scripts/mod/file2alias.o
> HOSTCC scripts/mod/modpost.o
> HOSTCC scripts/mod/sumversion.o
> HOSTLD scripts/mod/modpost
> 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
> CC init/do_mounts_rd.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/ppc_ksyms.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
> arch/powerpc/kernel/signal_32.c: In function `handle_rt_signal':
> arch/powerpc/kernel/signal_32.c:763: error: request for member
`vdso_base'
> in something not a structure or union
> arch/powerpc/kernel/signal_32.c:766: error: request for member
`vdso_base'
> in something not a structure or union
> arch/powerpc/kernel/signal_32.c: In function `handle_signal':
> arch/powerpc/kernel/signal_32.c:1037: error: request for member=20
> `vdso_base' in something not a structure or union
> arch/powerpc/kernel/signal_32.c:1040: error: request for member=20
> `vdso_base' in something not a structure or union
> make[1]: *** [arch/powerpc/kernel/signal_32.o] Fehler 1
> make: *** [arch/powerpc/kernel] Fehler 2
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> Could someone please help me to interprete this error??
> Could someone send me an working .config file for the kernel?
>=20
> I would be more then happy when someone could help me!!
> Thanks in advanced!!
>=20
> greetings Robert Zach
> heiguga@gmx.net
>=20
>=20
> --
>=20
>=20
> Echte DSL-Flatrate dauerhaft f?r 0,- Euro*!
> "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl=20
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
--=20
Echte DSL-Flatrate dauerhaft f?r 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl
------------------------------
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
End of Linuxppc-embedded Digest, Vol 22, Issue 32
*************************************************
^ permalink raw reply
* Re: cramfs and crontab timestamp
From: hubert.loewenguth @ 2006-06-15 16:04 UTC (permalink / raw)
Cc: linuxppc-embedded
In-Reply-To: <44917BF1.5070700@thales-bm.com>
[-- Attachment #1: Type: text/plain, Size: 2384 bytes --]
Hi
Just a little precision: the /etc "copy/mount" is done before having
start the cron process.
Thanks again if you have an idea.
hubert.loewenguth a écrit :
> hi to the community
>
> I'm not sure here is the good place for my question because it's not
> related to the ppc architecture, but i try.
> Here is my problem I don't understand:
> I have an embended linux 2.4.20 on a 8260 ppc with a cramfs root
> file-system I use since 1 year.
> Everything works fine.
> During the init process, the content of the /etc directory is copy in
> a tmpfs file system and then then a tmpfs file-system is mounted on
> /etc and fill with the old content.
> (thanks to that, I can replace after some files in the /etc by other
> specific files store in a little jffs part of the flash with the
> customer specific configurations /etc configuration files).
>
> Recently, I've decided to add cron to this platform and something very
> strange appear.
> My /etc/crontab file is very simple:
>
> -----------------------------------------------
> SHELL=/bin/sh
> PATH=/sbin:/bin:/usr/sbin:/usr/bin
> MAILTO=""
> HOME=/
>
> #test of cron
> * * * * * root echo date >>/tmp/essai
> -----------------------------------------------
>
> everything works fine when I boot on a nfs file-system.
> But nothing is done (/tmp/essai not created) if I boot on the cramfs
> file-system.
> And what is the only difference beetwen the two startup:........ the
> timestamp of the /etc/crontab (1/1/1970 for crontab coming from the
> cramfs)
>
> So I try something after having boot on cramfs:
> echo "#toto">>/etc/crontab
>
> And ones I have done this, the cron process start to work correctly,
> creating and editing the /tmp/essai.
> I know that cron verify if the /etc/crontab has changed every mn, so I
> think this is the reason it works after, but why does it not see the
> first crontab file ?
> It's juste like the 1/1/1970 timestamp of /etc/crontab make him
> invisible by cron.
>
> Does anyone having an idea or having already encounter this kind of
> problem ?
> I have find nothing on the web about this or a similar problem.
>
> Thanks for any help
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
[-- Attachment #2: hubert.loewenguth.vcf --]
[-- Type: text/x-vcard, Size: 285 bytes --]
begin:vcard
fn:Hubert Loewenguth
n:Loewenguth;Hubert
org:Thales Broadcast & Multimedia
adr:;;1 rue de l'hautil;Conflans Ste Honorine;;78700;France
email;internet:hubert.loewenguth@thales-bm.com
title:Software Engineer
tel;work:01-34-90-37-56
x-mozilla-html:TRUE
version:2.1
end:vcard
^ permalink raw reply
* Re: [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers
From: Arnd Bergmann @ 2006-06-15 16:06 UTC (permalink / raw)
To: Mike Kravetz
Cc: Bryan Rosenburg, linuxppc-dev, Nathan Lynch, Paul Mackerras,
Christopher Yeoh
In-Reply-To: <20060615145826.GA3461@monkey.ibm.com>
On Thursday 15 June 2006 16:58, Mike Kravetz wrote:
> But does debugfs have the same one value/one file rule? =A0Thought I could
> dump all the data in a single debugfs file.
Sure, you could. It just makes it a little more complicated. You probably
need to use a seq_file then.
Arnd <><
^ permalink raw reply
* Re: Problem in PCI initialization
From: G.Muruganandam @ 2006-06-15 19:27 UTC (permalink / raw)
To: Prabhat_Singh, linuxppc-embedded
In-Reply-To: <D8595042F3765A4285B848A78A2C2ED10494917B@bsdmsg002.corp.sa tyam.ad>
[-- Attachment #1: Type: text/plain, Size: 4700 bytes --]
Before testing the PCI in linux, you need to make
sure that the PCI is working under u-boot with out any issues.
Here are the check list.
1. pci long command under u-boot should display
the pci configuration registers of the device in PCI bus
consistently.
2. Check the PCI BAR registers at offset
0x10,0x14 and 0x18 are configured with proper values based on
whether it is a PCI memory mapped device or IO mapped device.
3. Check the TLB setting under U-boot whether it
is set correctly for the PCI memory and/or IO regions.
If you are using the u-boot 1.1.x, you should
look at init.S for the particular board/cpu.
Hope this helps!
Thanks
G.Muruganandam
At 11:39 PM 6/14/2006, Prabhat_Singh wrote:
>Content-class: urn:content-classes:message
>Content-Transfer-Encoding: 7bit
>Content-Type: multipart/alternative;
> boundary="----_=_NextPart_001_01C69046.65DE2215"
>
>Hi all
>I am using MPC8248 based board which has got one PCI interface at 66 MHz .
>
>I am not able to initialize PCI, I am really
>clueless and getting the following errors.
>
>Can any one tell me what is wrong with this?
>
>But I am initializing the pci in uboot also and
>there in uboot able to detect the network card,
>but while boot its give first time the machine
>check exception and then its reseting itself and
>then in second try it (uboot) is working fine.
>Do the register sets in uboot is again read by
>linux during linux PCI initialization?
>
>Someone please help.
>
>## Booting image at ffd00000 ...
>Image Name: Linux-2.4.28-1.3.1-517
>Image Type: PowerPC Linux Kernel Image (gzip compressed)
>Data Size: 643461 Bytes = 628.4 kB
>Load Address: 00000000
>Entry Point: 00000000
>Verifying Checksum ... OK
>Uncompressing Kernel Image ... OK
>## Current stack ends at 0x01FAB390 => set upper limit to 0x00800000
>No initrd
>## Transferring control to Linux (at address 00000000) ...
>Memory BAT mapping: BAT2=32Mb, BAT3=0Mb, residual: 0Mb
>
>Linux version 2.4.28-1.3.1-517
>(root@localhost.localdomain) (gcc version 3.3.4)
>#280 Tue Jun 13 16:17:02 IST 2006
>
>On node 0 totalpages: 8192
>
>zone(0): 8192 pages.
>
>zone(1): 0 pages.
>
>zone(2): 0 pages.
>
>Kernel command line: console=ttyS0,115200 root=1f00
>
>Calibrating delay loop... 266.24 BogoMIPS
>
>Memory: 30712k available (1228k kernel code, 368k data, 64k init, 0k highmem)
>
>Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
>
>Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
>
>Mount cache hash table entries: 512 (order: 0, 4096 bytes)
>
>Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
>
>Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
>
>POSIX conformance testing by UNIFIX
>
>PCI: Probing PCI hardware
>
>Scanning bus 00
>
>Oops: kernel access of bad area, sig: 11
>
>NIP: C000C6DC XER: 00000000 LR: C0003FAC SP:
>C0183DC0 REGS: c0183d10 TRAP: 0300 Not tainted
>
>MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
>
>DAR: 00000024, DSISR: 20000000
>
>TASK = c023a000[14] '¢pÀ }¬' Last syscall: -1
>
>last math 00000000 last altivec 00000000
>
>GPR00: 00000000 C0183DC0 C023A000 C0183E80
>00000024 20000000 C0170000 00000439
>
>GPR08: 00000000 C0183D20 00000000 00000000
>22004084 B5FFFFFF 01FF8000 007FFC1E
>
>GPR16: 00000001 00000000 FFFFFFFF 007FFC00
>00001032 00183E70 00000000 C0003FAC
>
>GPR24: 00000000 00030001 00000008 20000000
>C0183E80 00000024 00000024 00000008
>
>Call backtrace:
>
>C0019384 C0003FAC 00000000 C0003FAC 00000000 C0003FAC C0184214
>
>C0003FAC C0184380 C0003FAC C01844F0 C0003FAC C0184664 C0003FAC
>
>C01847D0 C0003FAC C0184940 C0003FAC C0184AB4 C0003FAC C0184C24
>
>C0003FAC C0184D94 C0003FAC C0184F04 C0003FAC C0185074 C0003FAC
>
>00000000 C0003FAC 00000000 C0003FAC 00000000
>
>Kernel panic: Aiee, killing interrupt handler!
>
>In interrupt handler - not syncing
>
><0>Rebooting in 180 seconds..
>
>
>
>DISCLAIMER:
>This email (including any attachments) is
>intended for the sole use of the intended
>recipient/s and may contain material that is
>CONFIDENTIAL AND PRIVATE COMPANY INFORMATION.
>Any review or reliance by others or copying or
>distribution or forwarding of any or all of the
>contents in this message is STRICTLY PROHIBITED.
>If you are not the intended recipient, please
>contact the sender by email and delete all
>copies; your cooperation in this regard is appreciated..
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
[-- Attachment #2: Type: text/html, Size: 5666 bytes --]
^ permalink raw reply
* MSI support on Linux PCI implementation for Ocotea
From: Shawn Jin @ 2006-06-15 21:14 UTC (permalink / raw)
To: ppcembed, ppcdev
Hi,
I'm looking at the linux PCI implementation, especially MSI support
for Ocotea. And I have some observations and questions about it. Maybe
somebody here can shed some light on them. Thanks.
1. Obviously MSI is supported in Linux 2.6.x, maybe even in 2.4.x. But
MSI implementation seems to support only IOxAPIC on x86 or IA64
architectures, though the implemenation is in generic drivers/pci
tree.
2. Why is the message data defined in a such way shown as follows? Or
does it just follow IOxAPIC's design? Further question is who defines
the format of the message data. The PCI/PCIe specs don't say anything
about the content of the message data register.
struct msg_data {
__u32 vector : 8;
__u32 delivery_mode : 3; /* 000b: FIXED | 001b: lowest prior */
__u32 reserved_1 : 3;
__u32 level : 1; /* 0: deassert | 1: assert */
__u32 trigger : 1; /* 0: edge | 1: level */
__u32 reserved_2 : 16;
} __attribute__ ((packed));
3. How is the pci subsystem initialized on a PPC platform? Is there
any existing document discussing PCI subsystem? Of course I've been
doing a lot internet search and couldn't find too much useful infor.
Thanks a lot,
-Shawn.
^ permalink raw reply
* Interrupt occurs but UIC0 MSR is still 0
From: Chris Dumoulin @ 2006-06-15 21:38 UTC (permalink / raw)
To: linuxppc-embedded
Hi All,
I'm working with a 2.6 linux kernel in a board with a PPC405 in a Virtex
II Pro FPGA. I'm trying to generate interrupts and handle them in a
device driver that I've written.
Here is the sequence of events that happen currently:
1. I generate an interrupt by setting registers in an interrupt
controller we've got in the FPGA (it's a Xilinx LogicCORE OPB Interrupt
Controller).
2. The function do_IRQ, in arch/powerpc/kernel/irq.c, is called.
3. ppc_md.get_irq is called from do_IRQ.
4. ppc_md.get_irq points to ppc4xx_pic_get_irq in
arch/ppc/syslib/ppc4xx_pic.c.
5. ppc4xx_pic_get_irq reads the MSR from UIC0 to determine the IRQ. In
my case, the MSR is all zero, so ppc4xx_pic_get_irq returns -1.
6. After this, we return from the interrupt, and do_IRQ is called again
and again, going through the same steps indefinitely.
I've looked at the UIC0 registers, and the SR, MSR, and ER registers are
all 0. How can an interrupt be triggered, but all the UIC0 bits are 0?
Is it possible that I'm not actually accessing UIC0? I've got the
following in my arch/ppc/platforms/4xx/my_board.h file:
#define DCRN_UIC0_BASE 0x0C0
#define UIC0 DCRN_UIC0_BASE
Any ideas would be appreciated.
Cheers,
Chris Dumoulin
--
*--Christopher Dumoulin--*
Software Team Leader
<http://ics-ltd.com/>
<http://ics-ltd.com/>
Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)
------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only.
If misdirected, please notify us by telephone and confirm that it has
been deleted from your system and any hard copies destroyed. You are
strictly prohibited from using, printing, distributing or disseminating
it or any information contained in it save to the intended recipient.
^ permalink raw reply
* Deerfield Internet connection
From: David H. Lynch Jr. @ 2006-06-15 22:00 UTC (permalink / raw)
To: barbara Lynch-Hughes, linuxppc-embedded, Bill Lynch,
maryJean Glick
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
Comcast finally installed internet at Deerfield.
There is a Linksys 802.11a+b+g Wireless Router in DTL's upstairs office.
The Wireless is setup using WEP security.
The ssid is "deerfield"
the WEP key is either "One Ring" or 40faad1ede
Barbara persuaded Comcast to bring in the service. I beleive it is
on a month-month basis.
--
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: 1435 bytes --]
^ permalink raw reply
* [PATCH]: powerpc: pseries: Print PCI slot location code on failure
From: Linas Vepstas @ 2006-06-15 22:15 UTC (permalink / raw)
To: Paul Mackerras; +Cc: linuxppc-dev, linux-kernel
Resending an older patch (from 28 April) that seems to have fallen
through the cracks, its not in mailine, is not in -mm and its not
controversial (its mostly a printk change). Tested.
--linas
The PCI error recovery code will printk diagnostic info when
a PCI error event occurs. Change the messages to include the slot
location code, which is how most sysadmins will know the device.
Signed-off-by: Linas Vepstas <linas@austin.ibm.com>
----
arch/powerpc/platforms/pseries/eeh_driver.c | 33 ++++++++++++++++------------
1 files changed, 20 insertions(+), 13 deletions(-)
Index: linux-2.6.17-rc6-mm2/arch/powerpc/platforms/pseries/eeh_driver.c
===================================================================
--- linux-2.6.17-rc6-mm2.orig/arch/powerpc/platforms/pseries/eeh_driver.c 2006-06-13 18:13:26.000000000 -0500
+++ linux-2.6.17-rc6-mm2/arch/powerpc/platforms/pseries/eeh_driver.c 2006-06-14 17:42:46.000000000 -0500
@@ -261,16 +261,20 @@ struct pci_dn * handle_eeh_events (struc
struct pci_bus *frozen_bus;
int rc = 0;
enum pci_ers_result result = PCI_ERS_RESULT_NONE;
- const char *pci_str, *drv_str;
+ const char *location, *pci_str, *drv_str;
frozen_dn = find_device_pe(event->dn);
frozen_bus = pcibios_find_pci_bus(frozen_dn);
if (!frozen_dn) {
- printk(KERN_ERR "EEH: Error: Cannot find partition endpoint for %s\n",
- pci_name(event->dev));
+
+ location = (char *) get_property(event->dn, "ibm,loc-code", NULL);
+ printk(KERN_ERR "EEH: Error: Cannot find partition endpoint "
+ "for location=%s pci addr=%s\n",
+ location, pci_name(event->dev));
return NULL;
}
+ location = (char *) get_property(frozen_dn, "ibm,loc-code", NULL);
/* There are two different styles for coming up with the PE.
* In the old style, it was the highest EEH-capable device
@@ -282,8 +286,9 @@ struct pci_dn * handle_eeh_events (struc
frozen_bus = pcibios_find_pci_bus (frozen_dn->parent);
if (!frozen_bus) {
- printk(KERN_ERR "EEH: Cannot find PCI bus for %s\n",
- frozen_dn->full_name);
+ printk(KERN_ERR "EEH: Cannot find PCI bus "
+ "for location=%s dn=%s\n",
+ location, frozen_dn->full_name);
return NULL;
}
@@ -318,8 +323,9 @@ struct pci_dn * handle_eeh_events (struc
eeh_slot_error_detail(frozen_pdn, 1 /* Temporary Error */);
printk(KERN_WARNING
- "EEH: This PCI device has failed %d times since last reboot: %s - %s\n",
- frozen_pdn->eeh_freeze_count, drv_str, pci_str);
+ "EEH: This PCI device has failed %d times since last reboot: "
+ "location=%s driver=%s pci addr=%s\n",
+ frozen_pdn->eeh_freeze_count, location, drv_str, pci_str);
/* Walk the various device drivers attached to this slot through
* a reset sequence, giving each an opportunity to do what it needs
@@ -368,17 +374,18 @@ excess_failures:
* due to actual, failed cards.
*/
printk(KERN_ERR
- "EEH: PCI device %s - %s has failed %d times \n"
- "and has been permanently disabled. Please try reseating\n"
- "this device or replacing it.\n",
- drv_str, pci_str, frozen_pdn->eeh_freeze_count);
+ "EEH: PCI device at location=%s driver=%s pci addr=%s \n"
+ "has failed %d times and has been permanently disabled. \n"
+ "Please try reseating this device or replacing it.\n",
+ location, drv_str, pci_str, frozen_pdn->eeh_freeze_count);
goto perm_error;
hard_fail:
printk(KERN_ERR
- "EEH: Unable to recover from failure of PCI device %s - %s\n"
+ "EEH: Unable to recover from failure of PCI device "
+ "at location=%s driver=%s pci addr=%s \n"
"Please try reseating this device or replacing it.\n",
- drv_str, pci_str);
+ location, drv_str, pci_str);
perm_error:
eeh_slot_error_detail(frozen_pdn, 2 /* Permanent Error */);
^ permalink raw reply
* [PATCH] powerpc: RTAS delay, fix module build breaks
From: John Rose @ 2006-06-15 22:32 UTC (permalink / raw)
To: Paul Mackerras; +Cc: External List, Anton Blanchard
In-Reply-To: <17553.4390.79327.634945@cargo.ozlabs.ibm.com>
Export both news RTAS delay functions, and change the scanlog module to
use the new delay functions.
Signed-off-by: John Rose <johnrose@austin.ibm.com>
---
Respun against the powerpc git tree. Thanks Paul.
2_6_ppc-johnrose/arch/powerpc/kernel/rtas.c | 1 +
2_6_ppc-johnrose/arch/powerpc/platforms/pseries/scanlog.c | 6 +++---
2 files changed, 4 insertions(+), 3 deletions(-)
diff -puN arch/powerpc/kernel/rtas.c~finish_delay_reorg arch/powerpc/kernel/rtas.c
--- 2_6_ppc/arch/powerpc/kernel/rtas.c~finish_delay_reorg 2006-06-15 17:27:20.000000000 -0500
+++ 2_6_ppc-johnrose/arch/powerpc/kernel/rtas.c 2006-06-15 17:28:11.000000000 -0500
@@ -797,6 +797,7 @@ EXPORT_SYMBOL(rtas_call);
EXPORT_SYMBOL(rtas_data_buf);
EXPORT_SYMBOL(rtas_data_buf_lock);
EXPORT_SYMBOL(rtas_busy_delay_time);
+EXPORT_SYMBOL(rtas_busy_delay);
EXPORT_SYMBOL(rtas_get_sensor);
EXPORT_SYMBOL(rtas_get_power_level);
EXPORT_SYMBOL(rtas_set_power_level);
diff -puN arch/powerpc/platforms/pseries/scanlog.c~finish_delay_reorg arch/powerpc/platforms/pseries/scanlog.c
--- 2_6_ppc/arch/powerpc/platforms/pseries/scanlog.c~finish_delay_reorg 2006-06-15 17:28:30.000000000 -0500
+++ 2_6_ppc-johnrose/arch/powerpc/platforms/pseries/scanlog.c 2006-06-15 17:29:30.000000000 -0500
@@ -107,9 +107,9 @@ static ssize_t scanlog_read(struct file
/* Break to sleep default time */
break;
default:
- if (status > 9900 && status <= 9905) {
- wait_time = rtas_extended_busy_delay_time(status);
- } else {
+ /* Assume extended busy */
+ wait_time = rtas_busy_delay_time(status);
+ if (!wait_time) {
printk(KERN_ERR "scanlog: unknown error from rtas: %d\n", status);
return -EIO;
}
_
^ permalink raw reply
* Re: [PATCH]: powerpc: pseries: Print PCI slot location code on failure
From: Paul Mackerras @ 2006-06-15 22:42 UTC (permalink / raw)
To: Linas Vepstas; +Cc: linuxppc-dev, linux-kernel
In-Reply-To: <20060615221527.GD12389@austin.ibm.com>
Linas Vepstas writes:
> Resending an older patch (from 28 April) that seems to have fallen
> through the cracks, its not in mailine, is not in -mm and its not
> controversial (its mostly a printk change). Tested.
I don't like doing printk on things that might be NULL (i.e. the
result of get_property). Even though printk doesn't crash, it would
be nicer for the user to see "location=unknown" or something rather
than "location=<NULL>".
Paul.
^ permalink raw reply
* Re: MSI support on Linux PCI implementation for Ocotea
From: Benjamin Herrenschmidt @ 2006-06-15 23:22 UTC (permalink / raw)
To: Shawn Jin; +Cc: ppcdev, ppcembed
In-Reply-To: <c3d0340b0606151414q6d218554j255fa74a68a5c9af@mail.gmail.com>
On Thu, 2006-06-15 at 14:14 -0700, Shawn Jin wrote:
> Hi,
>
> I'm looking at the linux PCI implementation, especially MSI support
> for Ocotea. And I have some observations and questions about it. Maybe
> somebody here can shed some light on them. Thanks.
Hi ! What is Ocotea ! :)
> 1. Obviously MSI is supported in Linux 2.6.x, maybe even in 2.4.x. But
> MSI implementation seems to support only IOxAPIC on x86 or IA64
> architectures, though the implemenation is in generic drivers/pci
> tree.
Exact. And it's also a pile of crap.
> 2. Why is the message data defined in a such way shown as follows? Or
> does it just follow IOxAPIC's design? Further question is who defines
> the format of the message data. The PCI/PCIe specs don't say anything
> about the content of the message data register.
.../...
It's all intel specific junk.
> 3. How is the pci subsystem initialized on a PPC platform? Is there
> any existing document discussing PCI subsystem? Of course I've been
> doing a lot internet search and couldn't find too much useful infor.
pci host bridges are initialized early, generally in setup_arch() and
the PCI bus is probed later. You can see the code in
arch/powerpc/kernel/pci_{32,64}.c
Now, regarding MSI, as you have noticed, the situation isn't great. I'm
currently in the middle of reworking our interrupt management (and
interrupt numbers allocation layer) and Michael Ellermann is looking at
the MSI issue in parallel.
We don't have a solution yet but are working on it.
Ben.
^ permalink raw reply
* Re: MSI support on Linux PCI implementation for Ocotea
From: Roland Dreier @ 2006-06-15 23:31 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: ppcdev, ppcembed
In-Reply-To: <1150413771.7725.20.camel@localhost.localdomain>
Benjamin> Hi ! What is Ocotea ! :)
It's an eval board for some PowerPC 440 ... 440GX I think (which has
the HW capability to support MSI on PCI-X iirc)
- R.
^ permalink raw reply
* Re: [PATCH] powerpc: Fix 64k pages on non-partitioned machines
From: Anton Blanchard @ 2006-06-16 0:14 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: linuxppc-dev, torvalds, Paul Mackerras
In-Reply-To: <200606151508.46613.arnd.bergmann@de.ibm.com>
Hi Arnd,
> Actually, I thought we decided to postpone 64k page support on cell
> to 2.6.18 already. This patch alone is not enough to make it work,
> at least one more fix is needed for being able to boot, while
> the spu file system needs major changes for it.
We are hitting the bug on other ppc64 systems too, so I think its worth
fixing for 2.6.17.
Anton
^ permalink raw reply
* Re: MSI support on Linux PCI implementation for Ocotea
From: Shawn Jin @ 2006-06-16 0:45 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: ppcdev, ppcembed
In-Reply-To: <1150413771.7725.20.camel@localhost.localdomain>
> Hi ! What is Ocotea ! :)
Did I spell it wrong?? I don't believe Ben doesn't know Ocotea.
Hmmm...Ocotea again? Let me check if I really spelled it wrong. Hey,
it's really Ocotea. ;)
Of course, there is no such MSI support specific for Ocotea.
> > 1. Obviously MSI is supported in Linux 2.6.x, maybe even in 2.4.x. But
> > MSI implementation seems to support only IOxAPIC on x86 or IA64
> > architectures, though the implemenation is in generic drivers/pci
> > tree.
>
> Exact. And it's also a pile of crap.
;) I'm not in a position where I can either agree or disagree with
you. :D But may I ask if ppc platform can make use of this crap in our
PCI express testing? That is, are the functionalities of this crap
working?
> pci host bridges are initialized early, generally in setup_arch() and
> the PCI bus is probed later. You can see the code in
> arch/powerpc/kernel/pci_{32,64}.c
>
> Now, regarding MSI, as you have noticed, the situation isn't great. I'm
> currently in the middle of reworking our interrupt management (and
> interrupt numbers allocation layer) and Michael Ellermann is looking at
> the MSI issue in parallel.
>
> We don't have a solution yet but are working on it.
It's good to know the development status. What's the relationship
between generic pci driver layer in drivers/pci and architecture
specific implementation? One thing I notice is that architectures
provide pcibios_init() and do resource allocation while the generic
driver provides PCI generic functions such as pci_scan_device().
Thanks,
-Shawn.
^ permalink raw reply
* Re: Interrupt occurs but UIC0 MSR is still 0
From: Eugene Surovegin @ 2006-06-16 2:02 UTC (permalink / raw)
To: Chris Dumoulin; +Cc: linuxppc-embedded
In-Reply-To: <4491D34B.4060201@ics-ltd.com>
On Thu, Jun 15, 2006 at 05:38:19PM -0400, Chris Dumoulin wrote:
> Hi All,
> I'm working with a 2.6 linux kernel in a board with a PPC405 in a Virtex
> II Pro FPGA. I'm trying to generate interrupts and handle them in a
> device driver that I've written.
> Here is the sequence of events that happen currently:
> 1. I generate an interrupt by setting registers in an interrupt
> controller we've got in the FPGA (it's a Xilinx LogicCORE OPB Interrupt
> Controller).
> 2. The function do_IRQ, in arch/powerpc/kernel/irq.c, is called.
> 3. ppc_md.get_irq is called from do_IRQ.
> 4. ppc_md.get_irq points to ppc4xx_pic_get_irq in
> arch/ppc/syslib/ppc4xx_pic.c.
> 5. ppc4xx_pic_get_irq reads the MSR from UIC0 to determine the IRQ. In
> my case, the MSR is all zero, so ppc4xx_pic_get_irq returns -1.
> 6. After this, we return from the interrupt, and do_IRQ is called again
> and again, going through the same steps indefinitely.
I don't think ppc4xx_pic.c is correct file for Xilinx Virtex II Pro.
You should be using xilinx_pic.c probably.
--
Eugene
^ permalink raw reply
* Re: [PATCH] powerpc: Use soft irq-disable on all 64-bit machines
From: Stephen Rothwell @ 2006-06-16 3:24 UTC (permalink / raw)
To: paulus; +Cc: linuxppc-dev
In-Reply-To: <20060614172309.59d7b76e.sfr@canb.auug.org.au>
On Wed, 14 Jun 2006 17:23:09 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Wed, 14 Jun 2006 17:08:40 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Looks good. A couple of small fixes below.
>
> Plus we want the below as well ...
And this ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
diff --git a/arch/powerpc/kernel/entry_64.S b/arch/powerpc/kernel/entry_64.S
index 434461a..c6b0400 100644
--- a/arch/powerpc/kernel/entry_64.S
+++ b/arch/powerpc/kernel/entry_64.S
@@ -89,6 +89,8 @@ system_call_common:
addi r9,r1,STACK_FRAME_OVERHEAD
ld r11,exception_marker@toc(r2)
std r11,-16(r9) /* "regshere" marker */
+ lbz r10,PACAPROCENABLED(r13)
+ std r10,SOFTE(r1)
#ifdef CONFIG_PPC_ISERIES
/* Hack for handling interrupts when soft-enabling on iSeries */
cmpdi cr1,r0,0x5555 /* syscall 0x5555 */
@@ -96,8 +98,6 @@ #ifdef CONFIG_PPC_ISERIES
crand 4*cr0+eq,4*cr1+eq,4*cr0+eq
beq hardware_interrupt_entry
#endif
- lbz r10,PACAPROCENABLED(r13)
- std r10,SOFTE(r1)
mfmsr r11
ori r11,r11,MSR_EE
mtmsrd r11,1
^ permalink raw reply related
* Block driver question (MPC852 with DoC)
From: deepesh @ 2006-06-16 8:37 UTC (permalink / raw)
To: linuxppc-dev
Processor: MPC852
OS : linuxppc-2.4.20 from denx
DoC: Disk On Chip, A block device.
We are using DiskOnChip on our board. And we have got a block driver from
the vendor, which can be insmoded.
The request function of the block driver:
DeviceRequest() {
some error checkings;
list_add_tail(&queue,&requestsList);
wake_up(&waitQueueHead);
}
There is an kernel thread which does the final block read-writes to the
disk on chip:
IOKernelThread() {
while(1) {
set_current_state(TASK_INTERRUPTIBLE);
interruptible_sleep_on_timeout(&waitQueueHead,1);
while(!list_empty(&requestsList)) {
read/write to the disk;
list_del(&queue);
}
}
}
The list manipulations happen in the DeviceRequest and the IOKernelThread.
Is there a potential chance of a race condition, when a timer interrupt
occurs?
Thank you,
Deepesh
^ permalink raw reply
* Re: Interrupt occurs but UIC0 MSR is still 0
From: Chris Dumoulin @ 2006-06-16 14:38 UTC (permalink / raw)
To: Chris Dumoulin, linuxppc-embedded
In-Reply-To: <20060616020221.GA3366@gate.ebshome.net>
Thanks Eugene,
You were right on the money. I changed the appropriate Makefile to
include xilinx_pic.c, instead of ppc4xx_pic.c, and things are now
working. It seems like the UIC of the PPC405 isn't used (or doesn't
exist) in the Virtex II Pro. The interrupt servicing code interfaces
with an external interrupt controller (OPB Interrupt Controller, in my
case) instead.
Regards,
Chris Dumoulin
Eugene Surovegin wrote:
> On Thu, Jun 15, 2006 at 05:38:19PM -0400, Chris Dumoulin wrote:
>
>> Hi All,
>> I'm working with a 2.6 linux kernel in a board with a PPC405 in a Virtex
>> II Pro FPGA. I'm trying to generate interrupts and handle them in a
>> device driver that I've written.
>> Here is the sequence of events that happen currently:
>> 1. I generate an interrupt by setting registers in an interrupt
>> controller we've got in the FPGA (it's a Xilinx LogicCORE OPB Interrupt
>> Controller).
>> 2. The function do_IRQ, in arch/powerpc/kernel/irq.c, is called.
>> 3. ppc_md.get_irq is called from do_IRQ.
>> 4. ppc_md.get_irq points to ppc4xx_pic_get_irq in
>> arch/ppc/syslib/ppc4xx_pic.c.
>> 5. ppc4xx_pic_get_irq reads the MSR from UIC0 to determine the IRQ. In
>> my case, the MSR is all zero, so ppc4xx_pic_get_irq returns -1.
>> 6. After this, we return from the interrupt, and do_IRQ is called again
>> and again, going through the same steps indefinitely.
>>
>
> I don't think ppc4xx_pic.c is correct file for Xilinx Virtex II Pro.
> You should be using xilinx_pic.c probably.
>
>
--
*--Christopher Dumoulin--*
Software Team Leader
<http://ics-ltd.com/>
<http://ics-ltd.com/>
Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)
------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only.
If misdirected, please notify us by telephone and confirm that it has
been deleted from your system and any hard copies destroyed. You are
strictly prohibited from using, printing, distributing or disseminating
it or any information contained in it save to the intended recipient.
^ permalink raw reply
* Re: Binding FCC interfaces to device names in reverse order
From: Laurent Pinchart @ 2006-06-16 14:50 UTC (permalink / raw)
To: Vitaly Bordug; +Cc: linuxppc-embedded
In-Reply-To: <20060615165344.7db8444e@vitb.ru.mvista.com>
> > Does anyone know why changing the device ids breaks the fs_enet driver ?
>
> Obviously, because board-specific platform_data fixup use that id field to
> detect what soc device is that - fcc1 or fcc2 this case. So the phy's will
> be wrong-assigned, as well as other stuff.
>
> To change order pdevs are registered, you may try to disable all the fccs
> at the startup, and then enable them after ppc_sys_init, or just shoot
> enable-disable seq (this was't tested at all, but supposed to work).
Enabling the FCCs in a device_initcall() call instead of arch_initcall()
works. I had to call ppc_sys_device_fixup manually.
Thanks for your help.
Laurent Pinchart
^ permalink raw reply
* secondary CPU kicking on 86xx
From: Jon Loeliger @ 2006-06-16 14:58 UTC (permalink / raw)
To: linuxppc-dev
Ben and folks,
I have a question regarding your comments on our proposed
additions for the mpc86xx secondary CPU release code.
We need a way to bounce the secondary CPUs through the
reset vector at 0x100, and can either statically lay down
an address like GEMINI does today:
--- a/arch/powerpc/kernel/head_32.S
+++ b/arch/powerpc/kernel/head_32.S
@@ -348,6 +348,9 @@ #define EXC_XFER_EE_LITE(n, hdlr) \
#if defined(CONFIG_GEMINI) && defined(CONFIG_SMP)
. = 0x100
b __secondary_start_gemini
+#elif defined(CONFIG_PPC_86xx) && defined(CONFIG_SMP)
+ . = 0x100
+ b __secondary_hold_mpc86xx
#else
EXCEPTION(0x100, Reset, unknown_exception, EXC_XFER_STD)
#endif
Or we can dynamically rewrite a branch instruction into
the reset vector from C code during smp_kick_cpu() time
like the current powermac code does.
I have working code for both; just need opinions
and preferences on correct approach/style voiced!
Thanks,
jdl
^ permalink raw reply
* Re: [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers
From: Mike Kravetz @ 2006-06-16 16:11 UTC (permalink / raw)
To: Paul Mackerras
Cc: Bryan Rosenburg, linuxppc-dev, Nathan Lynch, Christopher Yeoh
In-Reply-To: <17552.36563.460775.131555@cargo.ozlabs.ibm.com>
On Thu, Jun 15, 2006 at 08:33:55AM +1000, Paul Mackerras wrote:
> Nathan Lynch writes:
>
> > Without disabling preemption around the mfspr ... update_stats section
> > in these hcall wrappers, you risk updating the stats on the wrong cpu.
>
> I think we are only looking for total counts and times anyway, so it
> doesn't really matter which cpu updates the stats, as long as the time
> gets accounted on some cpu. The use of per-cpu counters is just for
> better cache behaviour.
Thought about this a little more.
We do an mfspr to get a 'timestamp' before the actual hcall. Then, make
the hcall and do another mfspr after. Isn't it possible to be preempted
and perform the mfspr's on separate CPUs? Worse yet, wouldn't this possibly
add 'time preempted' to the hcall time?. Do we have the same (skewed time)
issue with interrupts?
Thinking that enable/disable around the call might be worth the overhead.
But, disabling interrupts would not be worth it.
--
Mike
^ permalink raw reply
* Re: MSI support on Linux PCI implementation for Ocotea
From: Shawn Jin @ 2006-06-16 21:45 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: ppcdev
In-Reply-To: <1150413771.7725.20.camel@localhost.localdomain>
Hi Ben,
> Now, regarding MSI, as you have noticed, the situation isn't great. I'm
> currently in the middle of reworking our interrupt management (and
> interrupt numbers allocation layer) and Michael Ellermann is looking at
> the MSI issue in parallel.
Just one point about MSI(-X) message address and data format. I think
it should be the platform that defines the content. Current
implementation doesn't have this flexibility. We have a design where
MSI mode uses message data to carry vector number info while MSI-X
mode uses message address to carry this info. Although it seems
strange, but I think it's allowed by the spec.
Thanks,
-Shawn.
^ permalink raw reply
* Re: MSI support on Linux PCI implementation for Ocotea
From: Benjamin Herrenschmidt @ 2006-06-16 22:13 UTC (permalink / raw)
To: Shawn Jin; +Cc: ppcdev
In-Reply-To: <c3d0340b0606161445w5acb4da8j26870f56a4bf4d9@mail.gmail.com>
On Fri, 2006-06-16 at 14:45 -0700, Shawn Jin wrote:
> Hi Ben,
>
> > Now, regarding MSI, as you have noticed, the situation isn't great. I'm
> > currently in the middle of reworking our interrupt management (and
> > interrupt numbers allocation layer) and Michael Ellermann is looking at
> > the MSI issue in parallel.
>
> Just one point about MSI(-X) message address and data format. I think
> it should be the platform that defines the content.
That's an obvious requirement :)
> Current
> implementation doesn't have this flexibility. We have a design where
> MSI mode uses message data to carry vector number info while MSI-X
> mode uses message address to carry this info. Although it seems
> strange, but I think it's allowed by the spec.
The current implementation is bad :) There are some patches for altix
that are in -mm that add some platform hooks that make the situation a
little bit better, but it's still far from perfect.
Ben.
^ 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