[MinnowBoard] [Help] Communicating with an Arduino Based Autopilot (Minnow 1.0 dora RC1 BSP)

Darren Hart dvhart at linux.intel.com
Thu Apr 10 21:30:16 UTC 2014


Just FYI. I've updated the dora branch with the new meta-data and updated
the kernel to 3.10.35-LTSI. I've pushed and tagged this as
1.0-rc1-dora-10.0.1. This is pending final AB builds, but I don't expect
any changes between rc1 and 1.0 - unless testing here indicates a need.

This includes the CONFIG_USB_ACM module. I'd appreciate a build and test
to confirm this resolves the request.

On 4/9/14, 22:53, "Koen Kooi" <koen at dominion.thruhere.net> wrote:

>Normally the autobuilder will build do a nightly build for 'dora' once
>every week, but with the heartbleed issue there will be multiple builds
>this week.
>
>Op 10 apr. 2014, om 01:52 heeft Darren Hart <dvhart at linux.intel.com> het
>volgende geschreven:
>
>> I expect the meta-minnow/dora branch to be ready by Friday if not
>>earlier. You'll need a response from Koen on the Angstrom ETA and update
>>mechanism. Also depends on which Angstrom image you are running.
>> 
>> You can also build the image yourself using the Angstrom build scripts.
>> 
>> -- 
>> Darren Hart					Open Source Technology Center
>> darren.hart at intel.com				            Intel Corporation
>> 
>> From: Suresh Ratnam <suresh080891 at gmail.com>
>> Reply-To: MinnowBoard Development and Community Discussion
>><elinux-minnowboard at lists.elinux.org>
>> Date: Wednesday, April 9, 2014 at 15:30
>> To: MinnowBoard Development and Community Discussion
>><elinux-minnowboard at lists.elinux.org>
>> Subject: Re: [MinnowBoard] [Help] Communicating with an Arduino Based
>>Autopilot
>> 
>>> Thanks! Can I get an ETA for the update so that I can make decisions
>>>for this project. The communication between the two is the last piece.
>>> Also, how would the update be applied? Is it through opkg upgrade or
>>>do I need to update the kernel?
>>> Once again, I appreciate the help
>>> On Apr 9, 2014 2:34 PM, "Darren Hart" <dvhart at linux.intel.com> wrote:
>>>> I verified that it was missing from the BSP and I have submitted the
>>>>meta
>>>> data to add it to the linux-yocto repository. Once that merges, I'll
>>>> update the meta-minnow/dora branch to include it. At that point, I'll
>>>> likely tag and release minnow/dora and request Koen kick off new
>>>>Angstrom
>>>> builds for dora.
>>>> 
>>>> --
>>>> Darren
>>>> 
>>>> On 4/9/14, 11:26, "selsinork at gmail.com" <selsinork at gmail.com> wrote:
>>>> 
>>>> >No, it has nothing to do with opkg. CONFIG_USB_ACM is the kernel
>>>>config
>>>> >option that's required to have the cdc-acm driver built.
>>>> >
>>>> >Darren can add it in the BSP to make the module available.
>>>> >
>>>> >On 09/04/14 18:45, Suresh Ratnam wrote:
>>>> >> Thanks selsinor. I read up on that and try it later today.
>>>> >> Is it through opkg or are the specific steps?
>>>> >>
>>>> >> On Apr 9, 2014 11:12 AM, <selsinork at gmail.com> wrote:
>>>> >>
>>>> >>> CONFIG_USB_ACM will enable it, but really you probably want to
>>>>enable
>>>> >>>as
>>>> >>> modules drivers for every usb device you can.
>>>> >>>
>>>> >>>
>>>> >>> On 09/04/14 17:16, Darren Hart wrote:
>>>> >>>> This is very likely due to that particular driver not being
>>>>included
>>>> >>>>by
>>>> >>> the
>>>> >>>> BSP. You can verify by determining the specific CONFIG required
>>>>and
>>>> >>>> verifying it is or is not in your kernel config
>>>>(/proc/config.gz). If
>>>> >>>>it
>>>> >>> is,
>>>> >>>> you can verify in the driver source fi the vendor/product ID is
>>>> >>> supported by
>>>> >>>> the driver.
>>>> >>>>
>>>> >>>> I suspect you just need to build the driver. If you find the
>>>>CONFIG is
>>>> >>>> missing, just let me know what it is you want added and I'll
>>>>update
>>>> >>>>the
>>>> >>> BSP.
>>>> >>>> In the mean time, you can install the kernel dev packages and
>>>>build it
>>>> >>>> yourself.
>>>> >>>>
>>>> >>>> We have 3.10-LTSI support in the dora branch of the minnow BSP
>>>>layer
>>>> >>>> currently. I was about to tag it and release it, but let's make
>>>>sure
>>>> >>>>it
>>>> >>> has
>>>> >>>> the support you need first. If not, I'll add it first.
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> _______________________________________________
>>>> >>>> elinux-MinnowBoard mailing list
>>>> >>>> elinux-MinnowBoard at lists.elinux.org
>>>> >>>> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>>>> >>>>
>>>> >>>
>>>> >>> _______________________________________________
>>>> >>> elinux-MinnowBoard mailing list
>>>> >>> elinux-MinnowBoard at lists.elinux.org
>>>> >>> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>>>> >>>
>>>> >>
>>>> >>
>>>> >>
>>>> >> _______________________________________________
>>>> >> elinux-MinnowBoard mailing list
>>>> >> elinux-MinnowBoard at lists.elinux.org
>>>> >> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>>>> >>
>>>> >
>>>> >_______________________________________________
>>>> >elinux-MinnowBoard mailing list
>>>> >elinux-MinnowBoard at lists.elinux.org
>>>> >http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>>>> >
>>>> 
>>>> 
>>>> --
>>>> Darren Hart                                     Open Source
>>>>Technology Center
>>>> darren.hart at intel.com                                       Intel
>>>>Corporation
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> elinux-MinnowBoard mailing list
>>>> elinux-MinnowBoard at lists.elinux.org
>>>> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>>> _______________________________________________ elinux-MinnowBoard
>>>mailing list elinux-MinnowBoard at lists.elinux.org
>>>http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>
>


-- 
Darren Hart					Open Source Technology Center
darren.hart at intel.com				            Intel Corporation





More information about the elinux-MinnowBoard mailing list