Thank you very much, for your information Frank Agius and everybody, I will prove it. Anything I hope more information about it, I will grateful your help,  it has been a great help your answer, I will answer and tell more about it.
 
Greetings ...  Alvaro


> From: gumstix-users-request@lists.sourceforge.net
> Subject: gumstix-users Digest, Vol 45, Issue 59
> To: gumstix-users@lists.sourceforge.net
> Date: Thu, 14 Jan 2010 20:27:42 +0000help
>
> Send gumstix-users mailing list submissions to
> gumstix-users@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
> or, via email, send a message with subject or body 'help' to
> gumstix-users-request@lists.sourceforge.net
>
> You can reach the person managing the list at
> gumstix-users-owner@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gumstix-users digest..."
>
>
> Today's Topics:
>
> 1. Re: Can I use the 40 pin header, PWM outputs and ADCIN inputs
> (Frank Agius)
> 2. Re: Problems building DSPLink (paulhursky)
> 3. Re: Gumstix boot time (Cliff Brake)
> 4. Re: Overo Wifi Speed (titusgroan)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 14 Jan 2010 14:56:07 -0500
> From: Frank Agius <ftagius@yahoo.com>
> Subject: Re: [Gumstix-users] Can I use the 40 pin header, PWM outputs
> and ADCIN inputs
> To: gumstix-users@lists.sourceforge.net
> Message-ID: <hinssm$el1$1@ger.gmane.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Jose Alvaro C. H. wrote:
> >
> > Hello, I am a new user of the gumtsix overo computer on module, now I
> > have a overo fire with tobi. I want to control a servo motors,
> > Can I control a servo motor using a 40 pin header? ?How can I acces or
> > programming this 40 pin header? What is the level signal and frequency
> > output for the PWM and ADCIN? Is it possible? Can anybody help me
> > please? Or where can I to search information for my doubts?
> >
> > Greetins... Alvaro
> >
>
> ADC has a working device driver. The ADC pin values can be read from
> user space via ioctl. See the code in the following for a sample ADC
> test program:
> http://old.nabble.com/Re:-Help-with-Overo-ADC-td24174607.html
>
> The only PWM driver currently available for the OMAP/Overo is suitable
> to drive LED's. To get the frequency (50hz) and pulse width control
> (900us to 2100us) generally needed for servo motors, you'll have to
> write your own kernel driver or write directly to OMAP timer registers.
> You'll also need circuitry to level shift the 1.8v OMAP output levels
> to 5v.
>
> If you want to write to OMAP timer registers, you can do it from user
> space by writing directly to /dev/mem . The utility devmem2 allows for
> easy reading and writing through /dev/mem. I built the devmem2 package
> on my host (bitbake -b devmem2.bb), installed it on my overo with opkg,
> then spent a couple of hours playing with the timer load and timer match
> registers to get the pulse I was looking for. Here is a sample script
> that should enable a 50hz pulse on GPIO147_PWM8 of the 40 pin header:
>
> #!/bin/bash
> # for omap 35xx, setup pwm associated with general purpose timer 8 for
> # a frequency of 50hz, 1500us pulse width, then vary pulse width.
> # On the overo summit board 40 pin
> # header, the output can be observed on pin 29 (GPIO147_PWM8)
> devmem2 0x4903e024 w 0x00000000 # set gtp8_TCLR, stop the timer
> devmem2 0x48002178 w 0x01020102 # set mux for gpt8_pwm_evt
> devmem2 0x4903e02c w 0xfffc08F0 # set value for gpt8_TLDR, timer load
> (20ms period)
> devmem2 0x4903e038 w 0xfffC551c # set value for gpt8_TMAR, timer match
> (1500us pulse width)
> devmem2 0x4903e028 w 0xffffffff # set value for gpt8_TCRR, timercounter
> devmem2 0x4903e024 w 0x00001843 # set gtp8_TCLR, start the timer
> sleep 3
> devmem2 0x4903e038 w 0xfffC36a4 # set value for gpt8_TMAR, timer match
> 900us)
> sleep 3
> devmem2 0x4903e038 w 0xfffC7394 # set value for gpt8_TMAR, timer match
> (2100us)
> sleep 3
> devmem2 0x4903e038 w 0xfffC551c # set value for gpt8_TMAR, timer match
> (1500us)
>
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 14 Jan 2010 12:03:53 -0800 (PST)
> From: paulhursky <paul.hursky@hlsresearch.com>
> Subject: Re: [Gumstix-users] Problems building DSPLink
> To: gumstix-users@lists.sourceforge.net
> Message-ID: <27167276.post@talk.nabble.com>
> Content-Type: text/plain; charset=UTF-8
>
>
> I think I remember reading that bitbake has trouble or causes trouble with
> symbolic links.
> I'm sorry I don't have time to track this down, but if this is the key for
> you, then it is a very easy thing to try to fix.
> For example, a search under bitbake symbolic links turned up:
> http://wiki.openmoko.org/wiki/OpenEmbedded
> http://www.openzipit.org/Z2Develop/
> where they caution that the $OE path not contain any symbolic links.
> Not sure if this applies to the situation you are in...
> Paul
>
>
> Paul Wilson wrote:
> >
> > Greetings fellow list members,
> >
> > Having reached the point where I can successfully build and run my own
> > code on the ARM core in the OMAP on the Gumstix Overo, it is now time to
> > work on getting code to run on the DSP core. Accordingly, I am trying to
> > install DSPLink using the instructions found at
> > http://pixhawk.ethz.ch/wiki/tutorials/omap/dsp_toolchain#omap3_dsp_toolchain
> > but I have run into a problem I have not yet been able to solve. I can
> > run the make successfully (with no errors reported that is) for the DSP
> > side but the make for the ARM (GPP) side fails with several errors that
> > appear to be due to the inability to find the include file stdarg.h
> > referenced in the include file kernel.h. I have included the output from
> > make at the end of this posting.
> >
> > My OE environment was installed as per the instructions found at
> > http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html
> >
> > so it is rooted at $HOME/overo-oe.
> >
> > The one thing in the configuration for the build for the GPP side that
> > has to be configured for the specific environment is the
> > $DSPLINK/make/gpp/omap3530_2.6.mk file. The relevant lines in mine are
> > as follows:
> >
> > #
> > ----------------------------------------------------------------------------
> > # Base directory for the GPP OS
> > #
> > ----------------------------------------------------------------------------
> > BASE_BUILDOS :=
> > ${HOME}/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel
> >
> > #
> > ----------------------------------------------------------------------------
> > # Base for toolchain
> > #
> > ----------------------------------------------------------------------------
> > BASE_TOOLCHAIN := ${HOME}/cross/armv7a
> >
> > To permit the BASE_TOOLCHAIN to find the relevant cross tools, I have
> > placed a symbolic link in $HOME as follows:
> >
> > cross -> /home/Developer/overo-oe/tmp/cross
> >
> > I am not sure if the path I used for BASE_BUILDOS is correct so any
> > knowledgeable comments on that would be appreciated as well as any ideas
> > on what else may need changing to fix the problem.
> >
> > Thanks in advance for any help,
> >
> > Paul Wilson
> >
> >
> > Output from make:
> >
> > [Developer@Gumstix-dev src]$ make -s
> >
> > [SRC ] ======= DIRS ================== INCLUDE ============
> > [ARCH ] ------- DIRS ------------------ INCLUDE ------------
> > [GEN ] ------- DIRS ------------------ INCLUDE ------------
> > [OSAL ] ------- DIRS ------------------ INCLUDE ------------
> > [LDRV ] ------- DIRS ------------------ INCLUDE ------------
> > [PMGR ] ------- DIRS ------------------ INCLUDE ------------
> > [API ] ------- DIRS ------------------ INCLUDE ------------
> >
> > [SRC ] ======= DIRS ================== DEBUG ==============
> > [ARCH ] ------- DIRS ------------------ DEBUG --------------
> > [GEN ] ------- DIRS ------------------ DEBUG --------------
> > [OSAL ] ------- DIRS ------------------ DEBUG --------------
> > [LDRV ] ------- DIRS ------------------ DEBUG --------------
> > [PMGR ] ------- DIRS ------------------ DEBUG --------------
> > [API ] ------- DIRS ------------------ DEBUG --------------
> >
> > [SRC ] ======= DIRS ================== RELEASE ============
> > [ARCH ] ------- DIRS ------------------ RELEASE ------------
> > [GEN ] ------- DIRS ------------------ RELEASE ------------
> > [OSAL ] ------- DIRS ------------------ RELEASE ------------
> > [LDRV ] ------- DIRS ------------------ RELEASE ------------
> > [PMGR ] ------- DIRS ------------------ RELEASE ------------
> > [API ] ------- DIRS ------------------ RELEASE ------------
> >
> > [SRC ] ======= DIRS ================== EXPORT =============
> > [ARCH ] ------- DIRS ------------------ EXPORT -------------
> > [GEN ] ------- DIRS ------------------ EXPORT -------------
> > [OSAL ] ------- DIRS ------------------ EXPORT -------------
> > [LDRV ] ------- DIRS ------------------ EXPORT -------------
> > [PMGR ] ------- DIRS ------------------ EXPORT -------------
> > [API ] ------- DIRS ------------------ EXPORT -------------
> >
> > [SRC ] ======= CLEAN ================= DEBUG ==============
> > [ARCH ] ------- CLEAN ----------------- DEBUG --------------
> > [GEN ] ------- CLEAN ----------------- DEBUG --------------
> > [OSAL ] ------- CLEAN ----------------- DEBUG --------------
> > [LDRV ] ------- CLEAN ----------------- DEBUG --------------
> > [PMGR ] ------- CLEAN ----------------- DEBUG --------------
> > [API ] ------- CLEAN ----------------- DEBUG --------------
> >
> > [SRC ] ======= CLEAN ================= RELEASE ============
> > [ARCH ] ------- CLEAN ----------------- RELEASE ------------
> > [GEN ] ------- CLEAN ----------------- RELEASE ------------
> > [OSAL ] ------- CLEAN ----------------- RELEASE ------------
> > [LDRV ] ------- CLEAN ----------------- RELEASE ------------
> > [PMGR ] ------- CLEAN ----------------- RELEASE ------------
> > [API ] ------- CLEAN ----------------- RELEASE ------------
> >
> > [SRC ] ======= INCLUDES ===================================
> > [ARCH ] ------- INCLUDES -----------------------------------
> > [ARCH ] ------- DIRS ------------------ INCLUDE ------------
> > [GEN ] ------- INCLUDES -----------------------------------
> > [GEN ] ------- DIRS ------------------ INCLUDE ------------
> > [OSAL ] ------- INCLUDES -----------------------------------
> > [OSAL ] ------- DIRS ------------------ INCLUDE ------------
> > [LDRV ] ------- INCLUDES -----------------------------------
> > [LDRV ] ------- DIRS ------------------ INCLUDE ------------
> > [PMGR ] ------- INCLUDES -----------------------------------
> > [PMGR ] ------- DIRS ------------------ INCLUDE ------------
> > [API ] ------- INCLUDES -----------------------------------
> > [API ] ------- DIRS ------------------ INCLUDE ------------
> >
> > [SRC ] ======= BLDINFO =============== DEBUG ==============
> > [ARCH ] ------- DIRS ------------------ DEBUG --------------
> > [ARCH ] ------- BLDINFO --------------- DEBUG --------------
> > [GEN ] ------- DIRS ------------------ DEBUG --------------
> > [GEN ] ------- BLDINFO --------------- DEBUG --------------
> > [OSAL ] ------- DIRS ------------------ DEBUG --------------
> > [OSAL ] ------- BLDINFO --------------- DEBUG --------------
> > [LDRV ] ------- DIRS ------------------ DEBUG --------------
> > [LDRV ] ------- BLDINFO --------------- DEBUG --------------
> > [PMGR ] ------- DIRS ------------------ DEBUG --------------
> > [PMGR ] ------- BLDINFO --------------- DEBUG --------------
> > [API ] ------- DIRS ------------------ DEBUG --------------
> > [API ] ------- BLDINFO --------------- DEBUG --------------
> >
> > [SRC ] ======= BLDINFO =============== RELEASE ============
> > [ARCH ] ------- DIRS ------------------ RELEASE ------------
> > [ARCH ] ------- BLDINFO --------------- RELEASE ------------
> > [GEN ] ------- DIRS ------------------ RELEASE ------------
> > [GEN ] ------- BLDINFO --------------- RELEASE ------------
> > [OSAL ] ------- DIRS ------------------ RELEASE ------------
> > [OSAL ] ------- BLDINFO --------------- RELEASE ------------
> > [LDRV ] ------- DIRS ------------------ RELEASE ------------
> > [LDRV ] ------- BLDINFO --------------- RELEASE ------------
> > [PMGR ] ------- DIRS ------------------ RELEASE ------------
> > [PMGR ] ------- BLDINFO --------------- RELEASE ------------
> > [API ] ------- DIRS ------------------ RELEASE ------------
> > [API ] ------- BLDINFO --------------- RELEASE ------------
> >
> > [SRC ] ======= OBJECTS =============== DEBUG ==============
> > [ARCH ] ------- DIRS ------------------ DEBUG --------------
> > [ARCH ] ------- OBJECT ---------------- DEBUG --------------
> > Compiling CFG_map.c...
> > Compiling dsp.c...
> > Compiling omap3530_phy_shmem.c...
> > In file included from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/cache.h:4,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/time.h:7,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/stat.h:60,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/module.h:10,
> > from OMAP3530/shmem/Linux/omap3530_phy_shmem.c:34:
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:10:20:
> > error: stdarg.h: No such file or directory
> > In file included from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/cache.h:4,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/time.h:7,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/stat.h:60,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/module.h:10,
> > from OMAP3530/shmem/Linux/omap3530_phy_shmem.c:34:
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:180:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:180:
> > warning: conflicting types for built-in function ?vsprintf?
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:184:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:184:
> > warning: conflicting types for built-in function ?vsnprintf?
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:188:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:192:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:196:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:196:
> > warning: conflicting types for built-in function ?vsscanf?
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:236:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:508:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kernel.h:511:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > In file included from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/bitmap.h:8,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/nodemask.h:89,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/mmzone.h:16,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/gfp.h:4,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kmod.h:22,
> > from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/module.h:13,
> > from OMAP3530/shmem/Linux/omap3530_phy_shmem.c:34:
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/string.h:117:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > In file included from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/module.h:16,
> > from OMAP3530/shmem/Linux/omap3530_phy_shmem.c:34:
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/kobject.h:77:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > In file included from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/module.h:18,
> > from OMAP3530/shmem/Linux/omap3530_phy_shmem.c:34:
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/marker.h:34:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > In file included from
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/pci.h:53,
> > from OMAP3530/shmem/Linux/omap3530_phy_shmem.c:37:
> > /home/Developer/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/include/linux/device.h:524:
> > error: expected declaration specifiers or ?...? before ?va_list?
> > OMAP3530/shmem/Linux/omap3530_phy_shmem.c: In function
> > ?OMAP3530_phyShmemInit?:
> > OMAP3530/shmem/Linux/omap3530_phy_shmem.c:131: warning: assignment makes
> > integer from pointer without a cast
> > OMAP3530/shmem/Linux/omap3530_phy_shmem.c:132: warning: assignment makes
> > integer from pointer without a cast
> > OMAP3530/shmem/Linux/omap3530_phy_shmem.c:133: warning: assignment makes
> > integer from pointer without a cast
> > OMAP3530/shmem/Linux/omap3530_phy_shmem.c:134: warning: assignment makes
> > integer from pointer without a cast
> > OMAP3530/shmem/Linux/omap3530_phy_shmem.c:135: warning: assignment makes
> > integer from pointer without a cast
> > OMAP3530/shmem/Linux/omap3530_phy_shmem.c:136: warning: assignment makes
> > integer from pointer without a cast
> > make[2]: *** [OMAP3530/shmem/Linux/omap3530_phy_shmem.c.deb] Error 1
> > make[1]: *** [objdeb] Error 2
> > make: *** [arch.objdeb] Error 2
> > [Developer@Gumstix-dev src]$
> >
> >
> >
> > ------------------------------------------------------------------------------
> > Throughout its 18-year history, RSA Conference consistently attracts the
> > world's best and brightest in the field, creating opportunities for
> > Conference
> > attendees to learn about information security's most important issues
> > through
> > interactions with peers, luminaries and emerging and established
> > companies.
> > http://p.sf.net/sfu/rsaconf-dev2dev
> > _______________________________________________
> > gumstix-users mailing list
> > gumstix-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
> >
> >
>
> --
> View this message in context: http://old.nabble.com/Problems-building-DSPLink-tp27165895p27167276.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 14 Jan 2010 15:09:37 -0500
> From: Cliff Brake <cliff.brake@gmail.com>
> Subject: Re: [Gumstix-users] Gumstix boot time
> To: "General mailing list for gumstix users."
> <gumstix-users@lists.sourceforge.net>
> Message-ID:
> <f96d234e1001141209t4d80dca2j6364da15483e8ac5@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Thu, Jan 14, 2010 at 1:28 PM, Paul J. Perrone
> <pperrone@perronerobotics.com> wrote:
> >
> >
> > I'm looking for a Gumstix combination that has the following:
> > 1) Linux
> > 2) Can run a Java Virtual Machine
>
> 1&2 are doable.
>
> > 3) Can go from cold boot to a running Java application in 3-4 seconds.
>
> Likely impossible, and if possible, will required a very large effort.
>
> > 4) Lacking #3, can reliably go from suspended mode start to a running Java
> > application in 3-4 seconds
>
> should be possible.
>
> Cliff
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 14 Jan 2010 12:27:31 -0800 (PST)
> From: titusgroan <rahul.summan@eee.strath.ac.uk>
> Subject: Re: [Gumstix-users] Overo Wifi Speed
> To: gumstix-users@lists.sourceforge.net
> Message-ID: <27167582.post@talk.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> I would be interested in hearing about any Wi-Fi dongles that work well with
> the Overo
>
> Cheers
>
> Titusgroan
>
>
> Kirk Martinez wrote:
> >
> > yes I'm moving in that direction too - there's something shakey about
> > the onboard wifi at the moment - it doesn't seem stable (at least
> > running console image). We removed avahi and forced a connection and its
> > still not perfect. Its possibly a signal strength behaviour problem.
> >
> > Kirk
> >
> > Jason C. Mecham wrote:
> >> The work around would be to use a USB Wifi dongle.
> >>
> >> -----Original Message-----
> >> From: asufi [mailto:asufi@sarnoff.com]
> >> Sent: Thursday, January 14, 2010 6:00 AM
> >> To: gumstix-users@lists.sourceforge.net
> >> Subject: [Gumstix-users] Overo Wifi Speed
> >>
> >>
> >> Hi
> >>
> >> I am using the overo fire to interface to a camera and send selective
> >> frames
> >> of the video over wifi. However, the wifi speed is unbearably slow! I
> >> read
> >> up on some threads regarding the issue but saw no solutions to the
> >> problem.
> >> Has anyone been able to resolve the speed issue?
> >>
> >> Is there a work around?
> >>
> >> thanks
> >> Azhar
> >>
> >>
> >
> > --
> > Electronics and Computer Science
> > University of Southampton, UK
> > +44 (0)2380 594491
> > http://www.ecs.soton.ac.uk/~km
> >
> > ------------------------------------------------------------------------------
> > Throughout its 18-year history, RSA Conference consistently attracts the
> > world's best and brightest in the field, creating opportunities for
> > Conference
> > attendees to learn about information security's most important issues
> > through
> > interactions with peers, luminaries and emerging and established
> > companies.
> > http://p.sf.net/sfu/rsaconf-dev2dev
> > _______________________________________________
> > gumstix-users mailing list
> > gumstix-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
> >
> >
>
> --
> View this message in context: http://old.nabble.com/Overo-Wifi-Speed-tp27161641p27167582.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
>
> ------------------------------
>
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>
> End of gumstix-users Digest, Vol 45, Issue 59
> *********************************************


Cuida tu aguinaldo y tus cuentas bancarias, OTTO te enseña cómo.