![]() |
Re: Another Android port: NITdroid
I made a video about NITdroid :)
http://video.google.com/videoplay?do...47315953961035 As you can see it works pretty fast ;) It looks cool how it crashes at the end of the video :D |
Re: Another Android port: NITdroid
Quote:
Great work with NITdroid though ;) |
Re: Another Android port: NITdroid
Quote:
|
Re: Another Android port: NITdroid
Quote:
|
Re: Another Android port: NITdroid
Quote:
Quote:
Maybe there's a mistake here? Are you sure these are required N800 drivers? The tsc2301-core is staying; perhaps they're doing the audio mixing differently now? How dare they declare my beloved N800s LEGACY!? They're only two years old! OK, the N800 has been discontinued, and two years is a long time in this market, but come on, guys! |
Re: Another Android port: NITdroid
And unused touchscreen drivers... I'm using them in this moment thank you very much... :D
|
Re: Another Android port: NITdroid
Quote:
|
Re: Another Android port: NITdroid
Any ideas why wlan0 says No such file or directory?
|
Re: Another Android port: NITdroid
Quote:
It seems that I would need to learn how to implement double buffering using fb planes as the XV for Xomap to eliminate the flickering. |
Re: Another Android port: NITdroid
I couldn't get it to boot.
The doc says it boots from mmcblk0p3 (why p3?) so I used fdisk to partition the internal card and formatted the 3rd partition with ext3 and extracted the filesystem there (as root). Still, all I get is the penguin logo (N800) or no reaction at all (N810). The N810 is still on Chinook, the N800 on latest Diablo; is the Diablo bootloader needed for booting this kernel, because my N810 shows no reaction after flashing the kernel? |
All times are GMT. The time now is 12:53. |
vBulletin® Version 3.8.8