[Xenomai-help] problem with serial example

[Xenomai-help] problem with serial example

[Everett Wang]

Hi All,

I am trying to make my serial work with xenomai. I have managed to
compile and almost run the cross-link example.
When I tried to run it, I got a shared library problem:

examples
./cross-link
./cross-link: error while loading shared libraries: libxenomai.so.0: cannot...

I then added this:

$LD_LIBRARY_PATH=/usr/xenomai/lib
$export LD_LIBRARY_PATH

Is this the right thing to do?

I tried it again. I got a little further:

root@domain.hid# ./cross-link
main : can't open rtser0 (write), No such device

I googled a little bit and still can't find a solution. Here is the system I am
using: Beagleboard C4, xenomai 2.5.3, linux 2.6.33.3, cross-compiler CSL
2010Q1. In my kernel configuration, I do have CONFIG_XENO_DRIVERS_16550A
enabled as a module.

In a 2007 post, I saw  Philippe Gerum suggested to  have "vanilla
serial support disabled".
which kernel config is that? CONFIG_SERIAL_CORE? or CONFIG_SERIAL_8250?
I looked at my /dev/ directory and not found rtser*. It does have
ttyS0, ttyS1 and ttyS3
for my normal serial ports. Nothing called rtser in /proc/xenomai/rtdm either
root@domain.hid# ls
fildes         open_fildes       rttest-switchtest0
named_devices  protocol_devices  rttest-timerbench0

Any suggestions?

Have a nice weekend,

Everett

Re: [Xenomai-help] problem with serial example

[Wolfgang Grandegger]

On 05/23/2010 05:48 AM, Everett Wang wrote:
> Hi All,
> 
> I am trying to make my serial work with xenomai. I have managed to
> compile and almost run the cross-link example.
> When I tried to run it, I got a shared library problem:
> 
> examples
> ./cross-link
> ./cross-link: error while loading shared libraries: libxenomai.so.0: cannot...
> 
> I then added this:
> 
> $LD_LIBRARY_PATH=/usr/xenomai/lib
> $export LD_LIBRARY_PATH
> 
> Is this the right thing to do?
> 
> I tried it again. I got a little further:
> 
> root@domain.hid# ./cross-link
> main : can't open rtser0 (write), No such device
> 
> I googled a little bit and still can't find a solution. Here is the system I am
> using: Beagleboard C4, xenomai 2.5.3, linux 2.6.33.3, cross-compiler CSL
> 2010Q1. In my kernel configuration, I do have CONFIG_XENO_DRIVERS_16550A
> enabled as a module.

Is the module loaded. If not, it's no surprise that there is no rtser0
device. Anyway, I'm not sure if Xenomai's 16550A RTserial driver is
fully compatible with OMAPs 8250 devices, especially the proper access
method might not be supported.

> In a 2007 post, I saw  Philippe Gerum suggested to  have "vanilla
> serial support disabled".
> which kernel config is that? CONFIG_SERIAL_CORE? or CONFIG_SERIAL_8250?

This will disable all serial devices including the console. Not sure if
you want that.

> I looked at my /dev/ directory and not found rtser*. It does have
> ttyS0, ttyS1 and ttyS3
> for my normal serial ports. Nothing called rtser in /proc/xenomai/rtdm either
> root@domain.hid# ls
> fildes         open_fildes       rttest-switchtest0
> named_devices  protocol_devices  rttest-timerbench0
> 
> Any suggestions?

Which UART device do you want to use as rtser0? On the PC you can
shutdown the device you want to use for rtserial with:

# setserial /dev/ttyS0 uart none

Not sure if this works on the Beagle board, though. If not, you may need
to disable the UARTs in your board config code. Finally you must load
the module with the proper arguments:

# insmod xeno_16550A.ko mem=0x49020000 irq=74 baud_base=?

That requires XENO_DRIVERS_16550A_MMIO or XENO_DRIVERS_16550A_ANY to be
set. If you are lucky, it might work.

Wolfgang.

Re: [Xenomai-help] problem with serial example

[Everett Wang]

On Sun, May 23, 2010 at 5:37 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
> On 05/23/2010 05:48 AM, Everett Wang wrote:
>> Hi All,
>>
>> I am trying to make my serial work with xenomai. I have managed to
>> compile and almost run the cross-link example.
>> When I tried to run it, I got a shared library problem:
>>
>> examples
>> ./cross-link
>> ./cross-link: error while loading shared libraries: libxenomai.so.0: cannot...
>>
>> I then added this:
>>
>> $LD_LIBRARY_PATH=/usr/xenomai/lib
>> $export LD_LIBRARY_PATH
>>
>> Is this the right thing to do?
>>
>> I tried it again. I got a little further:
>>
>> root@domain.hid# ./cross-link
>> main : can't open rtser0 (write), No such device
>>
>> I googled a little bit and still can't find a solution. Here is the system I am
>> using: Beagleboard C4, xenomai 2.5.3, linux 2.6.33.3, cross-compiler CSL
>> 2010Q1. In my kernel configuration, I do have CONFIG_XENO_DRIVERS_16550A
>> enabled as a module.
>
> Is the module loaded. If not, it's no surprise that there is no rtser0
> device. Anyway, I'm not sure if Xenomai's 16550A RTserial driver is
> fully compatible with OMAPs 8250 devices, especially the proper access
> method might not be supported.

I checked with lsmod. No modules are loaded.

>
>> In a 2007 post, I saw  Philippe Gerum suggested to  have "vanilla
>> serial support disabled".
>> which kernel config is that? CONFIG_SERIAL_CORE? or CONFIG_SERIAL_8250?
>
> This will disable all serial devices including the console. Not sure if
> you want that.

That is right. Currently with a vanilla kernel and xenomai patch, my DVI display
and USB keyboard, mouse do not function. So uart3 is the only way to interact
with the beagleboard.

>> I looked at my /dev/ directory and not found rtser*. It does have
>> ttyS0, ttyS1 and ttyS3
>> for my normal serial ports. Nothing called rtser in /proc/xenomai/rtdm either
>> root@domain.hid# ls
>> fildes         open_fildes       rttest-switchtest0
>> named_devices  protocol_devices  rttest-timerbench0
>>
>> Any suggestions?
>
> Which UART device do you want to use as rtser0? On the PC you can
> shutdown the device you want to use for rtserial with:
>
> # setserial /dev/ttyS0 uart none
>
> Not sure if this works on the Beagle board, though. If not, you may need
> to disable the UARTs in your board config code. Finally you must load
> the module with the proper arguments:
>
> # insmod xeno_16550A.ko mem=0x49020000 irq=74 baud_base=?
>
> That requires XENO_DRIVERS_16550A_MMIO or XENO_DRIVERS_16550A_ANY to be
> set. If you are lucky, it might work.
>
> Wolfgang.
>
I am trying to use uart1 and uart2 (uart3 is for the console) for cross-link.

These lines are from my dmesg output:

Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled

I can see that I have xeno_16550A.ko in
/lib/modules/2.6.33.3/kernel/drivers/xenomai/serial. But I forgot if I
have set XENO_DRIVERS_16550A_MMIO or XENO_DRIVERS_16550A_ANY during
xenomai configuration. How to check
these configuration? I can't find a .config file like linux kernel.
The config.log
doesn't contain these.

When I tried to load the driver by:

root@domain.hid:~#  insmod xeno_16550A.ko mem=0x4806a000 irq=72 baud_base=19200
sh: insmod: not found
root@domain.hid:~#

I guess the Angstrom distribution doesn't include insmod. Let me try to install
that before I try the serial example again.

Everett

Re: [Xenomai-help] problem with serial example

[Gilles Chanteperdrix]

Everett Wang wrote:
> That is right. Currently with a vanilla kernel and xenomai patch, my DVI display
> and USB keyboard, mouse do not function. So uart3 is the only way to interact
> with the beagleboard.

That is not normal. If you are using the same configuration, things
should work. Do you get any messages about this on the console?

-- 
					    Gilles.

Re: [Xenomai-help] problem with serial example

[Wolfgang Grandegger]

On 05/23/2010 04:59 PM, Everett Wang wrote:
> On Sun, May 23, 2010 at 5:37 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>> On 05/23/2010 05:48 AM, Everett Wang wrote:
>>> Hi All,
>>>
>>> I am trying to make my serial work with xenomai. I have managed to
>>> compile and almost run the cross-link example.
>>> When I tried to run it, I got a shared library problem:
>>>
>>> examples
>>> ./cross-link
>>> ./cross-link: error while loading shared libraries: libxenomai.so.0: cannot...
>>>
>>> I then added this:
>>>
>>> $LD_LIBRARY_PATH=/usr/xenomai/lib
>>> $export LD_LIBRARY_PATH
>>>
>>> Is this the right thing to do?
>>>
>>> I tried it again. I got a little further:
>>>
>>> root@domain.hid# ./cross-link
>>> main : can't open rtser0 (write), No such device
>>>
>>> I googled a little bit and still can't find a solution. Here is the system I am
>>> using: Beagleboard C4, xenomai 2.5.3, linux 2.6.33.3, cross-compiler CSL
>>> 2010Q1. In my kernel configuration, I do have CONFIG_XENO_DRIVERS_16550A
>>> enabled as a module.
>>
>> Is the module loaded. If not, it's no surprise that there is no rtser0
>> device. Anyway, I'm not sure if Xenomai's 16550A RTserial driver is
>> fully compatible with OMAPs 8250 devices, especially the proper access
>> method might not be supported.
> 
> I checked with lsmod. No modules are loaded.
> 
>>
>>> In a 2007 post, I saw  Philippe Gerum suggested to  have "vanilla
>>> serial support disabled".
>>> which kernel config is that? CONFIG_SERIAL_CORE? or CONFIG_SERIAL_8250?
>>
>> This will disable all serial devices including the console. Not sure if
>> you want that.
> 
> That is right. Currently with a vanilla kernel and xenomai patch, my DVI display
> and USB keyboard, mouse do not function. So uart3 is the only way to interact
> with the beagleboard.

