aboutsummaryrefslogtreecommitdiffstats
path: root/isdb-t/br-ba-VitoriaDaConquista
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--isdb-t/br-ba-VitoriaDaConquista16
1 files changed, 8 insertions, 8 deletions
diff --git a/isdb-t/br-ba-VitoriaDaConquista b/isdb-t/br-ba-VitoriaDaConquista
index d446a284..dc9f8917 100644
--- a/isdb-t/br-ba-VitoriaDaConquista
+++ b/isdb-t/br-ba-VitoriaDaConquista
@@ -1,5 +1,5 @@
-# Channel table for Vitória Da Conquista - BA - Brazil
-# Source: http://www.portalbsd.com.br/tvterrestre/cidade/605
+# Channel table for Vitória Da Conquista - BA - Brazil
+# Source: https://portalbsd.com.br/terrestres_channels.php?cidade=605
# Physical channel 22 (virtual 10.1)
[Record TV Cabrália]
@@ -88,8 +88,8 @@
ISDBT_LAYERC_SEGMENT_COUNT = 0
ISDBT_LAYERC_TIME_INTERLEAVING = 0
-# Physical channel 33 (virtual 4.1)
-[TV UESB]
+# Physical channel 33 (virtual 4.2)
+[TV UESB, Educa Bahia]
DELIVERY_SYSTEM = ISDBT
BANDWIDTH_HZ = 6000000
FREQUENCY = 587142857
@@ -118,7 +118,7 @@
ISDBT_LAYERC_TIME_INTERLEAVING = 0
# Physical channel 34 (virtual 35.1)
-[RCI]
+[TV Pai Eterno]
DELIVERY_SYSTEM = ISDBT
BANDWIDTH_HZ = 6000000
FREQUENCY = 593142857
@@ -204,8 +204,8 @@
ISDBT_LAYERC_SEGMENT_COUNT = 0
ISDBT_LAYERC_TIME_INTERLEAVING = 0
-# Physical channel 43 (virtual 14.1)
-[Rede Vida]
+# Physical channel 43 (virtual 43.3)
+[Rede Vida, Rede Vida Educação]
DELIVERY_SYSTEM = ISDBT
BANDWIDTH_HZ = 6000000
FREQUENCY = 647142857
@@ -262,7 +262,7 @@
ISDBT_LAYERC_SEGMENT_COUNT = 0
ISDBT_LAYERC_TIME_INTERLEAVING = 0
-# Physical channel 49 (virtual 49.1)
+# Physical channel 49 (virtual 19.1)
[RIT]
DELIVERY_SYSTEM = ISDBT
BANDWIDTH_HZ = 6000000
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-25 13:36:17 +0000
/ .highlight .sa { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Affix */ .highlight .sb { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Backtick */ .highlight .sc { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Char */ .highlight .dl { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Delimiter */ .highlight .sd { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Doc */ .highlight .s2 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Double */ .highlight .se { color: #0044dd; background-color: #fff0f0 } /* Literal.String.Escape */ .highlight .sh { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Heredoc */ .highlight .si { color: #3333bb; background-color: #fff0f0 } /* Literal.String.Interpol */ .highlight .sx { color: #22bb22; background-color: #f0fff0 } /* Literal.String.Other */ .highlight .sr { color: #008800; background-color: #fff0ff } /* Literal.String.Regex */ .highlight .s1 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Single */ .highlight .ss { color: #aa6600; background-color: #fff0f0 } /* Literal.String.Symbol */ .highlight .bp { color: #003388 } /* Name.Builtin.Pseudo */ .highlight .fm { color: #0066bb; font-weight: bold } /* Name.Function.Magic */ .highlight .vc { color: #336699 } /* Name.Variable.Class */ .highlight .vg { color: #dd7700 } /* Name.Variable.Global */ .highlight .vi { color: #3333bb } /* Name.Variable.Instance */ .highlight .vm { color: #336699 } /* Name.Variable.Magic */ .highlight .il { color: #0000DD; font-weight: bold } /* Literal.Number.Integer.Long */
#
# $Id: README.Drivers,v 1.4 2001/03/09 13:08:11 ltoetsch Exp $
#

How to write new display drivers for lcd4linux

If you plan to write a new display driver for lcd4linux, you should follow
this guidelines:

* use Skeleton.c as a start point.
  You might also have a look at Text.c

* create a new sourcefile <drivername>.c and add it to the bottom of
  Makefile.am

* add an entry to configure.in

* there's no need for a <drivername>.h

* create one (or more) unique display names (your driver will be selected by
  this name in the 'Display'-line of lcd4linux.conf).

* include "display.h" in your driver, to get the LCD structure and various 
  BAR_ definitions

* include "cfg.h" if you need to access settings in the config file.

* create a LCD table at the bottom of your driver, and fill it with the
  appropriate values. Take care that you specify the correct bar capabilities
  of your display or driver:

  BAR_L:  horizontal bars headed left
  BAR_R:  horizontal bars headed right
  BAR_H2: driver supports horizontal dual-bars
  BAR_U:  vertical bars bottom-up
  BAR_D:  vertical bars top-down
  BAR_V2: driver supports vertical dual-bars

* edit display.c and create a reference to your LCD table:

     external LCD YourDriver[];

* extend the FAMILY table in display.c with your driver:

     FAMILY Driver[] = {
       { "Skeleton",      Skeleton },
       { "MatrixOrbital", MatrixOrbital },
       { "YourFamily",    YourDriver },
       { "" }
     };

* write the correspondig init(), clear(), put(), bar(), quit() and
  flush()-functions. There's no need to use a framebuffer and display its
  contents with the flush()- call (as in MatrixOrbital.c), you can directly
  write to the display in the put()- and bar()-functions, and use an empty
  flush()-function. But if you have a limited number of user-defined
  characters, and therefore you have to do some sort of 'character reduction'
  or similar stuff, you will have to use a framebuffer and the flush()-call.
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-25 13:36:17 +0000