On 10/28/2014 08:58 PM, Kevin Cernekee wrote:
> Some chips, such as BCM6328, only require the former driver. Some
> BCM7xxx STB configurations only require the latter driver. Treat them
> as two separate entities, and update the mach-bcm dependencies to
> reflect the change.
>
> Signed-off-by:
On Tuesday 28 October 2014 20:58:58 Kevin Cernekee wrote:
> Some chips, such as BCM6328, only require the former driver. Some
> BCM7xxx STB configurations only require the latter driver. Treat them
> as two separate entities, and update the mach-bcm dependencies to
> reflect the change.
>
>
On Tuesday 28 October 2014 20:58:58 Kevin Cernekee wrote:
Some chips, such as BCM6328, only require the former driver. Some
BCM7xxx STB configurations only require the latter driver. Treat them
as two separate entities, and update the mach-bcm dependencies to
reflect the change.
On 10/28/2014 08:58 PM, Kevin Cernekee wrote:
Some chips, such as BCM6328, only require the former driver. Some
BCM7xxx STB configurations only require the latter driver. Treat them
as two separate entities, and update the mach-bcm dependencies to
reflect the change.
Signed-off-by: Kevin
Some chips, such as BCM6328, only require the former driver. Some
BCM7xxx STB configurations only require the latter driver. Treat them
as two separate entities, and update the mach-bcm dependencies to
reflect the change.
Signed-off-by: Kevin Cernekee
---
arch/arm/mach-bcm/Kconfig| 1
Some chips, such as BCM6328, only require the former driver. Some
BCM7xxx STB configurations only require the latter driver. Treat them
as two separate entities, and update the mach-bcm dependencies to
reflect the change.
Signed-off-by: Kevin Cernekee cerne...@gmail.com
---
6 matches
Mail list logo