74 replies to this topic

[Erik Slagter]

Littlesat, I am happy with your solution, I was only trying to better explain the problem to Erik. It is not only the sockets swapped because Nim 0 is tuner A and Nim 1 is tuner B. And this is the case on all hardware that uses 7356.

Yes I understand. Swapping the labels on the outside is not the same as messing something up internally in the hardware. Tuner A is really Tuner A.

[Erik Slagter]

 

In that case these users should really use extern loopthrough, issue solved

If only that were true; Solo2 has no LNB-out ports......

So????

 

Never heard of a DC blocking T-connector? It can loop through EVERYTHING.

[Rob van der Does]

 

 

In that case these users should really use extern loopthrough, issue solved

If only that were true; Solo2 has no LNB-out ports......

 

So????
 
Never heard of a DC blocking T-connector? It can loop through EVERYTHING.

 

Indeed, never heard of.
But now that I have: cant imagine how E2 knows that a looped-through input is being used, with limited use (depending on the actual use of the other tuner).

[arn354]

Here:

entry["internally_connectable"] = entry["frontend_device"] - 1

For the 7356 SoC it should be:

entry["internally_connectable"] = entry["frontend_device"] + 1

But that screws the logic behind the compressed tuner names.

 

 

not true. this is vu specific. gb7356 is different and like expected. B (nim1) is internal connectable to A (nim0) and not vice-versa.

Edited by arn354, 7 July 2018 - 09:17.

[WanWizard]

I couldn't imagine that this would be a SoC issue, and not a hardware design issue... You can blame Broadcom for a lot of things, but not for being that stupid.

[Abu Baniaz]

This thread was started after a Gigablue user posted that the scanning options were missing. Tuner A was set to what was attached to it. Tuner B was disabled. "loop through" was not desired/set/involved. Pity he did not post the debug log when asked.

[Huevos]

I couldn't imagine that this would be a SoC issue, and not a hardware design issue... You can blame Broadcom for a lot of things, but not for being that stupid.

So you think it is more likely that at least 3 manufacturers (Gigablue, Technomate, Vu+) made the same error with this SoC?

[ims]

why not ? One steals from the other...

[Huevos]

 

Here:

entry["internally_connectable"] = entry["frontend_device"] - 1

For the 7356 SoC it should be:

entry["internally_connectable"] = entry["frontend_device"] + 1

But that screws the logic behind the compressed tuner names.

 

 

not true. this is vu specific. gb7356 is different and like expected. B (nim1) is internal connectable to A (nim0) and not vice-versa.

 

The somethingConnected() bug showed on a Gigablue. That was the box the bug was first reported on.

 

Are you saying "/proc/stb/frontend/0/rf_switch" does not exist on the Gigablue?

[littlesat]

Yes the first did make the mistake and the others did follow the same mistake.. when they printers a on b and b on a and in the drivers they swap NIM 0 with 1 this whole discussion was not needed... vu was the first and because of silly work a rounds in Some images the other manufacturers might consider to follow the same stupid mistake....

Edited by littlesat, 7 July 2018 - 13:38.

[Huevos]

 

 

 

In that case these users should really use extern loopthrough, issue solved

If only that were true; Solo2 has no LNB-out ports......

 

So????
 
Never heard of a DC blocking T-connector? It can loop through EVERYTHING.

 

Indeed, never heard of.
But now that I have: cant imagine how E2 knows that a looped-through input is being used, with limited use (depending on the actual use of the other tuner).

 

Proper way to do an external loopthrough is a "prioritory switch".

[Abu Baniaz]

Am I correct in assuming that "connected" is used in two contexts. If so, maybe they should be split up?

 

Context 1: Internally connected.

Context 2: Signal wire attached and/or tuner configured.

[Huevos]

The logic in nimmanager is screwed. Look here:

			if "frontend_device" in entry: # check if internally connectable
				if os.path.exists("/proc/stb/frontend/%d/rf_switch" % entry["frontend_device"]) and (not id or entries[id]["name"] == entries[id - 1]["name"]):
					entry["internally_connectable"] = entry["frontend_device"] - 1
				else:
entry["internally_connectable"] = None

Now look at the output from that proc:

root@gbquadplus2:/proc/stb/frontend/0# cat rf_switch
external

[Huevos]

Double post

Edited by Huevos, 7 July 2018 - 14:37.

[Huevos]

 

So the proc tells us the tuner is externally connectable. But nimmanager takes the presence of the file to mean the tuner is internally connectable.