unofficial Open PLi for AZBox , coming soon
#1
Posted 12 May 2012 - 07:19
http://openazbox.info/
Open AZBox MOD is Enigma 2 Image for AZBox receivers, fully based on OpenPLi Open Source project managed by PLi team. If You wish to contribute in Open AZBox Project, feel free to visit our project hosted on Sourceforge.net
sources (coming soon) :
http://sourceforge.n...s/azboxopenpli/
Open Vision sources: https://github.com/OpenVisionE2
Re: unofficial Open PLi for AZBox , coming soon #2
Posted 12 May 2012 - 09:34
Hmmm, I've seen that phrase before....sources (coming soon) :
Why not simply give "world" read-only access to your git repository?
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Re: unofficial Open PLi for AZBox , coming soon #3
Posted 12 May 2012 - 12:40
Hmmm, I've seen that phrase before....
sources (coming soon) :
Why not simply give "world" read-only access to your git repository?
actually i'm not a member of this project but as i wrote coming soon
(even read access to all sources)
Open Vision sources: https://github.com/OpenVisionE2
Re: unofficial Open PLi for AZBox , coming soon #4
Posted 12 May 2012 - 18:08
OpenAZBox PLi MOD image is fully based on OpenPLi 2.1 Enigma 2
Kernel: Linux azboxme 3.3.1
Enigma 2: 24. april 2012.
Drivers: Thu May 10 17:30:12 CEST 2012
Please expect that some things are disabled or not implemented in this prerelease version of Enigma 2, but for sure those things will be added in first stable release soon! Goal of Open AZBox Project is to be fully open source, and to give chance for other interested teams and developers to make their versions of Enigma 2 for this great devices!
Open AZBox PLi MOD GIT Repository on Sourceforge.net will be soon fully populated with all resources and files needed for development. We have also prepared all necessary patch files for Enigma 2.
Download Open AZBox PLi MOD Prerelease for AZBox Me:
http://image.openazb...-prerelease.rar
Open Vision sources: https://github.com/OpenVisionE2
Re: unofficial Open PLi for AZBox , coming soon #5
Posted 12 May 2012 - 19:06
Azboxopenpli does it mean that openpli agreed that they can use the name as openpli has an commercial value.
Why are they keep focusing on the name openpli and not just mention one time based on openpli.
Edited by Carl, 12 May 2012 - 19:08.
Re: unofficial Open PLi for AZBox , coming soon #6
Posted 12 May 2012 - 19:09
All other uses, including the name in the image, the bootlogo's and the reference to OpenPLi and/or this forum in green-screen-dumps are forbidden.
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: unofficial Open PLi for AZBox , coming soon #7
Re: unofficial Open PLi for AZBox , coming soon #8
Posted 13 May 2012 - 01:32
It seems it is finally happening - but the proof lies in the eating, so we wait to see the real release...
We have, indeed, seen this story many times before but it is still... "in the making"...
I hope OpenPLi are their saviour, for the sake of hobbyists who own AZ...
But I will need to test this myself and see it really kicking arse...
Re: unofficial Open PLi for AZBox , coming soon #9
Posted 15 May 2012 - 15:29
but what i cant understand is why you are always so critic about them
do you have a time to enjoy any single moment in front of tv or just to write sarcastic comments
What i could say about my Peugeot and problems which I had with it, and other owners of same car and model was enjoying in that time, while my car was on service full 2 months, and service was telling me it is not factory problem, it is problem of driver, inputing that i caused crash of dual mass flywheel and grearbox
and still i am owner of Peugeot, but this time new one, and I am happy with it
Edited by digitalchaos, 15 May 2012 - 15:32.
Re: unofficial Open PLi for AZBox , coming soon #10
Posted 15 May 2012 - 16:19
m8 no offence to you, i am just an azbox owner and what this guys maded for our stbs are amazing
I know that grammar very well, mistakes and all - why don't you say who you really are, for crying out loud, so we can have an honest discussion?!?
No, sadly, it's not yet amazing - maybe it could be but not yet! Reasons are everywhere...
but what i cant understand is why you are always so critic about them
Because I can compare and I tell the truth. If you have a problem with that - don't read it.
But if you have an interest in selling these boxes - state it openly, so we know how to deal with you and your "objective arguments"...
do you have a time to enjoy any single moment in front of tv or just to write sarcastic comments
They are not sarcastic but exasperated - how long is this going on now, any idea? And it's still on promises and more promises but no way anything functions really well as it is supposed to and as it does function in some other boxes...
What i could say about my Peugeot and problems which I had with it, and other owners of same car and model was enjoying in that time, while my car was on service full 2 months, and service was telling me it is not factory problem, it is problem of driver, inputing that i caused crash of dual mass flywheel and grearbox
and still i am owner of Peugeot, but this time new one, and I am happy with it
Indeed, they promised a Lamborghini, that will eat DMM for breakfast - and instead, we got a Peugeot, as you rightly state....
Maybe you are the one who is - for some strange reason we can not yet assess properly... - "happy" because your expectations are low and not on the same level as most users using these machines, having all sorts of various problems?!?
I know of one thing for sure: without open debate and honest reporting of the problems no one is going anywhere in speed...
And the culture surrounding that box is not supporting such a spirit, sadly...
For that I do not blame The_Ripper or Sattommy!
Re: unofficial Open PLi for AZBox , coming soon #11
Re: unofficial Open PLi for AZBox , coming soon #12
Re: unofficial Open PLi for AZBox , coming soon #13
Posted 15 May 2012 - 17:33
I am finishing some last preparation because of changes , where can "OpenPLI" string can stay and where not as requested by PLI team members (I hope I didnt miss something and didnt remove it when all files is up , but I want personally to say to PLi team members it will be removed if I miss something, mistake happens) , plus finishing some final touches in Azbox bitbake files.
Main files, like linux source, initramfs for kernel (for rescue mode, GUI update), Sigma MRUA libs, drivers, etc.. will be/is uploaded here
http://code.google.c.../downloads/list
Fork of the OpenPLI openembedded git is here http://azboxopenpli....tweb-index.cgi.
Right now its still dont have Azbox stuff, but soon I will upload all Azbox bitbake files, plus patches and stay sync to OpenPLI openembedded git.
Thanks.
Edited by The_Ripper, 15 May 2012 - 17:34.
Re: unofficial Open PLi for AZBox , coming soon #14
Posted 15 May 2012 - 17:37
Re: unofficial Open PLi for AZBox , coming soon #15
Posted 15 May 2012 - 18:52
Thanks for this link.... Just a question - you did not modify anything at OpenPli-E2 at all?
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: unofficial Open PLi for AZBox , coming soon #16
Posted 15 May 2012 - 19:49
Few changes,
diff -Naur a/lib/python/Components/Harddisk.py b/lib/python/Components/Harddisk.py --- a/lib/python/Components/Harddisk.py 2012-05-15 18:04:23.000000000 +0200 +++ b/lib/python/Components/Harddisk.py 2012-05-15 19:05:41.000000000 +0200 @@ -608,7 +608,7 @@ try: removable = bool(int(readFile(devpath + "/removable"))) dev = int(readFile(devpath + "/dev").split(':')[0]) - if dev in (7, 31, 253): # loop, mtdblock, romblock + if dev in (1, 7, 31, 253): # ram, loop, mtdblock, romblock blacklisted = True if blockdev[0:2] == 'sr': is_cdrom = True diff -Naur a/lib/python/Plugins/SystemPlugins/Videomode/VideoHardware.py b/lib/python/Plugins/SystemPlugins/Videomode/VideoHardware.py --- a/lib/python/Plugins/SystemPlugins/Videomode/VideoHardware.py 2012-05-14 16:45:54.000000000 +0200 +++ b/lib/python/Plugins/SystemPlugins/Videomode/VideoHardware.py 2012-04-19 03:26:00.000000000 +0200 @@ -10,6 +10,7 @@ # available and preferred modes, as well as handling the currently # selected mode. No other strict checking is done. class VideoHardware: + hw_type = HardwareInfo().get_device_name() rates = { } # high-level, use selectable modes. modes = { } # a list of (high-level) modes for a certain port. @@ -38,6 +39,11 @@ "60Hz": { 60: "1080i" }, "multi": { 50: "1080i50", 60: "1080i" } } + if hw_type == "me" or hw_type == "minime" : + rates["1080p"] = { "50Hz": { 50: "1080p50" }, + "60Hz": { 60: "1080p" }, + "multi": { 50: "1080p50", 60: "1080p" } } + rates["PC"] = { "1024x768": { 60: "1024x768" }, # not possible on DM7025 "800x600" : { 60: "800x600" }, # also not possible @@ -56,7 +62,11 @@ modes["Scart"] = ["PAL", "NTSC", "Multi"] modes["YPbPr"] = ["720p", "1080i", "576p", "480p", "576i", "480i"] - modes["DVI"] = ["720p", "1080i", "576p", "480p", "576i", "480i"] + if hw_type == "me" or hw_type == "minime" : + modes["DVI"] = ["720p", "1080p", "1080i", "576p", "480p", "576i", "480i"] + config.av.edid_override = True + else: + modes["DVI"] = ["720p", "1080i", "576p", "480p", "576i", "480i"] modes["DVI-PC"] = ["PC"] widescreen_modes = set(["720p", "1080i"]) @@ -97,10 +107,14 @@ self.readAvailableModes() + if self.hw_type == "me" or self.hw_type == "minime" : del self.modes["Scart"] + if self.modes.has_key("DVI-PC") and not self.getModeList("DVI-PC"): print "remove DVI-PC because of not existing modes" del self.modes["DVI-PC"] + if self.hw_type == "me" or self.hw_type == "minime" : self.readPreferredModes() + self.createConfig() # self.on_hotplug.append(self.createConfig) @@ -151,10 +165,13 @@ rate = self.rates[mode][rate] for mode in rate.values(): # DVI modes must be in "modes_preferred" -# if port == "DVI": -# if mode not in self.modes_preferred and not config.av.edid_override.value: -# print "no, not preferred" -# return False + if port == "DVI": +##### Only for test ##### + if self.hw_type == "me" or self.hw_type == "minime" : + if mode not in self.modes_preferred and not config.av.edid_override.value: + print "no, not preferred" + return False +##### Only for test ##### if mode not in self.modes_available: return False return True diff -Naur a/lib/python/Plugins/SystemPlugins/Videomode/videowizard.xml b/lib/python/Plugins/SystemPlugins/Videomode/videowizard.xml --- a/lib/python/Plugins/SystemPlugins/Videomode/videowizard.xml 2012-05-14 16:45:54.000000000 +0200 +++ b/lib/python/Plugins/SystemPlugins/Videomode/videowizard.xml 2012-04-25 19:18:56.000000000 +0200 @@ -9,7 +9,7 @@ self.selectKey("OK") </code> </step> - <step id="modeselection" nextstep="rateselection" timeout="20" timeoutaction="selectnext"> + <step id="modeselection" nextstep="rateselection" timeout="30" timeoutaction="selectnext"> <text value="Video mode selection." /> <displaytext value="Select video mode" /> <list type="dynamic" source="listModes" evaluation="modeSelectionMade" onselect="modeSelectionMoved" /> @@ -20,7 +20,7 @@ self["portpic"].hide() </code> </step> - <step id="rateselection" nextstep="end" timeout="20" timeoutaction="selectnext"> + <step id="rateselection" nextstep="end" timeout="30" timeoutaction="selectnext"> <condition> self.condition = (self.port != "DVI" or self.mode == "PC") </condition> diff -Naur a/lib/python/Tools/HardwareInfo.py b/lib/python/Tools/HardwareInfo.py --- a/lib/python/Tools/HardwareInfo.py 2012-05-14 16:45:54.000000000 +0200 +++ b/lib/python/Tools/HardwareInfo.py 2012-04-18 22:47:00.000000000 +0200 @@ -44,4 +44,4 @@ return HardwareInfo.device_version def has_hdmi(self): - return (HardwareInfo.device_name == 'dm800se' or HardwareInfo.device_name == 'dm500hd' or (HardwareInfo.device_name == 'dm8000' and HardwareInfo.device_version != None)) + return (HardwareInfo.device_name == 'me' or HardwareInfo.device_name == 'minime' or HardwareInfo.device_name == 'dm800se' or HardwareInfo.device_name == 'dm500hd' or (HardwareInfo.device_name == 'dm8000' and HardwareInfo.device_version != None))
First one block virtual RAM block device, not important patch , can stay default code, but we added to block it.
Second one is changes regarding 1080p support and test for reading preffered modes (what TV return in EDID message)
Third one is incrise in timeout from 20 sec to 30 sec for Sigma, unfortunally Sigma API regarding TV out seems litlle slow compared to BCM API.
Fourth is just to return HDMI support for me/minime.
Plus changes in enigma2.bb regarding overwriting default remote pictures rc.png/rcold.png to me/minime ones.
So thats all patches regarding E2. Rest of the E2 default code works ok and we dont have a plan to change it.
Re: unofficial Open PLi for AZBox , coming soon #17
Re: unofficial Open PLi for AZBox , coming soon #18
Re: unofficial Open PLi for AZBox , coming soon #19
Posted 15 May 2012 - 20:47
Are you reffering to this variable in openembedded ?
DISTRO_FEED_URI ?= "http://downloads.openazbox.info/feeds/${FEED_NAME}/${MACHINE}"
Thanks
Re: unofficial Open PLi for AZBox , coming soon #20
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users