On Thu, Aug 11, 2011 at 2:21 AM, DUBOST Brice <dubost@xxxxxxxxxxxxxxxxxxx> wrote: > Hello > > I'm the upstream author of MuMuDVB (http://mumudvb.braice.net) > > The diseqc related code is here > http://gitweb.braice.net/gitweb?p=mumudvb;a=blob;f=src/tune.c > > On the document > > http://www.eutelsat.com/satellites/pdf/Diseqc/associated%20docs/applic_info_LNB_switchers.pdf > > Page 7 (page 10 of the PDF) the band is the LSB and the table > is organized in increasing binary data > > But in > http://www.eutelsat.com/satellites/pdf/Diseqc/associated%20docs/update_recomm_for_implim.pdf > > page 33 (35 in the PDF) > > The LSB SEEMS to be the polarization, but it's still the band, the table > is just organized in a strange way > > If you look deeply into the code of scan > http://www.linuxtv.org/hg/dvb-apps/file/36a084aace47/util/scan/diseqc.c > > You'll see that the table is organized as in the second document and the > code addresses the table for making the message but there is no mistake > in the real data since it's f0,f2,f1 etc ... > > So the difference is if the diseqc data is wrote directly (as in > MuMuDVB) or taken from a table organised as in the specification (as in > scan) > > Hope it's clear and it helps > > Regards > > -- > Brice > Thanks for the response. It really helped :) -- Nima Mohammadi -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
