The problem is that "MIPI" is not a standard plug where both ends are certified. Yes, they are - but not completely. Only on the physical layers. It is like that you can plug in any USB device into a USB socket. But it does not work on your machine, because you don't find a compatible driver. But it may work on another one. So you try to write your own driver. Or you have a web browser and can't open some page (isn't http and html standardized?).Why do the gazillions devices appear to have less problems?I still don't get this "MIPI" thing. If it is so complicated to get an LCD working on an SoC, how the hell do all the gazillion Mobile Devices out there solve these issues? They pop out so fast, I can't imagine they have to deal alot with such issues at all." Does really every single one uses custom, "dirty" hacks just to get every LCD/SoC combo working? And if the OMAP5 has a (general?) bug that prevents it from communicating properly with an LCD, how do other OMAP5 mobile devices (if tere are any) get an image on screen? If they have solutions, it could help to just ask them for the workaround.
This all somehow makes no sense (due Pandora development, MIPI was afaik not even mentioned once), at least not if they actualy WANT a easy to use standard at all. Sounds like this is not the case. Sad, that the display manufactureres don't deliver their hardware with the matching drivers, I guess this would make stuff a little bit easier then. ^^"So good luck with the new LCD, I'm sure you will find a solution.The problem is that "MIPI" is not a standard plug where both ends are certified. Yes, they are - but not completely. Only on the physical layers. It is like that you can plug in any USB device into a USB socket. But it does not work on your machine, because you don't find a compatible driver. But it may work on another one. So you try to write your own driver. Or you have a web browser and can't open some page (isn't http and html standardized?).Why do the gazillions devices appear to have less problems?I still don't get this "MIPI" thing. If it is so complicated to get an LCD working on an SoC, how the hell do all the gazillion Mobile Devices out there solve these issues? They pop out so fast, I can't imagine they have to deal alot with such issues at all." Does really every single one uses custom, "dirty" hacks just to get every LCD/SoC combo working? And if the OMAP5 has a (general?) bug that prevents it from communicating properly with an LCD, how do other OMAP5 mobile devices (if tere are any) get an image on screen? If they have solutions, it could help to just ask them for the workaround.
1. they don't use the latest and greatest display like we try
2. they have more people on their payroll to run around the world to knock at doors (so they may get answers faster than we do)
3. they are members of the MIPI organization (I think that costs >25000 USD membership fee per year) and therefore have a more direct contact
4. they have much more expensive equipment for analyzing circuits (e.g. a 16 channnel 5 GHz logic analyser or a special MIPI-DSI tester like one built by Agilent)
5. they buy reference designs where someone has done exactly the same challenging and time-consuming task we are doing (and reporting to the public) - but some months ago and behind the curtain - so it appears that it was easy for them
So they don't talk as much about issues, and may be faster because they spend more money on it.
I hope not, this would be unfair. Customer is customer so everyone that buys their LCDs should be able to use it without much trouble. Otherwise it would not make sense to sell their stuff to low quantities that may get the hardware but not the software.But maybe they have all that stuff more readily for the big payers who buy from them directly instead of through distributors..
Since when we are treated fairly? Ed had to pay premium for most of Pandora's parts since we are small fish. So Pyra will be similar...I hope not, this would be unfair. Customer is customer so everyone that buys their LCDs should be able to use it without much trouble. Otherwise it would not make sense to sell their stuff to low quantities that may get the hardware but not the software.But maybe they have all that stuff more readily for the big payers who buy from them directly instead of through distributors..
My Fairness-senses are tingeling...
I've never seen it. Where?Besides, he already said, it shouldn't add that much size.
I said if you wanted to use the Pandora battery, you don't think there wouldn't be a smallercase option?Logically, as big as a 6000mah battery
I can't point it out now, but he basically said the lid is smaller, soweight and size should be about the same.I've never seen it. Where?
ED says he thinks it can be done without increasing the volume of the unit at all.I've never seen it. Where?
Presumably that means keeping it close to the same thickness as the Pandora, which most people are okay with.EvilDragon said:On the Pyra, this shouldn't be a big problem, and I think it can be done without increasing the size of the unit (needs a bit more puzzling).
Okay, I didn't understand at all. I meant if 4200 is chosen, there will be a thinner case than 6000.How do you know it's going to be a big case? If you decide to pick the Pandora battery, it would make sense to have smaller cases.
Besides, he already said, it shouldn't add that much size.
Yes, 4200 would make a thinner case. Yes, 6000 would be thicker than 4200.6000 as the default battery, doesn't mean you can't oped out for 4200+smaller frame/case/cover.Okay, I didn't understand at all. I meant if 4200 is chosen, there will be a thinner case than 6000.
6000 would be bigger and if you want to add battery life you should carry another 6000 battery or 4200+frame which are too much for pockets.
ED an Gta04 are the ones who know, but I have a hard time believing that they can fit all the stuff in, they currently planning to, without making the Pyra bigger than the Pandora.ED says he thinks it can be done without increasing the volume of the unit at all.
