* [Xenomai-help] Kernel OOps large appl.
@ 2006-10-31 13:25 Daniel Schnell
2006-10-31 13:43 ` Philippe Gerum
` (2 more replies)
0 siblings, 3 replies; 11+ messages in thread
From: Daniel Schnell @ 2006-10-31 13:25 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 3520 bytes --]
Hi,
we are porting our application to the POSIX skin of Xenomai. We are
using a 2.4.25 Denx based Kernel with 4 days old Xenomai 2.3-devel svn
trunk on a MPC5200B based custom board. The application spawns 36
Threads, uses 265 mutexes and 22 condition variables. We increased all
numbers that can be set inside Xenomai kernel config to 10x, just to be
sure we are not blowing out Kernel limits (Prinzip: Stange im Nebel).
The following output of ksymoops will be done for the occuring oops:
Oops: kernel access of bad area, sig: 11
NIP: C0012A00 XER: 20000000 LR: C00129DC SP: C9589E30 REGS: c9589d80
TRAP: 0300 Not tainted
Using defaults from ksymoops -t elf32-powerpc -a powerpc:common
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c9588000[294] 'ApplicationExe' Last syscall: 285344299
last math c8020000 last altivec 00000000
GPR00: C00129DC C9589E30 C9588000 FFFFFFFF C0008878 C01F82C0 C9587FFF
C01FCF48
GPR08: 003C62E0 C01FCF40 6C800000 CDE86268 00000000 1001A288 00000000
00000000
GPR16: 00000000 00000000 C0200000 C0240000 C0210000 C0200000 C0200000
C0210000
GPR24: 00000001 C0230000 C0260000 C0222420 CFE50000 00000000 00000000
C9589E30
Call backtrace:
C00129DC C011FB94 C0120F18 C0025FBC C000D638 C0005A3C 0FFD9F80
0FC4B888 0FC4B750 0FC0CF40 0FFD890C 0FF68FC0 0EE6C9A0
Warning (Oops_read): Code line not seen, dumping what data is available
>>NIP; c0012a00 <schedule+2a4/574> <=====
>>GPR0; c00129dc <schedule+280/574>
>>GPR4; c0008878 <_switch_to+5c/90>
>>GPR5; c01f82c0 <init_signals+3d4/504>
>>GPR7; c01fcf48 <ipipe_root+1008/2dc0>
>>GPR9; c01fcf40 <ipipe_root+1000/2dc0>
>>GPR18; c0200000 <pid_base_dentry_operations+4/18>
>>GPR19; c0240000 <read_buffers+b20/8000>
>>GPR20; c0210000 <__ksymtab_get_buffer_flushtime+0/8>
>>GPR21; c0200000 <pid_base_dentry_operations+4/18>
>>GPR22; c0200000 <pid_base_dentry_operations+4/18>
>>GPR23; c0210000 <__ksymtab_get_buffer_flushtime+0/8>
>>GPR25; c0230000 <exec_domains_lock+394/400>
>>GPR26; c0260000 <xnpipe_states+1630/9600>
>>GPR27; c0222420 <rtcan_init+4/4c>
Trace; c00129dc <schedule+280/574>
Trace; c011fb94 <xnshadow_ppd_lookup_inner+12c/1d4>
Trace; c0120f18 <xnshadow_sys_bind+298/300>
Trace; c0025fbc <__ipipe_dispatch_event+b4/198>
Trace; c000d638 <__ipipe_syscall_root+44/e0>
Trace; c0005a3c <DoSyscall+1c/90>
Trace; 0ffd9f80 Before first symbol
Trace; 0fc4b888 Before first symbol
Trace; 0fc4b750 Before first symbol
Trace; 0fc0cf40 Before first symbol
Trace; 0ffd890c Before first symbol
Trace; 0ff68fc0 Before first symbol
Trace; 0ee6c9a0 Before first symbol
The call right before entering the system space traced down with a
running gdb is __wrap_clock_nanosleep().
It always happens here. But when just testing this function alone in a
cycle, no kernel oops happens. The oops seems to be a correlation of
different events.
On the other side we have a constant problem with clock_nanosleep() in
that it always returns after 1/4 of the supposed time.
I.e. calling
struct timespec t
t.tv_sec = 5; t.tv_nsec = 0;
clock_nanosleep(CLOCK_REALTIME, 0, &t, NULL);
returns after 1 second and not 4.
Whereas clock_gettime(CLOCK_REALTIME, &t) works correctly (i.e. the
difference of two timestamps taken before and after clock_nanosleep()
with the above settings results in a diff time of 1 sec). So somehow the
external hardware timer setup is incorrect or maybe frequencies ?
Any ideas ?
Regards,
Daniel.
[-- Attachment #2: Type: text/html, Size: 7217 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Xenomai-help] Kernel OOps large appl.
2006-10-31 13:25 [Xenomai-help] Kernel OOps large appl Daniel Schnell
@ 2006-10-31 13:43 ` Philippe Gerum
2006-10-31 15:07 ` Daniel Schnell
2006-10-31 13:54 ` Philippe Gerum
2006-10-31 14:04 ` Daniel Schnell
2 siblings, 1 reply; 11+ messages in thread
From: Philippe Gerum @ 2006-10-31 13:43 UTC (permalink / raw)
To: Daniel Schnell; +Cc: xenomai
On Tue, 2006-10-31 at 13:25 +0000, Daniel Schnell wrote:
> Hi,
>
> we are porting our application to the POSIX skin of Xenomai. We are
> using a 2.4.25 Denx based Kernel with 4 days old Xenomai 2.3-devel svn
> trunk on a MPC5200B based custom board. The application spawns 36
> Threads, uses 265 mutexes and 22 condition variables. We increased all
> numbers that can be set inside Xenomai kernel config to 10x, just to
> be sure we are not blowing out Kernel limits (Prinzip: Stange im
> Nebel).
>
>
> The following output of ksymoops will be done for the occuring oops:
>
[...]
> Trace; c00129dc <schedule+280/574>
> Trace; c011fb94 <xnshadow_ppd_lookup_inner+12c/1d4>
This backtrace looks weird.
> Trace; c0120f18 <xnshadow_sys_bind+298/300>
> Trace; c0025fbc <__ipipe_dispatch_event+b4/198>
> Trace; c000d638 <__ipipe_syscall_root+44/e0>
> Trace; c0005a3c <DoSyscall+1c/90>
> Trace; 0ffd9f80 Before first symbol
> Trace; 0fc4b888 Before first symbol
> Trace; 0fc4b750 Before first symbol
> Trace; 0fc0cf40 Before first symbol
> Trace; 0ffd890c Before first symbol
> Trace; 0ff68fc0 Before first symbol
> Trace; 0ee6c9a0 Before first symbol
>
>
>
> The call right before entering the system space traced down with a
> running gdb is __wrap_clock_nanosleep().
This means that you are linking your application with the POSIX skin
too. So your setup is UVM/psos library + POSIX skin support?
Please send your Makefile, this should help understanding what's bound
to your application.
> It always happens here. But when just testing this function alone in a
> cycle, no kernel oops happens. The oops seems to be a correlation of
> different events.
The stack trace does not even match the wrapped nanosleep syscall, so
there is some strange interactions ongoing between the interfaces used.
>
>
> On the other side we have a constant problem with clock_nanosleep() in
> that it always returns after 1/4 of the supposed time.
>
> I.e. calling
>
> struct timespec t
> t.tv_sec = 5; t.tv_nsec = 0;
> clock_nanosleep(CLOCK_REALTIME, 0, &t, NULL);
>
> returns after 1 second and not 4.
>
> Whereas clock_gettime(CLOCK_REALTIME, &t) works correctly (i.e. the
> difference of two timestamps taken before and after clock_nanosleep()
> with the above settings results in a diff time of 1 sec). So somehow
> the external hardware timer setup is incorrect or maybe frequencies ?
The setup for a lite5200 hw on a Denx 2.4.25 kernel should work out of
the box. This is much more likely a software issue, maybe related to the
strangenesses above.
>
> Any ideas ?
>
>
> Regards,
>
> Daniel.
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: [Xenomai-help] Kernel OOps large appl.
2006-10-31 13:43 ` Philippe Gerum
@ 2006-10-31 15:07 ` Daniel Schnell
2006-10-31 15:25 ` Philippe Gerum
0 siblings, 1 reply; 11+ messages in thread
From: Daniel Schnell @ 2006-10-31 15:07 UTC (permalink / raw)
To: xenomai
Philippe Gerum wrote:
> This means that you are linking your application with the POSIX skin
> too. So your setup is UVM/psos library + POSIX skin support?
> Please send your Makefile, this should help understanding what's
> bound to your application.
>
Simply forget anything related to pSOS. There is no pSOS call anymore
inside the app. And we are not using pSOS skins and even have not
compiled the pSOS skin into the Kernel. Only the POSIX skin is used and
the native skin is compiled into the kernel so we can start the
testsuite.
We are using no modules. Everything is compiled into the kernel. See my
last mail with the attached configuration.
Our build environment is built around SCONS, so a Makefile alone
wouldn't be of any help. I rather would have to post the whole build
system ;) I am using the options in /usr/xenomai/bin/xeno-config
--posix-cflags and --posix-ldflags
> The stack trace does not even match the wrapped nanosleep syscall, so
> there is some strange interactions ongoing between the interfaces
> used.
>
What exactly you mean ?
> The setup for a lite5200 hw on a Denx 2.4.25 kernel should work out
> of the box. This is much more likely a software issue, maybe related
> to the strangenesses above.
We have our own 5200B board and the lite5200 setup doesn't work with our
hardware. In fact we had to tweak u-boot quite a bit to make it run on
the board.
Regards,
Daniel.
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: [Xenomai-help] Kernel OOps large appl.
2006-10-31 15:07 ` Daniel Schnell
@ 2006-10-31 15:25 ` Philippe Gerum
2006-10-31 16:37 ` Daniel Schnell
0 siblings, 1 reply; 11+ messages in thread
From: Philippe Gerum @ 2006-10-31 15:25 UTC (permalink / raw)
To: Daniel Schnell; +Cc: xenomai
On Tue, 2006-10-31 at 15:07 +0000, Daniel Schnell wrote:
> Philippe Gerum wrote:
>
> > This means that you are linking your application with the POSIX skin
> > too. So your setup is UVM/psos library + POSIX skin support?
> > Please send your Makefile, this should help understanding what's
> > bound to your application.
> >
> Simply forget anything related to pSOS. There is no pSOS call anymore
> inside the app.
Ok, I got this from your previous mail.
> And we are not using pSOS skins and even have not
> compiled the pSOS skin into the Kernel. Only the POSIX skin is used and
> the native skin is compiled into the kernel so we can start the
> testsuite.
> We are using no modules. Everything is compiled into the kernel. See my
> last mail with the attached configuration.
>
> Our build environment is built around SCONS, so a Makefile alone
> wouldn't be of any help. I rather would have to post the whole build
> system ;) I am using the options in /usr/xenomai/bin/xeno-config
> --posix-cflags and --posix-ldflags
Ok.
>
> > The stack trace does not even match the wrapped nanosleep syscall, so
> > there is some strange interactions ongoing between the interfaces
> > used.
> >
>
> What exactly you mean ?
>
This means that when issuing a nanosleep call emulated over the POSIX
skin, the kernel should not exhibit the backtrace given. So there is
something strange happening. The context represented by the backtrace
looks like the app binding to the POSIX skin, which must have happened
way earlier automatically through the POSIX skin library constructor,
before your app could even emit any Xenomai syscall. I initially thought
of some mismatches between the POSIX skin and the UVM support related to
some pSOS emulation use, but as there is no UVM/pSOS in the picture, I
now understand that your environment is purely POSIX-based, so the
latter cannot happen.
IOW, something seems out of sync in your configuration. Does the
testsuite work on your board, and specifically the "cyclic" test?
> > The setup for a lite5200 hw on a Denx 2.4.25 kernel should work out
> > of the box. This is much more likely a software issue, maybe related
> > to the strangenesses above.
>
> We have our own 5200B board and the lite5200 setup doesn't work with our
> hardware. In fact we had to tweak u-boot quite a bit to make it run on
> the board.
>
>
> Regards,
>
> Daniel.
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: [Xenomai-help] Kernel OOps large appl.
2006-10-31 15:25 ` Philippe Gerum
@ 2006-10-31 16:37 ` Daniel Schnell
2006-10-31 17:02 ` Jan Kiszka
0 siblings, 1 reply; 11+ messages in thread
From: Daniel Schnell @ 2006-10-31 16:37 UTC (permalink / raw)
To: xenomai
Philippe Gerum wrote:
> IOW, something seems out of sync in your configuration. Does the
> testsuite work on your board, and specifically the "cyclic" test?
The cyclic test does the following output:
./cyclictest -c 1 -d 500 -i 500 -l 10000 -n
0.06 0.03 0.01 1/21 354
T: 0 ( 354) P: 0 I: 500 C: 10000 Min: 7 Act: 7 Avg:
10 Max: 201
(needs a relatively short time)
./cyclictest -c 0 -d 500 -i 500 -l 10000 -n
0.00 0.01 0.00 1/21 357
T: 0 ( 357) P: 0 I: 500 C: 10000 Min: 6 Act: 6 Avg:
12 Max: 403
(needs a relatively short time)
./cyclictest -c 1 -d 500 -i 500 -l 10000 -n -r
0.00 0.00 0.00 1/21 367
T: 0 ( 367) P: 0 I: 500 C: 10000 Min: 10 Act: 11 Avg:
19 Max: 491
(needs a relatively short time)
./cyclictest -c 1 -d 500 -i 500 -l 10000 -s
T: 0 ( 360) P: 0 I: 500 C: 10000 Min: -6174 Act:94983888
Avg:47488852 Max:94983888
(needs much longer)
./cyclictest -c 1 -d 500 -i 500 -l 10000
0.16 0.03 0.01 1/22 379
T: 0 ( 379) P: 0 I: 500 C: 10000 Min:-5964339 Act:-5964339
Avg:-3481100 Max: -997872
(returns immediately without doing anything)
./cyclictest
(locks up system immediately)
Probably not good....
Regards,
Daniel.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Kernel OOps large appl.
2006-10-31 16:37 ` Daniel Schnell
@ 2006-10-31 17:02 ` Jan Kiszka
2006-10-31 17:32 ` Daniel Schnell
0 siblings, 1 reply; 11+ messages in thread
From: Jan Kiszka @ 2006-10-31 17:02 UTC (permalink / raw)
To: Daniel Schnell; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
Daniel Schnell wrote:
> Philippe Gerum wrote:
>
>
>> IOW, something seems out of sync in your configuration. Does the
>> testsuite work on your board, and specifically the "cyclic" test?
>
>
> The cyclic test does the following output:
>
> ./cyclictest -c 1 -d 500 -i 500 -l 10000 -n
> 0.06 0.03 0.01 1/21 354
>
> T: 0 ( 354) P: 0 I: 500 C: 10000 Min: 7 Act: 7 Avg:
> 10 Max: 201
> (needs a relatively short time)
>
> ./cyclictest -c 0 -d 500 -i 500 -l 10000 -n
> 0.00 0.01 0.00 1/21 357
>
> T: 0 ( 357) P: 0 I: 500 C: 10000 Min: 6 Act: 6 Avg:
> 12 Max: 403
> (needs a relatively short time)
>
> ./cyclictest -c 1 -d 500 -i 500 -l 10000 -n -r
> 0.00 0.00 0.00 1/21 367
>
> T: 0 ( 367) P: 0 I: 500 C: 10000 Min: 10 Act: 11 Avg:
> 19 Max: 491
> (needs a relatively short time)
>
> ./cyclictest -c 1 -d 500 -i 500 -l 10000 -s
> T: 0 ( 360) P: 0 I: 500 C: 10000 Min: -6174 Act:94983888
> Avg:47488852 Max:94983888
> (needs much longer)
>
> ./cyclictest -c 1 -d 500 -i 500 -l 10000
> 0.16 0.03 0.01 1/22 379
>
> T: 0 ( 379) P: 0 I: 500 C: 10000 Min:-5964339 Act:-5964339
> Avg:-3481100 Max: -997872
>
> (returns immediately without doing anything)
>
> ./cyclictest
>
> (locks up system immediately)
>
>
>
> Probably not good....
False positive of the test: only the -n mode is supported over Xenomai,
which is unfortunately not default. The default mode seems to cause a
busy loop in cyclictest, effectively locking up the box (the Xenomai
watchdog would have detected this).
Anyway, the test needs fixing to avoid misunderstandings.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: [Xenomai-help] Kernel OOps large appl.
2006-10-31 17:02 ` Jan Kiszka
@ 2006-10-31 17:32 ` Daniel Schnell
2006-10-31 17:48 ` Jan Kiszka
0 siblings, 1 reply; 11+ messages in thread
From: Daniel Schnell @ 2006-10-31 17:32 UTC (permalink / raw)
To: xenomai
jan.kiszka@domain.hid wrote:
>>
>> ./cyclictest -c 1 -d 500 -i 500 -l 10000 -n
>> 0.06 0.03 0.01 1/21 354
>>
>> T: 0 ( 354) P: 0 I: 500 C: 10000 Min: 7 Act: 7
>> Avg: 10 Max: 201 (needs a relatively short time)
> False positive of the test: only the -n mode is supported over
> Xenomai, which is unfortunately not default. The default mode seems
> to cause a busy loop in cyclictest, effectively locking up the box
> (the Xenomai watchdog would have detected this).
>
> Anyway, the test needs fixing to avoid misunderstandings.
Au ja !
So should I enable the watchdog ? What is the principle behind it ? Can
I somehow configure its behaviour ?
If I look on my reliable mechanical stopwatch and would activate the
cylictest with the above parameters: how long actually should the test
take ?
Next: the min, avg and max results mean latency in us ? Are these values
sane ? Any other test results I should give ? Other parameters ?
Regards,
Daniel.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Kernel OOps large appl.
2006-10-31 17:32 ` Daniel Schnell
@ 2006-10-31 17:48 ` Jan Kiszka
0 siblings, 0 replies; 11+ messages in thread
From: Jan Kiszka @ 2006-10-31 17:48 UTC (permalink / raw)
To: xenomai, Wolfgang Grandegger
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
Daniel Schnell wrote:
> jan.kiszka@domain.hid wrote:
>>> ./cyclictest -c 1 -d 500 -i 500 -l 10000 -n
>>> 0.06 0.03 0.01 1/21 354
>>>
>>> T: 0 ( 354) P: 0 I: 500 C: 10000 Min: 7 Act: 7
>>> Avg: 10 Max: 201 (needs a relatively short time)
>
>> False positive of the test: only the -n mode is supported over
>> Xenomai, which is unfortunately not default. The default mode seems
>> to cause a busy loop in cyclictest, effectively locking up the box
>> (the Xenomai watchdog would have detected this).
>>
>> Anyway, the test needs fixing to avoid misunderstandings.
>
> Au ja !
>
> So should I enable the watchdog ? What is the principle behind it ? Can
> I somehow configure its behaviour ?
It can help here to tell "normal" RT-thread lock-ups apart from real
kernel deadlocks.
>
> If I look on my reliable mechanical stopwatch and would activate the
> cylictest with the above parameters: how long actually should the test
> take ?
>
5 seconds. Do you get different runtimes for -c0 vs. -c1?
>
> Next: the min, avg and max results mean latency in us ? Are these values
> sane ? Any other test results I should give ? Other parameters ?
Yes, microseconds. The maximum numbers (for the -n cases) appeared a
"bit" high to me, even for low-end embedded. Wolfgang? Anyone else? What
are normal numbers for that board category? Some table on the wiki would
be nice as reference, not only for poor x86'ers like me...
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Kernel OOps large appl.
2006-10-31 13:25 [Xenomai-help] Kernel OOps large appl Daniel Schnell
2006-10-31 13:43 ` Philippe Gerum
@ 2006-10-31 13:54 ` Philippe Gerum
2006-10-31 13:57 ` Daniel Schnell
2006-10-31 14:04 ` Daniel Schnell
2 siblings, 1 reply; 11+ messages in thread
From: Philippe Gerum @ 2006-10-31 13:54 UTC (permalink / raw)
To: Daniel Schnell; +Cc: xenomai
On Tue, 2006-10-31 at 13:25 +0000, Daniel Schnell wrote:
> Hi,
>
> we are porting our application to the POSIX skin of Xenomai. We are
> using a 2.4.25 Denx based Kernel with 4 days old Xenomai 2.3-devel svn
Mm, 2.3-devel, so there is no UVM in the picture since the latter
support has been removed from the trunk/ in favour of the direct syscall
interfaces. But then, how do you emulate pSOS? Using your own
POSIX-based emulator (i.e. _not_ Xenomai's pSOS skin)?
--
Philippe.
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: [Xenomai-help] Kernel OOps large appl.
2006-10-31 13:54 ` Philippe Gerum
@ 2006-10-31 13:57 ` Daniel Schnell
0 siblings, 0 replies; 11+ messages in thread
From: Daniel Schnell @ 2006-10-31 13:57 UTC (permalink / raw)
To: xenomai
Philippe Gerum wrote:
> Mm, 2.3-devel, so there is no UVM in the picture since the latter
> support has been removed from the trunk/ in favour of the direct
> syscall interfaces. But then, how do you emulate pSOS? Using your own
> POSIX-based emulator (i.e. _not_ Xenomai's pSOS skin)?
No, we are simply not using any pSOS call at all. We replaced everything
with POSIX calls. The remark about pSOS was just a hint from which
background the application is coming.
Regards,
Daniel.
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: [Xenomai-help] Kernel OOps large appl.
2006-10-31 13:25 [Xenomai-help] Kernel OOps large appl Daniel Schnell
2006-10-31 13:43 ` Philippe Gerum
2006-10-31 13:54 ` Philippe Gerum
@ 2006-10-31 14:04 ` Daniel Schnell
2 siblings, 0 replies; 11+ messages in thread
From: Daniel Schnell @ 2006-10-31 14:04 UTC (permalink / raw)
To: Daniel Schnell, xenomai
[-- Attachment #1: Type: text/plain, Size: 86 bytes --]
Hi,
Here comes the kernel configuration we are using ...
Regards,
Daniel.
[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 26015 bytes --]
#
# Automatically generated by make menuconfig: don't edit
#
# CONFIG_UID16 is not set
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_HAVE_DEC_LOCK=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_ADVANCED_OPTIONS=y
#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# Platform support
#
CONFIG_PPC=y
CONFIG_PPC32=y
CONFIG_6xx=y
# CONFIG_40x is not set
# CONFIG_44x is not set
# CONFIG_E500 is not set
# CONFIG_POWER3 is not set
# CONFIG_POWER4 is not set
# CONFIG_8xx is not set
# CONFIG_8260 is not set
# CONFIG_83xx is not set
CONFIG_PPC_STD_MMU=y
# CONFIG_ALL_PPC is not set
# CONFIG_APUS is not set
# CONFIG_INKA4X0 is not set
# CONFIG_WILLOW is not set
# CONFIG_TOP5200 is not set
# CONFIG_CPCI690 is not set
# CONFIG_PCORE is not set
# CONFIG_POWERPMC250 is not set
# CONFIG_PPMC260 is not set
# CONFIG_EV64260 is not set
# CONFIG_SPRUCE is not set
CONFIG_NS4=y
# CONFIG_HMI1001 is not set
# CONFIG_PP01 is not set
# CONFIG_CPC45 is not set
# CONFIG_CU824 is not set
# CONFIG_PM520 is not set
# CONFIG_MCC200 is not set
# CONFIG_PUMA_A is not set
# CONFIG_ALASKA is not set
# CONFIG_GLACIER is not set
# CONFIG_ICECUBE is not set
# CONFIG_LITE5200B is not set
# CONFIG_HXEB100 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_P3G4 is not set
# CONFIG_ADIR is not set
# CONFIG_K2 is not set
# CONFIG_PAL4 is not set
# CONFIG_SL8245 is not set
# CONFIG_SMMACO4 is not set
# CONFIG_GEMINI is not set
# CONFIG_TQM5200 is not set
# CONFIG_O2DNT is not set
# CONFIG_SORCERY is not set
CONFIG_PPC_5xxx=y
# CONFIG_SMP is not set
# CONFIG_ALTIVEC is not set
# CONFIG_TAU is not set
CONFIG_PPC_ISATIMER=y
# CONFIG_MPC5100 is not set
CONFIG_MPC5200=y
CONFIG_PPC_5xxx_PSC_CONSOLE_BAUD=115200
CONFIG_UBOOT=y
CONFIG_PPC_5xxx_PSC_CONSOLE_PORT=0
CONFIG_UBOOT=y
#
# General setup
#
# CONFIG_BIGPHYS_AREA is not set
# CONFIG_HIGHMEM is not set
# CONFIG_LOWMEM_SIZE_BOOL is not set
# CONFIG_KERNEL_START_BOOL is not set
# CONFIG_TASK_SIZE_BOOL is not set
CONFIG_HIGHMEM_START=0xfe000000
CONFIG_LOWMEM_SIZE=0x30000000
CONFIG_KERNEL_START=0xc0000000
CONFIG_TASK_SIZE=0x80000000
# CONFIG_ISA is not set
# CONFIG_EISA is not set
# CONFIG_SBUS is not set
# CONFIG_MCA is not set
CONFIG_PCI=y
CONFIG_IPIPE=y
CONFIG_NET=y
CONFIG_SYSCTL=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_OOM_KILLER is not set
# CONFIG_PCI_NAMES is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
# CONFIG_GEN_RTC is not set
# CONFIG_PPC_RTC is not set
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE="ip=off"
#
# Embedded options
#
# CONFIG_EMBEDDED is not set
#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_CONCAT is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
# CONFIG_MTD_CMDLINE_PARTS is not set
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_CFI_ADV_OPTIONS=y
CONFIG_MTD_CFI_NOSWAP=y
# CONFIG_MTD_CFI_BE_BYTE_SWAP is not set
# CONFIG_MTD_CFI_LE_BYTE_SWAP is not set
# CONFIG_MTD_CFI_GEOMETRY is not set
# CONFIG_MTD_OTP 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_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_INTELEXT is not set
CONFIG_MTD_CFI_AMDSTD=y
# CONFIG_MTD_CFI_STAA is not set
CONFIG_MTD_CFI_UTIL=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_OBSOLETE_CHIPS is not set
# CONFIG_MTD_AMDSTD is not set
# CONFIG_MTD_SHARP is not set
# CONFIG_MTD_JEDEC is not set
#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_PUMA_A is not set
# CONFIG_MTD_CHESTNUT is not set
# CONFIG_MTD_K2 is not set
# CONFIG_MTD_HXEB100 is not set
# CONFIG_MTD_PPMC260 is not set
# CONFIG_MTD_CU824 is not set
# CONFIG_MTD_CPC45 is not set
# CONFIG_MTD_HMI1001 is not set
# CONFIG_MTD_ICECUBE is not set
CONFIG_MTD_NS4=y
# CONFIG_MTD_ICECUBE is not set
# CONFIG_MTD_INKA4X0 is not set
# CONFIG_MTD_O2DNT is not set
# CONFIG_MTD_P3G4 is not set
# CONFIG_MTD_PP01 is not set
# CONFIG_MTD_MCC200 is not set
# CONFIG_MTD_PM520 is not set
# CONFIG_MTD_SL8245 is not set
# CONFIG_MTD_SMMACO4 is not set
# CONFIG_MTD_SORCERY is not set
# CONFIG_MTD_TQM5200 is not set
# CONFIG_MTD_PCI is not set
# CONFIG_MTD_PCMCIA is not set
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
# CONFIG_MTD_DOCPROBE is not set
# CONFIG_MTD_DOCECC is not set
#
# NAND Flash Device Drivers
#
# CONFIG_MTD_NAND is not set
# CONFIG_MTD_NAND_DISKONCHIP is not set
# CONFIG_MTD_NAND_NANDSIM is not set
#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set
#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_CISS_SCSI_TAPE is not set
# CONFIG_CISS_MONITOR_THREAD is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_BLK_STATS is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
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 is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
#
# Appletalk devices
#
# CONFIG_DEV_APPLETALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y
#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECS is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
# CONFIG_BLK_DEV_IDEPCI is not set
CONFIG_BLK_DEV_IDE_MPC5xxx=y
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_ATARAID is not set
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set
# CONFIG_BLK_DEV_ATARAID_SII is not set
#
# SCSI support
#
CONFIG_SCSI=y
# CONFIG_BLK_DEV_SD is not set
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_SCSI_DEBUG_QUEUES is not set
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_MEGARAID2 is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_NCR53C8XX is not set
# CONFIG_SCSI_SYM53C8XX is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_BOOT is not set
# CONFIG_FUSION_ISENSE is not set
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LAN is not set
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set
#
# Network device support
#
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MACE is not set
# CONFIG_BMAC is not set
# CONFIG_GMAC is not set
# CONFIG_SUNLANCE is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_PCI is not set
# CONFIG_NET_POCKET is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_MYRI_SBUS 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
# CONFIG_GIANFAR is not set
# CONFIG_GFAR_NAPI is not set
# CONFIG_GFAR_BDSTASH is not set
# CONFIG_GFAR_BUFSTASH is not set
# CONFIG_FDDI is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Console drivers
#
# CONFIG_VGA_CONSOLE is not set
#
# Frame-buffer support
#
# CONFIG_FB is not set
#
# Input core support
#
# CONFIG_INPUT is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_UINPUT is not set
#
# Macintosh device drivers
#
#
# Character devices
#
# CONFIG_VT is not set
# CONFIG_SERIAL is not set
# CONFIG_SERIAL_EXTENDED is not set
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_DIGI is not set
# CONFIG_ESPSERIAL is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_N_HDLC is not set
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set
# CONFIG_PS2MULT is not set
# CONFIG_KEYMAP_DE_LATIN1 is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
# I2C support
#
CONFIG_I2C=y
# CONFIG_I2C_ALGOBIT is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_ALGOPCF is not set
CONFIG_I2C_ALGO_MPC5xxx=y
# CONFIG_I2C_ADAP_ICECUBE is not set
CONFIG_I2C_ADAP_NS4=y
# CONFIG_I2C_ADAP_PM520 is not set
# CONFIG_I2C_ADAP_PP01 is not set
# CONFIG_I2C_ADAP_TOP5200 is not set
# CONFIG_I2C_ADAP_TQM5200 is not set
# CONFIG_I2C_ADAP_HMI1001 is not set
# CONFIG_I2C_ADAP_O2DNT is not set
# CONFIG_I2C_ADAP_MCC200 is not set
#
# I2C Chips support
#
# CONFIG_I2C_CHIPS is not set
CONFIG_I2C_CHARDEV=y
# CONFIG_I2C_PROC is not set
#
# SPI support
#
# CONFIG_SPI is not set
#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_MOUSE is not set
#
# Joysticks
#
# CONFIG_INPUT_GAMEPORT is not set
# CONFIG_QIC02_TAPE is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_IPMI_PANIC_EVENT is not set
# CONFIG_IPMI_DEVICE_INTERFACE is not set
# CONFIG_IPMI_KCS is not set
# CONFIG_IPMI_WATCHDOG is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_SCx200 is not set
# CONFIG_SCx200_GPIO is not set
# CONFIG_AMD_PM768 is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
CONFIG_PCF8563_RTC=y
# CONFIG_RTC_11_MINUTE_MODE is not set
# CONFIG_X1226_RTC is not set
# CONFIG_M41ST85_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_FLASH is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
#
# Direct Rendering Manager (XFree86 DRI support)
#
# CONFIG_DRM is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_QFMT_V2 is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW 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_BEFS_DEBUG is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_FAT_FS is not set
# CONFIG_MSDOS_FS is not set
# CONFIG_UMSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
# CONFIG_JFFS2_FS_WRITEBUFFER is not set
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
# CONFIG_JFFS2_LZO is not set
# CONFIG_JFFS2_LZARI is not set
# CONFIG_JFFS2_CMODE_NONE is not set
CONFIG_JFFS2_CMODE_PRIORITY=y
# CONFIG_JFFS2_CMODE_SIZE is not set
# CONFIG_JFFS2_PROC is not set
CONFIG_CRAMFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
# CONFIG_ISO9660_FS is not set
# CONFIG_JOLIET is not set
# CONFIG_ZISOFS is not set
# CONFIG_JFS_FS is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_XFS_FS is not set
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_RT is not set
# CONFIG_XFS_TRACE is not set
# CONFIG_XFS_DEBUG is not set
#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFSD is not set
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_SMB_FS=y
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_SMB_UNIX is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
# CONFIG_ZISOFS_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=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL 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
CONFIG_SMB_NLS=y
CONFIG_NLS=y
#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Sound
#
# CONFIG_SOUND is not set
#
# MPC5xxx I/O Options
#
CONFIG_BESTCOMM_API=y
CONFIG_PPC_5xxx_FEC=y
CONFIG_USE_MDIO=y
CONFIG_FEC_GENERIC_PHY=y
# CONFIG_FEC_LXT971 is not set
CONFIG_FEC_DP83847=y
# CONFIG_USB_USEBOTH is not set
CONFIG_PPC_5xxx_PSC=y
CONFIG_PPC_5xxx_PSC_CONSOLE=y
CONFIG_SERIAL_CONSOLE=y
# CONFIG_5200_I2S is not set
# CONFIG_5200_I2S_RING is not set
#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_UHCI is not set
# CONFIG_USB_UHCI_ALT is not set
# CONFIG_USB_OHCI_PCI is not set
CONFIG_USB_OHCI_5xxx=y
# CONFIG_USB_SINGLEENDED is not set
# CONFIG_USB_USEBOTH is not set
CONFIG_USB_OHCI_BIG_ENDIAN=y
CONFIG_USB_OHCI=y
# CONFIG_USB_ISP1362 is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_BLUETOOTH is not set
# CONFIG_USB_MIDI is not set
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_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e 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_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_HID is not set
# CONFIG_USB_HIDINPUT is not set
# CONFIG_USB_HIDDEV is not set
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_CATC is not set
# CONFIG_USB_CDCETHER is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_ISP1362_USB is not set
# CONFIG_ISP1362_NETLINK is not set
#
# Support for USB gadgets
#
# CONFIG_USB_GADGET is not set
#
# Bluetooth support
#
# CONFIG_BLUEZ is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
CONFIG_CRC32=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
# CONFIG_REED_SOLOMON is not set
# CONFIG_FW_LOADER is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_WAITQ is not set
# CONFIG_KGDB is not set
# CONFIG_XMON is not set
CONFIG_BDI_SWITCH=y
CONFIG_MORE_COMPILE_OPTIONS=y
CONFIG_COMPILE_OPTIONS="-g -ggdb"
# CONFIG_SERIAL_TEXT_DEBUG is not set
CONFIG_LOG_BUF_SHIFT=0
#
# Real-time sub-system
#
CONFIG_XENOMAI=y
CONFIG_XENO_OPT_NUCLEUS=y
#
# Nucleus options
#
CONFIG_XENO_OPT_PERVASIVE=y
# CONFIG_XENO_OPT_RPIDISABLE is not set
# CONFIG_XENO_OPT_SECURITY_ACCESS is not set
CONFIG_XENO_OPT_PIPE=y
CONFIG_XENO_OPT_PIPE_NRDEV=320
CONFIG_XENO_OPT_REGISTRY=y
CONFIG_XENO_OPT_REGISTRY_NRSLOTS=2560
CONFIG_XENO_OPT_SYS_HEAPSZ=1280
# CONFIG_XENO_OPT_ISHIELD is not set
# CONFIG_XENO_OPT_PIPELINE_HEAD is not set
CONFIG_XENO_OPT_STATS=y
CONFIG_XENO_OPT_DEBUG=y
# CONFIG_XENO_OPT_DEBUG_QUEUES is not set
CONFIG_XENO_OPT_DEBUG_BHEAP=y
# CONFIG_XENO_OPT_WATCHDOG is not set
# CONFIG_XENO_OPT_TIMING_PERIODIC is not set
CONFIG_XENO_OPT_TIMING_PERIOD=0
CONFIG_XENO_OPT_TIMING_TIMERLAT=0
CONFIG_XENO_OPT_TIMING_SCHEDLAT=0
#
# Scalability options
#
# CONFIG_XENO_OPT_SCALABLE_SCHED is not set
CONFIG_XENO_OPT_TIMER_LIST=y
# CONFIG_XENO_OPT_TIMER_HEAP is not set
# CONFIG_XENO_OPT_TIMER_WHEEL is not set
#
# Shared interrupts
#
# CONFIG_XENO_OPT_SHIRQ_LEVEL is not set
# CONFIG_XENO_OPT_SHIRQ_EDGE is not set
#
# LTT tracepoints filtering
#
# CONFIG_XENO_OPT_FILTER_EVIRQ is not set
# CONFIG_XENO_OPT_FILTER_EVTHR is not set
# CONFIG_XENO_OPT_FILTER_EVSYS is not set
# CONFIG_XENO_OPT_FILTER_EVALL is not set
#
# Interfaces
#
CONFIG_XENO_SKIN_NATIVE=y
#
# Native interface options
#
CONFIG_XENO_OPT_NATIVE_PIPE=y
CONFIG_XENO_OPT_NATIVE_PIPE_BUFSZ=40960
CONFIG_XENO_OPT_NATIVE_SEM=y
CONFIG_XENO_OPT_NATIVE_EVENT=y
CONFIG_XENO_OPT_NATIVE_MUTEX=y
CONFIG_XENO_OPT_NATIVE_COND=y
CONFIG_XENO_OPT_NATIVE_QUEUE=y
CONFIG_XENO_OPT_NATIVE_HEAP=y
CONFIG_XENO_OPT_NATIVE_ALARM=y
CONFIG_XENO_OPT_NATIVE_MPS=y
# CONFIG_XENO_OPT_NATIVE_INTR is not set
CONFIG_XENO_SKIN_POSIX=y
#
# POSIX interface options
#
CONFIG_XENO_OPT_POSIX_SHM=y
# CONFIG_XENO_OPT_POSIX_INTR is not set
CONFIG_XENO_SKIN_RTDM=y
#
# RTDM interface options
#
CONFIG_XENO_OPT_RTDM_FILDES=512
CONFIG_XENO_OPT_DEBUG_RTDM=y
# CONFIG_XENO_SKIN_PSOS is not set
# CONFIG_XENO_SKIN_VXWORKS is not set
# CONFIG_XENO_SKIN_VRTX is not set
# CONFIG_XENO_SKIN_UITRON is not set
# CONFIG_XENO_SKIN_RTAI is not set
#
# Drivers
#
#
# Serial drivers
#
# CONFIG_XENO_DRIVERS_16550A is not set
#
# Testing drivers
#
CONFIG_XENO_DRIVERS_TIMERBENCH=y
CONFIG_XENO_DRIVERS_IRQBENCH=y
CONFIG_XENO_DRIVERS_SWITCHTEST=y
#
# CAN drivers
#
CONFIG_XENO_DRIVERS_RTCAN=y
CONFIG_XENO_DRIVERS_RTCAN_DEBUG=y
CONFIG_XENO_DRIVERS_RTCAN_RXBUF_SIZE=1024
CONFIG_XENO_DRIVERS_RTCAN_MAX_DEVICES=2
CONFIG_XENO_DRIVERS_RTCAN_MAX_RECEIVERS=16
# CONFIG_XENO_DRIVERS_RTCAN_VIRT is not set
CONFIG_XENO_DRIVERS_RTCAN_MSCAN=y
CONFIG_XENO_DRIVERS_RTCAN_MSCAN_1=y
CONFIG_XENO_DRIVERS_RTCAN_MSCAN_2=y
CONFIG_XENO_DRIVERS_RTCAN_MSCAN_CLOCK=66000000
CONFIG_XENO_DRIVERS_RTCAN_MSCAN_ALT=y
# CONFIG_XENO_DRIVERS_RTCAN_MSCAN_PSC2 is not set
# CONFIG_XENO_DRIVERS_RTCAN_SJA1000 is not set
# CONFIG_XENO_DRIVERS_RTCAN_SJA1000_ISA is not set
# CONFIG_XENO_DRIVERS_RTCAN_SJA1000_MEM is not set
# CONFIG_XENO_DRIVERS_RTCAN_SJA1000_PEAK_PCI is not set
# CONFIG_XENO_DRIVERS_RTCAN_SJA1000_PEAK_DNG is not set
#
# Machine
#
CONFIG_XENO_HW_FPU=y
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2006-10-31 17:48 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-31 13:25 [Xenomai-help] Kernel OOps large appl Daniel Schnell
2006-10-31 13:43 ` Philippe Gerum
2006-10-31 15:07 ` Daniel Schnell
2006-10-31 15:25 ` Philippe Gerum
2006-10-31 16:37 ` Daniel Schnell
2006-10-31 17:02 ` Jan Kiszka
2006-10-31 17:32 ` Daniel Schnell
2006-10-31 17:48 ` Jan Kiszka
2006-10-31 13:54 ` Philippe Gerum
2006-10-31 13:57 ` Daniel Schnell
2006-10-31 14:04 ` Daniel Schnell
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.