Jump to content


Photo

One proc file for detecting the MACHINE in all enigma2 images.


  • Please log in to reply
772 replies to this topic

Re: One proc file for detecting the MACHINE in all enigma2 images. #581 littlesat

  • PLi® Core member
  • 57,064 posts

+698
Excellent

Posted 14 December 2020 - 08:52

Just a suggestion... put the complete 'new' stuff to the already existing proc folder /proc/stb/info.... it already exists... but can now get 'more info'... So just extend the existing - not create/hack a new one, where we somehow 'never' can agree a good name for (as there is already a folder for it why create a different?)

+

For multi-boot it would be fine to have a file in /etc that gives and image description (short) in the first row and an extended in the following rows.


Edited by littlesat, 14 December 2020 - 08:58.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: One proc file for detecting the MACHINE in all enigma2 images. #582 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 14 December 2020 - 09:42

Hi Littlesat,

 

Just a suggestion... put the complete 'new' stuff to the already existing proc folder /proc/stb/info.... it already exists... but can now get 'more info'... So just extend the existing - not create/hack a new one, where we somehow 'never' can agree a good name for (as there is already a folder for it why create a different?)

+

For multi-boot it would be fine to have a file in /etc that gives and image description (short) in the first row and an extended in the following rows.

 

You have just brought this thread back to the start.  This was suggested in the first place as the "simple" option.  It was rejected because the settings were mutable.  You are now proposing two different sources for the information.  This was also rejected as problematic.  This looping back over already rejected ideas is just wasting time and distracting everyone from making real progress.

 

If you want a simple text file as a single source of the information then I am okay with that concept.  Others were not.  Do people want to revisit a single text file as the repository of all this information?

 

Regards,

Ian.



Re: One proc file for detecting the MACHINE in all enigma2 images. #583 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 14 December 2020 - 12:19

Just a suggestion... put the complete 'new' stuff to the already existing proc folder /proc/stb/info.... it already exists... but can now get 'more info'... So just extend the existing - not create/hack a new one, where we somehow 'never' can agree a good name for (as there is already a folder for it why create a different?)

+

For multi-boot it would be fine to have a file in /etc that gives and image description (short) in the first row and an extended in the following rows.

 

Try it yourself, try it on Zgemma HiSilicon for example and you'll understand the problems.

 

We should avoid existing folders and to be more specific we should avoid existing folders created by main STB drivers.


Open Vision sources: https://github.com/OpenVisionE2


Re: One proc file for detecting the MACHINE in all enigma2 images. #584 littlesat

  • PLi® Core member
  • 57,064 posts

+698
Excellent

Posted 14 December 2020 - 13:02

Procs are not mutable...
The multiboot solution are.... but that has somehow added value as a user can change a description....

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: One proc file for detecting the MACHINE in all enigma2 images. #585 Huevos

  • PLi® Contributor
  • 4,622 posts

+161
Excellent

Posted 14 December 2020 - 14:14

Procs are not mutable...
The multiboot solution are.... but that has somehow added value as a user can change a description....

The user can't change the output of the procs or modinfo. That would require a rebuild.



Re: One proc file for detecting the MACHINE in all enigma2 images. #586 Huevos

  • PLi® Contributor
  • 4,622 posts

+161
Excellent

Posted 14 December 2020 - 14:17

Hi Littlesat,

 

Just a suggestion... put the complete 'new' stuff to the already existing proc folder /proc/stb/info.... it already exists... but can now get 'more info'... So just extend the existing - not create/hack a new one, where we somehow 'never' can agree a good name for (as there is already a folder for it why create a different?)

+

For multi-boot it would be fine to have a file in /etc that gives and image description (short) in the first row and an extended in the following rows.

 

You have just brought this thread back to the start.  This was suggested in the first place as the "simple" option.  It was rejected because the settings were mutable.  You are now proposing two different sources for the information.  This was also rejected as problematic.  This looping back over already rejected ideas is just wasting time and distracting everyone from making real progress.

 

If you want a simple text file as a single source of the information then I am okay with that concept.  Others were not.  Do people want to revisit a single text file as the repository of all this information?

 

Regards,

Ian.

