* Re: Efika, initrd and current kernel
From: Matt Sealey @ 2007-09-30 16:22 UTC (permalink / raw)
To: Jon Smirl; +Cc: Sven Luther, linuxppc-embedded
In-Reply-To: <9e4733910709300728p1f1a2c87vad38a2b047da54e0@mail.gmail.com>
How did you attach the initrd to the kernel?
Compiled in using the initramfs feature, or did you use mkvmlinuz (debian/ubuntu)
or mkzImage (suse) or have genkernel build it (--genzimage) on Gentoo? It looks
like you're trying to boot Gentoo from the boot line..
--
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations
Jon Smirl wrote:
> On 9/30/07, Sven Luther <sven@genesi-usa.com> wrote:
>> On Sun, Sep 30, 2007 at 10:09:47AM -0400, Jon Smirl wrote:
>>> On 9/30/07, Matt Sealey <matt@genesi-usa.com> wrote:
>>>> How did you build the kernel?
>>> I attached the .config
>>> Am I supposed to have both chrp and efika selected?
>> I think so, yes.
>
> I have then both selected.
>
> I'm sure it is something simple about how I have my kernel configured
> wrong but I can't figure out what it is. I have BLK_INITRD turned on.
> I can trace in the initrd code and see that it is exiting because
> strat_initrd is not set. start_initrd is set in the platform specfic
> code which I haven't figured out yet.
>
>
>> Friendly,
>>
>> Sven Luther
>>
>
>
^ permalink raw reply
* Re: Is it safe to use these Linux function (test_bit(), set_bit(), clear_bit()) in character device driver for 2.6.10 ppc kernel.
From: Misbah khan @ 2007-09-30 14:54 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <12937117.post@talk.nabble.com>
Misbah khan wrote:
>
>
>
> Jeff Mock-2 wrote:
>>
>>
>>
>> Misbah khan wrote:
>>>
>>>
>>> Scott Wood-2 wrote:
>>>> Misbah khan wrote:
>>>>> Hi all I am using "test_bit(),set_bit(),clear_bit() etc" API functions
>>>>> provided by the Linux kernel. I want to know that if anybody is used
>>>>> it
>>>>> and have full faith in its operation then please let me know. Driver
>>>>> in
>>>>> the while loop is calling these API's hence i want to make sure that
>>>>> its
>>>>> operation will remain stable.
>>>> They're used all over the place. Is there anything about them that you
>>>> find suspect?
>>>>
>>>> -Scott
>>>>
>>>> I have devloped a character driver for FPGA which is memory mapped and
>>>> using these API's to test a bit , set a bit or to clear a bit in the
>>>> memory for eg :-
>>>>
>>>> /* poll till data is transfered from sdram to dpram */
>>>> while((test_bit(DFR_BUSY,(UINT32 *)(\
>>>> (void *)mmap_reg_ptr + DATA_STATUS_REG))==1)\
>>>> && (delay < MAX_DELAY_BUSY))
>>>> {
>>>> KDEBUG3(" In the Dfr delay loop \n");
>>>> mdelay(DELAY);
>>>> delay+=DELAY;
>>>> }/* End of while(test_bit(FPGA_BUSY,(void *)register name) */
>>>>
>>>> if(delay==MAX_DELAY_BUSY)
>>>> {
>>>> KDEBUG1("Out of the the Dfr busy loop \n");
>>>> return -1;
>>>> }
>>>>
>>>> People working for FPGA are sure that they are not making the bit high
>>>> where in my driver is returning -1 from the kernel space aborting it
>>>> after
>>>> running for few minutes or so . Please let me know that This function
>>>> is
>>>> stable and i should tell them that the driver is stable in its
>>>> operation
>>>> and they should check it from there side.
>>>>
>>
>>
>> I think a more more likely source of the problem is that the FPGA
>> pointer is not cast volatile, or perhaps the FPGA is mapped cached and
>> the hardware doesn't always get touched when you think it does. The bit
>> manipulation macros are probably fine.
>>
>> jeff
>>
>> FPGA is Indeed mapped non cashed here is the part of the code
>>
>> /* Physical bus memory is mapped */
>> mmap_reg_ptr=(UINT32 *)ioremap_nocache(PHY_MEM_ADDR,PHY_MEM_SIZE);
>>
>> And is it ok if I caste FPGA pointer volatile like this will reduce the
>> probability of failure
>>
>> /* poll till data is transfered from sdram to dpram */
>> while((test_bit(DFR_BUSY,(volatile UINT32 *)(\
>> (volatile UINT32 *)mmap_reg_ptr + DATA_STATUS_REG))==1)\
>> && (delay < MAX_DELAY_BUSY))
>> {
>> KDEBUG3(" In the Dfr delay loop \n");
>> mdelay(DELAY);
>> delay+=DELAY;
>> }/* End of while(test_bit(FPGA_BUSY,(void *)register name) */
>>
>> if(delay==MAX_DELAY_BUSY)
>> {
>> KDEBUG1("Out of the the Dfr busy loop \n");
>> return CASHEL_FAILURE;
>> }
>> __________________
>>
>> is there anything else that we could do to rely fully in our code.
>>
>> Misbah
>> MAX_DELAY_BUSY corresponds to 10 ms .Driver should poll the bit for few
>> micro second at the max and come out .
>>
>> I had earlier tried with ioread32() and iowrite32() wrapper functions but
>> the output i got is bit swapped hence i went for direct dereferencing
>> the pointer .
>>
>> do you think in_be32() could be the best approach than direct
>> dereferencing. And about test_bit() function does it looks fine to you
>>
>> Misbah
>>
>>
>> _____________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Is-it-safe-to-use-these-Linux-function-%28test_bit%28%29%2Cset_bit%28%29%2Cclear_bit%28%29%29-in-character-device-driver-for-2.6.10-ppc-kernel.-tf4527008.html#a12966462
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
^ permalink raw reply
* Re: Efika, initrd and current kernel
From: Jon Smirl @ 2007-09-30 14:28 UTC (permalink / raw)
To: Sven Luther; +Cc: linuxppc-embedded
In-Reply-To: <20070930141926.GA1431@powerlinux.fr>
On 9/30/07, Sven Luther <sven@genesi-usa.com> wrote:
> On Sun, Sep 30, 2007 at 10:09:47AM -0400, Jon Smirl wrote:
> > On 9/30/07, Matt Sealey <matt@genesi-usa.com> wrote:
> > > How did you build the kernel?
> >
> > I attached the .config
> > Am I supposed to have both chrp and efika selected?
>
> I think so, yes.
I have then both selected.
I'm sure it is something simple about how I have my kernel configured
wrong but I can't figure out what it is. I have BLK_INITRD turned on.
I can trace in the initrd code and see that it is exiting because
strat_initrd is not set. start_initrd is set in the platform specfic
code which I haven't figured out yet.
>
> Friendly,
>
> Sven Luther
>
--
Jon Smirl
jonsmirl@gmail.com
^ permalink raw reply
* Re: Efika, initrd and current kernel
From: Sven Luther @ 2007-09-30 14:19 UTC (permalink / raw)
To: Jon Smirl; +Cc: sven, linuxppc-embedded
In-Reply-To: <9e4733910709300709t72078992s1bad7967c565b6e1@mail.gmail.com>
On Sun, Sep 30, 2007 at 10:09:47AM -0400, Jon Smirl wrote:
> On 9/30/07, Matt Sealey <matt@genesi-usa.com> wrote:
> > How did you build the kernel?
>
> I attached the .config
> Am I supposed to have both chrp and efika selected?
I think so, yes.
Friendly,
Sven Luther
^ permalink raw reply
* Re: Efika, initrd and current kernel
From: Jon Smirl @ 2007-09-30 14:09 UTC (permalink / raw)
To: Matt Sealey; +Cc: linuxppc-embedded
In-Reply-To: <46FF7A7D.6040300@genesi-usa.com>
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
On 9/30/07, Matt Sealey <matt@genesi-usa.com> wrote:
> How did you build the kernel?
I attached the .config
Am I supposed to have both chrp and efika selected?
--
Jon Smirl
jonsmirl@gmail.com
[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 26973 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.23-rc8
# Sat Sep 29 23:54:16 2007
#
# CONFIG_PPC64 is not set
#
# Processor support
#
CONFIG_6xx=y
# CONFIG_PPC_85xx is not set
# CONFIG_PPC_8xx is not set
# CONFIG_40x is not set
# CONFIG_44x is not set
# CONFIG_E200 is not set
CONFIG_PPC_FPU=y
# CONFIG_ALTIVEC is not set
CONFIG_PPC_STD_MMU=y
CONFIG_PPC_STD_MMU_32=y
# CONFIG_PPC_MM_SLICES is not set
# CONFIG_SMP is not set
CONFIG_PPC32=y
CONFIG_PPC_MERGE=y
CONFIG_MMU=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_IRQ_PER_CPU=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_ILOG2_U32=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
# CONFIG_ARCH_NO_VIRT_TO_BUS is not set
CONFIG_PPC=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_NVRAM=y
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_PPC_OF=y
CONFIG_OF=y
CONFIG_PPC_UDBG_16550=y
# CONFIG_GENERIC_TBSYNC is not set
CONFIG_AUDIT_ARCH=y
CONFIG_GENERIC_BUG=y
# CONFIG_DEFAULT_UIMAGE is not set
# CONFIG_PPC_DCR_NATIVE is not set
# CONFIG_PPC_DCR_MMIO is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION="-efika"
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set
# CONFIG_USER_NS is not set
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# 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_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
# CONFIG_BLK_DEV_BSG is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_IOSCHED_CFQ is not set
# CONFIG_DEFAULT_AS is not set
CONFIG_DEFAULT_DEADLINE=y
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="deadline"
#
# Platform support
#
CONFIG_PPC_MULTIPLATFORM=y
# CONFIG_EMBEDDED6xx is not set
# CONFIG_PPC_82xx is not set
# CONFIG_PPC_83xx is not set
# CONFIG_PPC_86xx is not set
CONFIG_CLASSIC32=y
CONFIG_PPC_CHRP=y
CONFIG_PPC_MPC52xx=y
# CONFIG_PPC_MPC5200 is not set
CONFIG_PPC_EFIKA=y
# CONFIG_PPC_PCM030 is not set
# CONFIG_PPC_LITE5200 is not set
# CONFIG_PPC_PMAC is not set
# CONFIG_PPC_CELL is not set
# CONFIG_PPC_CELL_NATIVE is not set
# CONFIG_PQ2ADS is not set
CONFIG_PPC_NATIVE=y
CONFIG_UDBG_RTAS_CONSOLE=y
CONFIG_MPIC=y
# CONFIG_MPIC_WEIRD is not set
CONFIG_PPC_I8259=y
CONFIG_PPC_RTAS=y
# CONFIG_RTAS_ERROR_LOGGING is not set
CONFIG_RTAS_PROC=y
# CONFIG_MMIO_NVRAM is not set
CONFIG_PPC_MPC106=y
# CONFIG_PPC_970_NAP is not set
# CONFIG_PPC_INDIRECT_IO is not set
# CONFIG_GENERIC_IOMAP is not set
# CONFIG_CPU_FREQ is not set
# CONFIG_TAU is not set
# CONFIG_CPM2 is not set
# CONFIG_FSL_ULI1575 is not set
CONFIG_PPC_BESTCOMM=y
CONFIG_PPC_BESTCOMM_ATA=y
CONFIG_PPC_BESTCOMM_FEC=y
CONFIG_PPC_BESTCOMM_GEN_BD=y
#
# Kernel options
#
# CONFIG_HIGHMEM is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_300=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=300
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
# CONFIG_KEXEC is not set
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
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_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_PROC_DEVICETREE=y
# CONFIG_CMDLINE_BOOL is not set
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set
CONFIG_SUSPEND_UP_POSSIBLE=y
# CONFIG_SUSPEND is not set
CONFIG_HIBERNATION_UP_POSSIBLE=y
# CONFIG_HIBERNATION is not set
# CONFIG_SECCOMP is not set
# CONFIG_WANT_DEVICE_TREE is not set
CONFIG_ISA_DMA_API=y
#
# Bus options
#
# CONFIG_ISA is not set
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_PPC_INDIRECT_PCI=y
CONFIG_FSL_SOC=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCI_SYSCALL=y
# CONFIG_PCIEPORTBUS is not set
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI 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_BOOT_LOAD=0x00800000
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
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=y
CONFIG_IP_PNP_RARP=y
# 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_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=y
CONFIG_IPV6_PRIVACY=y
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET6_XFRM_MODE_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_BEET is not set
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
# CONFIG_IPV6_SIT is not set
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
CONFIG_NETWORK_SECMARK=y
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# 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_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_AF_RXRPC is not set
#
# Wireless
#
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT is not set
# CONFIG_MAC80211 is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_CONCAT is not set
# CONFIG_MTD_PARTITIONS is not set
#
# User Modules And Translation Layers
#
# CONFIG_MTD_CHAR is not set
# CONFIG_MTD_BLKDEVS is not set
# CONFIG_MTD_BLOCK is not set
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE 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_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PLATRAM is not set
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_DATAFLASH is not set
# CONFIG_MTD_M25P80 is not set
# 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
# CONFIG_MTD_NAND is not set
# CONFIG_MTD_ONENAND is not set
#
# UBI - Unsorted block images
#
# CONFIG_MTD_UBI is not set
CONFIG_OF_DEVICE=y
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_MISC_DEVICES is not set
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_RAID_ATTRS=y
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=y
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
CONFIG_CHR_DEV_OSST=y
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
CONFIG_CHR_DEV_SCH=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_LOWLEVEL is not set
# CONFIG_ATA is not set
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=y
#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_FIXED_PHY is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
# CONFIG_NET_PCI is not set
#
# MPC5200 Networking Options
#
CONFIG_FEC_MPC52xx=y
CONFIG_FEC_MPC52xx_MDIO=y
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET_MII is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC 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
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
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=y
# 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_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Hardware I/O ports
#
# CONFIG_SERIO is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
# CONFIG_VT is not set
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_UARTLITE is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_MPC52xx=y
CONFIG_SERIAL_MPC52xx_CONSOLE=y
CONFIG_SERIAL_MPC52xx_CONSOLE_BAUD=115200
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# CONFIG_BRIQ_PANEL is not set
# CONFIG_HVC_RTAS is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
CONFIG_MPC5200_WDT=y
# CONFIG_WATCHDOG_RTAS is not set
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
# CONFIG_HW_RANDOM is not set
CONFIG_NVRAM=y
CONFIG_GEN_RTC=y
CONFIG_GEN_RTC_X=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_TCG_TPM is not set
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=y
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_HYDRA is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
CONFIG_I2C_MPC=y
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_TINY_USB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_DS1682 is not set
CONFIG_SENSORS_EEPROM=y
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_M41T00 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
#
# SPI support
#
CONFIG_SPI=y
CONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_BITBANG is not set
CONFIG_SPI_MPC52xx_PSC=y
#
# SPI Protocol Masters
#
# CONFIG_SPI_AT25 is not set
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_DAB is not set
#
# Graphics support
#
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_FB_IBM_GXT4500 is not set
#
# Sound
#
# CONFIG_SOUND is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_PERSIST is not set
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_PPC_SOC=y
CONFIG_USB_OHCI_HCD_PPC_OF=y
CONFIG_USB_OHCI_HCD_PPC_OF_BE=y
CONFIG_USB_OHCI_HCD_PPC_OF_LE=y
CONFIG_USB_OHCI_HCD_PCI=y
CONFIG_USB_OHCI_BIG_ENDIAN_DESC=y
CONFIG_USB_OHCI_BIG_ENDIAN_MMIO=y
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
# CONFIG_USB_UHCI_HCD is not set
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_MON is not set
#
# USB port drivers
#
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
#
# USB DSL modem support
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
#
# MMC/SD Card Drivers
#
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_BOUNCE=y
#
# MMC/SD Host Controller Drivers
#
# CONFIG_MMC_SDHCI is not set
# CONFIG_MMC_WBSD is not set
# CONFIG_MMC_TIFM_SD is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
CONFIG_RTC_DRV_PCF8563=y
CONFIG_RTC_DRV_PCF8583=y
# CONFIG_RTC_DRV_M41T80 is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_V3020 is not set
#
# on-CPU RTC drivers
#
#
# DMA Engine support
#
# CONFIG_DMA_ENGINE is not set
#
# DMA Clients
#
#
# DMA Devices
#
#
# Userspace I/O
#
# CONFIG_UIO is not set
#
# 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 is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG 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_GFS2_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_INOTIFY_USER=y
# CONFIG_QUOTA is not set
# CONFIG_DNOTIFY is not set
# 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=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y
#
# 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 is not set
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# 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_JFFS2_FS is not set
CONFIG_CRAMFS=y
CONFIG_SQUASHFS=y
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
# CONFIG_SQUASHFS_VMALLOC 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=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
# CONFIG_NFSD is not set
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
# CONFIG_SUNRPC_BIND34 is not set
CONFIG_RPCSEC_GSS_KRB5=y
# 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
#
# 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=y
# 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=y
CONFIG_NLS_ISO8859_1=y
# 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=y
#
# Distributed Lock Manager
#
# CONFIG_DLM is not set
# CONFIG_UCC_SLOW is not set
CONFIG_PPC_LIB_RHEAP=y
#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
#
# Instrumentation Support
#
# CONFIG_PROFILING is not set
# CONFIG_KPROBES is not set
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_DEBUG_BUGVERBOSE is not set
CONFIG_BOOTX_TEXT=y
# CONFIG_PPC_EARLY_DEBUG is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_MANAGER=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_SHA1 is not set
CONFIG_CRYPTO_SHA256=y
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_GF128MUL is not set
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_PCBC=y
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
CONFIG_CRYPTO_ARC4=y
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
CONFIG_CRYPTO_MICHAEL_MIC=y
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_TEST is not set
# CONFIG_CRYPTO_HW is not set
^ permalink raw reply
* Re: Efika, initrd and current kernel
From: Matt Sealey @ 2007-09-30 10:29 UTC (permalink / raw)
To: Jon Smirl; +Cc: linuxppc-embedded
In-Reply-To: <9e4733910709292205p7b1cdda9m661b241908fdedab@mail.gmail.com>
How did you build the kernel?
--
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations
Jon Smirl wrote:
> I'm trying to boot a current kernel on the Efika like this:
> boot hd:0 efika init=/linuxrc root=/dev/ram0 looptype=squashfs
> loop=/squashfs.img cdroot
>
> It is not finding the initrd.
> I added some printks and start_initrd is not getting set.
>
> The 2.6.19 gentoo kernel described here boots and finds the same initrd
> http://gentoo-wiki.com/Efika
>
> Something is missing in the hand off from the OF to the kernel code.
> I'm poking around in powerpc/kernel/prom_init.c
> looking for answers.
>
^ permalink raw reply
* Re: Powerbook shuts down hard when hot, patch found
From: Michael Buesch @ 2007-09-30 10:16 UTC (permalink / raw)
To: benh; +Cc: linuxppc-dev
In-Reply-To: <200709301213.36821.mb@bu3sch.de>
On Sunday 30 September 2007 12:13:36 Michael Buesch wrote:
> On Sunday 30 September 2007 00:49:05 Benjamin Herrenschmidt wrote:
> > Well, it's possible that they have a too weak pull-up resistor on those
> > lines, and thus when asserted to 0, a significant current goes through
> > causing the whole thing to heat up. That heat added to the residual heat
> > of a hot boot becomes then enough to trigger the temperature sensor
> > threshold... just one possible explanation.
>
> Possible, yes.
>
> > > That's why I thought about some silicon bug. Why only when it's hot? :)
> > >
> > > > Also, the other change I made you do turns these into inputs, thus the
> > >
> > > The _EN bits are already all cleared, as you can see in my printk dump.
> > > So clearing them has no effect, of course.
> > > So the ports are Inputs as default on boot.
> >
> > Hrm, that's weird then, because in that case, changing the output bits
> > shouldn't have any effect, unless maybe on some chips, the EN bits are
> > flipped. I don't have anything specific about the rv350 tho.
> >
> > Can you print which specific DDC register is doing that (it's called
> > twice right ?) and maybe do a patch preventing that write only for one
> > of them and let me know if it makes a difference.
>
> Here's the log of a working kernel.
> As you can see, I only removed the write for register 0x60 here.
> So it only crashes when I clear the bits in this register.
> (makes sense, as there's nothing to clear in the other one).
>
> [ 0.453703] PCI: Enabling device 0000:00:10.0 (0006 -> 0007)
> [ 0.649319] radeonfb (0000:00:10.0): Invalid ROM signature 303 should be 0xaa55
> [ 0.649329] radeonfb: Retrieved PLL infos from Open Firmware
> [ 0.649340] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz
> [ 0.649350] radeonfb: PLL min 12000 max 35000
> [ 0.650146] DDC REG 0x00000060 IS 0x00000303
> [ 0.793754] i2c-adapter i2c-2: unable to read EDID block.
> [ 1.013748] i2c-adapter i2c-2: unable to read EDID block.
> [ 1.233748] i2c-adapter i2c-2: unable to read EDID block.
> [ 1.310002] DDC REG 0x0000006C IS 0x00000000
> [ 1.310007] WRITING
> [ 1.650506] ieee1394: Host added: ID:BUS[0-00:1023] GUID[001124fffed98036]
> [ 1.700986] radeonfb: Monitor 1 type LCD found
> [ 1.700995] radeonfb: EDID probed
> [ 1.701001] radeonfb: Monitor 2 type no found
> [ 1.701015] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0
> [ 1.701130] radeonfb: Dynamic Clock Power Management enabled
> [ 1.742608] Console: switching to colour frame buffer device 160x53
> [ 1.765577] radeonfb: Backlight initialized (radeonbl0)
> [ 1.765767] radeonfb (0000:00:10.0): ATI Radeon NP
> [ 1.776757] Generic RTC Driver v1.07
> [ 1.777085] Macintosh non-volatile memory driver v1.1
> [ 1.777429] Linux agpgart interface v0.102
> [ 1.777739] agpgart: Detected Apple UniNorth 2 chipset
>
Ah, forgot to say.
It does not crash immediately when the register is written. It takes about two seconds
to crash. And when the machine is colder to begin with, it takes slightly
longer to trigger. That _might_ support your overheating theory.
Though, it does not trigger when it's up and running, no matter how hot you drive it.
--
Greetings Michael.
^ permalink raw reply
* Re: Powerbook shuts down hard when hot, patch found
From: Michael Buesch @ 2007-09-30 10:13 UTC (permalink / raw)
To: benh; +Cc: linuxppc-dev
In-Reply-To: <1191106145.28637.11.camel@pasglop>
On Sunday 30 September 2007 00:49:05 Benjamin Herrenschmidt wrote:
> Well, it's possible that they have a too weak pull-up resistor on those
> lines, and thus when asserted to 0, a significant current goes through
> causing the whole thing to heat up. That heat added to the residual heat
> of a hot boot becomes then enough to trigger the temperature sensor
> threshold... just one possible explanation.
Possible, yes.
> > That's why I thought about some silicon bug. Why only when it's hot? :)
> >
> > > Also, the other change I made you do turns these into inputs, thus the
> >
> > The _EN bits are already all cleared, as you can see in my printk dump.
> > So clearing them has no effect, of course.
> > So the ports are Inputs as default on boot.
>
> Hrm, that's weird then, because in that case, changing the output bits
> shouldn't have any effect, unless maybe on some chips, the EN bits are
> flipped. I don't have anything specific about the rv350 tho.
>
> Can you print which specific DDC register is doing that (it's called
> twice right ?) and maybe do a patch preventing that write only for one
> of them and let me know if it makes a difference.
Here's the log of a working kernel.
As you can see, I only removed the write for register 0x60 here.
So it only crashes when I clear the bits in this register.
(makes sense, as there's nothing to clear in the other one).
[ 0.453703] PCI: Enabling device 0000:00:10.0 (0006 -> 0007)
[ 0.649319] radeonfb (0000:00:10.0): Invalid ROM signature 303 should be 0xaa55
[ 0.649329] radeonfb: Retrieved PLL infos from Open Firmware
[ 0.649340] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz
[ 0.649350] radeonfb: PLL min 12000 max 35000
[ 0.650146] DDC REG 0x00000060 IS 0x00000303
[ 0.793754] i2c-adapter i2c-2: unable to read EDID block.
[ 1.013748] i2c-adapter i2c-2: unable to read EDID block.
[ 1.233748] i2c-adapter i2c-2: unable to read EDID block.
[ 1.310002] DDC REG 0x0000006C IS 0x00000000
[ 1.310007] WRITING
[ 1.650506] ieee1394: Host added: ID:BUS[0-00:1023] GUID[001124fffed98036]
[ 1.700986] radeonfb: Monitor 1 type LCD found
[ 1.700995] radeonfb: EDID probed
[ 1.701001] radeonfb: Monitor 2 type no found
[ 1.701015] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0
[ 1.701130] radeonfb: Dynamic Clock Power Management enabled
[ 1.742608] Console: switching to colour frame buffer device 160x53
[ 1.765577] radeonfb: Backlight initialized (radeonbl0)
[ 1.765767] radeonfb (0000:00:10.0): ATI Radeon NP
[ 1.776757] Generic RTC Driver v1.07
[ 1.777085] Macintosh non-volatile memory driver v1.1
[ 1.777429] Linux agpgart interface v0.102
[ 1.777739] agpgart: Detected Apple UniNorth 2 chipset
--
Greetings Michael.
^ permalink raw reply
* problem wint port linux 2.6.23 to MPC860T
From: keng_629 @ 2007-09-30 9:32 UTC (permalink / raw)
To: linuxppc-embedded@ozlabs.org
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
recently i am working with porting the linux2.6.23 to MPC860T
i don't have a good debugger,i use the lighter to test where my kernel is now runing.
i find it out of control after the local_irq_enable() funciton in the asmlinkage void __init start_kernel(void) in init/main.c file.
Can somebody give me a hand?thank you .
keng_629
2007-09-30
[-- Attachment #2: Type: text/html, Size: 1060 bytes --]
^ permalink raw reply
* Re: 2.6.23-rc8-mm2 - PowerPC link failure at arch/powerpc/kernel/head_64.o
From: Kamalesh Babulal @ 2007-09-30 9:37 UTC (permalink / raw)
To: Kamalesh Babulal
Cc: linux-kernel, linuxppc-dev, paulus, Andrew Morton, sam,
Balbir Singh
In-Reply-To: <46FF2199.2060202@linux.vnet.ibm.com>
Kamalesh Babulal wrote:
> Hi Andrew,
>
> The compilation with the cross compiler for the PowerPC-405 on the powerbox
> fails at linking
>
> LD init/built-in.o
> LD .tmp_vmlinux1
> ld: arch/powerpc/kernel/head_64.o(.text+0x80c8): sibling call optimization to `.text.init.refok' does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or make `.text.init.refok' extern
> ld: arch/powerpc/kernel/head_64.o(.text+0x8160): sibling call optimization to `.text.init.refok' does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or make `.text.init.refok' extern
> ld: arch/powerpc/kernel/head_64.o(.text+0x81c4): sibling call optimization to `.text.init.refok' does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or make `.text.init.refok' extern
> ld: final link failed: Bad value
> make: *** [.tmp_vmlinux1] Error 1
>
Adding CC to the powerpc mailing list
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
^ permalink raw reply
* Efika, initrd and current kernel
From: Jon Smirl @ 2007-09-30 5:05 UTC (permalink / raw)
To: linuxppc-embedded
I'm trying to boot a current kernel on the Efika like this:
boot hd:0 efika init=/linuxrc root=/dev/ram0 looptype=squashfs
loop=/squashfs.img cdroot
It is not finding the initrd.
I added some printks and start_initrd is not getting set.
The 2.6.19 gentoo kernel described here boots and finds the same initrd
http://gentoo-wiki.com/Efika
Something is missing in the hand off from the OF to the kernel code.
I'm poking around in powerpc/kernel/prom_init.c
looking for answers.
--
Jon Smirl
jonsmirl@gmail.com
^ permalink raw reply
* A FEC problem on fsl_mpc5121e_ads board.
From: Andrew Liu @ 2007-09-30 3:49 UTC (permalink / raw)
To: jrigby, linuxppc-embedded
Hello All,
When I boot from NFS, it doesn't work, so I boot system from NOR flash.
I found FEC hasn't produced any interrupts ( of course, I have plugged
in cable, and make sure the cable works on other boards, what's more, I
can see FEC light blinks)
when system boot up:
-sh-2.05b# cat /proc/interrupts
CPU0
16: 0 IPIC Level fs_enet-mac
17: 36 IPIC Level i2c-mpc
18: 1 IPIC Level i2c-mpc
19: 1 IPIC Level i2c-mpc
40: 1117 IPIC Level mpc512x_psc_uart
BAD: 0
-sh-2.05b# ethtool eth0
Settings for eth0:
Supported ports: [ TP AUI BNC MII FIBRE ]
Supported link modes:
Supports auto-negotiation: No
Advertised link modes: Not reported
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 1
Transceiver: external
Auto-negotiation: on
Current message level: 0x00000000 (0)
* Link detected: n*
it seems very strange that link detected is no, I have tried the kernel
uImage from Freescale ISO, the thing is same to above.
The part of DTS as bellow:
mdio@2840 {
device_type = "mdio";
compatible = "fs_nocpm_enet";
reg = <2840 4>;
#address-cells = <1>;
#size-cells = <0>;
phy: ethernet-phy@0 {
// interrupt-parent = < &cpld_pic >;
// interrupts = <b 8>;
reg = <1>;
device_type = "ethernet-phy";
};
};
ethernet@2800 {
device_type = "network";
model = "FEC";
compatible = "fs_nocpm_enet";
device-id = <1>;
reg = <2800 800>;
address = [ 00 E0 0C BC E5 40 ];
local-mac-address = [ 00 E0 0C BC E5 40 ];
interrupts = <4 8 >;
interrupt-parent = < &ipic >;
// NOTE: for 7-wire, remove phy-handle
// and add seven-wire
phy-handle = < &phy >;
//seven-wire;
};
when boot from NFS, some information as belows:
011400.serial: ttyPSC1 at MMIO 0x80011400 (irq = 40) is a MPC52xx PSC
RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
loop: module loaded
*fs_enet.c:v1.0 (Aug 8, 2005)
FEC MII Bus: probed
...............................
*Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17*
IP-Config: Complete:
device=eth0, addr=128.224.162.57, mask=255.255.254.0,
gw=128.224.162.1,
host=mpc5121e_ads, domain=, nis-domain=(none),
bootserver=128.224.162.142, rootserver=128.224.162.142, rootpath=
*md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.*
Looking up port of RPC 100003/2 on 128.224.162.142
rpcbind: server 128.224.162.142 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 128.224.162.142
rpcbind: server 128.224.162.142 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 128.224.162.142 not responding, timed out
Root-NFS: Server returned error -5 while mounting
Who can give me some advice ?
Thanks in adance.
BRs,
Andrew
^ permalink raw reply
* Re: Powerbook shuts down hard when hot, patch found
From: Benjamin Herrenschmidt @ 2007-09-29 22:49 UTC (permalink / raw)
To: Michael Buesch; +Cc: linuxppc-dev
In-Reply-To: <200709300026.07219.mb@bu3sch.de>
On Sun, 2007-09-30 at 00:26 +0200, Michael Buesch wrote:
> On Sunday 30 September 2007 00:19:53 Benjamin Herrenschmidt wrote:
> >
> > >
> > > This all smells to me like a silicon bug, so I'd start searching
> > > in the silicon erratas. But I'm not sure, of course. It's also strange
> > > that it depends on temperature. (That's why I first expected the PMU
> > > would cause this).
> > >
> > > Thanks for your help.
> >
> > Could be that we are creating a short by driving the output low, thus
> > causing the silicon to heat up, but that's strange.
>
> Well. The machine needs to be hot in the first place to trigger it.
> If it's cold it boots and runs fine even with that patch.
> Even if I run it hot after boot it does not shutdown. It only shuts down
> on boot when this register is written and when it's hot at this point.
Well, it's possible that they have a too weak pull-up resistor on those
lines, and thus when asserted to 0, a significant current goes through
causing the whole thing to heat up. That heat added to the residual heat
of a hot boot becomes then enough to trigger the temperature sensor
threshold... just one possible explanation.
> That's why I thought about some silicon bug. Why only when it's hot? :)
>
> > Also, the other change I made you do turns these into inputs, thus the
>
> The _EN bits are already all cleared, as you can see in my printk dump.
> So clearing them has no effect, of course.
> So the ports are Inputs as default on boot.
Hrm, that's weird then, because in that case, changing the output bits
shouldn't have any effect, unless maybe on some chips, the EN bits are
flipped. I don't have anything specific about the rv350 tho.
Can you print which specific DDC register is doing that (it's called
twice right ?) and maybe do a patch preventing that write only for one
of them and let me know if it makes a difference.
> > DDL lines should be pulled up, unless ... the board doesn't have
> > pullups.
>
> Well, I can't tell you :)
Heh
Ben.
^ permalink raw reply
* Re: Powerbook shuts down hard when hot, patch found
From: Michael Buesch @ 2007-09-29 22:26 UTC (permalink / raw)
To: benh; +Cc: linuxppc-dev
In-Reply-To: <1191104393.28637.5.camel@pasglop>
On Sunday 30 September 2007 00:19:53 Benjamin Herrenschmidt wrote:
>
> >
> > This all smells to me like a silicon bug, so I'd start searching
> > in the silicon erratas. But I'm not sure, of course. It's also strange
> > that it depends on temperature. (That's why I first expected the PMU
> > would cause this).
> >
> > Thanks for your help.
>
> Could be that we are creating a short by driving the output low, thus
> causing the silicon to heat up, but that's strange.
Well. The machine needs to be hot in the first place to trigger it.
If it's cold it boots and runs fine even with that patch.
Even if I run it hot after boot it does not shutdown. It only shuts down
on boot when this register is written and when it's hot at this point.
That's why I thought about some silicon bug. Why only when it's hot? :)
> Also, the other change I made you do turns these into inputs, thus the
The _EN bits are already all cleared, as you can see in my printk dump.
So clearing them has no effect, of course.
So the ports are Inputs as default on boot.
> DDL lines should be pulled up, unless ... the board doesn't have
> pullups.
Well, I can't tell you :)
--
Greetings Michael.
^ permalink raw reply
* Re: Powerbook shuts down hard when hot, patch found
From: Benjamin Herrenschmidt @ 2007-09-29 22:19 UTC (permalink / raw)
To: Michael Buesch; +Cc: linuxppc-dev
In-Reply-To: <200709292353.06476.mb@bu3sch.de>
>
> This all smells to me like a silicon bug, so I'd start searching
> in the silicon erratas. But I'm not sure, of course. It's also strange
> that it depends on temperature. (That's why I first expected the PMU
> would cause this).
>
> Thanks for your help.
Could be that we are creating a short by driving the output low, thus
causing the silicon to heat up, but that's strange.
Also, the other change I made you do turns these into inputs, thus the
DDL lines should be pulled up, unless ... the board doesn't have
pullups.
Ben.
^ permalink raw reply
* Re: Powerbook shuts down hard when hot, patch found
From: Michael Buesch @ 2007-09-29 21:53 UTC (permalink / raw)
To: benh; +Cc: linuxppc-dev
In-Reply-To: <1191102715.28637.0.camel@pasglop>
On Saturday 29 September 2007 23:51:55 Benjamin Herrenschmidt wrote:
>
> On Sat, 2007-09-29 at 13:22 +0200, Michael Buesch wrote:
> > On Saturday 29 September 2007 13:06:59 Michael Buesch wrote:
> > > > This is very strange... Can you try also clearing VGA_DDC_CLK_OUT_EN and
> > > > VGA_DDC_DATA_OUT_EN and the same time and see if that helps ?
> > >
> > > It still triggers the bug then.
> >
> > I tried something else.
> > I removed the write and only added a printk with a register read
> > to print the contents (DDC REG IS 0x...) . This is the result:
> >
> > [ 0.431304] PCI: Enabling device 0000:00:10.0 (0006 -> 0007)
> > [ 0.626866] radeonfb (0000:00:10.0): Invalid ROM signature 303 should be 0xaa55
> > [ 0.626877] radeonfb: Retrieved PLL infos from Open Firmware
> > [ 0.626887] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz
> > [ 0.626897] radeonfb: PLL min 12000 max 35000
> > [ 0.627194] DDC REG IS 0x00000303
> > [ 0.763751] i2c-adapter i2c-2: unable to read EDID block.
> > [ 0.983746] i2c-adapter i2c-2: unable to read EDID block.
> > [ 1.203745] i2c-adapter i2c-2: unable to read EDID block.
> > [ 1.280001] DDC REG IS 0x00000000
> > [ 1.620189] ieee1394: Host added: ID:BUS[0-00:1023] GUID[001124fffed98036]
> > [ 1.670984] radeonfb: Monitor 1 type LCD found
> > [ 1.670992] radeonfb: EDID probed
> > [ 1.670997] radeonfb: Monitor 2 type no found
> > [ 1.671012] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0
> > [ 1.671075] radeonfb: Dynamic Clock Power Management enabled
> > [ 1.712658] Console: switching to colour frame buffer device 160x53
> > [ 1.735555] radeonfb: Backlight initialized (radeonbl0)
> > [ 1.735746] radeonfb (0000:00:10.0): ATI Radeon NP
> > [ 1.738776] Generic RTC Driver v1.07
> > [ 1.738995] Macintosh non-volatile memory driver v1.1
> > ...
> >
> > Note that the function is called twice. Is that correct?
>
> Yes. That's expected, with different registers though.
>
> I don't quite get what's going on. I'll have to figure that out with ATI
> if they bother helping...
This all smells to me like a silicon bug, so I'd start searching
in the silicon erratas. But I'm not sure, of course. It's also strange
that it depends on temperature. (That's why I first expected the PMU
would cause this).
Thanks for your help.
--
Greetings Michael.
^ permalink raw reply
* Re: Powerbook shuts down hard when hot, patch found
From: Benjamin Herrenschmidt @ 2007-09-29 21:51 UTC (permalink / raw)
To: Michael Buesch; +Cc: linuxppc-dev
In-Reply-To: <200709291322.59607.mb@bu3sch.de>
On Sat, 2007-09-29 at 13:22 +0200, Michael Buesch wrote:
> On Saturday 29 September 2007 13:06:59 Michael Buesch wrote:
> > > This is very strange... Can you try also clearing VGA_DDC_CLK_OUT_EN and
> > > VGA_DDC_DATA_OUT_EN and the same time and see if that helps ?
> >
> > It still triggers the bug then.
>
> I tried something else.
> I removed the write and only added a printk with a register read
> to print the contents (DDC REG IS 0x...) . This is the result:
>
> [ 0.431304] PCI: Enabling device 0000:00:10.0 (0006 -> 0007)
> [ 0.626866] radeonfb (0000:00:10.0): Invalid ROM signature 303 should be 0xaa55
> [ 0.626877] radeonfb: Retrieved PLL infos from Open Firmware
> [ 0.626887] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz
> [ 0.626897] radeonfb: PLL min 12000 max 35000
> [ 0.627194] DDC REG IS 0x00000303
> [ 0.763751] i2c-adapter i2c-2: unable to read EDID block.
> [ 0.983746] i2c-adapter i2c-2: unable to read EDID block.
> [ 1.203745] i2c-adapter i2c-2: unable to read EDID block.
> [ 1.280001] DDC REG IS 0x00000000
> [ 1.620189] ieee1394: Host added: ID:BUS[0-00:1023] GUID[001124fffed98036]
> [ 1.670984] radeonfb: Monitor 1 type LCD found
> [ 1.670992] radeonfb: EDID probed
> [ 1.670997] radeonfb: Monitor 2 type no found
> [ 1.671012] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0
> [ 1.671075] radeonfb: Dynamic Clock Power Management enabled
> [ 1.712658] Console: switching to colour frame buffer device 160x53
> [ 1.735555] radeonfb: Backlight initialized (radeonbl0)
> [ 1.735746] radeonfb (0000:00:10.0): ATI Radeon NP
> [ 1.738776] Generic RTC Driver v1.07
> [ 1.738995] Macintosh non-volatile memory driver v1.1
> ...
>
> Note that the function is called twice. Is that correct?
Yes. That's expected, with different registers though.
I don't quite get what's going on. I'll have to figure that out with ATI
if they bother helping...
Ben.
^ permalink raw reply
* Re: [PATCH] cpm: Describe multi-user ram in its own device node.
From: Kumar Gala @ 2007-09-29 14:34 UTC (permalink / raw)
To: Vitaly Bordug; +Cc: PowerPC dev list, Timur Tabi
In-Reply-To: <20070929104917.1585737e@kernel.crashing.org>
On Sep 29, 2007, at 1:49 AM, Vitaly Bordug wrote:
> Hello Kumar,
>
> On Fri, 28 Sep 2007 18:53:38 -0500
> Kumar Gala wrote:
>
>>
>> On Sep 28, 2007, at 3:30 PM, Vitaly Bordug wrote:
>>
>>> Kumar,
>>>
>>> Realizing this may suffer a bit from cleanest-dts flame war, but
>>> anyway I pretty much see a lot of
>>> sense in getting this in during next merge window. Is this possible?
>>
>> Probably, does QE have muram? I can't keep these things straight.
>>
>
> cpms have dpram, qe has muram. these two are the same stuff in
> fact. Or you are asking about have QE stuff utilize such a binding
> at the same pass?
I was asking about both these things.
- k
^ permalink raw reply
* Re: Powerbook shuts down hard when hot, patch found
From: Michael Buesch @ 2007-09-29 11:22 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <200709291306.59627.mb@bu3sch.de>
On Saturday 29 September 2007 13:06:59 Michael Buesch wrote:
> > This is very strange... Can you try also clearing VGA_DDC_CLK_OUT_EN and
> > VGA_DDC_DATA_OUT_EN and the same time and see if that helps ?
>
> It still triggers the bug then.
I tried something else.
I removed the write and only added a printk with a register read
to print the contents (DDC REG IS 0x...) . This is the result:
[ 0.431304] PCI: Enabling device 0000:00:10.0 (0006 -> 0007)
[ 0.626866] radeonfb (0000:00:10.0): Invalid ROM signature 303 should be 0xaa55
[ 0.626877] radeonfb: Retrieved PLL infos from Open Firmware
[ 0.626887] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz
[ 0.626897] radeonfb: PLL min 12000 max 35000
[ 0.627194] DDC REG IS 0x00000303
[ 0.763751] i2c-adapter i2c-2: unable to read EDID block.
[ 0.983746] i2c-adapter i2c-2: unable to read EDID block.
[ 1.203745] i2c-adapter i2c-2: unable to read EDID block.
[ 1.280001] DDC REG IS 0x00000000
[ 1.620189] ieee1394: Host added: ID:BUS[0-00:1023] GUID[001124fffed98036]
[ 1.670984] radeonfb: Monitor 1 type LCD found
[ 1.670992] radeonfb: EDID probed
[ 1.670997] radeonfb: Monitor 2 type no found
[ 1.671012] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0
[ 1.671075] radeonfb: Dynamic Clock Power Management enabled
[ 1.712658] Console: switching to colour frame buffer device 160x53
[ 1.735555] radeonfb: Backlight initialized (radeonbl0)
[ 1.735746] radeonfb (0000:00:10.0): ATI Radeon NP
[ 1.738776] Generic RTC Driver v1.07
[ 1.738995] Macintosh non-volatile memory driver v1.1
...
Note that the function is called twice. Is that correct?
--
Greetings Michael.
^ permalink raw reply
* Re: Powerbook shuts down hard when hot, patch found
From: Michael Buesch @ 2007-09-29 11:06 UTC (permalink / raw)
To: benh; +Cc: linuxppc-dev
In-Reply-To: <1191020653.6158.90.camel@pasglop>
On Saturday 29 September 2007 01:04:13 Benjamin Herrenschmidt wrote:
>
> On Fri, 2007-09-28 at 23:32 +0200, Michael Buesch wrote:
> > Hi,
> >
> > some time ago I already mailed you about this problem.
> > I will quickly describe what's going on, again:
> >
> > My powerbook boots fine when it's cold. You can work with
> > it and you can also run it hot (compile something, etc...).
> > But when you try to boot it while it is hot, it will
> > automatically shutdown hard inside of the boot process.
> > Some part of the hardware is shutting it down.
> > This does not happen when it's getting hot _after_ boot.
> > Only while boot when it's hot.
> >
> > I bisected the problem and found out that the following patch
> > is responsible for this. Yeah, this sounds a little bit
> > crazy, as this patch does not seem to be related to
> > this at all. But I confirmed it by booting kernel
> > 4f71c5de19c27f2198105d3b26b398494d5c353b
> > That kernel triggered the bug. Then I patch -R the patch below
> > and it booted properly, even when hot. I also rechecked
> > that it really was hot enough to trigger the event by
> > immediately rebooting into a known bad kernel, that immediately
> > shut down the pbook, as expected.
> > So I'm pretty sure it's the patch below causing this weird
> > behaviour. Any idea why?
>
> This is very strange... Can you try also clearing VGA_DDC_CLK_OUT_EN and
> VGA_DDC_DATA_OUT_EN and the same time and see if that helps ?
It still triggers the bug then.
--
Greetings Michael.
^ permalink raw reply
* Re: [Cbe-oss-dev] [patch 0/8] PS3 AV Settings Driver patches for 2.6.24
From: Geert Uytterhoeven @ 2007-09-29 8:00 UTC (permalink / raw)
To: Geoff Levand
Cc: linuxppc-dev, linux-fbdev-devel, cbe-oss-dev, Antonino A. Daplas
In-Reply-To: <46FD5604.3060104@am.sony.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2234 bytes --]
On Fri, 28 Sep 2007, Geoff Levand wrote:
> Michael Ellerman wrote:
> > On Thu, 2007-09-27 at 10:23 -0700, Geoff Levand wrote:
> >> Michael Ellerman wrote:
> >> > On Wed, 2007-09-26 at 18:33 +0200, Geert Uytterhoeven wrote:
> >> >> Question: As several DVI-D displays advertise they support 1080i modes while
> >> >> they actually don't (cfr. the quirk database), perhaps I should drop 1080i
> >> >> modes completely from the ps3av_preferred_modes[] table? Usually 720p looks
> >> >> better than 1080i anyway. What do you think?
> >> >
> >> > Definitely. If the autodetection fails Linux is basically unusable on
> >> > PS3 unless you hack the kernel sources and build your own kboot and
> >> > otheros.bld - not entirely trivial for novice users. So it's pretty
> >> > important that it works 100%.
> >>
> >> It is not that bad. If a bootloader is configued to use autodetection
> >> so that it is shown at best video mode, then it should have advertised
> >> key sequences to default to known video modes, with at least a 480p 'safe'
> >> mode.
> >
> > Oh OK, that is a good idea. What's the "safe mode" key sequence for the
> > otheros.bld you provide on kernel.org?
>
> I don't maintain that, and have no idea how it sets its video mode. Did you
> have trouble with it? I know in the past it used a fixed 480p mode.
It uses the autodetect mode. In the past, the kernel defaulted to 480p for
DVI-D/HDMI displays, 480i for other displays.
So far no one complained about the new otheros.bld (AFAIK). Which doesn't mean
that (a) the problem doesn't happen and (b) it wouldn't be nice to have a `safe
mode' key sequence...
With kind regards,
Geert Uytterhoeven
Software Architect
Sony Network and Software Technology Center Europe
The Corporate Village · Da Vincilaan 7-D1 · B-1935 Zaventem · Belgium
Phone: +32 (0)2 700 8453
Fax: +32 (0)2 700 8622
E-mail: Geert.Uytterhoeven@sonycom.com
Internet: http://www.sony-europe.com/
Sony Network and Software Technology Center Europe
A division of Sony Service Centre (Europe) N.V.
Registered office: Technologielaan 7 · B-1840 Londerzeel · Belgium
VAT BE 0413.825.160 · RPR Brussels
Fortis Bank Zaventem · Swift GEBABEBB08A · IBAN BE39001382358619
^ permalink raw reply
* Re: [PATCH] cpm: Describe multi-user ram in its own device node.
From: Vitaly Bordug @ 2007-09-29 6:49 UTC (permalink / raw)
To: Kumar Gala; +Cc: PowerPC dev list, Timur Tabi
In-Reply-To: <08C0C9CB-C958-4B95-81B8-D0677CBA4399@kernel.crashing.org>
Hello Kumar,
On Fri, 28 Sep 2007 18:53:38 -0500
Kumar Gala wrote:
>
> On Sep 28, 2007, at 3:30 PM, Vitaly Bordug wrote:
>
> > Kumar,
> >
> > Realizing this may suffer a bit from cleanest-dts flame war, but
> > anyway I pretty much see a lot of
> > sense in getting this in during next merge window. Is this possible?
>
> Probably, does QE have muram? I can't keep these things straight.
>
cpms have dpram, qe has muram. these two are the same stuff in fact. Or you are asking about have QE stuff utilize such a binding at the same pass?
--
Sincerely, Vitaly
^ permalink raw reply
* Re: [PATCH 1/9] fs_enet: Whitespace cleanup.
From: Jeff Garzik @ 2007-09-29 5:21 UTC (permalink / raw)
To: Scott Wood; +Cc: netdev, linuxppc-dev
In-Reply-To: <20070920220116.GA28784@loki.buserror.net>
Scott Wood wrote:
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
> drivers/net/fs_enet/fs_enet-main.c | 85 ++++++++++++++++-------------------
> drivers/net/fs_enet/fs_enet.h | 4 +-
> drivers/net/fs_enet/mac-fcc.c | 1 -
> drivers/net/fs_enet/mii-bitbang.c | 3 -
> drivers/net/fs_enet/mii-fec.c | 1 -
> 5 files changed, 41 insertions(+), 53 deletions(-)
ACK patches 1-2, 4-9
This patch doesn't apply cleanly to netdev-2.6.git#upstream (nor
net-2.6.24.git), so this and the rest of the patch series failed to apply.
Please resend series on top of netdev-2.6.git#upstream or net-2.6.24.git.
^ permalink raw reply
* Re: [PATCH 3/9] fs_enet: Don't share the interrupt.
From: Jeff Garzik @ 2007-09-29 5:18 UTC (permalink / raw)
To: Scott Wood; +Cc: netdev, linuxppc-dev
In-Reply-To: <20070920220118.GC28784@loki.buserror.net>
Scott Wood wrote:
> This driver can't handle an interrupt immediately after request_irq
You MUST assume that you will receive an interrupt immediately after
request_irq(). If fs_enet cannot handle that, then that is what wants
fixing.
Please send along a fix for this, rather than band-aiding the problem.
^ permalink raw reply
* Re: [PATCH] cpm: Describe multi-user ram in its own device node.
From: Kumar Gala @ 2007-09-28 23:53 UTC (permalink / raw)
To: Vitaly Bordug; +Cc: PowerPC dev list, Timur Tabi
In-Reply-To: <20070929003005.59afc2a0@kernel.crashing.org>
On Sep 28, 2007, at 3:30 PM, Vitaly Bordug wrote:
> Kumar,
>
> Realizing this may suffer a bit from cleanest-dts flame war, but
> anyway I pretty much see a lot of
> sense in getting this in during next merge window. Is this possible?
Probably, does QE have muram? I can't keep these things straight.
- k
^ 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