summaryrefslogtreecommitdiff
path: root/drivers/media/test-drivers/vidtv/vidtv_channel.c
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab+huawei@kernel.org>2020-11-23 14:20:45 +0300
committerMauro Carvalho Chehab <mchehab+huawei@kernel.org>2020-11-26 10:05:23 +0300
commit1d2b2a6d8c599be2cbb1e984eeb970186694ef38 (patch)
tree4825906a06ffa1076792d65eeea4794f2228a715 /drivers/media/test-drivers/vidtv/vidtv_channel.c
parentb9e09e06e32e61269342e34f41321499da50d428 (diff)
downloadlinux-1d2b2a6d8c599be2cbb1e984eeb970186694ef38.tar.xz
media: vidtv: fix the network ID range
As defined at ETSI TS 101 162, original network IDs up to 0xfebf are reserved for registration at dvb.org. Let's use, instead, an original network ID at the range 0xff00-0xffff, as this is for private temporary usage. As the same value is also used for the network ID, the range 0xff01-0xffff also fits better, as values lower than that depend if the network is used for satellite, terrestrial, cable of CI. While here, move the TS ID to the bridge code, where it is used, and change its value, as it was identical to the value previously used by network ID. While we could keep the same value, let's change it, just to make easier to check for the new code while reading it with DVB tools like dvbinspector. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Diffstat (limited to 'drivers/media/test-drivers/vidtv/vidtv_channel.c')
0 files changed, 0 insertions, 0 deletions