No... we already have an immutable, it's called box branding. Why would we ever consider flat files? How would that be a forwards step compared to what we have used for 10 years.



Re: One proc file for detecting the MACHINE in all enigma2 images. #587 Huevos

  • PLi® Contributor
  • 4,622 posts

+161
Excellent

Posted 14 December 2020 - 14:25

Just a suggestion... put the complete 'new' stuff to the already existing proc folder /proc/stb/info.... it already exists... but can now get 'more info'... So just extend the existing - not create/hack a new one, where we somehow 'never' can agree a good name for (as there is already a folder for it why create a different?)

+

For multi-boot it would be fine to have a file in /etc that gives and image description (short) in the first row and an extended in the following rows.

To me this looks like a good idea. i.e.

 

/proc/stb/boxtype

/proc/stb/machine

/proc/stb/machinebuild

/proc/stb/hdmiin

/proc/stb/wol

etc



Re: One proc file for detecting the MACHINE in all enigma2 images. #588 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 14 December 2020 - 14:31

Hello Huevos,

 

 

No... we already have an immutable, it's called box branding. Why would we ever consider flat files? How would that be a forwards step compared to what we have used for 10 years.

 

 

That is not a global solution and it has already been rejected by OpenPLi.  There are also issues with boxbranding that don't make it a better solution over Persian Prince's proposal.  Why keep pushing the boxbranding agenda?

 

Regards,

Ian.



Re: One proc file for detecting the MACHINE in all enigma2 images. #589 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 14 December 2020 - 14:32

Hello Huevos,

 

 

Just a suggestion... put the complete 'new' stuff to the already existing proc folder /proc/stb/info.... it already exists... but can now get 'more info'... So just extend the existing - not create/hack a new one, where we somehow 'never' can agree a good name for (as there is already a folder for it why create a different?)

+

For multi-boot it would be fine to have a file in /etc that gives and image description (short) in the first row and an extended in the following rows.

To me this looks like a good idea. i.e.

 

/proc/stb/boxtype

/proc/stb/machine

/proc/stb/machinebuild

/proc/stb/hdmiin

/proc/stb/wol

etc

 

It was mentioned that entries in this tree *might* clash with entries provided by manufacturers.  I am told that the entries created by manufacturers are not always correct or reliable.  I think it is better to stay clear of directories used by others.

 

Regards,

Ian.



Re: One proc file for detecting the MACHINE in all enigma2 images. #590 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 14 December 2020 - 14:38

 

Just a suggestion... put the complete 'new' stuff to the already existing proc folder /proc/stb/info.... it already exists... but can now get 'more info'... So just extend the existing - not create/hack a new one, where we somehow 'never' can agree a good name for (as there is already a folder for it why create a different?)

+

For multi-boot it would be fine to have a file in /etc that gives and image description (short) in the first row and an extended in the following rows.

To me this looks like a good idea. i.e.

 

/proc/stb/boxtype

/proc/stb/machine

/proc/stb/machinebuild

/proc/stb/hdmiin

/proc/stb/wol

etc

 

As I said we should avoid existing folders and to be more specific we should avoid existing folders created by main STB drivers.

 

You could check what will happen on Zgemma HiSilicon for example.


Open Vision sources: https://github.com/OpenVisionE2


Re: One proc file for detecting the MACHINE in all enigma2 images. #591 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 14 December 2020 - 17:10

compiledate proc added: https://github.com/O...6f45ad4bdacadfb

 

This will give us a static date time, as the module compiles each time image gets compiled it's the correct date for image compile date.

 

And I'm sad to see all you care in your fork is NAMES and names all the time: https://github.com/H...c5545c58d934a95

 

And how OE-A is the "PKG_MAINTAINER" only GOD knows.


Open Vision sources: https://github.com/OpenVisionE2


Re: One proc file for detecting the MACHINE in all enigma2 images. #592 Huevos

  • PLi® Contributor
  • 4,622 posts

+161
Excellent

Posted 14 December 2020 - 18:43

Anything I do in my fork is not relevant outside my own build.

If you don't want to use /proc/stb can we please use /proc/hardware and /proc/firmware.

