<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>

   jafa: in DVB-T2 mode both the mn88472 and 88473 drivers uses the equation you linked to and produce similar results, however the resulting number seems too low (perfect error-free reception for qam256 but it is only reporting 19dB CNR)
   xdarklight: I must admit that I was only able to test it on DVB-C and DVB-T(1) - the latter one only with bad reception
   jafa: I plan to compare T CNR numbers with other hardware that is arriving next week
   xdarklight: that would be great
   <br> although I know that some people in here have a hardware signal generator - that would make things easier ;)
   jafa: sure would
   <br> need a way to verify the CNR numbers for T2
   xdarklight: I also have no idea if my BER / PER implementations are using the DVBv5 API correctly
   <br> and signal strength seems to be "too low", but that's only what I could compare against em28xx with drxk
   ***: kaspter has quit IRC (Ping timeout: 245 seconds)
   <br> amarsh04 has quit IRC (Quit: Konversation terminated!)
   <br> aknv75 has quit IRC (Remote host closed the connection)
   <br> mchehab has quit IRC (Ping timeout: 268 seconds)
   <br> XSoul has quit IRC (Ping timeout: 260 seconds)