On 17-05-08 11:30 AM, Florian Fainelli wrote:
On 05/08/2017 11:18 AM, Eric Anholt wrote:
With the Cygnus port, we needed to add at least "|| ARCH_BCM_CYGNUS"
to let the module get built on a cygnus-only kernel. However, I
anticipate having a port for Kona soon, so just present the module on
al
On 05/08/2017 11:18 AM, Eric Anholt wrote:
> With the Cygnus port, we needed to add at least "|| ARCH_BCM_CYGNUS"
> to let the module get built on a cygnus-only kernel. However, I
> anticipate having a port for Kona soon, so just present the module on
> all of BCM.
This seems reasonable, but by r
Florian Fainelli writes:
> On 05/08/2017 11:18 AM, Eric Anholt wrote:
>> With the Cygnus port, we needed to add at least "|| ARCH_BCM_CYGNUS"
>> to let the module get built on a cygnus-only kernel. However, I
>> anticipate having a port for Kona soon, so just present the module on
>> all of BCM.
With the Cygnus port, we needed to add at least "|| ARCH_BCM_CYGNUS"
to let the module get built on a cygnus-only kernel. However, I
anticipate having a port for Kona soon, so just present the module on
all of BCM.
Signed-off-by: Eric Anholt
---
I would be sending this through drm-misc-next, as