There are other possibilities to interact with Linux, e.g. telnet,
slogin or netcat. But it's always good to have a console.

>>> I looked at my /dev/ directory and not found rtser*. It does have
>>> ttyS0, ttyS1 and ttyS3
>>> for my normal serial ports. Nothing called rtser in /proc/xenomai/rtdm either
>>> root@domain.hid# ls
>>> fildes         open_fildes       rttest-switchtest0
>>> named_devices  protocol_devices  rttest-timerbench0
>>>
>>> Any suggestions?
>>
>> Which UART device do you want to use as rtser0? On the PC you can
>> shutdown the device you want to use for rtserial with:
>>
>> # setserial /dev/ttyS0 uart none
>>
>> Not sure if this works on the Beagle board, though. If not, you may need
>> to disable the UARTs in your board config code. Finally you must load
>> the module with the proper arguments:
>>
>> # insmod xeno_16550A.ko mem=0x49020000 irq=74 baud_base=?
>>
>> That requires XENO_DRIVERS_16550A_MMIO or XENO_DRIVERS_16550A_ANY to be
>> set. If you are lucky, it might work.
>>
>> Wolfgang.
>>
> I am trying to use uart1 and uart2 (uart3 is for the console) for cross-link.
> 
> These lines are from my dmesg output:
> 
> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
> serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
> serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
> console [ttyS2] enabled

All three uarts are occupied by Linux and you cannot use them as
rtserial. First you need to release at least one of them. What Linux
config do you use for your board?

> I can see that I have xeno_16550A.ko in
> /lib/modules/2.6.33.3/kernel/drivers/xenomai/serial. But I forgot if I
> have set XENO_DRIVERS_16550A_MMIO or XENO_DRIVERS_16550A_ANY during
> xenomai configuration. How to check
> these configuration? I can't find a .config file like linux kernel.
> The config.log
> doesn't contain these.

It should be in the kernels .config!

> When I tried to load the driver by:
> 
> root@domain.hid:~#  insmod xeno_16550A.ko mem=0x4806a000 irq=72 baud_base=19200
> sh: insmod: not found
> root@domain.hid:~#

Hm, maybe modprobe is present. Might be a busybox config issue.

Wolfgang.

Re: [Xenomai-help] problem with serial example

[Everett Wang]

I think I didn't state correctly. It is not due to xenomai patch for my display
and USB. I am using Angstrom distribution. But I replaced its kernel and
modules with xenomai patched vanilla kernel 2.6.33.3. I think due to the fact
that Angstrom distribution is heavily patched kernel for display and
USB to work.
If I replaced its kernel with a vanilla one, many of the 3D and usb stuff could
be broken. So it is the kernel replacement that caused the display and USB
trouble.

Having said that, I really don't need 3D display. If I can get a console
display on my DVI, then I can use all the uarts for xenomai. Should I
use debian or ubuntu distribution for xenomai instead of Angstrom?

Best regards,

Everett



On Sun, May 23, 2010 at 11:29 PM, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
> Everett Wang wrote:
>> That is right. Currently with a vanilla kernel and xenomai patch, my DVI display
>> and USB keyboard, mouse do not function. So uart3 is the only way to interact
>> with the beagleboard.
>
> That is not normal. If you are using the same configuration, things
> should work. Do you get any messages about this on the console?
>
> --
>                                            Gilles.
>

Re: [Xenomai-help] problem with serial example

[Everett Wang]

On Sun, May 23, 2010 at 11:46 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
> On 05/23/2010 04:59 PM, Everett Wang wrote:
>> On Sun, May 23, 2010 at 5:37 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>> On 05/23/2010 05:48 AM, Everett Wang wrote:
>>>> Hi All,
>>>>
>>>> I am trying to make my serial work with xenomai. I have managed to
>>>> compile and almost run the cross-link example.
>>>> When I tried to run it, I got a shared library problem:
>>>>
>>>> examples
>>>> ./cross-link
>>>> ./cross-link: error while loading shared libraries: libxenomai.so.0: cannot...
>>>>
>>>> I then added this:
>>>>
>>>> $LD_LIBRARY_PATH=/usr/xenomai/lib
>>>> $export LD_LIBRARY_PATH
>>>>
>>>> Is this the right thing to do?
>>>>
>>>> I tried it again. I got a little further:
>>>>
>>>> root@domain.hid# ./cross-link
>>>> main : can't open rtser0 (write), No such device
>>>>
>>>> I googled a little bit and still can't find a solution. Here is the system I am
>>>> using: Beagleboard C4, xenomai 2.5.3, linux 2.6.33.3, cross-compiler CSL
>>>> 2010Q1. In my kernel configuration, I do have CONFIG_XENO_DRIVERS_16550A
>>>> enabled as a module.
>>>
>>> Is the module loaded. If not, it's no surprise that there is no rtser0
>>> device. Anyway, I'm not sure if Xenomai's 16550A RTserial driver is
>>> fully compatible with OMAPs 8250 devices, especially the proper access
>>> method might not be supported.
>>
>> I checked with lsmod. No modules are loaded.
>>
>>>
>>>> In a 2007 post, I saw  Philippe Gerum suggested to  have "vanilla
>>>> serial support disabled".
>>>> which kernel config is that? CONFIG_SERIAL_CORE? or CONFIG_SERIAL_8250?
>>>
>>> This will disable all serial devices including the console. Not sure if
>>> you want that.
>>
>> That is right. Currently with a vanilla kernel and xenomai patch, my DVI display
>> and USB keyboard, mouse do not function. So uart3 is the only way to interact
>> with the beagleboard.
>
> There are other possibilities to interact with Linux, e.g. telnet,
> slogin or netcat. But it's always good to have a console.
>
I guess I need a USB to ethernet for these.

>>>> I looked at my /dev/ directory and not found rtser*. It does have
>>>> ttyS0, ttyS1 and ttyS3
>>>> for my normal serial ports. Nothing called rtser in /proc/xenomai/rtdm either
>>>> root@domain.hid# ls
>>>> fildes         open_fildes       rttest-switchtest0
>>>> named_devices  protocol_devices  rttest-timerbench0
>>>>
>>>> Any suggestions?
>>>
>>> Which UART device do you want to use as rtser0? On the PC you can
>>> shutdown the device you want to use for rtserial with:
>>>
>>> # setserial /dev/ttyS0 uart none
>>>
>>> Not sure if this works on the Beagle board, though. If not, you may need
>>> to disable the UARTs in your board config code. Finally you must load
>>> the module with the proper arguments:
>>>
>>> # insmod xeno_16550A.ko mem=0x49020000 irq=74 baud_base=?
>>>
>>> That requires XENO_DRIVERS_16550A_MMIO or XENO_DRIVERS_16550A_ANY to be
>>> set. If you are lucky, it might work.
>>>
>>> Wolfgang.
>>>
>> I am trying to use uart1 and uart2 (uart3 is for the console) for cross-link.
>>
>> These lines are from my dmesg output:
>>
>> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
>> serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
>> serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
>> console [ttyS2] enabled
>
> All three uarts are occupied by Linux and you cannot use them as
> rtserial. First you need to release at least one of them. What Linux
> config do you use for your board?

I didn't do any configuration. Do you mean to config these during kernel
configuration?

>> I can see that I have xeno_16550A.ko in
>> /lib/modules/2.6.33.3/kernel/drivers/xenomai/serial. But I forgot if I
>> have set XENO_DRIVERS_16550A_MMIO or XENO_DRIVERS_16550A_ANY during
>> xenomai configuration. How to check
>> these configuration? I can't find a .config file like linux kernel.
>> The config.log
>> doesn't contain these.
>
> It should be in the kernels .config!

You are right. I found them in my .config for the kernel. I will enable them
and recompile the kernel and xenomai.

>> When I tried to load the driver by:
>>
>> root@domain.hid:~#  insmod xeno_16550A.ko mem=0x4806a000 irq=72 baud_base=19200
>> sh: insmod: not found
>> root@domain.hid:~#
>
> Hm, maybe modprobe is present. Might be a busybox config issue.

modeprobe doesn't exist either. I will try to ask Angstrom mailing list for
these.

> Wolfgang.
>

Everett

Re: [Xenomai-help] problem with serial example

[Wolfgang Grandegger]

On 05/23/2010 06:19 PM, Everett Wang wrote:
> On Sun, May 23, 2010 at 11:46 PM, Wolfgang Grandegger <wg@domain.hid> wrote:

>> There are other possibilities to interact with Linux, e.g. telnet,
>> slogin or netcat. But it's always good to have a console.
>>
> I guess I need a USB to ethernet for these.

Yes.

...
>> All three uarts are occupied by Linux and you cannot use them as
>> rtserial. First you need to release at least one of them. What Linux
>> config do you use for your board?
> 
> I didn't do any configuration. Do you mean to config these during kernel
> configuration?

Can you show us the .config of your kernel?

Some more insights:

I think the serial ports for the beagle boards are configured in:

http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c

Therein you find entries like:

http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L82

