Jump to content


Photo

Bootlogo


  • Please log in to reply
256 replies to this topic

Re: Bootlogo #41 johnny0705

  • Senior Member
  • 206 posts

0
Neutral

Posted 28 September 2013 - 09:08

With the new showiframe the boot logo is back.

Gr. Jan

 

ET-10000 + VU+ Solo2 OpenPLI 4

 


Re: Bootlogo #42 ims

  • PLi® Core member
  • 11,196 posts

+168
Excellent

Posted 28 September 2013 - 09:29

@pieterg - it is  .c without 1), 2) and without write_all  ( = original dmm's  ... it is under GPL2)


Kdo nic nedělá, nic nezkazí!

Re: Bootlogo #43 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 28 September 2013 - 10:43

I will not revert the write_all wrapper, it's harmless (and good practise to restart interrupted syscalls)

Re: Bootlogo #44 ims

  • PLi® Core member
  • 11,196 posts

+168
Excellent

Posted 28 September 2013 - 11:50

I do not talking about removing. I wrote, what version works under dm8000 too.  => for DM8000 is problem 1) or 2)


Kdo nic nedělá, nic nezkazí!

Re: Bootlogo #45 ims

  • PLi® Core member
  • 11,196 posts

+168
Excellent

Posted 29 September 2013 - 15:41

Hello, after update from today there is no boot logo anymore on DM8000.

but there cannot be pieter's revert yet, because building for dmm's machines is last 27.9. It stopped due conflict patch in dvbmediasink (dmm added support for ac3+ - new drivers,gst-plugin-dreambox-dvbmediasink... )


Kdo nic nedělá, nic nezkazí!

Re: Bootlogo #46 johnny0705

  • Senior Member
  • 206 posts

0
Neutral

Posted 29 September 2013 - 15:59

As i wrote earlier with use of your file it works again, thanks.

Gr. Jan

 

ET-10000 + VU+ Solo2 OpenPLI 4

 


Re: Bootlogo #47 cinnabar

  • Member
  • 5 posts

+2
Neutral

Posted 29 September 2013 - 17:28

Here is a bootlogo, homage to Grand Theft Auto 5. Enjoy.

 

Attached Files



Re: Bootlogo #48 daimon

  • Senior Member
  • 196 posts

+5
Neutral

Posted 29 September 2013 - 21:07

thanks. :)



Re: Bootlogo #49 daimon

  • Senior Member
  • 196 posts

+5
Neutral

Posted 30 September 2013 - 12:38

flash with today's bootlogo on the 7020HD does not work



Re: Bootlogo #50 hemertje

  • Forum Moderator
    PLi® Core member
  • 33,000 posts

+116
Excellent

Posted 30 September 2013 - 12:59

explain: "does not work"


on the Glassfibre 1GB DVB-C...


Re: Bootlogo #51 daimon

  • Senior Member
  • 196 posts

+5
Neutral

Posted 30 September 2013 - 14:23

you only see the initial image then all the load time black screen when you restart enigma black screen



Re: Bootlogo #52 ims

  • PLi® Core member
  • 11,196 posts

+168
Excellent

Posted 30 September 2013 - 14:31

yes, last revert does not work, there is problem in 1) or 2) .

I will investigate, if problem is 1) or 2) , but I will home at 18:00


Kdo nic nedělá, nic nezkazí!

Re: Bootlogo #53 Beeker

  • Senior Member
  • 849 posts

+135
Excellent

Posted 30 September 2013 - 17:02

yes, last revert does not work, there is problem in 1) or 2) .

I will investigate, if problem is 1) or 2) , but I will home at 18:00

 

 I try showiframe.c with and without loop/usleep. I only get a bootlogo with usleep and loop. Otherwise just a black screen.

 

I compiled your showiframe.c  from post #27 and it gives a bootlogo without a big black border(DM8000). Thanks.

 

write_all  is proberly the solution. But i am not sure.


Edited by Beeker, 30 September 2013 - 17:03.

DM8000.  Wavefrontier T55  13.0|19.2|23.5|28.2 + Ziggo.


Re: Bootlogo #54 ims

  • PLi® Core member
  • 11,196 posts

+168
Excellent

Posted 30 September 2013 - 17:13

@pieterg: in actual file in line:

 

int fd = open("/dev/dvb/adapter0/video0", O_WRONLY|O_NONBLOCK);
 

remove  flag O_NONBLOCK, then it works.


Edited by ims, 30 September 2013 - 17:19.

Kdo nic nedělá, nic nezkazí!

Re: Bootlogo #55 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 30 September 2013 - 17:54

OK, the write_all wrapper should have handled that, but what can you do about crappy drivers...

Re: Bootlogo #56 gutemine

  • Senior Member
  • 873 posts

+68
Good

Posted 1 October 2013 - 19:39

Please don't start this again, because I still wait for an excuse. It is not my, or the driver's fault if you don't understand the code.


Edited by gutemine, 1 October 2013 - 19:42.


Re: Bootlogo #57 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 1 October 2013 - 20:46

Just check the write wrapper, then I guess you understand what I mean.
(at least, I thought you knew some c yourself)

Re: Bootlogo #58 gutemine

  • Senior Member
  • 873 posts

+68
Good

Posted 1 October 2013 - 20:57

If I were you I would consider kicking out showiframe completely as it is a legacy from dm7025 and the code is more then shabby, but fixable.

 

Even DMM uses on ALL new boxes the jpg files, and for example replacing showiframe with a simple jpeg viewer would be a real improvement. Instead all your other great boxes prefere to copy (only) and the developers prefere to blame drivers. With all the code you can find with your favourite search engine (including busybox code btw.) it takes less then 1h to find a faster, better and space saving solution (as all *.mvi would be GONE). But this would mean an enhancement - but I agree complaining is easier.

 

And yes, I have done such code for png, jpeg and bitmap Files as I needed it for my bootmanager, so the 1h is just the estimate of a very bad programmer (=me) who needed days to make it work.


Edited by gutemine, 1 October 2013 - 20:59.


Re: Bootlogo #59 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 1 October 2013 - 21:00

Of course, programmers always blame eachother, never themselves. I thought you would understand ;)

Anyway, I just noticed the write wrapper doesn't handle EAGAIN, so nonblocking mode wouldn't have worked.

BTW, for stillframes we should be using the VIDEO_STILLPICTURE ioctl.
But last time I checked, it wasn't implemented.

Re: Bootlogo #60 gutemine

  • Senior Member
  • 873 posts

+68
Good

Posted 1 October 2013 - 21:10

You are forgetting that showiframe on the old box is run already VERY early in the boot process, not only for enigma2 restart, and shortly after the drivers have initialized some strange things could happen if you try that.

 

You are ignoring that I still support showing *.mvi bootlogos as Barry Allen Bootmanager background (besides bmp and png) so I know most of the fun you can have with that code.

 

And I'm not blaming you, I simply try to explain that the problem is solveable without any fingerpointing in wrong directions (except when you look in a mirror) and that if you don't like something you should think about how to improve it and not moaning how bad it is. But this is just another advice .. take it or not.


Edited by gutemine, 1 October 2013 - 21:13.





3 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users


    Google (2)