Re: One proc file for detecting the MACHINE in all enigma2 images. #593 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 14 December 2020 - 19:02

Anything I do in my fork is not relevant outside my own build.

If you don't want to use /proc/stb can we please use /proc/hardware and /proc/firmware.

 

We should not use existing folders in /proc so "stb" is out of the list, are "firmware" and "hardware" empty and available in all drivers?

 

Those are suspicious words so we should care.

 

I think /proc/enigma is fine although it's not general and we may use the proc files in other programs like Kodi later but we're enigma2 developers so the kernel is the reflection of our work.


Open Vision sources: https://github.com/OpenVisionE2


Re: One proc file for detecting the MACHINE in all enigma2 images. #594 Huevos

  • PLi® Contributor
  • 4,622 posts

+161
Excellent

Posted 14 December 2020 - 19:05

BTW, I didn't realise this project was only for non-oe-alliance teams. So no point me continuing with it further.

Re: One proc file for detecting the MACHINE in all enigma2 images. #595 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 14 December 2020 - 19:42

BTW, I didn't realise this project was only for non-oe-alliance teams. So no point me continuing with it further.

 

Who said that? But do you see any OE-A team here except ViX? Why I should I care about any other OE-A team when they don't care about this matter at all?

 

And please save the lecture that they're monitoring this topic which is a joke to me.

 

We respect ViX devs as they're great, supportive, cooperative and friendly so it's for you all not just non-oe-a teams.

 

Final API is not even out and this is a prototype that's all.


Open Vision sources: https://github.com/OpenVisionE2


Re: One proc file for detecting the MACHINE in all enigma2 images. #596 littlesat

  • PLi® Core member
  • 57,064 posts

+698
Excellent

Posted 14 December 2020 - 19:57

To me this looks like a good idea. i.e.

/proc/stb/boxtype
/proc/stb/machine
/proc/stb/machinebuild
/proc/stb/hdmiin
/proc/stb/wol

Nope please all in /proc/stb/info

Edited by littlesat, 14 December 2020 - 19:59.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: One proc file for detecting the MACHINE in all enigma2 images. #597 WanWizard

  • PLi® Core member
  • 70,235 posts

+1,798
Excellent

Posted 14 December 2020 - 20:12

You also need to be careful with module loading order, what happens if /proc/stb doesn't exist because the box drivers haven't been loaded yet (takes 30s on a VU+ 4K box)...

 

I still think it is a very bad idea to re-use an existing proc node. Like PP wrote, we have to make sure it is unique, and available on every box.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: One proc file for detecting the MACHINE in all enigma2 images. #598 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 14 December 2020 - 20:13

To me this looks like a good idea. i.e.

/proc/stb/boxtype
/proc/stb/machine
/proc/stb/machinebuild
/proc/stb/hdmiin
/proc/stb/wol

Nope please all in /proc/stb/info

 

Why don't you test it yourself?

 

Fork and change it to what you need then install it on ARM HiSilicon Zgemma and similars.

 

We tested that before so we won't go for it again.


Open Vision sources: https://github.com/OpenVisionE2


Re: One proc file for detecting the MACHINE in all enigma2 images. #599 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 14 December 2020 - 20:14

You also need to be careful with module loading order, what happens if /proc/stb doesn't exist because the box drivers haven't been loaded yet (takes 30s on a VU+ 4K box)...

 

I still think it is a very bad idea to re-use an existing proc node. Like PP wrote, we have to make sure it is unique, and available on every box.

 

That's what I'm trying to say, no matter what order you use the result is not good.


Open Vision sources: https://github.com/OpenVisionE2


Re: One proc file for detecting the MACHINE in all enigma2 images. #600 Huevos

  • PLi® Contributor
  • 4,622 posts

+161
Excellent

Posted 14 December 2020 - 22:36

You also need to be careful with module loading order, what happens if /proc/stb doesn't exist because the box drivers haven't been loaded yet (takes 30s on a VU+ 4K box)...

 

I still think it is a very bad idea to re-use an existing proc node. Like PP wrote, we have to make sure it is unique, and available on every box.

Are you saying the kernel is not fully running when enigma loads?




9 user(s) are reading this topic

0 members, 9 guests, 0 anonymous users