As you can see, a regshift of 2 is used, which is not yet supported by
the 16550A RTDM driver. Should not be a big deal to add it, though.
Also, as "baud_base" you should use OMAP24XX_BASE_BAUD.

Wolfgang.

Re: [Xenomai-help] problem with serial example

[Wolfgang Grandegger]

Hello,

some more insights:

On 05/23/2010 05:46 PM, Wolfgang Grandegger wrote:
> On 05/23/2010 04:59 PM, Everett Wang wrote:
>> On Sun, May 23, 2010 at 5:37 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>> On 05/23/2010 05:48 AM, Everett Wang wrote:
>>>> Hi All,
>>>>
>>>> I am trying to make my serial work with xenomai. I have managed to
>>>> compile and almost run the cross-link example.
>>>> When I tried to run it, I got a shared library problem:
>>>>
>>>> examples
>>>> ./cross-link
>>>> ./cross-link: error while loading shared libraries: libxenomai.so.0: cannot...
>>>>
>>>> I then added this:
>>>>
>>>> $LD_LIBRARY_PATH=/usr/xenomai/lib
>>>> $export LD_LIBRARY_PATH
>>>>
>>>> Is this the right thing to do?
>>>>
>>>> I tried it again. I got a little further:
>>>>
>>>> root@domain.hid# ./cross-link
>>>> main : can't open rtser0 (write), No such device
>>>>
>>>> I googled a little bit and still can't find a solution. Here is the system I am
>>>> using: Beagleboard C4, xenomai 2.5.3, linux 2.6.33.3, cross-compiler CSL
>>>> 2010Q1. In my kernel configuration, I do have CONFIG_XENO_DRIVERS_16550A
>>>> enabled as a module.
>>>
>>> Is the module loaded. If not, it's no surprise that there is no rtser0
>>> device. Anyway, I'm not sure if Xenomai's 16550A RTserial driver is
>>> fully compatible with OMAPs 8250 devices, especially the proper access
>>> method might not be supported.

I think the serial ports for the beagle boards are configured in:

http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c

Therein you find entries like:

http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L82

As you can see, a regshift of 2 is used, which is not yet supported by
the 16550A RTDM driver. Should not be a big deal to add it, though.
Also, as baud_base you should use OMAP24XX_BASE_BAUD.

Wolfgang.

Re: [Xenomai-help] problem with serial example

[Everett Wang]

[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]

On Mon, May 24, 2010 at 12:28 AM, Wolfgang Grandegger <wg@domain.hid> wrote:
> On 05/23/2010 06:19 PM, Everett Wang wrote:
>> On Sun, May 23, 2010 at 11:46 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>
>>> There are other possibilities to interact with Linux, e.g. telnet,
>>> slogin or netcat. But it's always good to have a console.
>>>
>> I guess I need a USB to ethernet for these.
>
> Yes.
>
> ...
>>> All three uarts are occupied by Linux and you cannot use them as
>>> rtserial. First you need to release at least one of them. What Linux
>>> config do you use for your board?
>>
>> I didn't do any configuration. Do you mean to config these during kernel
>> configuration?
>
> Can you show us the .config of your kernel?
>
> Some more insights:
>
> I think the serial ports for the beagle boards are configured in:
>
> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c
>
> Therein you find entries like:
>
> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L82
>
> As you can see, a regshift of 2 is used, which is not yet supported by
> the 16550A RTDM driver. Should not be a big deal to add it, though.
> Also, as "baud_base" you should use OMAP24XX_BASE_BAUD.
>
> Wolfgang.
>

Thanks for the suggestions. The .config file is attached. I will look at the
code you pointed to today to study the configuration of the serial port.

Everett

