From: Gary Thomas <gary@mlbassoc.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH] wl12xx-firmware: Port wl12xx-firmware recipe
Date: Fri, 05 Oct 2012 15:57:25 -0600 [thread overview]
Message-ID: <506F57C5.7000400@mlbassoc.com> (raw)
In-Reply-To: <6CF2DE49-0D65-4216-B374-805CE3754A17@ti.com>
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.
>
> On Oct 5, 2012, at 2:09 PM, "Enrico" <ebutera@users.berlios.de> wrote:
>
>> On Fri, Oct 5, 2012 at 9:01 PM, Gary Thomas <gary@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@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@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-10-05 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 19:24 [PATCH] wl12xx-firmware: Port wl12xx-firmware recipe Franklin S. Cooper Jr
2012-10-05 19:01 ` Gary Thomas
2012-10-05 19:09 ` Enrico
2012-10-05 19:20 ` Cooper Jr., Franklin
2012-10-05 21:57 ` Gary Thomas [this message]
2012-10-05 22:03 ` Denys Dmytriyenko
2012-10-05 22:09 ` Maupin, Chase
2012-10-05 22:11 ` Cooper Jr., Franklin
2012-10-05 22:14 ` Gary Thomas
2012-10-05 22:08 ` Denys Dmytriyenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=506F57C5.7000400@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=fcooper@ti.com \
--cc=meta-ti@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.