diff options
| author | Mauro Carvalho Chehab <mchehab@redhat.com> | 2012-05-25 07:47:07 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2012-05-25 07:47:07 -0300 |
| commit | 75b5e4d6a9b32c230cb3970587bd4a7d5337576d (patch) | |
| tree | 2d1263ce923144e0dd01246b62f03acd670aff2a /scripts | |
| parent | 7ca50c90e9915a6115cc20e375f733ec5db333db (diff) | |
| download | kernel-75b5e4d6a9b32c230cb3970587bd4a7d5337576d.tar.gz kernel-75b5e4d6a9b32c230cb3970587bd4a7d5337576d.tar.xz kernel-75b5e4d6a9b32c230cb3970587bd4a7d5337576d.zip | |
Don't customise tuners or frontends
The option to customise tuners/frontends are there to allow
embedded systems or advanced users that compile their own
kernels to disable I2C modules that aren't used by their
specific device. When those options are not selected, the
building system will automatically select the modules that
are needed by each DVB device.
The end result is that dummy frontends used only for testing,
like DVB_DUMMY_FE won't be selected.
Also, when newer frontends are added (and they're added all
the times), the new ones will automatically be selected, if
the bridge drivers that support them are selected.
This also makes the configuration simpler to understand.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions