# rm /dev/log (if you have)
# mkdir /dev/log;touch /dev/log/{main,events,radio}
* you can see usefull infos from strace log and /dev/log/main
and instead of:
chroot . /a.sh
I execute the android init process:
chroot . /init
Not sure yet what exactly of those steps solved the problem (maybe the
qemu one), but it does work.
After a quick try I see that the touchscreen doesn't work (the
keyboard does though), but that shouldn't be too hard to fix.
Great, congrats!!! I will try it on N800 as soon as I find some time
for it.
Regarding the touch screen problems:
The existing touchscreen driver propably needs to be replaced by one
that can work on fb level. See this site for details:
http://qtablet.laginen.net/doku.php. Its about porting Qt to Maemo,
but the problems are similar.
Cheers,
Sebastian
On 5 Apr., 13:35, sim0nx <Georges.T...@gmail.com> wrote:
> # rm /dev/log (if you have)
> # mkdir /dev/log;touch /dev/log/{main,events,radio}
> * you can see usefull infos from strace log and /dev/log/main
> and instead of:
> chroot . /a.sh
> I execute the android init process:
> chroot . /init
> Not sure yet what exactly of those steps solved the problem (maybe the
> qemu one), but it does work.
> After a quick try I see that the touchscreen doesn't work (the
> keyboard does though), but that shouldn't be too hard to fix.
> Great, congrats!!! I will try it on N800 as soon as I find some time > for it.
Thanks :-)
> Regarding the touch screen problems: > The existing touchscreen driver propably needs to be replaced by one > that can work on fb level. See this site for details: > http://qtablet.laginen.net/doku.php. Its about porting Qt to Maemo, > but the problems are similar.
>> Maybe you don't have /sys/class/input/input1/. Android looks for drivers in /sys.
>> I guess you'd better to platform_driver_register() in your dev_init() and let the
>> probe function do the current mxc_ts_init() job. Your keyboard driver or
>> corgi_ts.c would be helpful.
Regards,
On Apr 11, 7:48 am, Georges Toth <georges.t...@gmail.com> wrote:
> > Great, congrats!!! I will try it on N800 as soon as I find some time
> > for it.
> Thanks :-)
> > Regarding the touch screen problems:
> > The existing touchscreen driver propably needs to be replaced by one
> > that can work on fb level. See this site for details:
> >http://qtablet.laginen.net/doku.php. Its about porting Qt to Maemo,
> > but the problems are similar.
> Thanks for the link...I'll check that out soon !
> # rm /dev/log (if you have)
> # mkdir /dev/log;touch /dev/log/{main,events,radio}
> * you can see usefull infos from strace log and /dev/log/main
> and instead of:
> chroot . /a.sh
> I execute the android init process:
> chroot . /init
> Not sure yet what exactly of those steps solved the problem (maybe the
> qemu one), but it does work.
> After a quick try I see that the touchscreen doesn't work (the
> keyboard does though), but that shouldn't be too hard to fix.
Mohan Parthasarathy wrote: > Thanks. Is it okay to take the user space (data, system) from rc15 ?
No it is not because the m5-rcX userspace expects the framebuffer driver to support page-flipping which the framebuffer driver for the n8xx currently does not support. So you'll only get a blank screen.
I finally found the time to try your tips on my N800 and after some
hazzling it also works.
The actual trick was using my patched m5 kernel with the m3 file
system.
Georges, have you already updated the keyboard mapping in the android
config files? If yes, could please post them?
Have you tried the other touchscreen driver, I mentioned?
Regarding HW acceleration:
The OMAP 2420 has some graphics acceleration available but it has not
been utilized in N800 and N810. Because of that there are no
respective drivers running. But there should drivers available.
> Mohan Parthasarathy wrote: > > Thanks. Is it okay to take the user space (data, system) from rc15 ? > No it is not because the m5-rcX userspace expects the framebuffer driver > to support page-flipping which the framebuffer driver for the n8xx > currently does not support. > So you'll only get a blank screen.
stolzi wrote: > I finally found the time to try your tips on my N800 and after some > hazzling it also works. > The actual trick was using my patched m5 kernel with the m3 file > system.
Good :-) Did you use init to start android ?
> Georges, have you already updated the keyboard mapping in the android > config files? If yes, could please post them?
I haven't had time last week for working on this any further. Last time I worked on this I was stuck trying to figure out a way to get the keycodes. I'll hope to be able to work on this again this week :-(
> Have you tried the other touchscreen driver, I mentioned?
I checked that website but the only thing I could find regarding touchscreen was that tslib. Android used the event device directly, so this won't help.
My setup is slightly different. I am going to describe it in detail at
the project pages.
As mentioned earlier I'm using a multiboot initfs which lets me choose
from which drive (flash, mmc1, mmc2) to boot. On the mmc I have the
Android filesystem and a small script eventually starting android's
init.
I am using the m3-rc37 tools and the corresponding kernel on N810. The
red
cylon keeps swinging but nothing happens after that. From the trace i
can see
the following errors:
15:53:39.584808 open("/dev/alarm", O_RDWR|O_LARGEFILE) = 6
15:53:39.590454 ioctl(6, 0x40086104, 0xbeef5bd0) = -1 ENOIOCTLCMD
(Unknown error 515)
15:53:39.593597 writev(3, [{"\5", 1}, {"runtime\0", 8}, {"Unable to
read rtc, No such file or directory\n\0", 47}], 3) = 56
15:53:39.602172 writev(3, [{"\5", 1}, {"runtime\0", 8}, {"Invalid time
detected, 1 set to 1167652800\n\0", 44}], 3) = 53
15:53:39.607421 ioctl(6, 0x40086105, 0xbeef5bd0) = -1 ENOIOCTLCMD
(Unknown error 515)
15:53:39.611022 writev(3, [{"\5", 1}, {"runtime\0", 8}, {"Unable to
set rtc to 1167652800: No such file or directory\n\0", 60}], 3) = 69
I am wondering why the SurfaceFlinger is not starting and is this the
reason for not seeing any
progress beyond red cyclon swinging ? Any clues would be
appreciated ? i have set the permissions
to 0666 on most of the stuff. I am using ext2 filesystem on a SD card.
As i am using m3, i am using
the the driver/binder.
thanks
mohan
On Apr 18, 1:57 am, stolzi <sebastian.stolzenb...@googlemail.com>
wrote:
> My setup is slightly different. I am going to describe it in detail at
> the project pages.
> As mentioned earlier I'm using a multiboot initfs which lets me choose
> from which drive (flash, mmc1, mmc2) to boot. On the mmc I have the
> Android filesystem and a small script eventually starting android's
> init.
Can n810 make a telephone call? it seems that
this product have not sell in china now.does somebody
know whethere this product can make a telphone call in china?
On Sat, Apr 19, 2008 at 9:32 PM, PowerGUI <powergui...@gmail.com> wrote:
> Can n810 make a telephone call? it seems that > this product have not sell in china now.does somebody > know whethere this product can make a telphone call in china?
but after n810 has bootup, the /proc/misc file shows no alarm device
available in kernel:
Nokia-N810-51-3:/sys# cat /proc/misc
59 log_radio
60 log_events
61 log_main
200 tun
130 watchdog
62 retu
63 tahvo
Nokia-N810-51-3:/sys#
Could somebody give some hints about how to add android's alarm device
in kernel. BTW, I am using m3 kernel with m3 root file system.
On Apr 5, 7:35 pm, sim0nx <Georges.T...@gmail.com> wrote:
> # rm /dev/log (if you have)
> # mkdir /dev/log;touch /dev/log/{main,events,radio}
> * you can see usefull infos from strace log and /dev/log/main
> and instead of:
> chroot . /a.sh
> I execute the android init process:
> chroot . /init
> Not sure yet what exactly of those steps solved the problem (maybe the
> qemu one), but it does work.
> After a quick try I see that the touchscreen doesn't work (the
> keyboard does though), but that shouldn't be too hard to fix.
This is exactly the problem i am having since yesterday. I am debugging currently.. Also, i use m3 kernel and m3 filesystem and i see the same entries in /proc/misc entries. Let me know if you find something or someone has clues..
> > # rm /dev/log (if you have) > > # mkdir /dev/log;touch /dev/log/{main,events,radio} > > * you can see usefull infos from strace log and /dev/log/main
> > and instead of: > > chroot . /a.sh > > I execute the android init process: > > chroot . /init
> > Not sure yet what exactly of those steps solved the problem (maybe the > > qemu one), but it does work. > > After a quick try I see that the touchscreen doesn't work (the > > keyboard does though), but that shouldn't be too hard to fix.
Mohan Parthasarathy wrote: > This is exactly the problem i am having since yesterday. I am > debugging currently.. > Also, i use m3 kernel and m3 filesystem and i see the same entries in > /proc/misc > entries. Let me know if you find something or someone has clues..
> -thx > mohan
Use the m5 kernel instead. If you don't see a binder entry in /proc/misc it for sure won't work... (there also has to be a node in /dev of course..) Also checkout elinux.org and http://code.google.com/p/android-on-n8xx/ ...
I fixed the alarm driver problem. At least, it looks like the misc_register should be called in __init and not in late_init. Interestingly, i get other errors which i did not get before :-) runtime seems to get EINVALs and coredumps.
in my reading of this thread, i thought m5 filesystem had issues with n810. Is that right ? Are you suggesting to use both m5 filesystem and m5 kernel ? I tried this early on and then reverted to m3. In the pointer below, the versions are not mentioned.
thanks mohan
On Mon, Apr 21, 2008 at 10:12 AM, Georges Toth <georges.t...@gmail.com> wrote:
> Mohan Parthasarathy wrote: > > This is exactly the problem i am having since yesterday. I am > > debugging currently.. > > Also, i use m3 kernel and m3 filesystem and i see the same entries in > > /proc/misc > > entries. Let me know if you find something or someone has clues..
> > -thx > > mohan > Use the m5 kernel instead. > If you don't see a binder entry in /proc/misc it for sure won't work... > (there also has to be a node in /dev of course..) > Also checkout elinux.org and http://code.google.com/p/android-on-n8xx/ ...
> in my reading of this thread, i thought m5 filesystem had issues with > n810. Is that right ? Are you > suggesting to use both m5 filesystem and m5 kernel ? I tried this > early on and then reverted to > m3. In the pointer below, the versions are not mentioned.
m5 userspace does not work with the n8xx ... that's right. There's an issue with the framebuffer driver...
I'm suggesting that you use the m5-rc14 kernel with the m3 userspace. That combination does work fine.
If you're actively working on this ... maybe you want to join the android-on-n8xx as well, in order to document your findings on that website and add your patches etc, for other people to find ?
> I fixed the alarm driver problem. At least, it looks like the > misc_register should be called in __init and > not in late_init. Interestingly, i get other errors which i did not > get before :-) runtime seems to get > EINVALs and coredumps.
> in my reading of this thread, i thought m5 filesystem had issues with > n810. Is that right ? Are you > suggesting to use both m5 filesystem and m5 kernel ? I tried this > early on and then reverted to > m3. In the pointer below, the versions are not mentioned.
> thanks > mohan
> On Mon, Apr 21, 2008 at 10:12 AM, Georges Toth <georges.t...@gmail.com > <mailto:georges.t...@gmail.com>> wrote:
> Hi,
> Mohan Parthasarathy wrote: > > This is exactly the problem i am having since yesterday. I am > > debugging currently.. > > Also, i use m3 kernel and m3 filesystem and i see the same > entries in > > /proc/misc > > entries. Let me know if you find something or someone has clues..
> > -thx > > mohan > Use the m5 kernel instead. > If you don't see a binder entry in /proc/misc it for sure won't > work... > (there also has to be a node in /dev of course..) > Also checkout elinux.org <http://elinux.org> and > http://code.google.com/p/android-on-n8xx/ ...
> > in my reading of this thread, i thought m5 filesystem had issues with > > n810. Is that right ? Are you > > suggesting to use both m5 filesystem and m5 kernel ? I tried this > > early on and then reverted to > > m3. In the pointer below, the versions are not mentioned. > m5 userspace does not work with the n8xx ... that's right. > There's an issue with the framebuffer driver...
> I'm suggesting that you use the m5-rc14 kernel with the m3 userspace. > That combination does work fine.
> If you're actively working on this ... maybe you want to join the > android-on-n8xx as well, in order to document your findings on that > website and add your patches etc, for other people to find ?
> > I fixed the alarm driver problem. At least, it looks like the > > misc_register should be called in __init and > > not in late_init. Interestingly, i get other errors which i did not > > get before :-) runtime seems to get > > EINVALs and coredumps.
> > in my reading of this thread, i thought m5 filesystem had issues with > > n810. Is that right ? Are you > > suggesting to use both m5 filesystem and m5 kernel ? I tried this > > early on and then reverted to > > m3. In the pointer below, the versions are not mentioned.
> > thanks > > mohan
> > On Mon, Apr 21, 2008 at 10:12 AM, Georges Toth <georges.t...@gmail.com > > <mailto:georges.t...@gmail.com>> wrote:
> > Hi,
> > Mohan Parthasarathy wrote: > > > This is exactly the problem i am having since yesterday. I am > > > debugging currently.. > > > Also, i use m3 kernel and m3 filesystem and i see the same > > entries in > > > /proc/misc > > > entries. Let me know if you find something or someone has clues..
> > > -thx > > > mohan > > Use the m5 kernel instead. > > If you don't see a binder entry in /proc/misc it for sure won't > > work... > > (there also has to be a node in /dev of course..) > > Also checkout elinux.org <http://elinux.org> and > > http://code.google.com/p/android-on-n8xx/ ...
|