[-- Attachment #2: config.3 --]
[-- Type: application/octet-stream, Size: 47301 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.33.3
# Sun May 23 16:51:26 2010
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_GENERIC_GPIO=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_ARCH_HAS_CPUFREQ=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_VECTORS_BASE=0xffff0000
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_LZO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_TREE_PREEMPT_RCU is not set
# CONFIG_TINY_RCU is not set
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_FANOUT=32
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
# CONFIG_CGROUPS is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
# CONFIG_RD_BZIP2 is not set
# CONFIG_RD_LZMA is not set
# CONFIG_RD_LZO is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y

#
# Kernel Performance Events And Counters
#
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_COMPAT_BRK=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_CLK=y

#
# GCOV-based kernel profiling
#
# CONFIG_SLOW_WORK is not set
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_BLOCK=y
CONFIG_LBDAF=y
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_INTEGRITY is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
CONFIG_INLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
CONFIG_INLINE_READ_UNLOCK=y
# CONFIG_INLINE_READ_UNLOCK_BH is not set
CONFIG_INLINE_READ_UNLOCK_IRQ=y
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
CONFIG_INLINE_WRITE_UNLOCK=y
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
# CONFIG_MUTEX_SPIN_ON_OWNER is not set

#
# Real-time sub-system
#
CONFIG_XENOMAI=y
CONFIG_XENO_GENERIC_STACKPOOL=y
CONFIG_XENO_FASTSYNCH_DEP=y
CONFIG_XENO_FASTSYNCH=y
CONFIG_XENO_OPT_NUCLEUS=y
CONFIG_XENO_OPT_PERVASIVE=y
CONFIG_XENO_OPT_PRIOCPL=y
CONFIG_XENO_OPT_PIPELINE_HEAD=y
# CONFIG_XENO_OPT_SCHED_CLASSES is not set
CONFIG_XENO_OPT_PIPE=y
CONFIG_XENO_OPT_PIPE_NRDEV=32
CONFIG_XENO_OPT_REGISTRY_NRSLOTS=512
CONFIG_XENO_OPT_SYS_HEAPSZ=256
CONFIG_XENO_OPT_SYS_STACKPOOLSZ=128
CONFIG_XENO_OPT_SEM_HEAPSZ=12
CONFIG_XENO_OPT_GLOBAL_SEM_HEAPSZ=12
CONFIG_XENO_OPT_STATS=y
# CONFIG_XENO_OPT_DEBUG is not set
# CONFIG_XENO_OPT_SHIRQ is not set

#
# Timing
#
# CONFIG_XENO_OPT_TIMING_PERIODIC is not set
CONFIG_XENO_OPT_TIMING_VIRTICK=1000
CONFIG_XENO_OPT_TIMING_SCHEDLAT=0

#
# Scalability
#
# 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

#
# Machine
#
CONFIG_IPIPE_WANT_PREEMPTIBLE_SWITCH=y
CONFIG_XENO_HW_FPU=y
CONFIG_XENO_HW_UNLOCKED_SWITCH=y

#
# Interfaces
#
CONFIG_XENO_SKIN_NATIVE=y
CONFIG_XENO_OPT_NATIVE_PERIOD=0
CONFIG_XENO_OPT_NATIVE_PIPE=y
CONFIG_XENO_OPT_NATIVE_PIPE_BUFSZ=1024
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_BUFFER=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
CONFIG_XENO_OPT_POSIX_PERIOD=0
# CONFIG_XENO_OPT_POSIX_SHM is not set
# CONFIG_XENO_OPT_POSIX_INTR is not set
# CONFIG_XENO_OPT_POSIX_SELECT is not set
# CONFIG_XENO_OPT_DEBUG_POSIX is not set
# CONFIG_XENO_SKIN_PSOS is not set
# CONFIG_XENO_SKIN_UITRON is not set
# CONFIG_XENO_SKIN_VRTX is not set
# CONFIG_XENO_SKIN_VXWORKS is not set
CONFIG_XENO_SKIN_RTAI=m
CONFIG_XENO_OPT_RTAI_PERIOD=0
CONFIG_XENO_OPT_RTAI_FIFO=y
CONFIG_XENO_OPT_RTAI_SEM=y
CONFIG_XENO_OPT_RTAI_SHM=y
# CONFIG_XENO_OPT_NOWARN_DEPRECATED is not set
CONFIG_XENO_SKIN_RTDM=y
CONFIG_XENO_OPT_RTDM_PERIOD=0
CONFIG_XENO_OPT_RTDM_FILDES=128
# CONFIG_XENO_OPT_RTDM_SELECT is not set

#
# Drivers
#

#
# Serial drivers
#
CONFIG_XENO_DRIVERS_16550A=m
CONFIG_XENO_DRIVERS_16550A_PIO=y
# CONFIG_XENO_DRIVERS_16550A_MMIO is not set
# CONFIG_XENO_DRIVERS_16550A_ANY is not set

#
# Testing drivers
#
# CONFIG_XENO_DRIVERS_TESTING_LEGACY_NAMES is not set
CONFIG_XENO_DRIVERS_TIMERBENCH=y
CONFIG_XENO_DRIVERS_KLATENCY=m
CONFIG_XENO_DRIVERS_IRQBENCH=m
CONFIG_XENO_DRIVERS_SWITCHTEST=y
CONFIG_XENO_DRIVERS_SIGTEST=m
CONFIG_XENO_DRIVERS_RTDMTEST=m

#
# CAN drivers
#
# CONFIG_XENO_DRIVERS_CAN is not set

#
# ANALOGY drivers
#
# CONFIG_XENO_DRIVERS_ANALOGY is not set

#
# Real-time IPC drivers
#
# CONFIG_XENO_DRIVERS_RTIPC is not set
CONFIG_FREEZER=y

#
# System Type
#
CONFIG_MMU=y
# CONFIG_ARCH_AAEC2000 is not set
# CONFIG_ARCH_INTEGRATOR is not set
# CONFIG_ARCH_REALVIEW is not set
# CONFIG_ARCH_VERSATILE is not set
# CONFIG_ARCH_AT91 is not set
# CONFIG_ARCH_CLPS711X is not set
# CONFIG_ARCH_GEMINI is not set
# CONFIG_ARCH_EBSA110 is not set
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_MXC is not set
# CONFIG_ARCH_STMP3XXX is not set
# CONFIG_ARCH_NETX is not set
# CONFIG_ARCH_H720X is not set
# CONFIG_ARCH_NOMADIK is not set
# CONFIG_ARCH_IOP13XX is not set
# CONFIG_ARCH_IOP32X is not set
# CONFIG_ARCH_IOP33X is not set
# CONFIG_ARCH_IXP23XX is not set
# CONFIG_ARCH_IXP2000 is not set
# CONFIG_ARCH_IXP4XX is not set
# CONFIG_ARCH_L7200 is not set
# CONFIG_ARCH_DOVE is not set
# CONFIG_ARCH_KIRKWOOD is not set
# CONFIG_ARCH_LOKI is not set
# CONFIG_ARCH_MV78XX0 is not set
# CONFIG_ARCH_ORION5X is not set
# CONFIG_ARCH_MMP is not set
# CONFIG_ARCH_KS8695 is not set
# CONFIG_ARCH_NS9XXX is not set
# CONFIG_ARCH_W90X900 is not set
# CONFIG_ARCH_PNX4008 is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_MSM is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C2410 is not set
# CONFIG_ARCH_S3C64XX is not set
# CONFIG_ARCH_S5PC1XX is not set
# CONFIG_ARCH_SHARK is not set
# CONFIG_ARCH_LH7A40X is not set
# CONFIG_ARCH_U300 is not set
# CONFIG_ARCH_DAVINCI is not set
CONFIG_ARCH_OMAP=y
# CONFIG_ARCH_BCMRING is not set
# CONFIG_ARCH_U8500 is not set

#
# TI OMAP Implementations
#
CONFIG_ARCH_OMAP_OTG=y
# CONFIG_ARCH_OMAP1 is not set
# CONFIG_ARCH_OMAP2 is not set
CONFIG_ARCH_OMAP3=y
# CONFIG_ARCH_OMAP4 is not set

#
# OMAP Feature Selections
#
# CONFIG_OMAP_RESET_CLOCKS is not set
# CONFIG_OMAP_MUX is not set
CONFIG_OMAP_MCBSP=y
# CONFIG_OMAP_MBOX_FWK is not set
CONFIG_OMAP_MPU_TIMER=y
# CONFIG_OMAP_32K_TIMER is not set
CONFIG_OMAP_DM_TIMER=y
# CONFIG_OMAP_LL_DEBUG_UART1 is not set
# CONFIG_OMAP_LL_DEBUG_UART2 is not set
CONFIG_OMAP_LL_DEBUG_UART3=y
# CONFIG_OMAP_LL_DEBUG_NONE is not set
# CONFIG_OMAP_PM_NONE is not set
CONFIG_OMAP_PM_NOOP=y
CONFIG_ARCH_OMAP34XX=y
CONFIG_ARCH_OMAP3430=y
CONFIG_OMAP_PACKAGE_CBB=y

#
# OMAP Board Type
#
CONFIG_MACH_OMAP3_BEAGLE=y
# CONFIG_MACH_OMAP_LDP is not set
# CONFIG_MACH_OVERO is not set
# CONFIG_MACH_OMAP3EVM is not set
# CONFIG_MACH_OMAP3517EVM is not set
# CONFIG_MACH_OMAP3_PANDORA is not set
# CONFIG_MACH_OMAP3_TOUCHBOOK is not set
# CONFIG_MACH_OMAP_3430SDP is not set
# CONFIG_MACH_NOKIA_RX51 is not set
# CONFIG_MACH_OMAP_ZOOM2 is not set
# CONFIG_MACH_OMAP_ZOOM3 is not set
# CONFIG_MACH_CM_T35 is not set
# CONFIG_MACH_IGEP0020 is not set
# CONFIG_MACH_OMAP_3630SDP is not set
# CONFIG_OMAP3_EMU is not set
# CONFIG_OMAP3_SDRC_AC_TIMING is not set

#
# Processor Type
#
CONFIG_CPU_32v6K=y
CONFIG_CPU_V7=y
CONFIG_CPU_32v7=y
CONFIG_CPU_ABRT_EV7=y
CONFIG_CPU_PABRT_V7=y
CONFIG_CPU_CACHE_V7=y
CONFIG_CPU_CACHE_VIPT=y
CONFIG_CPU_COPY_V6=y
CONFIG_CPU_TLB_V7=y
CONFIG_CPU_HAS_ASID=y
CONFIG_CPU_CP15=y
CONFIG_CPU_CP15_MMU=y

#
# Processor Features
#
CONFIG_ARM_THUMB=y
# CONFIG_ARM_THUMBEE is not set
# CONFIG_CPU_ICACHE_DISABLE is not set
# CONFIG_CPU_DCACHE_DISABLE is not set
# CONFIG_CPU_BPREDICT_DISABLE is not set
CONFIG_HAS_TLS_REG=y
CONFIG_ARM_L1_CACHE_SHIFT=6
# CONFIG_ARM_ERRATA_430973 is not set
# CONFIG_ARM_ERRATA_458693 is not set
# CONFIG_ARM_ERRATA_460075 is not set
CONFIG_COMMON_CLKDEV=y

#
# Bus support
#
# CONFIG_PCI_SYSCALL is not set
# CONFIG_ARCH_SUPPORTS_MSI is not set
# CONFIG_PCCARD is not set

#
# Kernel Features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_IPIPE=y
CONFIG_IPIPE_DOMAINS=4
CONFIG_IPIPE_DELAYED_ATOMICSW=y
# CONFIG_IPIPE_UNMASKED_CONTEXT_SWITCH is not set
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_HZ=100
# CONFIG_THUMB2_KERNEL is not set
CONFIG_AEABI=y
CONFIG_OABI_COMPAT=y
CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set
# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set
# CONFIG_HIGHMEM is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_PHYS_ADDR_T_64BIT is not set
CONFIG_ZONE_DMA_FLAG=0
CONFIG_VIRT_TO_BUS=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
# CONFIG_LEDS is not set
CONFIG_ALIGNMENT_TRAP=y
# CONFIG_UACCESS_WITH_MEMCPY is not set

#
# Boot options
#
CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZBOOT_ROM_BSS=0x0
CONFIG_CMDLINE="root=/dev/nfs nfsroot=192.168.0.1:/home/user/buildroot ip=192.168.0.2:192.168.0.1:192.168.0.1:255.255.255.0:tgt:eth0:off rw console=ttyS2,115200n8"
# CONFIG_XIP_KERNEL is not set
# CONFIG_KEXEC is not set

#
# CPU Power Management
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_IDLE is not set

#
# Floating point emulation
#

#
# At least one emulation must be selected
#
CONFIG_FPE_NWFPE=y
# CONFIG_FPE_NWFPE_XP is not set
# CONFIG_FPE_FASTFPE is not set
CONFIG_VFP=y
CONFIG_VFPv3=y
CONFIG_NEON=y

#
# Userspace binary formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
CONFIG_HAVE_AOUT=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y

#
# Power management options
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_APM_EMULATION is not set
# CONFIG_PM_RUNTIME is not set
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_NET_KEY=y
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_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_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
CONFIG_WIRELESS=y
CONFIG_WIRELESS_EXT=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_PRIV=y
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_WIRELESS_OLD_REGULATORY is not set
CONFIG_CFG80211_WEXT=y
CONFIG_WIRELESS_EXT_SYSFS=y
# CONFIG_LIB80211 is not set
# CONFIG_MAC80211 is not set
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_DEVTMPFS is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_TESTS is not set
# CONFIG_MTD_CONCAT is not set
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_REDBOOT_PARTS is not set
# CONFIG_MTD_CMDLINE_PARTS is not set
# CONFIG_MTD_AFS_PARTS is not set
# CONFIG_MTD_AR7_PARTS is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_MTD_OOPS is not set

#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set

#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PLATRAM is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_DATAFLASH is not set
# CONFIG_MTD_M25P80 is not set
# CONFIG_MTD_SST25L is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
CONFIG_MTD_NAND=y
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
# CONFIG_MTD_NAND_ECC_SMC is not set
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
# CONFIG_MTD_NAND_GPIO is not set
# CONFIG_MTD_NAND_OMAP2 is not set
CONFIG_MTD_NAND_IDS=y
# CONFIG_MTD_NAND_DISKONCHIP is not set
# CONFIG_MTD_NAND_NANDSIM is not set
# CONFIG_MTD_NAND_PLATFORM is not set
# CONFIG_MTD_ALAUDA is not set
# CONFIG_MTD_ONENAND is not set

#
# LPDDR flash memory drivers
#
# CONFIG_MTD_LPDDR is not set

#
# UBI - Unsorted block images
#
# CONFIG_MTD_UBI is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set

#
# DRBD disabled because PROC_FS, INET or CONNECTOR not selected
#
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_MG_DISK is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST 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_CHR_DEV_SCH is not set
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_LIBFC is not set
# CONFIG_LIBFCOE is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
# CONFIG_ATA is not set
# CONFIG_MD is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NET_ETHERNET is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
CONFIG_WLAN=y
CONFIG_USB_ZD1201=m
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_ATH_COMMON is not set
# CONFIG_HOSTAP is not set
# CONFIG_IWM is not set
# CONFIG_LIBERTAS is not set

#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set
# CONFIG_INPUT_SPARSEKMAP is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=m
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_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_TWL4030 is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_SERPORT=y
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MAX3100 is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
# CONFIG_LEGACY_PTYS is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_R3964 is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_TCG_TPM is not set
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_HELPER_AUTO=y

#
# I2C Hardware Bus support
#

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_DESIGNWARE is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set
CONFIG_I2C_OMAP=y
# CONFIG_I2C_SIMTEC is not set

#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set

#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_STUB is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
CONFIG_SPI=y
CONFIG_SPI_DEBUG=y
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_GPIO is not set
CONFIG_SPI_OMAP24XX=m
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_DESIGNWARE is not set

#
# SPI Protocol Masters
#
CONFIG_SPI_SPIDEV=m
# CONFIG_SPI_TLE62X0 is not set

#
# PPS support
#
# CONFIG_PPS is not set
CONFIG_ARCH_REQUIRE_GPIOLIB=y
CONFIG_GPIOLIB=y
# CONFIG_DEBUG_GPIO is not set
CONFIG_GPIO_SYSFS=y

#
# Memory mapped GPIO expanders:
#

#
# I2C GPIO expanders:
#
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not set
CONFIG_GPIO_TWL4030=y
# CONFIG_GPIO_ADP5588 is not set

#
# PCI GPIO expanders:
#

#
# SPI GPIO expanders:
#
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MCP23S08 is not set
# CONFIG_GPIO_MC33880 is not set

#
# AC97 GPIO expanders:
#
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_THERMAL is not set
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set

#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_OMAP_WATCHDOG is not set
CONFIG_TWL4030_WATCHDOG=m

#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_ASIC3 is not set
# CONFIG_HTC_EGPIO is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_TPS65010 is not set
CONFIG_TWL4030_CORE=y
# CONFIG_TWL4030_POWER is not set
# CONFIG_TWL4030_CODEC is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_T7L66XB is not set
# CONFIG_MFD_TC6387XB is not set
# CONFIG_MFD_TC6393XB is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_MC13783 is not set
# CONFIG_AB3100_CORE is not set
# CONFIG_EZX_PCAP is not set
# CONFIG_MFD_88PM8607 is not set
# CONFIG_AB4500_CORE is not set
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
# CONFIG_REGULATOR_BQ24022 is not set
# CONFIG_REGULATOR_MAX1586 is not set
# CONFIG_REGULATOR_MAX8660 is not set
CONFIG_REGULATOR_TWL4030=y
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set
# CONFIG_MEDIA_SUPPORT is not set

#
# Graphics support
#
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=m
CONFIG_FB_CFB_COPYAREA=m
CONFIG_FB_CFB_IMAGEBLIT=m
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
# CONFIG_FB_MODE_HELPERS is not set
# CONFIG_FB_TILEBLITTING is not set

#
# Frame buffer hardware drivers
#
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
# CONFIG_FB_OMAP_BOOTLOADER_INIT is not set
CONFIG_OMAP2_VRAM=y
CONFIG_OMAP2_VRFB=y
CONFIG_OMAP2_DSS=m
CONFIG_OMAP2_VRAM_SIZE=12
CONFIG_OMAP2_DSS_DEBUG_SUPPORT=y
# CONFIG_OMAP2_DSS_COLLECT_IRQ_STATS is not set
# CONFIG_OMAP2_DSS_RFBI is not set
CONFIG_OMAP2_DSS_VENC=y
CONFIG_OMAP2_DSS_SDI=y
CONFIG_OMAP2_DSS_DSI=y
# CONFIG_OMAP2_DSS_USE_DSI_PLL is not set
# CONFIG_OMAP2_DSS_FAKE_VSYNC is not set
CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0
CONFIG_FB_OMAP2=m
CONFIG_FB_OMAP2_DEBUG_SUPPORT=y
# CONFIG_FB_OMAP2_FORCE_AUTO_UPDATE is not set
CONFIG_FB_OMAP2_NUM_FBS=3

#
# OMAP2/3 Display Device Drivers
#
# CONFIG_PANEL_GENERIC is not set
# CONFIG_PANEL_SHARP_LS037V7DW01 is not set
# CONFIG_PANEL_TAAL is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Console display driver support
#
# CONFIG_VGA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_7x14 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
# CONFIG_FONT_10x18 is not set
# CONFIG_LOGO is not set
# CONFIG_SOUND is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HIDRAW is not set

#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_HID_PID is not set
# CONFIG_USB_HIDDEV is not set

#
# Special HID drivers
#
# CONFIG_HID_A4TECH is not set
# CONFIG_HID_APPLE is not set
# CONFIG_HID_BELKIN is not set
# CONFIG_HID_CHERRY is not set
# CONFIG_HID_CHICONY is not set
# CONFIG_HID_CYPRESS is not set
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EZKEY is not set
# CONFIG_HID_KYE is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_TWINHAN is not set
# CONFIG_HID_KENSINGTON is not set
# CONFIG_HID_LOGITECH is not set
# CONFIG_HID_MICROSOFT is not set
# CONFIG_HID_MONTEREY is not set
# CONFIG_HID_NTRIG is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_SAMSUNG is not set
# CONFIG_HID_SONY is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_ZEROPLUS is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
CONFIG_USB_OTG=y
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
CONFIG_USB_MON=y
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HWA_HCD is not set
CONFIG_USB_MUSB_HDRC=y
CONFIG_USB_MUSB_SOC=y

#
# OMAP 343x high speed USB support
#
# CONFIG_USB_MUSB_HOST is not set
# CONFIG_USB_MUSB_PERIPHERAL is not set
CONFIG_USB_MUSB_OTG=y
CONFIG_USB_GADGET_MUSB_HDRC=y
CONFIG_USB_MUSB_HDRC_HCD=y
# CONFIG_MUSB_PIO_ONLY is not set
CONFIG_USB_INVENTRA_DMA=y
# CONFIG_USB_TI_CPPI_DMA is not set
# CONFIG_USB_MUSB_DEBUG is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#

#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
# 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_USBAT is not set
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB port drivers
#
CONFIG_USB_SERIAL=m
# CONFIG_USB_EZUSB is not set
CONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_AIRCABLE is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_CH341 is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
CONFIG_USB_SERIAL_CP210X=m
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
CONFIG_USB_SERIAL_FTDI_SIO=m
# CONFIG_USB_SERIAL_FUNSOFT is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_GARMIN is not set
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_IUU is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_MOTOROLA is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
CONFIG_USB_SERIAL_PL2303=m
# CONFIG_USB_SERIAL_OTI6858 is not set
# CONFIG_USB_SERIAL_QUALCOMM is not set
# CONFIG_USB_SERIAL_SPCP8X5 is not set
# CONFIG_USB_SERIAL_HP4X is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIEMENS_MPI is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
# CONFIG_USB_SERIAL_SYMBOL is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
CONFIG_USB_SERIAL_OPTION=m
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_SERIAL_OPTICON is not set
# CONFIG_USB_SERIAL_DEBUG is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_VST is not set
CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_SELECTED=y
# CONFIG_USB_GADGET_AT91 is not set
# CONFIG_USB_GADGET_ATMEL_USBA is not set
# CONFIG_USB_GADGET_FSL_USB2 is not set
# CONFIG_USB_GADGET_LH7A40X is not set
# CONFIG_USB_GADGET_OMAP is not set
# CONFIG_USB_GADGET_PXA25X is not set
# CONFIG_USB_GADGET_R8A66597 is not set
# CONFIG_USB_GADGET_PXA27X is not set
# CONFIG_USB_GADGET_S3C_HSOTG is not set
# CONFIG_USB_GADGET_IMX is not set
# CONFIG_USB_GADGET_S3C2410 is not set
# CONFIG_USB_GADGET_M66592 is not set
# CONFIG_USB_GADGET_AMD5536UDC is not set
# CONFIG_USB_GADGET_FSL_QE is not set
# CONFIG_USB_GADGET_CI13XXX is not set
# CONFIG_USB_GADGET_NET2280 is not set
# CONFIG_USB_GADGET_GOKU is not set
# CONFIG_USB_GADGET_LANGWELL is not set
# CONFIG_USB_GADGET_DUMMY_HCD is not set
CONFIG_USB_GADGET_DUALSPEED=y
# CONFIG_USB_ZERO is not set
# CONFIG_USB_AUDIO is not set
CONFIG_USB_ETH=m
CONFIG_USB_ETH_RNDIS=y
# CONFIG_USB_ETH_EEM is not set
# CONFIG_USB_GADGETFS is not set
# CONFIG_USB_FILE_STORAGE is not set
# CONFIG_USB_MASS_STORAGE is not set
# CONFIG_USB_G_SERIAL is not set
# CONFIG_USB_MIDI_GADGET is not set
# CONFIG_USB_G_PRINTER is not set
# CONFIG_USB_CDC_COMPOSITE is not set
# CONFIG_USB_G_MULTI is not set

#
# OTG and related infrastructure
#
CONFIG_USB_OTG_UTILS=y
# CONFIG_USB_GPIO_VBUS is not set
CONFIG_ISP1301_OMAP=m
# CONFIG_USB_ULPI is not set
CONFIG_TWL4030_USB=y
# CONFIG_NOP_USB_XCEIV is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set

#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set

#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_SDHCI is not set
# CONFIG_MMC_OMAP is not set
CONFIG_MMC_OMAP_HS=y
# CONFIG_MMC_AT91 is not set
# CONFIG_MMC_ATMELMCI is not set
# CONFIG_MMC_SPI is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set

#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_TWL4030 is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set

#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_DS3234 is not set
# CONFIG_RTC_DRV_PCF2123 is not set

#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set

#
# on-CPU RTC drivers
#
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set

#
# TI VLYNQ
#
# CONFIG_STAGING is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
# CONFIG_EXT3_FS_XATTR is not set
# CONFIG_EXT4_FS is not set
CONFIG_JBD=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
# CONFIG_QUOTA_NETLINK_INTERFACE is not set
CONFIG_PRINT_QUOTA_WARNING=y
CONFIG_QUOTA_TREE=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

#
# Caches
#
# CONFIG_FSCACHE 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=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
# CONFIG_JFFS2_SUMMARY is not set
# CONFIG_JFFS2_FS_XATTR is not set
# CONFIG_JFFS2_COMPRESSION_OPTIONS is not set
CONFIG_JFFS2_ZLIB=y
# CONFIG_JFFS2_LZO is not set
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFSD is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=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_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
# CONFIG_DLM is not set

#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
CONFIG_MAGIC_SYSRQ=y
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
# CONFIG_IPIPE_DEBUG is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
CONFIG_DEBUG_MUTEXES=y
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_BUGVERBOSE is not set
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_WRITECOUNT is not set
# CONFIG_DEBUG_MEMORY_INIT is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_DETECTOR=y
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
# CONFIG_PAGE_POISONING is not set
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
CONFIG_ARM_UNWIND=y
# CONFIG_DEBUG_USER is not set
# CONFIG_DEBUG_ERRORS is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_LL is not set
# CONFIG_OC_ETM is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_DEFAULT_SECURITY_SELINUX is not set
# CONFIG_DEFAULT_SECURITY_SMACK is not set
# CONFIG_DEFAULT_SECURITY_TOMOYO is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
CONFIG_CRYPTO_WORKQUEUE=y
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_TEST is not set

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set

#
# Block modes
#
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
CONFIG_CRYPTO_ECB=m
# CONFIG_CRYPTO_LRW is not set
CONFIG_CRYPTO_PCBC=m
# CONFIG_CRYPTO_XTS is not set

#
# Hash modes
#
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set

#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
# CONFIG_CRYPTO_GHASH is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set

#
# Ciphers
#
CONFIG_CRYPTO_AES=m
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set

#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_ZLIB is not set
# CONFIG_CRYPTO_LZO is not set

#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=m
CONFIG_CRYPTO_HW=y
# CONFIG_BINARY_PRINTF is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=y
# CONFIG_CRC16 is not set
# CONFIG_CRC_T10DIF is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_DECOMPRESS_GZIP=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_NLATTR=y

Re: [Xenomai-help] problem with serial example

[Everett Wang]

On Mon, May 24, 2010 at 7:36 AM, Everett Wang <everteq@domain.hid> wrote:
> On Mon, May 24, 2010 at 12:28 AM, Wolfgang Grandegger <wg@domain.hid> wrote:
>> On 05/23/2010 06:19 PM, Everett Wang wrote:
>>> On Sun, May 23, 2010 at 11:46 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>
>>>> There are other possibilities to interact with Linux, e.g. telnet,
>>>> slogin or netcat. But it's always good to have a console.
>>>>
>>> I guess I need a USB to ethernet for these.
>>
>> Yes.
>>
>> ...
>>>> All three uarts are occupied by Linux and you cannot use them as
>>>> rtserial. First you need to release at least one of them. What Linux
>>>> config do you use for your board?
>>>
>>> I didn't do any configuration. Do you mean to config these during kernel
>>> configuration?
>>
>> Can you show us the .config of your kernel?
>>
>> Some more insights:
>>
>> I think the serial ports for the beagle boards are configured in:
>>
>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c
>>
>> Therein you find entries like:
>>
>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L82
>>
>> As you can see, a regshift of 2 is used, which is not yet supported by
>> the 16550A RTDM driver. Should not be a big deal to add it, though.
>> Also, as "baud_base" you should use OMAP24XX_BASE_BAUD.
>>
>> Wolfgang.
>>
>
> Thanks for the suggestions. The .config file is attached. I will look at the
> code you pointed to today to study the configuration of the serial port.
>
> Everett
>

Hi Wolfgang,

I looked at the serial.c and function you pointed too. I have can't figure
out how to modify it. Could you point me to the right direction to read so
I can understand and eventually improve the serial for beagleboard? I thought
I could limit the kernel to use only one of the uart (console) by
changing function
 __init omap_serial_init(void):

 void __init omap_serial_init(void)
{
        int i;

//        for (i = 0; i < ARRAY_SIZE(omap_uart); i++)
//                omap_serial_init_port(i);
      omap_serial_init_port(2);
}

But the kernel hangs during booting after printing this message:

uncompressing Linux... done.

I guess it is not that simple to let kernel not to claim the uart0 and uart1.


Everett

Re: [Xenomai-help] problem with serial example

[Wolfgang Grandegger]

On 05/24/2010 09:32 AM, Everett Wang wrote:
> On Mon, May 24, 2010 at 7:36 AM, Everett Wang <everteq@domain.hid> wrote:
>> On Mon, May 24, 2010 at 12:28 AM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>> On 05/23/2010 06:19 PM, Everett Wang wrote:
>>>> On Sun, May 23, 2010 at 11:46 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>>
>>>>> There are other possibilities to interact with Linux, e.g. telnet,
>>>>> slogin or netcat. But it's always good to have a console.
>>>>>
>>>> I guess I need a USB to ethernet for these.
>>>
>>> Yes.
>>>
>>> ...
>>>>> All three uarts are occupied by Linux and you cannot use them as
>>>>> rtserial. First you need to release at least one of them. What Linux
>>>>> config do you use for your board?
>>>>
>>>> I didn't do any configuration. Do you mean to config these during kernel
>>>> configuration?
>>>
>>> Can you show us the .config of your kernel?
>>>
>>> Some more insights:
>>>
>>> I think the serial ports for the beagle boards are configured in:
>>>
>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c
>>>
>>> Therein you find entries like:
>>>
>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L82
>>>
>>> As you can see, a regshift of 2 is used, which is not yet supported by
>>> the 16550A RTDM driver. Should not be a big deal to add it, though.
>>> Also, as "baud_base" you should use OMAP24XX_BASE_BAUD.
>>>
>>> Wolfgang.
>>>
>>
>> Thanks for the suggestions. The .config file is attached. I will look at the
>> code you pointed to today to study the configuration of the serial port.
>>
>> Everett
>>
> 
> Hi Wolfgang,
> 
> I looked at the serial.c and function you pointed too. I have can't figure
> out how to modify it. Could you point me to the right direction to read so
> I can understand and eventually improve the serial for beagleboard? I thought
> I could limit the kernel to use only one of the uart (console) by
> changing function
>  __init omap_serial_init(void):
> 
>  void __init omap_serial_init(void)
> {
>         int i;
> 
> //        for (i = 0; i < ARRAY_SIZE(omap_uart); i++)
> //                omap_serial_init_port(i);
>       omap_serial_init_port(2);
> }
> 
> But the kernel hangs during booting after printing this message:
> 
> uncompressing Linux... done.
> 
> I guess it is not that simple to let kernel not to claim the uart0 and uart1.

Yes, unfortunately. I would try to comment out the uarts you want to
use for rtser in the following struct:

http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L562

Maybe the better option is to download setserial from

http://sourceforge.net/projects/setserial/files/setserial/2.17/setserial-2.17.tar.gz/download

and cross-compile it for your target. Then try:

# setserial /dev/ttyS2 uart none

Wolfgang.

Re: [Xenomai-help] problem with serial example

[Everett Wang]

On Mon, May 24, 2010 at 11:45 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
> On 05/24/2010 09:32 AM, Everett Wang wrote:
>> On Mon, May 24, 2010 at 7:36 AM, Everett Wang <everteq@domain.hid> wrote:
>>> On Mon, May 24, 2010 at 12:28 AM, Wolfgang Grandegger <wg@domain.hidm> wrote:
>>>> On 05/23/2010 06:19 PM, Everett Wang wrote:
>>>>> On Sun, May 23, 2010 at 11:46 PM, Wolfgang Grandegger <wg@domain.hid.com> wrote:
>>>>
>>>>>> There are other possibilities to interact with Linux, e.g. telnet,
>>>>>> slogin or netcat. But it's always good to have a console.
>>>>>>
>>>>> I guess I need a USB to ethernet for these.
>>>>
>>>> Yes.
>>>>
>>>> ...
>>>>>> All three uarts are occupied by Linux and you cannot use them as
>>>>>> rtserial. First you need to release at least one of them. What Linux
>>>>>> config do you use for your board?
>>>>>
>>>>> I didn't do any configuration. Do you mean to config these during kernel
>>>>> configuration?
>>>>
>>>> Can you show us the .config of your kernel?
>>>>
>>>> Some more insights:
>>>>
>>>> I think the serial ports for the beagle boards are configured in:
>>>>
>>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c
>>>>
>>>> Therein you find entries like:
>>>>
>>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L82
>>>>
>>>> As you can see, a regshift of 2 is used, which is not yet supported by
>>>> the 16550A RTDM driver. Should not be a big deal to add it, though.
>>>> Also, as "baud_base" you should use OMAP24XX_BASE_BAUD.
>>>>
>>>> Wolfgang.
>>>>
>>>
>>> Thanks for the suggestions. The .config file is attached. I will look at the
>>> code you pointed to today to study the configuration of the serial port.
>>>
>>> Everett
>>>
>>
>> Hi Wolfgang,
>>
>> I looked at the serial.c and function you pointed too. I have can't figure
>> out how to modify it. Could you point me to the right direction to read so
>> I can understand and eventually improve the serial for beagleboard? I thought
>> I could limit the kernel to use only one of the uart (console) by
>> changing function
>>  __init omap_serial_init(void):
>>
>>  void __init omap_serial_init(void)
>> {
>>         int i;
>>
>> //        for (i = 0; i < ARRAY_SIZE(omap_uart); i++)
>> //                omap_serial_init_port(i);
>>       omap_serial_init_port(2);
>> }
>>
>> But the kernel hangs during booting after printing this message:
>>
>> uncompressing Linux... done.
>>
>> I guess it is not that simple to let kernel not to claim the uart0 and uart1.
>
> Yes, unfortunately. I would try to comment out the uarts you want to
> use for rtser in the following struct:
>
> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L562
>
> Maybe the better option is to download setserial from
>
> http://sourceforge.net/projects/setserial/files/setserial/2.17/setserial-2.17.tar.gz/download
>
> and cross-compile it for your target. Then try:
>
> # setserial /dev/ttyS2 uart none
>
> Wolfgang.
>
>

Hi Wolfgang,

Thanks,

I took the easiest way by
opkg install setserial

The setserial got installed into my flash. I then

 # setserial /dev/ttyS0 uart none
Linux has no complain. dmesg | tail doesn't show anything

Finally I did this:
 # setserial /dev/ttyS2 uart none
Linux reports "Can't set serial info: Device or resource busy". The
uart3 is used by console login.
And my console login still works,

I guess I still don't have a clear direction what to do next. What are
needed to make the uart
to work with xenomai? I also want to make SPI to work with xenomai. Is
that even harder to
do?

Everett

Re: [Xenomai-help] problem with serial example

[Wolfgang Grandegger]

On 05/25/2010 03:47 PM, Everett Wang wrote:
> On Mon, May 24, 2010 at 11:45 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>> On 05/24/2010 09:32 AM, Everett Wang wrote:
>>> On Mon, May 24, 2010 at 7:36 AM, Everett Wang <everteq@domain.hid> wrote:
>>>> On Mon, May 24, 2010 at 12:28 AM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>>>> On 05/23/2010 06:19 PM, Everett Wang wrote:
>>>>>> On Sun, May 23, 2010 at 11:46 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>>>>
>>>>>>> There are other possibilities to interact with Linux, e.g. telnet,
>>>>>>> slogin or netcat. But it's always good to have a console.
>>>>>>>
>>>>>> I guess I need a USB to ethernet for these.
>>>>>
>>>>> Yes.
>>>>>
>>>>> ...
>>>>>>> All three uarts are occupied by Linux and you cannot use them as
>>>>>>> rtserial. First you need to release at least one of them. What Linux
>>>>>>> config do you use for your board?
>>>>>>
>>>>>> I didn't do any configuration. Do you mean to config these during kernel
>>>>>> configuration?
>>>>>
>>>>> Can you show us the .config of your kernel?
>>>>>
>>>>> Some more insights:
>>>>>
>>>>> I think the serial ports for the beagle boards are configured in:
>>>>>
>>>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c
>>>>>
>>>>> Therein you find entries like:
>>>>>
>>>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L82
>>>>>
>>>>> As you can see, a regshift of 2 is used, which is not yet supported by
>>>>> the 16550A RTDM driver. Should not be a big deal to add it, though.
>>>>> Also, as "baud_base" you should use OMAP24XX_BASE_BAUD.
>>>>>
>>>>> Wolfgang.
>>>>>
>>>>
>>>> Thanks for the suggestions. The .config file is attached. I will look at the
>>>> code you pointed to today to study the configuration of the serial port.
>>>>
>>>> Everett
>>>>
>>>
>>> Hi Wolfgang,
>>>
>>> I looked at the serial.c and function you pointed too. I have can't figure
>>> out how to modify it. Could you point me to the right direction to read so
>>> I can understand and eventually improve the serial for beagleboard? I thought
>>> I could limit the kernel to use only one of the uart (console) by
>>> changing function
>>>  __init omap_serial_init(void):
>>>
>>>  void __init omap_serial_init(void)
>>> {
>>>         int i;
>>>
>>> //        for (i = 0; i < ARRAY_SIZE(omap_uart); i++)
>>> //                omap_serial_init_port(i);
>>>       omap_serial_init_port(2);
>>> }
>>>
>>> But the kernel hangs during booting after printing this message:
>>>
>>> uncompressing Linux... done.
>>>
>>> I guess it is not that simple to let kernel not to claim the uart0 and uart1.
>>
>> Yes, unfortunately. I would try to comment out the uarts you want to
>> use for rtser in the following struct:
>>
>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L562
>>
>> Maybe the better option is to download setserial from
>>
>> http://sourceforge.net/projects/setserial/files/setserial/2.17/setserial-2.17.tar.gz/download
>>
>> and cross-compile it for your target. Then try:
>>
>> # setserial /dev/ttyS2 uart none
>>
>> Wolfgang.
>>
>>
> 
> Hi Wolfgang,
> 
> Thanks,
> 
> I took the easiest way by
> opkg install setserial
> 
> The setserial got installed into my flash. I then
> 
>  # setserial /dev/ttyS0 uart none
> Linux has no complain. dmesg | tail doesn't show anything
> 
> Finally I did this:
>  # setserial /dev/ttyS2 uart none
> Linux reports "Can't set serial info: Device or resource busy". The
> uart3 is used by console login.
> And my console login still works,
> 
> I guess I still don't have a clear direction what to do next. What are
> needed to make the uart
> to work with xenomai? I also want to make SPI to work with xenomai. Is
> that even harder to
> do?

Next I would try to load the xeno_16550a.ko as described earlier. Then
you need to fix the register access by introducing a proper regshift, at
least. I can't tell if other fixups are necessary but if you are lucky
it will already work. And yes, implementing a RTDM SPI driver is even
harder, unfortunately.

Wolfgang.

Re: [Xenomai-help] problem with serial example

[Everett Wang]

On Wed, May 26, 2010 at 1:38 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
> On 05/25/2010 03:47 PM, Everett Wang wrote:
>> On Mon, May 24, 2010 at 11:45 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>> On 05/24/2010 09:32 AM, Everett Wang wrote:
>>>> On Mon, May 24, 2010 at 7:36 AM, Everett Wang <everteq@domain.hid> wrote:
>>>>> On Mon, May 24, 2010 at 12:28 AM, Wolfgang Grandegger <wg@domain.hid.com> wrote:
>>>>>> On 05/23/2010 06:19 PM, Everett Wang wrote:
>>>>>>> On Sun, May 23, 2010 at 11:46 PM, Wolfgang Grandegger <wg@domain.hidr.com> wrote:
>>>>>>
>>>>>>>> There are other possibilities to interact with Linux, e.g. telnet,
>>>>>>>> slogin or netcat. But it's always good to have a console.
>>>>>>>>
>>>>>>> I guess I need a USB to ethernet for these.
>>>>>>
>>>>>> Yes.
>>>>>>
>>>>>> ...
>>>>>>>> All three uarts are occupied by Linux and you cannot use them as
>>>>>>>> rtserial. First you need to release at least one of them. What Linux
>>>>>>>> config do you use for your board?
>>>>>>>
>>>>>>> I didn't do any configuration. Do you mean to config these during kernel
>>>>>>> configuration?
>>>>>>
>>>>>> Can you show us the .config of your kernel?
>>>>>>
>>>>>> Some more insights:
>>>>>>
>>>>>> I think the serial ports for the beagle boards are configured in:
>>>>>>
>>>>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c
>>>>>>
>>>>>> Therein you find entries like:
>>>>>>
>>>>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L82
>>>>>>
>>>>>> As you can see, a regshift of 2 is used, which is not yet supported by
>>>>>> the 16550A RTDM driver. Should not be a big deal to add it, though.
>>>>>> Also, as "baud_base" you should use OMAP24XX_BASE_BAUD.
>>>>>>
>>>>>> Wolfgang.
>>>>>>
>>>>>
>>>>> Thanks for the suggestions. The .config file is attached. I will look at the
>>>>> code you pointed to today to study the configuration of the serial port.
>>>>>
>>>>> Everett
>>>>>
>>>>
>>>> Hi Wolfgang,
>>>>
>>>> I looked at the serial.c and function you pointed too. I have can't figure
>>>> out how to modify it. Could you point me to the right direction to read so
>>>> I can understand and eventually improve the serial for beagleboard? I thought
>>>> I could limit the kernel to use only one of the uart (console) by
>>>> changing function
>>>>  __init omap_serial_init(void):
>>>>
>>>>  void __init omap_serial_init(void)
>>>> {
>>>>         int i;
>>>>
>>>> //        for (i = 0; i < ARRAY_SIZE(omap_uart); i++)
>>>> //                omap_serial_init_port(i);
>>>>       omap_serial_init_port(2);
>>>> }
>>>>
>>>> But the kernel hangs during booting after printing this message:
>>>>
>>>> uncompressing Linux... done.
>>>>
>>>> I guess it is not that simple to let kernel not to claim the uart0 and uart1.
>>>
>>> Yes, unfortunately. I would try to comment out the uarts you want to
>>> use for rtser in the following struct:
>>>
>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L562
>>>
>>> Maybe the better option is to download setserial from
>>>
>>> http://sourceforge.net/projects/setserial/files/setserial/2.17/setserial-2.17.tar.gz/download
>>>
>>> and cross-compile it for your target. Then try:
>>>
>>> # setserial /dev/ttyS2 uart none
>>>
>>> Wolfgang.
>>>
>>>
>>
>> Hi Wolfgang,
>>
>> Thanks,
>>
>> I took the easiest way by
>> opkg install setserial
>>
>> The setserial got installed into my flash. I then
>>
>>  # setserial /dev/ttyS0 uart none
>> Linux has no complain. dmesg | tail doesn't show anything
>>
>> Finally I did this:
>>  # setserial /dev/ttyS2 uart none
>> Linux reports "Can't set serial info: Device or resource busy". The
>> uart3 is used by console login.
>> And my console login still works,
>>
>> I guess I still don't have a clear direction what to do next. What are
>> needed to make the uart
>> to work with xenomai? I also want to make SPI to work with xenomai. Is
>> that even harder to
>> do?
>
> Next I would try to load the xeno_16550a.ko as described earlier. Then
> you need to fix the register access by introducing a proper regshift, at
> least. I can't tell if other fixups are necessary but if you are lucky
> it will already work. And yes, implementing a RTDM SPI driver is even
> harder, unfortunately.
>
> Wolfgang.
>

Hi Wolfgang,

Thanks for your information. I am still interested in doing work on both
xeno_16550a.ko and RTDM SPI. Could you give me an overview of
what kind of knowledge is required, and where I can find more information
about them? Right now I feel I don't have a clear understanding to
modify the code.

Thanks,

Everett

Re: [Xenomai-help] problem with serial example

[Wolfgang Grandegger]

On 05/27/2010 03:22 AM, Everett Wang wrote:
> On Wed, May 26, 2010 at 1:38 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>> On 05/25/2010 03:47 PM, Everett Wang wrote:
>>> On Mon, May 24, 2010 at 11:45 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>>> On 05/24/2010 09:32 AM, Everett Wang wrote:
>>>>> On Mon, May 24, 2010 at 7:36 AM, Everett Wang <everteq@domain.hid> wrote:
>>>>>> On Mon, May 24, 2010 at 12:28 AM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>>>>>> On 05/23/2010 06:19 PM, Everett Wang wrote:
>>>>>>>> On Sun, May 23, 2010 at 11:46 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
>>>>>>>
>>>>>>>>> There are other possibilities to interact with Linux, e.g. telnet,
>>>>>>>>> slogin or netcat. But it's always good to have a console.
>>>>>>>>>
>>>>>>>> I guess I need a USB to ethernet for these.
>>>>>>>
>>>>>>> Yes.
>>>>>>>
>>>>>>> ...
>>>>>>>>> All three uarts are occupied by Linux and you cannot use them as
>>>>>>>>> rtserial. First you need to release at least one of them. What Linux
>>>>>>>>> config do you use for your board?
>>>>>>>>
>>>>>>>> I didn't do any configuration. Do you mean to config these during kernel
>>>>>>>> configuration?
>>>>>>>
>>>>>>> Can you show us the .config of your kernel?
>>>>>>>
>>>>>>> Some more insights:
>>>>>>>
>>>>>>> I think the serial ports for the beagle boards are configured in:
>>>>>>>
>>>>>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c
>>>>>>>
>>>>>>> Therein you find entries like:
>>>>>>>
>>>>>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L82
>>>>>>>
>>>>>>> As you can see, a regshift of 2 is used, which is not yet supported by
>>>>>>> the 16550A RTDM driver. Should not be a big deal to add it, though.
>>>>>>> Also, as "baud_base" you should use OMAP24XX_BASE_BAUD.
>>>>>>>
>>>>>>> Wolfgang.
>>>>>>>
>>>>>>
>>>>>> Thanks for the suggestions. The .config file is attached. I will look at the
>>>>>> code you pointed to today to study the configuration of the serial port.
>>>>>>
>>>>>> Everett
>>>>>>
>>>>>
>>>>> Hi Wolfgang,
>>>>>
>>>>> I looked at the serial.c and function you pointed too. I have can't figure
>>>>> out how to modify it. Could you point me to the right direction to read so
>>>>> I can understand and eventually improve the serial for beagleboard? I thought
>>>>> I could limit the kernel to use only one of the uart (console) by
>>>>> changing function
>>>>>  __init omap_serial_init(void):
>>>>>
>>>>>  void __init omap_serial_init(void)
>>>>> {
>>>>>         int i;
>>>>>
>>>>> //        for (i = 0; i < ARRAY_SIZE(omap_uart); i++)
>>>>> //                omap_serial_init_port(i);
>>>>>       omap_serial_init_port(2);
>>>>> }
>>>>>
>>>>> But the kernel hangs during booting after printing this message:
>>>>>
>>>>> uncompressing Linux... done.
>>>>>
>>>>> I guess it is not that simple to let kernel not to claim the uart0 and uart1.
>>>>
>>>> Yes, unfortunately. I would try to comment out the uarts you want to
>>>> use for rtser in the following struct:
>>>>
>>>> http://lxr.linux.no/#linux+v2.6.34/arch/arm/mach-omap2/serial.c#L562
>>>>
>>>> Maybe the better option is to download setserial from
>>>>
>>>> http://sourceforge.net/projects/setserial/files/setserial/2.17/setserial-2.17.tar.gz/download
>>>>
>>>> and cross-compile it for your target. Then try:
>>>>
>>>> # setserial /dev/ttyS2 uart none
>>>>
>>>> Wolfgang.
>>>>
>>>>
>>>
>>> Hi Wolfgang,
>>>
>>> Thanks,
>>>
>>> I took the easiest way by
>>> opkg install setserial
>>>
>>> The setserial got installed into my flash. I then
>>>
>>>  # setserial /dev/ttyS0 uart none
>>> Linux has no complain. dmesg | tail doesn't show anything
>>>
>>> Finally I did this:
>>>  # setserial /dev/ttyS2 uart none
>>> Linux reports "Can't set serial info: Device or resource busy". The
>>> uart3 is used by console login.
>>> And my console login still works,
>>>
>>> I guess I still don't have a clear direction what to do next. What are
>>> needed to make the uart
>>> to work with xenomai? I also want to make SPI to work with xenomai. Is
>>> that even harder to
>>> do?
>>
>> Next I would try to load the xeno_16550a.ko as described earlier. Then
>> you need to fix the register access by introducing a proper regshift, at
>> least. I can't tell if other fixups are necessary but if you are lucky
>> it will already work. And yes, implementing a RTDM SPI driver is even
>> harder, unfortunately.
>>
>> Wolfgang.
>>
> 
> Hi Wolfgang,
> 
> Thanks for your information. I am still interested in doing work on both
> xeno_16550a.ko and RTDM SPI. Could you give me an overview of
> what kind of knowledge is required, and where I can find more information
> about them? Right now I feel I don't have a clear understanding to
> modify the code.

I already explained what I would do to get the xeno_16550a.ko working on
your hardware (see above). Concerning a RTDM SPI driver, there has been
some discussion on this topic recently. You can find further information
in t he following thread (see also follow-up mail):

https://mail.gna.org/public/xenomai-help/2010-04/msg00084.html

The doc for the RTDM driver interface is here:

http://www.xenomai.org/documentation/trunk/html/api/index.html

Wolfgang.

[Xenomai-help] problem with xeno_16550A:Fatal Module not found

[zair]

Hi All,
I am new to serial programming.. as i was looking for my error got this 
permalink. I don find xeno_16550A.ko in my lib/modules/<kernel>/kernel/drivers/ 
serial   
How to insert tat module into that.. Am using laptop now for this sserial 
programming. I will be getting my beagle board on monday.. 28th.. so I will be 
using tat for my applcn using xenomai.. pls help me in this regard.. I wud be 
very thankfull...


zair.

Re: [Xenomai-help] problem with xeno_16550A:Fatal Module not found

[Gilles Chanteperdrix]

zair wrote:
> Hi All,

Hi,

as a general rule, please do not reply some random mail even remotely
related when having a new issue.

> I am new to serial programming.. as i was looking for my error got this 
> permalink. 

What permalink?

> I don find xeno_16550A.ko in my lib/modules/<kernel>/kernel/drivers/serial   

Well, did you enable it in the kernel configuration?
If yes, are you sure you enabled it as a module and not built-in the kernel?
If that is not the issue you have, we need more details about your
setup, see:
http://www.xenomai.org/index.php/Request_for_information

> How to insert tat module into that.. 

See:
http://www.xenomai.org/index.php/16550A

> Am using laptop now for this sserial 
> programming. I will be getting my beagle board on monday.. 28th.. so I will be 
> using tat for my applcn using xenomai.. pls help me in this regard..

Your project deadlines are your problem, there is nothing we can do
about it.

-- 
					    Gilles.

Re: [Xenomai-help] problem with xeno_16550A:Fatal Module not found

[Gilles Chanteperdrix]

zaheer sheriff wrote:
> Sir,
>      Sorry I am unaware of that .. ll not do tat mistake in future..

Ok. Since we are at it, there are other rules, please:
- no html
- no top-posting
- no personal mails

>      Yes now i ve included serial in .config file recompiled n configured
> xenomai..
>      Now when i give modprobe xeno_16550A io=0x03f8 irq=4 baud_base=115200
> tx_fifo=16 start_index=0
> its not showing any message immediately $ prompt s comin..
> Now when I use setserial /dev/ttyS0
> its showing UART:none
> I dunno where the problem is.. I don ve serial port RS232 in my laptop dell
> inspiron 1464.
> Is tat a problem... for that i connected usb to serial converter... dunno
> how to make use of the driver xeno_16550A
> pls help me.. I need to know wher the problem could be..

If you want help, please read the links I posted, and do what they tell you.

-- 
                                                                Gilles.