[meta-ti] [PATCH] wl12xx-firmware: Port wl12xx-firmware recipe

Gary Thomas gary at mlbassoc.com
Fri Oct 5 15:14:11 PDT 2012

On 2012-10-05 16:09, Maupin, Chase wrote:
>> -----Original Message-----
>> From: meta-ti-bounces at yoctoproject.org [mailto:meta-ti-
>> bounces at yoctoproject.org] On Behalf Of Dmytriyenko, Denys
>> Sent: Friday, October 05, 2012 5:04 PM
>> To: Gary Thomas
>> Cc: meta-ti at yoctoproject.org
>> Subject: Re: [meta-ti] [PATCH] wl12xx-firmware: Port wl12xx-
>> firmware recipe
>> On Fri, Oct 05, 2012 at 03:57:25PM -0600, Gary Thomas wrote:
>>> On 2012-10-05 13:20, Cooper Jr., Franklin wrote:
>>>> The custom git tree is wl12xx only not all the different
>> components that linux-firmware provides. My understanding is that
>> the team that works on wl12xx should be pushing it back to linux-
>> firmware. But like I said this will contain the latest changes.
>>> I still don't think it should be separate.  If the upstream
>> (TI) stuff
>>> isn't being properly tracked (there should be an effort to make
>> this so),
>>> just add a .bbappend that fixes things.  I use these packages
>> and I don't
>>> want to have to track the "flavour of the week" to keep
>> current.
>> That would require extracting individual commits from the git
>> tree and listing
>> them in .bbappend. I would not personally mind that approach, but
>> it may
>> require extra work for the wireless team. We need to check with
>> them...
> Couldn't you use the bbappend to just change the SRC_URI and SRCREV?  Is the issue the recipe name changing from linux-firmware to wl12xx-firmware?
> Wireless team went with their own recipe because of the issues with tracking/maintaining the patch set from their development team.  I know this may not make sense outside of TI but there is a development team in wireless making and pushing changes to mainline and then there is the integration team responsible for providing the validated code drop.  I'm not saying this is a good work flow, but the integration team pushed to get a single repo of the proper sources from the development team because the patch set was un-wieldy.
> That's just a little context of what I know about how these recipes were created.  So again my question is what is the particular pain point you want to avoid?  The name of the recipe or something else?

My biggest concern was that currently my images use 'linux-firmware-wl12xx'
and now, for the same but updated functionality, I need to use 'wl12xx-firmware'
instead.  What will it be next week?  wl12xx-I-like-Maui-better??

Get my point?

>>>> On Oct 5, 2012, at 2:09 PM, "Enrico"
>> <ebutera at users.berlios.de> wrote:
>>>>> On Fri, Oct 5, 2012 at 9:01 PM, Gary Thomas
>> <gary at mlbassoc.com> wrote:
>>>>>> On 2012-10-05 13:24, Franklin S. Cooper Jr wrote:
>>>>>>> * Port wl12xx-firmware recipe from arago. This recipe was
>> originally
>>>>>>>    named linux-firmware in arago.
>>>>>>> * Wl12xx-firmware provides the firmware files for use with
>> the TI
>>>>>>>    Wi-Fi + Bluetooth module.
>>>>>>> Signed-off-by: Franklin S. Cooper Jr <fcooper at ti.com>
>>>>>> Why not just keep the main linux-firmware recipe up to date
>> instead of
>>>>>> duplicate
>>>>>> functionality?
>>>>> I made myself the same question at first, but the answer was
>> there:
>>>>>>> +# This recipe provides the latest firmware files for
>> wl12xx.
>>>>>>> +# Therefore, use the contents of this recipe instead of
>> the contents
>>>>>>> +# of linux-firmware-wl12xx.
>>>>>>> +SRC_URI = "git://github.com/TI-ECS/ti-
>> utils.git;protocol=git"
>>>>> Well one could ask why they are there and not in linux-
>> firmware git
>>>>> (not polemic, just curious).
>>>>> Enrico
>>>>> _______________________________________________
>>>>> meta-ti mailing list
>>>>> meta-ti at yoctoproject.org
>>>>> https://lists.yoctoproject.org/listinfo/meta-ti
>>> --
>>> ------------------------------------------------------------
>>> Gary Thomas                 |  Consulting for the
>>> MLB Associates              |    Embedded world
>>> ------------------------------------------------------------
>>> _______________________________________________
>>> meta-ti mailing list
>>> meta-ti at yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/meta-ti
>> _______________________________________________
>> meta-ti mailing list
>> meta-ti at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti

Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world

More information about the meta-ti mailing list