On 17 February 2017 at 17:56, Rafał Miłecki <zaj...@gmail.com> wrote:
> On 17 February 2017 at 16:06, Jonas Gorski <jonas.gor...@gmail.com> wrote:
>> On 17 February 2017 at 15:38, Rafał Miłecki <zaj...@gmail.com> wrote:
>>> On 17 February 2017 at 15:14, Jonas Gorski <jonas.gor...@gmail.com> wrote:
>>>> If that isn't enough you could also create a
>>>> KernelPackage/ssb/brcm47xx (see e.g. crypto-misc, which as a x86
>>>> variant, or crypto-sha512 which even has a x86_64 one). With some
>>>> oppropriate overrides.
>>>
>>> This also doesn't help me. I need two variants of b43 package, not one
>>> modified. It's because most mips74k devices can work with b43 with
>>> bcma only. There are only about 2 devices than need modified b43
>>> package with ssb support enabled.
>>> In other words I need exactly something like PROVIDES ;)
>>
>> So you want to build b43 twice for the same subtarget, once with bcma
>> only, and once with ssb support in addtion?
>
> So far I only started playing with this, but yes, that was my initial
> idea. I don't know if I'll implement it yet. Just fun project for now
> :)
Maybe it would make more sense to refactor the ssb and bcma specific
code paths into their own modules, so you wouldn't have a direct
dependency anymore, and instead b43-bcma-glue => { b43, bcma} and
b43-ssb-glue => { b43, ssb }.
Regards
Jonas
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
