View Single Post
  #102 (permalink)  
Old 10-05-2010, 10:02 PM
manekineko's Avatar
manekineko
Regular 'Geeker
Offline
 
Join Date: Jul 2009
Posts: 478
Reputation: 845
manekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update

Quote:
Originally Posted by [ACL] View Post
I'm not sure what to attack next. I wanted to implement a blit scaler similar to what dzo did for the vogue. It would allow us to run our device at different resolutions so we dont need to worry about certain roms not fitting properly (like sense ui). If this works, we can in theory run the 2.2 froyo from the wildfire without modifying anything since the gpu will scale it for us. Or if you dont mind an old release, run the hero/eris 2.1 sense ui. If i dont tackle that, i guess i can start looking at something more useful, headset? hmm maybe seeing if we can squeeze more ouf of the gpu. Not sure.. or i can help join the fight against .35 now thats a big project
How transparent would a scaler like that work? Even on the latest kernel, when running something in Nesoid, if it's scaled at all the lag is quite heavy. If it's only doubled (which should really be a very simple operation) the lag is bad, if it's actually scaled to the screen resolution, the lag is really bad.

What're the benefits of moving to a .35 kernel?

Obviously you're always free to work on whatever, but the headset would be an amazing improvement, not just to be able to use it, but since there aren't many other devs that are in a position to work on it.
Reply With Quote