* Linux MPC8280 patch
From: Srivatsan @ 2004-12-13 4:40 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <20041213010004.457862BF24@ozlabs.org>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
Dear all,
1) I am trying to bring up a Rattler board by using MPC8260ADS
kernel. From what I am seeing from all my trials MPC8260ADS kernel is
not bringing up the MPC8280 based board.
2) Is there any patch to be added to the MPC8260 based kernel to
bring up the MPC8280 based board? If so, May I know the name of the
patch?
Expecting all your help.
With Best Regards,
C.R.Srivatsan
********************************DISCLAIMER**********************************
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege of Deccanet Designs Ltd.
If you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you are strictly prohibited from retaining, using, copying, altering or
disclosing the contents of this message.
****************************************************************************
^ permalink raw reply
* Re: Write Combining on PowerPC
From: Lawrence E. Bakst @ 2004-12-13 8:38 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <41B9A33A.21673.5DDD7F64@localhost>
At 1:23 PM -0800 12/10/04, Kendall Bennett wrote:
>Hi Guys,
>
>We are working on some PowerPC machines and noticed that the boxes don't
>appear to support the equivalent of Write Combining that we get on x86
>boxes. Copies to Video Memory on our Motorola Sandpoint box run about
>10Mb/s, which is terribly, terribly slow!
>
>Does anyone know if it is possible to do something similar to Write
>Combining for the PowerPC architecture, to speed up CPU access to the
>linear framebuffer? Part of the problem is that for video overlay support
>(not motion compensation) you have to dump the entire YUV frame into
>video memory for the hardware overlay, and even on a 1GHz PPC box playing
>an MPEG2 stream is not possible as X takes up over 80% of the CPU just to
>copy the YUV data to video memory!
1. As a previous poster mentioned many PPCs have write combining but they usually call it store gathering. I was just reading about it in the IBM 970fx.
2. What you need are cache line reads or writes through your bridge to the video memory.
3. If your frame buffer is marked non-cachable, which is the usually case, see if you can set up a second aperture that is cached. Otherwise I don't think the store gatherin will work. I don't know your board or processor but you should experiment with cache modes to see which if any work best.
4. Assuming you can get a cachable aperture you need to remember when writing a complete image to frame buffer memory is that you waste 50% of your bandwidth reading cache lines from the frame buffer into your cache. You can use dcbz to clear a cache line and then write it. This should double your bandwidth to 20 MB/sec.
5. How good is your copy loop? if you have floating point registers you can often use these to increase your efficiency. There may be other ways to make the copy loop more efficient using processor specific instructions that generate more efficient memory loads and stores. Try loop unrolling. Also make sure you prefetch the source using a dcbt or similar instruction. You have to experiment to see how far ahead of needed the data you need to prefecth.
6. Use small test programs to get it right.
7. You don't mention your processor type/speed, bus speeds and memory speed so it's pretty hard to tell what efficiency you might be able to achieve.
8. I make no comment about the efficiency of X. It's not would I would use for video applications although I am sure there are those that have hacked it work there.
Best,
leb
>
>
>Obviously bus mastering will help solve this problem, but it would be
>better if there was a way to enabling faster CPU access to the
>framebuffer as well.
>
>Regards,
>
>---
>Kendall Bennett
>Chief Executive Officer
>SciTech Software, Inc.
>Phone: (530) 894 8400
>http://www.scitechsoft.com
>
>~ SciTech SNAP - The future of device driver technology! ~
>
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply
* Re: [BUG?] [PPC/403/IBM] compile error 2.6.9 and earlier
From: Eugene Surovegin @ 2004-12-13 9:52 UTC (permalink / raw)
To: Nico Schottelius, linux-kernel; +Cc: linuxppc-embedded
In-Reply-To: <20041213091027.GA2384@schottelius.org>
On Mon, Dec 13, 2004 at 10:10:28AM +0100, Nico Schottelius wrote:
> I didn't find linux-ppc list on vger, so I hope this list is correct:
Look at http://ozlabs.org/mailman/listinfo. I'm forwarding my reply to
linuxppc-embedded as well.
> When trying to compile a kernel for my ibm thinclient, which has a
> 403 PPC processor, I get the attached compile error.
Yes, it's a known problem, 403 build is broken and 4xx maintainer told
me that it hadn't been removed completely mostly because of
sentimental reasons (IIRC first TiVos used 403 chip);
Looks like we have a person who needs it working. Feel free to fix it
and submit a patch :).
--
Eugene
^ permalink raw reply
* Re: PPC4XX DMA polarity bug in linuxppc-2.6.9
From: Mark Powell @ 2004-12-13 9:48 UTC (permalink / raw)
To: cwernham; +Cc: linuxppc-dev
In-Reply-To: <41B8255A.3040101@airspan.com>
Colin Wernham wrote:
> I believe that there is a PPC4xx DMA driver bug in the following
> kernel, file and function:
> linuxppc-2.6.9,
> /arch/ppc/syslib/ppc4xx_dma.c,
> ppc4xx_init_dma_channel()
>
>
> Is there anyone else using the PPC4XX DMA?
FWIW
I have used the PPC4xx dma on 405GP systems and a 440GP system with
2.4.21 and 2.4.25. I found the ppc4xx_dma.c functions didn't work in the
way I needed. I just read the code very carefully and used a few of the
functions combined with some direct manipulation of the DMA registers.
As I recall, I don't think the polarity is the only problem in that
file. It certainly doesn't support the 440 DMA registers - the COUNT
register is different.
The code in ppc4xx_dma.c is however, very useful as a guide in how to go
about setting up a DMA transfer; just read it carefully with the
processor manual to hand.
--
Mark Powell, Senior Software Engineer
Curtiss-Wright Controls Embedded Computing
Tel: +44 (0) 1763 852222
Email: medp@primagraphics.com
^ permalink raw reply
* fcc_enet driver in linux 2.6.9
From: Saso Kavcic @ 2004-12-13 9:40 UTC (permalink / raw)
To: linuxppc-embedded
Hi,
I am new to working in embedded linux applications and would appreciate
a little help.
We are porting linux to a custom mpc8275 board and we are having some
difficulties
with the fcc ethernet driver. Does anyone know if the fcc enet driver in
linux 2.6.9
kernel works and if it works if the kernel is compiled preemptible. We
are trying to
boot the kernel with dhcp, but the network seems very slow and
unreliable and this
only with "preemptible kernel" option disabled. We are using mpc8275VR
and LXT972A
PHY, could this be the cause for trouble.
Best Regards, Saso
^ permalink raw reply
* Re: [PATCH][EMAC] allow rx of the maximum sized VLAN tagged packets
From: Andriy Korud @ 2004-12-13 13:08 UTC (permalink / raw)
To: Matt Porter; +Cc: jgarzik, linuxppc-embedded
In-Reply-To: <20041207105250.C13540@home.com>
Hi,
as I know from documentation and IBM's support when you program VTPID
register, EMAC will receive only frames with programmed ID. Other frames
will be received only if they do not exceed 1518 bytes.
Can anybody please comment this?
Thanks in advance,
--
Andriy Korud
On Tue, 2004-12-07 at 10:52 -0700, Matt Porter wrote:
> Patch enables EMAC to receive maximum sized VLAN tagged packets.
>
> Signed-off-by: Eugene Surovegin <ebs@ebshome.net>
> Signed-off-by: Matt Porter <mporter@kernel.crashing.org>
>
> ===== drivers/net/ibm_emac/ibm_emac.h 1.1 vs edited =====
> --- 1.1/drivers/net/ibm_emac/ibm_emac.h 2004-05-22 10:13:08 -07:00
> +++ edited/drivers/net/ibm_emac/ibm_emac.h 2004-08-24 12:19:41 -07:00
> @@ -98,7 +98,7 @@
> #endif /* CONFIG_IBM_EMAC4 */
> #define EMAC_M1_BASE (EMAC_M1_TX_FIFO_2K | \
> EMAC_M1_APP | \
> - EMAC_M1_TR)
> + EMAC_M1_TR | EMAC_M1_VLE)
>
> /* Transmit Mode Register 0 */
> #define EMAC_TMR0_GNP0 0x80000000
> ===== drivers/net/ibm_emac/ibm_emac_core.c 1.2 vs edited =====
> --- 1.2/drivers/net/ibm_emac/ibm_emac_core.c 2004-06-04 08:50:36 -07:00
> +++ edited/drivers/net/ibm_emac/ibm_emac_core.c 2004-08-24 12:18:27 -07:00
> @@ -1335,6 +1335,9 @@
>
> /* set frame gap */
> out_be32(&emacp->em0ipgvr, CONFIG_IBM_EMAC_FGAP);
> +
> + /* set VLAN Tag Protocol Identifier */
> + out_be32(&emacp->em0vtpid, 0x8100);
>
> /* Init ring buffers */
> emac_init_rings(fep->ndev);
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply
* depmod.pl script & kernel 2.6
From: alebas @ 2004-12-13 13:32 UTC (permalink / raw)
To: linuxppc-embedded
Hi all,
Till now I've been using the ELDK 3.0 framework for development.
Now I am involved in some development on kernel 2.6, and I would
prefer using kernel modules. But I can't get script depmod.pl in
eldk/usr/sbin working with kernel 2.6 modules.
I've checked for a new version of this script on Busybox (I think
it's the same than ELDK's one), but since version 1.0 this is not
available.
So, how are you coping with this? Is there any way to use ELDK
with kernel 2.6 modules? Or should I change to another framework?
Currently, I work with ELDK on an i686 system, cross-compiling
onto PPC with the ppc_82xx- toolchain included in the ELDK.
I use the SELF's RamFS from the ELDK, with Busybox shell and
modutils. The depmod.pl script creates the modules.dep file
in this rootfs.
Thanks,
Alex
^ permalink raw reply
* [PATCH]PPC4XX DMA polarity init fix kernel 2.6.9
From: Colin Wernham @ 2004-12-13 14:08 UTC (permalink / raw)
To: mporter; +Cc: inuxppc-dev, linuxppc-embedded
This patch applies to the kernel 2.6.9 and fixes the initialisation of
the DMA channel polarity in the function ppc4xx_init_dma_channel() for
the PPC 4XX processor.
Signed-off-by: Colin P Wernham <cwernham@airspan.com>
--- /home/cwernham/work/linux-2.6.9.old/arch/ppc/syslib/ppc4xx_dma.c
2004-10-18 22:55:35.000000000 +0100
+++ arch/ppc/syslib/ppc4xx_dma.c 2004-12-10 09:19:19.000000000 +0000
@@ -466,7 +466,7 @@ ppc4xx_init_dma_channel(unsigned int dma
/* clear all polarity signals and then "or" in new signal levels */
polarity &= ~GET_DMA_POLARITY(dmanr);
- polarity |= p_dma_ch->polarity;
+ polarity |= p_init->polarity;
#if DCRN_POL > 0
mtdcr(DCRN_POL, polarity);
#endif
^ permalink raw reply
* [PATCH]PPC4XX DMA polarity init fix kernel 2.6.9
From: Colin Wernham @ 2004-12-13 14:51 UTC (permalink / raw)
To: linuxppc-dev
This patch applies to the kernel 2.6.9 and fixes the initialisation of
the DMA channel polarity in the function ppc4xx_init_dma_channel() for
the PPC 4XX processor.
Signed-off-by: Colin P Wernham <cwernham@airspan.com>
--- /home/cwernham/work/linux-2.6.9.old/arch/ppc/syslib/ppc4xx_dma.c
2004-10-18 22:55:35.000000000 +0100
+++ arch/ppc/syslib/ppc4xx_dma.c 2004-12-10 09:19:19.000000000 +0000
@@ -466,7 +466,7 @@ ppc4xx_init_dma_channel(unsigned int dma
/* clear all polarity signals and then "or" in new signal levels */
polarity &= ~GET_DMA_POLARITY(dmanr);
- polarity |= p_dma_ch->polarity;
+ polarity |= p_init->polarity;
#if DCRN_POL > 0
mtdcr(DCRN_POL, polarity);
#endif
^ permalink raw reply
* Lite5200 and PCI1520
From: Zeitler, Nathan @ 2004-12-13 17:50 UTC (permalink / raw)
To: linuxppc-embedded
Greetings all,
I would greatly appreciate some advice regarding getting Linux to read
and write to CompactFlash devices behind a PCI1520 PCI bridge on a
custom Lite5200 board. I am admittedly new to this process within
embedded devices and could use some direction. We're using a recent
2.4.25 kernel from Denx, as well as UBOOT 1.1.1 and ELDK2.1. =20
My status:
UBOOT detects the PCI Bridge just fine. I'm able to read and write to
the registers within the PCI1520 using the BDI2000 as well as UBOOT's
pci command. I've therefore set up the bridge to use its output to run
the power chip instead of reading an EEPROM for its settings. I've also
set up the multifunction pins to be "parallel PCI only", as they are
connected to hardware "IRQ1" and "IRQ2" of the MPC5200. I've tried
several different values for the Interrupt Line register, but am mostly
flying blind in this respect. I've enabled most every PCMCIA option in
the Linux kernel I could find, enabled PnP and Cardbus support, but not
i82365 compatible bridge support as it seemed to scan for ISA resources
that weren't there (I understand the yenta driver doesn't want nor need
this anyway?).
My problem:
I can't access anything plugged into the sockets! PCI1520 registers
detect a card is inserted, but I can't read and write to flash cards
from Linux. I checked out PCMCIA Card Services from CVS, compiled and
ran cardmgr and it gives a seg-fault, but indicates it is watching the
sockets (debug output seems to confirm this). I can read the status and
config using cardctl, but reading the identification or info causes
another seg fault. I suspect I may be running into a combination of
interrupt and driver issues, but I need a knowledgeable opinion on this.
I'm most confused by the line between ISA and PCI IRQs, and how or why
CF uses these. I've appended some interesting messages from Linux's
boot sequence. Thanks in advance.
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus]
yenta 00:18.0: no resource of type 100 available, trying to continue...
yenta 00:18.0: no resource of type 100 available, trying to continue...
yenta 00:18.1: no resource of type 100 available, trying to continue...
yenta 00:18.1: no resource of type 100 available, trying to continue...=20
/* type 100 =3D=3D IO_RESOURCE, recoding yenta.c to bind them=20
to a 0x5000nnnn address range stopped the error,=20
but seemed to fix nothing */=20
...
Yenta ISA IRQ mask 0x0000, PCI irq 255
Socket status: 30000810
Yenta ISA IRQ mask 0x0000, PCI irq 255
Socket status: 30000006
/* 255 seems to be the default value,
But what should it be instead? */
Nathan Zeitler
Systems Engineer
Open Systems International, Inc.
3600 Holly Lane North, Suite 40
Minneapolis, MN 55447-1286
Phone: (763) 551-0559
Fax: (763)551-0750
Email: nzeitler@osii.com
^ permalink raw reply
* Re: [PATCH][EMAC] allow rx of the maximum sized VLAN tagged packets
From: Eugene Surovegin @ 2004-12-13 18:02 UTC (permalink / raw)
To: Andriy Korud; +Cc: jgarzik, linuxppc-embedded
In-Reply-To: <1102943302.28201.14.camel@localhost>
On Mon, Dec 13, 2004 at 02:08:22PM +0100, Andriy Korud wrote:
> as I know from documentation and IBM's support when you program VTPID
> register, EMAC will receive only frames with programmed ID. Other frames
> will be received only if they do not exceed 1518 bytes.
> Can anybody please comment this?
I'm not sure I understand your question.
EMAC can process 1518-sized packets without any problems (1500 + 12 +
2 + 4) even without this patch. These are normal (non-VLAN tagged
packets).
With my patch EMAC will be able to receive 1522 sized frames which
are VLAN-tagged with _any_ VLAN tag. Note VTPID contains L2 protocol
id, _not_ VLAN/priority field itself. If frame is bigger than 1518
but doesn't have 0x8100 right after the source MAC address, "Packet
Too Long" error will be generated.
Also, 440GX has an option to process jumbo frames, but this is
completely different story.
--
Eugene
^ permalink raw reply
* [BUG?] [PPC/403/IBM] compile error 2.6.9 and earlier
From: Nico Schottelius @ 2004-12-13 21:37 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1.1: Type: text/plain, Size: 966 bytes --]
[repost: posted on linux-kernel before / hit the wrong list]
Hello!
I didn't find linux-ppc list on vger, so I hope this list is correct:
When trying to compile a kernel for my ibm thinclient, which has a
403 PPC processor, I get the attached compile error.
The error exists since 2.6.X, but the times before I tried to cross-compile,
this time I tried to built the kernel from my 'new' g3-ibook, which
failed again (so this is not a cross-compile error).
Thanks for any hints,
Nico
P.S.: See http://marc.theaimsgroup.com/?l=linux-kernel&m=110293175523284&w=2
for one 'possible answer' to my question. If that's true, is anyone
out there who wants me to guide to fix it? I'd really love to let the
IBM thinclients live with Linux.
P.P.S.: Please CC-me, I am not subscribed.
--
Keep it simple & stupid, use what's available.
Please use pgp encryption: 8D0E 27A4 is my id.
http://nico.schotteli.us | http://linux.schottelius.org
[-- Attachment #1.2: Log.oak --]
[-- Type: text/plain, Size: 4538 bytes --]
CLEAN arch/ppc/kernel
CLEAN init
CLEAN usr
CLEAN .tmp_versions
CLEAN include/asm-ppc/offsets.h arch/ppc/kernel/asm-offsets.s
CHK include/linux/version.h
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/split-include
HOSTCC scripts/basic/docproc
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/pnmtologo
HOSTCC scripts/conmakehash
HOSTCC scripts/bin2c
CC arch/ppc/kernel/asm-offsets.s
CHK include/asm-ppc/offsets.h
UPD include/asm-ppc/offsets.h
CC init/main.o
CHK include/linux/compile.h
dnsdomainname: No address associated with name
UPD include/linux/compile.h
CC init/version.o
CC init/do_mounts.o
CC init/do_mounts_devfs.o
CC init/do_mounts_rd.o
CC init/do_mounts_initrd.o
LD init/mounts.o
CC init/initramfs.o
LD init/built-in.o
HOSTCC usr/gen_init_cpio
CPIO usr/initramfs_data.cpio
GZIP 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/irq.o
CC arch/ppc/kernel/idle.o
CC arch/ppc/kernel/time.o
AS arch/ppc/kernel/misc.o
CC arch/ppc/kernel/process.o
CC arch/ppc/kernel/signal.o
CC arch/ppc/kernel/ptrace.o
CC arch/ppc/kernel/align.o
CC arch/ppc/kernel/semaphore.o
CC arch/ppc/kernel/syscalls.o
CC arch/ppc/kernel/setup.o
CC arch/ppc/kernel/cputable.o
CC arch/ppc/kernel/ppc_htab.o
CC arch/ppc/kernel/module.o
CC arch/ppc/kernel/ppc_ksyms.o
CC arch/ppc/kernel/dma-mapping.o
CC arch/ppc/kernel/pci.o
LD arch/ppc/kernel/built-in.o
AS arch/ppc/kernel/head_4xx.o
LDS arch/ppc/kernel/vmlinux.lds
LD arch/ppc/platforms/built-in.o
CC arch/ppc/mm/fault.o
CC arch/ppc/mm/init.o
CC arch/ppc/mm/mem_pieces.o
CC arch/ppc/mm/mmu_context.o
CC arch/ppc/mm/pgtable.o
CC arch/ppc/mm/4xx_mmu.o
LD arch/ppc/mm/built-in.o
AS arch/ppc/lib/checksum.o
AS arch/ppc/lib/string.o
CC arch/ppc/lib/strcase.o
CC arch/ppc/lib/dec_and_lock.o
AS arch/ppc/lib/div64.o
LD arch/ppc/lib/built-in.o
CC arch/ppc/syslib/ppc4xx_pic.o
arch/ppc/syslib/ppc4xx_pic.c: In function `ppc4xx_uic_enable':
arch/ppc/syslib/ppc4xx_pic.c:164: warning: implicit declaration of function `DCRN_UIC_ER'
arch/ppc/syslib/ppc4xx_pic.c:164: error: `UIC0' undeclared (first use in this function)
arch/ppc/syslib/ppc4xx_pic.c:164: error: (Each undeclared identifier is reported only once
arch/ppc/syslib/ppc4xx_pic.c:164: error: for each function it appears in.)
arch/ppc/syslib/ppc4xx_pic.c:165: warning: implicit declaration of function `DCRN_UIC_TR'
arch/ppc/syslib/ppc4xx_pic.c: In function `ppc4xx_uic_disable':
arch/ppc/syslib/ppc4xx_pic.c:202: error: `UIC0' undeclared (first use in this function)
arch/ppc/syslib/ppc4xx_pic.c: In function `ppc4xx_uic_disable_and_ack':
arch/ppc/syslib/ppc4xx_pic.c:228: error: `UIC0' undeclared (first use in this function)
arch/ppc/syslib/ppc4xx_pic.c:229: warning: implicit declaration of function `DCRN_UIC_SR'
arch/ppc/syslib/ppc4xx_pic.c: In function `ppc4xx_uic_end':
arch/ppc/syslib/ppc4xx_pic.c:270: error: `UIC0' undeclared (first use in this function)
arch/ppc/syslib/ppc4xx_pic.c: In function `ppc4xx_pic_get_irq':
arch/ppc/syslib/ppc4xx_pic.c:352: warning: implicit declaration of function `DCRN_UIC_MSR'
arch/ppc/syslib/ppc4xx_pic.c:352: error: `UIC0' undeclared (first use in this function)
arch/ppc/syslib/ppc4xx_pic.c: In function `ppc4xx_extpic_init':
arch/ppc/syslib/ppc4xx_pic.c:442: warning: implicit declaration of function `DCRN_UIC_PR'
arch/ppc/syslib/ppc4xx_pic.c:442: error: `UIC0' undeclared (first use in this function)
arch/ppc/syslib/ppc4xx_pic.c: In function `ppc4xx_pic_init':
arch/ppc/syslib/ppc4xx_pic.c:509: error: `UIC0' undeclared (first use in this function)
arch/ppc/syslib/ppc4xx_pic.c:510: warning: implicit declaration of function `DCRN_UIC_CR'
make[1]: *** [arch/ppc/syslib/ppc4xx_pic.o] Error 1
make: *** [arch/ppc/syslib] Error 2
[-- Attachment #1.3: 2.6.9-config-oak --]
[-- Type: text/plain, Size: 17811 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.9
# Mon Dec 13 10:45:14 2004
#
CONFIG_MMU=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_PPC=y
CONFIG_PPC32=y
CONFIG_GENERIC_NVRAM=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_LOCALVERSION="eiche"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
# CONFIG_TINY_SHMEM is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
#
# Processor
#
# CONFIG_6xx is not set
CONFIG_40x=y
# CONFIG_44x is not set
# CONFIG_POWER3 is not set
# CONFIG_POWER4 is not set
# CONFIG_8xx is not set
# CONFIG_E500 is not set
CONFIG_MATH_EMULATION=y
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_4xx=y
#
# IBM 4xx options
#
# CONFIG_ASH is not set
# CONFIG_BUBINGA is not set
# CONFIG_CPCI405 is not set
# CONFIG_EP405 is not set
CONFIG_OAK=y
# CONFIG_REDWOOD_5 is not set
# CONFIG_REDWOOD_6 is not set
# CONFIG_SYCAMORE is not set
# CONFIG_WALNUT is not set
CONFIG_IBM405_ERR51=y
CONFIG_403GCX=y
CONFIG_PPC4xx_DMA=y
CONFIG_PPC4xx_EDMA=y
CONFIG_PM=y
CONFIG_UART0_TTYS0=y
# CONFIG_UART0_TTYS1 is not set
CONFIG_NOT_COHERENT_CACHE=y
#
# Platform options
#
# CONFIG_PPC_MULTIPLATFORM is not set
# CONFIG_APUS is not set
# CONFIG_WILLOW is not set
# CONFIG_PCORE is not set
# CONFIG_POWERPMC250 is not set
# CONFIG_EV64260 is not set
# CONFIG_SPRUCE is not set
# CONFIG_LOPEC is not set
# CONFIG_MCPN765 is not set
# CONFIG_MVME5100 is not set
# CONFIG_PPLUS is not set
# CONFIG_PRPMC750 is not set
# CONFIG_PRPMC800 is not set
# CONFIG_SANDPOINT is not set
# CONFIG_ADIR is not set
# CONFIG_K2 is not set
# CONFIG_PAL4 is not set
# CONFIG_GEMINI is not set
# CONFIG_EST8260 is not set
# CONFIG_SBC82xx is not set
# CONFIG_SBS8260 is not set
# CONFIG_RPX8260 is not set
# CONFIG_TQM8260 is not set
# CONFIG_ADS8272 is not set
# CONFIG_LITE5200 is not set
CONFIG_PC_KEYBOARD=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
# CONFIG_HIGHMEM is not set
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE=""
#
# Bus options
#
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCI_LEGACY_PROC is not set
# CONFIG_PCI_NAMES is not set
#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_YENTA=m
CONFIG_CARDBUS=y
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_TCIC=m
#
# Advanced setup
#
CONFIG_ADVANCED_OPTIONS=y
CONFIG_HIGHMEM_START=0xfe000000
# CONFIG_LOWMEM_SIZE_BOOL is not set
CONFIG_LOWMEM_SIZE=0x30000000
# CONFIG_KERNEL_START_BOOL is not set
CONFIG_KERNEL_START=0xc0000000
# CONFIG_TASK_SIZE_BOOL is not set
CONFIG_TASK_SIZE=0x80000000
# CONFIG_CONSISTENT_START_BOOL is not set
CONFIG_CONSISTENT_START=0xff100000
# CONFIG_CONSISTENT_SIZE_BOOL is not set
CONFIG_CONSISTENT_SIZE=0x00200000
# CONFIG_BOOT_LOAD_BOOL is not set
CONFIG_BOOT_LOAD=0x00400000
#
# Device Drivers
#
#
# Generic Driver Options
#
# CONFIG_STANDALONE is not set
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER 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_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_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_LBD=y
#
# ATA/ATAPI/MFM/RLL support
#
# CONFIG_IDE is not set
#
# SCSI device support
#
# CONFIG_SCSI is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Macintosh device drivers
#
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_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 is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_NETFILTER is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP 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
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_IBM_EMAC=y
CONFIG_IBM_EMAC_ERRMSG=y
CONFIG_IBM_EMAC_RXB=64
CONFIG_IBM_EMAC_TXB=8
CONFIG_IBM_EMAC_FGAP=8
CONFIG_IBM_EMAC_SKBRES=0
# CONFIG_NET_PCI is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# PCMCIA network device support
#
# CONFIG_NET_PCMCIA is not set
#
# Wan interfaces
#
# 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_SHAPER is not set
# CONFIG_NETCONSOLE is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=y
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
# CONFIG_SERIO_RAW is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# 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=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_CS is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_NVRAM is not set
CONFIG_GEN_RTC=y
# CONFIG_GEN_RTC_X is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_RAW_DRIVER is not set
#
# I2C support
#
CONFIG_I2C=y
# CONFIG_I2C_CHARDEV is not set
#
# 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_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_ISA is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set
#
# Hardware Sensors Chip support
#
# CONFIG_I2C_SENSOR is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set
#
# Other I2C Chip support
#
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 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
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Misc devices
#
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
CONFIG_FB_CT65550=y
CONFIG_FB_ASILIANT=y
CONFIG_FB_IMSTT=y
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_RIVA is not set
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
# CONFIG_FB_MATROX_G450 is not set
CONFIG_FB_MATROX_G100A=y
CONFIG_FB_MATROX_G100=y
CONFIG_FB_MATROX_I2C=y
# CONFIG_FB_MATROX_MAVEN is not set
# CONFIG_FB_MATROX_MULTIHEAD is not set
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=y
CONFIG_FB_ATY=y
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GX=y
# CONFIG_FB_ATY_XL_INIT is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
CONFIG_FB_3DFX=y
# CONFIG_FB_3DFX_ACCEL is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
# CONFIG_USB is not set
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# File systems
#
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
# CONFIG_REISERFS_FS is not set
CONFIG_JFS_FS=y
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_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=y
# CONFIG_MSDOS_FS is not set
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="utf-8"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_DEVFS_FS=y
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# 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=y
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
# CONFIG_NFSD is not set
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
# CONFIG_EXPORTFS is not set
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=y
# CONFIG_SMB_NLS_DEFAULT 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=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
# CONFIG_MSDOS_PARTITION is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf-8"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=m
# 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=m
#
# IBM 40x options
#
#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
CONFIG_DEBUG_INFO=y
# CONFIG_KGDB is not set
# CONFIG_XMON is not set
# CONFIG_BDI_SWITCH is not set
# CONFIG_SCHEDSTATS is not set
# CONFIG_SERIAL_TEXT_DEBUG is not set
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_NULL is not set
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_TEST is not set
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
^ permalink raw reply
* RE: Lite5200 and PCI1520
From: Zeitler, Nathan @ 2004-12-13 22:09 UTC (permalink / raw)
To: wd; +Cc: linuxppc-embedded
Hello Wolfgang,=20
>Now what? Is it a custom board, or a Lite5200?=20
My apologies. It is a custom board based closely on the design of the
Lite5200. Thus we are able to put a PCI1520 chip on the same PCB and
connect it to the MPC5200 PCI bus.
>U-Boot 1.1.1 is old. You better use current code (top of CVS).
>
>ELDK 2.1 is extremely old. You better use a current version (3.1).
Agreed, they are old, although I was hoping to be more certain that the
age of the toolchain was a problem first. I have tried top-of-CVS
UBOOT, but reverted when no evident improvement occurred.=20
=20
>What's you PCMCIA config file looking like?
Under /etc/sysconfig/pcmcia:
PCMCIA=3Dyes
PCIC=3Dyenta_socket
PCIC_OPTS=3D
CORE_OPTS=3D
CARDMGR_OPTS=3D
Under /etc/pcmcia/config.opts...=20
(This is as how I found it, although I added the 4th port address and
changed the memory range in an attempt to get it to cooperate. I/O
resources aren't even being detected, so I tried adding 0x50000000 to
each I/O port address in yenta.c and adding the same value to each I/O
here to no avail):
include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff, port
0x1000-0x10ff
include memory 0x40000000-0x40001fff
include port 0xa00-0xaff
exclude irq 4
exclude irq 7
module "ray_cs" opts "essid=3DADHOC_ESSID hop_dwell=3D128 =
beacon_period=3D256
translate=3D1"
Help with respect to getting the interrupts and anything further
(configuration files and more) is appreciated, although for the sake of
keeping on topic, I can send any Card Services-based queries to the
pcmcia-cs mailing list if so desired :-)
^ permalink raw reply
* Re: Lite5200 and PCI1520
From: Wolfgang Denk @ 2004-12-13 21:13 UTC (permalink / raw)
To: Zeitler, Nathan; +Cc: linuxppc-embedded
In-Reply-To: <01C22B6B78D52B46BE3C38FB525617EF909AC5@osimail.osii.com>
In message <01C22B6B78D52B46BE3C38FB525617EF909AC5@osimail.osii.com> you wrote:
>
> and write to CompactFlash devices behind a PCI1520 PCI bridge on a
> custom Lite5200 board. I am admittedly new to this process within
Now what? Is it a custom board, or a Lite5200?
> embedded devices and could use some direction. We're using a recent
> 2.4.25 kernel from Denx, as well as UBOOT 1.1.1 and ELDK2.1.
U-Boot 1.1.1 is old. You better use current code (top of CVS).
ELDK 2.1 is extremely old. You better use a current version (3.1).
> I can't access anything plugged into the sockets! PCI1520 registers
> detect a card is inserted, but I can't read and write to flash cards
> from Linux. I checked out PCMCIA Card Services from CVS, compiled and
> ran cardmgr and it gives a seg-fault, but indicates it is watching the
What's you PCMCIA config file looking like?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Perl already has an IDE. It's called Unix.
-- Tom Christiansen in 375bd509@cs.colorado.edu
^ permalink raw reply
* Re: CONFIG_DUMMY_CONSOLE question
From: Tom Rini @ 2004-12-13 22:38 UTC (permalink / raw)
To: alebas; +Cc: linuxppc-embedded
In-Reply-To: <1102586055.41b820c776f7f@webmail.televes.com:443>
On Thu, Dec 09, 2004 at 10:54:15AM +0100, alebas@televes.com wrote:
> Hi all,
>
> Checking console initialization on mpc8272ads board,
> I have seen that the CONFIG_DUMMY_CONSOLE config
> parameter is allways set in root .config file, regardless
> of its value on my arch/ppc/configs/ads8272_defconfig file.
>
> This parameter drives to the VGA dummy console being
> compiled and included in the vmlinux binary, and started
> as default console for the board (which must be changed
> with console boot arg).
>
> Does anyone knows if this parameter is a must in any kernel
> 2.6 configuration? And why? Can it be removed, as my board
> doesn't use VGA at all? How? (I have tried several options)
It's not a "dummy" VGA console, it's a "dummy" console. IIRC, this is
selected with CONFIG_VT (or is it CONFIG_VT_CONSOLE?). IIRC, the real
problem is that when you have dummy console, it steals the console even
if you would have had console on some sort of serial port.
The bottom line is that if you don't have some sort of video device,
just disable CONFIG_VT.
--
Tom Rini
http://gate.crashing.org/~trini/
^ permalink raw reply
* RE: Lite5200 and PCI1520
From: Andrew Dennison @ 2004-12-13 23:48 UTC (permalink / raw)
To: 'Zeitler, Nathan', wd; +Cc: linuxppc-embedded
In-Reply-To: <01C22B6B78D52B46BE3C38FB525617EF909AC7@osimail.osii.com>
Nathan Zeitler wrote:
> Hello Wolfgang,
>=20
>> Now what? Is it a custom board, or a Lite5200?
>=20
> My apologies. It is a custom board based closely on the design of the
> Lite5200. Thus we are able to put a PCI1520 chip on the same PCB and
> connect it to the MPC5200 PCI bus.
Nathan,
I posted a question on cardbus with the 5200 a few weeks ago but got no
reply. I think the reason is that cardbus / pcmcia support may not have
been considered when the 5200 PCI memory map was laid out, but I would
love to be contradicted!
I also have a custom board with a mpc5200, pci1520 cardbus bridge, DDR,
etc.
Which kernel are you using?
I'm using Denx linuxppc_2_4_devel cvs and so far I've had to make =
several
changes to get close to a working system. I've changed the PCI bus =
mapping
so ISA I/O (ie PCMCIA) is at the bottom of the PCI address space, from =
my
reading / debugging this seems to be required to get PCMCIA to work. I
initially tried hacking yenta.c to use a high I/O range (like you have)
but this doesn't seem to be the solution. My memory map is now as =
follows:
/*
* VPC mapping deviates from icecube so PCMCIA can work!
* From Processor to PCI:
* PCI Mem Space: 0x40000000 - 0x50000000 -> 0x40000000 - 0x50000000
(256 MB)
* PCI I/O Space: 0x50000000 - 0x51000000 -> 0x00000000 - 0x01000000 =
(16
MB)
*
* From PCI to Processor:
* System Memory: 0x80000000 -> 0x00000000
*/
this also requires:
#define _IO_BASE isa_io_base=20
and isa_io_base to be set to the correct virtual address, =
pci_dram_offset
=3D 0x8000000, among other changes.
I also have a few outstanding issues that I haven't resolved yet, hence =
I
haven't posted a full patch, but I can now load and configure a wireless
ethernet card. Loading cardbus drivers currently fails when accessing =
PCI
configuration space on the cardbus bus, and I haven't sorted this out =
yet.
Part of the reason for my reply is also to check if my current approach
(remapping the PCI address space) is sane - comments anyone? I have made
similar changes in u-boot and can now read / write CF cards so it seems
like the right approach for the kernel too.
Andrew
^ permalink raw reply
* RE: Lite5200 and PCI1520
From: Zeitler, Nathan @ 2004-12-14 0:06 UTC (permalink / raw)
To: Andrew Dennison; +Cc: linuxppc-embedded
Hello Andrew,
>Nathan,
>I posted a question on cardbus with the 5200 a few weeks ago but got no
reply. I think the reason is that=20
>cardbus / pcmcia support may not have been considered when the 5200 PCI
memory map was laid out, but I >would love to be contradicted!
This would certainly help explain some of the pain in getting it to
work. :-/
>Which kernel are you using?
I'm using the 2.4.25 kernel from Denx also. The version I have is a
couple months old (trying to keep from changing too many things at once!
:-) ),but I have also tried the top-of-CVS version to no avail. My
ELDK version is old, as explained earlier, but I'm taking steps to
change that.
>I also have a few outstanding issues that I haven't resolved yet, hence
I haven't posted a full patch, but I can=20
>now load and configure a wireless ethernet card. Loading cardbus
drivers currently fails when accessing PCI >configuration space on the
cardbus bus, and I haven't sorted this out yet.
It sounds like we're working towards the same end! I would like to
assist in some way if possible. I am willing to believe that remapping
the PCI bus is a possible approach, although I'd like to hear the
opinion of others as well. Where in UBOOT did you change the PCI bus
mappings?
^ permalink raw reply
* Re: Lite5200 and PCI1520
From: Wolfgang Denk @ 2004-12-14 0:32 UTC (permalink / raw)
To: Andrew Dennison; +Cc: linuxppc-embedded
In-Reply-To: <002a01c4e16e$34451010$4000a8c0@CAT>
Dear Andrew,
in message <002a01c4e16e$34451010$4000a8c0@CAT> you wrote:
>
> I posted a question on cardbus with the 5200 a few weeks ago but got no
> reply. I think the reason is that cardbus / pcmcia support may not have
> been considered when the 5200 PCI memory map was laid out, but I would
> love to be contradicted!
I think I can confirm that this was not considered, but I'm not sure
that this is an issue here.
> I also have a few outstanding issues that I haven't resolved yet, hence I
> haven't posted a full patch, but I can now load and configure a wireless
> ethernet card. Loading cardbus drivers currently fails when accessing PCI
> configuration space on the cardbus bus, and I haven't sorted this out yet.
I'd like to see your patch (even if preliminary).
> Part of the reason for my reply is also to check if my current approach
> (remapping the PCI address space) is sane - comments anyone? I have made
> similar changes in u-boot and can now read / write CF cards so it seems
> like the right approach for the kernel too.
Unfortunately I don't have any hardware yet with a working cardbus
interface. But this might change soon...
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Men don't talk peace unless they're ready to back it up with war.
-- Col. Green, "The Savage Curtain", stardate 5906.4
^ permalink raw reply
* RE: Lite5200 and PCI1520
From: Andrew Dennison @ 2004-12-14 0:45 UTC (permalink / raw)
To: 'Zeitler, Nathan'; +Cc: linuxppc-embedded
In-Reply-To: <01C22B6B78D52B46BE3C38FB525617EF909AC8@osimail.osii.com>
On Tuesday, 14 December 2004 11:06 AM, Zeitler, Nathan wrote:
> Hello Andrew,
>=20
>=20
> This would certainly help explain some of the pain in getting it to
> work. :-/=20
I understand your pain :)
> I'm using the 2.4.25 kernel from Denx also. The version I have is a
> couple months old (trying to keep from changing too many
> things at once!
I'm actually using the "RTAI validated" version, but tried top of tree =
and
it doesn't help - no changes to the relevant parts.
> It sounds like we're working towards the same end! I would like to
> assist in some way if possible. =20
Cool - no point us both doing the same stuff. I've actually taken a =
break
from this for the last week but you've given me renewed enthusiasm:)
> I am willing to believe that
> remapping the PCI bus is a possible approach, although I'd like to
> hear the opinion of others as well. Where in UBOOT did you change
> the PCI bus mappings?
//Relevant section of u-boot/include/configs/VPC.h
/*
* Physical PCI Resource
* 0x00000000 - 0x3fffffff 0x80000000 - 0xBfffffff SDRAM
* 0x40000000 - 0x4fffffff 0x40000000 - 0x4fffffff PCI Memory
* 0x50000000 - 0x50ffffff 0x00000000 - 0x00ffffff PCI IO Space
*/
#define CONFIG_SDRAM_PHYS CFG_SDRAM_BASE
#define CONFIG_SDRAM_BUS 0x80000000
#define CONFIG_SDRAM_SIZE (1024 * 1024 * 1024)
#define CONFIG_PCI_MEM_PHYS 0x40000000
#define CONFIG_PCI_MEM_BUS 0x40000000
#define CONFIG_PCI_MEM_SIZE 0x10000000
#define CONFIG_PCI_IO_PHYS 0x50000000
#define CONFIG_PCI_IO_BUS 0x00000000
#define CONFIG_PCI_IO_SIZE 0x01000000
// This section does the actual pcmcia setup, and is kinda OT for this
list...
// but included for completeness
#define CONFIG_I82365
#define CFG_PCMCIA_MEM_ADDR 0x40400000 /* after last cardbus base
* window assigend
by
* pci_auto, but
can be anywhere in PCI_MEM range*/
#define CFG_PCMCIA_MEM_SIZE 0x1000
#define CONFIG_IDE_8xx_PCCARD 1 /* Use IDE with PC Card Adapter */
#define CFG_IDE_MAXBUS 1 /* max. 1 IDE bus */
#define CFG_IDE_MAXDEVICE 1 /* max. 1 drive per IDE bus */
#define CFG_ATA_IDE0_OFFSET 0
#define CFG_ATA_BASE_ADDR CONFIG_PCI_IO_PHYS
/* Offset for data I/O */
#define CFG_ATA_DATA_OFFSET 0x100 /* don't change - hard coded in
i82365 */
/* Offset for normal register accesses */
#define CFG_ATA_REG_OFFSET 0x100 /* don't change - hard coded in
i82365 */
/* Offset for alternate registers */
#define CFG_ATA_ALT_OFFSET 0x108 /* don't change - hard coded in
i82365 */
#define CONFIG_PCMCIA_SLOT_A /* there can be only one... */
^ permalink raw reply
* [PATCH] drivers/ide/ppc/pmac.c - CONFIG_BLK_DEV_IDEDMA_PMAC
From: Magnus Damm @ 2004-12-14 1:14 UTC (permalink / raw)
To: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
Hello,
The file drivers/ide/ppc/pmac.c in vanilla 2.6.9 and 2.6.10-rc3 will
not compile with some configurations, the attached patch contains the
following fixes:
- Make sure pmac.c compiles with CONFIG_BLK_DEV_IDEDMA_PMAC unset.
- CONFIG_BLK_DEV_IDEDMA_PMAC needs CONFIG_BLK_DEV_IDEDMA_PCI.
- Removes the default value of CONFIG_BLK_DEV_IDEPCI due to recursive deps.
Thanks,
/ magnus
[-- Attachment #2: linux-2.6.10-rc3-ide_pmac.patch --]
[-- Type: application/octet-stream, Size: 2792 bytes --]
diff -urN linux-2.6.10-rc3/drivers/ide/Kconfig linux-2.6.10-rc3-ide_pmac/drivers/ide/Kconfig
--- linux-2.6.10-rc3/drivers/ide/Kconfig 2004-12-13 23:38:32.000000000 +0100
+++ linux-2.6.10-rc3-ide_pmac/drivers/ide/Kconfig 2004-12-14 01:22:19.000000000 +0100
@@ -325,7 +325,6 @@
config BLK_DEV_IDEPCI
bool "PCI IDE chipset support" if PCI
- default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC
help
Say Y here for PCI systems which use IDE drive(s).
This option helps the IDE driver to automatically detect and
@@ -758,7 +757,7 @@
config BLK_DEV_IDEDMA_PMAC
bool "PowerMac IDE DMA support"
- depends on BLK_DEV_IDE_PMAC
+ depends on BLK_DEV_IDE_PMAC && BLK_DEV_IDEDMA_PCI
help
This option allows the driver for the built-in IDE controller on
Power Macintoshes and PowerBooks to use DMA (direct memory access)
diff -urN linux-2.6.10-rc3/drivers/ide/ppc/pmac.c linux-2.6.10-rc3-ide_pmac/drivers/ide/ppc/pmac.c
--- linux-2.6.10-rc3/drivers/ide/ppc/pmac.c 2004-12-13 23:38:33.000000000 +0100
+++ linux-2.6.10-rc3-ide_pmac/drivers/ide/ppc/pmac.c 2004-12-14 01:13:50.000000000 +0100
@@ -276,6 +276,8 @@
{ 0, 90, 30 } /* 4 */
};
+#endif /* CONFIG_BLK_DEV_IDEDMA_PMAC */
+
/* UniNorth 2 ATA/100 timings */
struct kauai_timing {
int cycle_time;
@@ -297,6 +299,8 @@
{ 120 , 0x04000148 }
};
+#ifdef CONFIG_BLK_DEV_IDEDMA_PMAC
+
static struct kauai_timing kauai_mdma_timings[] __pmacdata =
{
{ 1260 , 0x00fff000 },
@@ -322,6 +326,11 @@
{ 0 , 0 },
};
+static void pmac_ide_setup_dma(pmac_ide_hwif_t *pmif, ide_hwif_t *hwif);
+static int pmac_ide_build_dmatable(ide_drive_t *drive, struct request *rq);
+
+#endif /* CONFIG_BLK_DEV_IDEDMA_PMAC */
+
static inline u32
kauai_lookup_timing(struct kauai_timing* table, int cycle_time)
{
@@ -350,14 +359,11 @@
*/
#define IDE_WAKEUP_DELAY (1*HZ)
-static void pmac_ide_setup_dma(pmac_ide_hwif_t *pmif, ide_hwif_t *hwif);
-static int pmac_ide_build_dmatable(ide_drive_t *drive, struct request *rq);
static int pmac_ide_tune_chipset(ide_drive_t *drive, u8 speed);
static void pmac_ide_tuneproc(ide_drive_t *drive, u8 pio);
static void pmac_ide_selectproc(ide_drive_t *drive);
static void pmac_ide_kauai_selectproc(ide_drive_t *drive);
-#endif /* CONFIG_BLK_DEV_IDEDMA_PMAC */
/*
* Below is the code for blinking the laptop LED along with hard
@@ -1343,12 +1349,16 @@
/* The inteface is released to the common IDE layer */
dev_set_drvdata(&mdev->ofdev.dev, NULL);
iounmap(base);
+#ifdef CONFIG_BLK_DEV_IDEDMA_PMAC
if (pmif->dma_regs)
iounmap(pmif->dma_regs);
+#endif
memset(pmif, 0, sizeof(*pmif));
macio_release_resource(mdev, 0);
+#ifdef CONFIG_BLK_DEV_IDEDMA_PMAC
if (pmif->dma_regs)
macio_release_resource(mdev, 1);
+#endif
}
return rc;
^ permalink raw reply
* RE: Lite5200 and PCI1520
From: Andrew Dennison @ 2004-12-14 1:25 UTC (permalink / raw)
To: wd; +Cc: linuxppc-embedded
In-Reply-To: <20041214003301.2CC13C1430@atlas.denx.de>
On Tuesday, 14 December 2004 11:33 AM, wd@denx.de wrote:
> Dear Andrew,
>=20
> in message <002a01c4e16e$34451010$4000a8c0@CAT> you wrote:
>>=20
>> I posted a question on cardbus with the 5200 a few weeks ago but got
>> no reply. I think the reason is that cardbus / pcmcia support may
>> not have been considered when the 5200 PCI memory map was laid out,
>> but I would love to be contradicted!
>=20
> I think I can confirm that this was not considered, but I'm not sure
> that this is an issue here.
Hi Wolfgang,
It's a problem for PCMCIA, but probably not for cardbus. The PCMCIA =
16bit
I/O space can't be mapped above 0x1000 in the PCI address space. The CPU
physical address doesn't matter.
The PCMCIA memory space can be mapped to any 16MiB boundary so this =
isn't
a problem
>=20
>> I also have a few outstanding issues that I haven't resolved yet,
>> hence I haven't posted a full patch, but I can now load and
>> configure a wireless ethernet card. Loading cardbus drivers
>> currently fails when accessing PCI configuration space on the
>> cardbus bus, and I haven't sorted this out yet.=20
>=20
> I'd like to see your patch (even if preliminary).
I'll work on bundling it up in the next day or two. There are lots of
changes, including partial support for IRQ0 being a valid interrupt...
sigh. The setup of the BAT for MBAR also doesn't seem correct to me, but
I'm now using io_block_mapping() in my platform support.
Another problem I noticed is pcibios trashing the 5200 bridge setup. =
I've
hacked around this for now. Not a problem for PCMCIA but would have =
broken
bus mastering for cardbus / PCI.
While looking at PCI I noticed that the icecube platform (which I =
copied:)
compiles in pci_auto and indirect_pci but they aren't used. Is this work
in progress or a "cut-n-paste" error?
> Unfortunately I don't have any hardware yet with a working cardbus
> interface. But this might change soon...
Good to hear:)
^ permalink raw reply
* System hanged, which one is the killer? [was Re: What's the problem could be?]
From: Sam Song @ 2004-12-14 1:51 UTC (permalink / raw)
To: Embedded PPC Linux list
In-Reply-To: <20041207113615.9141.qmail@web15805.mail.cnb.yahoo.com>
Sam Song <samlinuxppc@yahoo.com.cn> wrote：
> Hi, all
>
> An system application crash running on 2.4.18 was
> happened on my custom 8xx board every now and then,
> especially recently. Yeah, the probelm is becoming
> more and more obvious. Personally, I deem it as an
> default of application software because there are
> some complicated application softwares like GUI and
a
> browser. But I also suspect that my custom keyboard
> did it because there were about 70-80 PCMCIA
> interrupts created once I hit just one key. I used
> PCMCIA interrupt to accept the rubber keyboard
> input.
Well, after some test on keyboard drivers, I found
that neither USB HOST keyboard nor my PCMCIA keyboard
could lead to system hang. It seems that the killer
isn't the PCMCIA keyboard driver.
> Any other possibility?
Seems have. The interesting thing was that I could
quit from the hanged application with a special key
and restarted the application and continued operate.
I, however, noticed some errors hints printed on the
LCD panel as "No enough video memory" during the
break.
So my attention was drawn to the 823 LCD driver. Two
different 10.4" SHARP TFT LCD panel with 640*480 and
800*600 were tested on the same target. I found that
640*480 system was more robust than 800*600 one. There
were also some hang happened with some disorder input
on 640*480 but the system could recover to normal
after some time like 3-5 mintues. The recoverable
result never appeared on 800*600.
Here I'd like to make sure one thing that whether I
could extend the video memory to meet the application
need. There are a lot of RAM on my target, at least
64MB. Any suggestion?
Thanks in advance,
=====
Best regards,
Sam
_________________________________________________________
Do You Yahoo!?
150万曲MP3疯狂搜，带您闯入音乐殿堂
http://music.yisou.com/
美女明星应有尽有，搜遍美图、艳图和酷图
http://image.yisou.com
1G就是1000兆，雅虎电邮自助扩容！
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/
^ permalink raw reply
* Re: System hanged, which one is the killer? [was Re: What's the problem could be?]
From: Sam Song @ 2004-12-14 2:04 UTC (permalink / raw)
To: Sam Song, Embedded PPC Linux list
Sam Song <samlinuxppc@yahoo.com.cn> wrote：
> I found that neither USB HOST keyboard nor my PCMCIA
> keyboard could lead to system hang.
Sorry, syntax error.
The above line sould be: I found that BOTH USB HOST
keyboard AND my PCMCIA keyboard could lead to system
hang.
Thanks,
=====
Best regards,
Sam
_________________________________________________________
Do You Yahoo!?
150万曲MP3疯狂搜，带您闯入音乐殿堂
http://music.yisou.com/
美女明星应有尽有，搜遍美图、艳图和酷图
http://image.yisou.com
1G就是1000兆，雅虎电邮自助扩容！
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/
^ permalink raw reply
* Re: System hanged, which one is the killer? [was Re: What's the problem could be?]
From: Sam Song @ 2004-12-14 2:04 UTC (permalink / raw)
To: Sam Song, Embedded PPC Linux list
Sam Song <samlinuxppc@yahoo.com.cn> wrote：
> I found that neither USB HOST keyboard nor my PCMCIA
> keyboard could lead to system hang.
Sorry, syntax error.
The above line sould be: I found that BOTH USB HOST
keyboard AND my PCMCIA keyboard could lead to system
hang.
Thanks,
=====
Best regards,
Sam
_________________________________________________________
Do You Yahoo!?
150万曲MP3疯狂搜，带您闯入音乐殿堂
http://music.yisou.com/
美女明星应有尽有，搜遍美图、艳图和酷图
http://image.yisou.com
1G就是1000兆，雅虎电邮自助扩容！
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/
^ permalink raw reply
* state of 8xx
From: Kalle Pokki @ 2004-12-14 7:04 UTC (permalink / raw)
To: linuxppc-embedded
Hi,
I have tried to compile Linux 2.6 for my custom 8xx board, but the
support for 8xx seems to be broken at the moment. Searching the lists
indicates there was at least some problem with memory management a
couple of months ago. Is anyone looking into this, or do you have any
idea when 8xx could be working again?
^ 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