I was doing some googling and found that some ppl successfully got bluetooth keyboard, mouse working on N900. Any thought of that ?
From: Chen Dai Sent: Wednesday, September 29, 2010 10:08 AM To: Andy Lee Cc: gw zhang ; [email protected] Subject: Re: [MeeGo-dev] Still question on MeeGo on devkit8000 I think it doesn't support it. On the wiki, it said "Unfortunately there's no mouse cursor yet, but with a touchscreen the UI is usable. Although the beagleboards 128MB memory is not enough and the device keeps swapping and is very slow." 2010/9/29 Andy Lee <[email protected]> Does anyone know how to make mouse cursor visible ? From: gw zhang Sent: Wednesday, September 29, 2010 9:51 AM To: Chen Dai Cc: [email protected] Subject: Re: [MeeGo-dev] Still question on MeeGo on devkit8000 1. Omapfb initilize correctly? Does /dev/fb[0-2] exist? 2. For meego-dm killed, I think it's due to the sgx driver. I recomment you to build the rootfs according to http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch#Prepare_SGX.2FGLES_libs First use create_sgx_module.sh to create the lib file, then put the lib in some place, and use image-creator to build the rootfs under the place, well, you should use the specific kickstart file in the above url (in my opinion, or if you are familiar with kickstart, you can write it yourself) 3. For mcompositor, sorry , I don't encouter this problem, so I cannot give you any advice 2010/9/28 Chen Dai <[email protected]> Hi, With gw's suggestions, I successfully mounted the rootfs via NFS, and booted the kernel. But unfortunately, the LCD is still black. I checked the Xorg.0.log, there are two errors, 1. dlopen of /usr/lib/dri/swrast_dri.so failed, No such file or directory . 2. Error opening /sys/devices/platform/omapfb/ctrl/name: No such file or directory if run startx: ok if run meego-dm :"killed" if run "/usr/bin/mcompositor" :mcompositor: cannot connect to X server For the error 1, I installed mesa-dri-swrast-driver-7.8.99.1~gitb018ea19a3-3.5.armv7l.rpm and libtalloc-2.0.1-1.7.armv7l.rpm for the devkit8000. The problem is solved. For the error 2, I don't know how to fix it, I thinks maybe it is the problem why LCD is black. I use the latest 2.6 stable to build the kernel, and use the this kickstart file to create the image. My bootarg is setenv bootargs 'console=ttyS2,115200n8 root=/dev/nfs nfsroot=192.168.16.54:/home/rootfs,hard,tcp,rsize=65536,wsize=65536 ip=dhcp rw rootdelay=5 omapdss.def_disp=lcd omapfb.vram=0:2M,1:0M,2:0M omapfb.mode=lcd:800x480' Can you give some advice? The logs are attached. Thanks in advice! Chen 2010/9/26 gw zhang <[email protected]> HI Nelson, please refer to the attachment for the log file. 2010/9/25 Robert Nelson <[email protected]> On Sat, Sep 25, 2010 at 4:31 AM, gw zhang <[email protected]> wrote: > Great! It works well for me! > > Sorry for a stupid question: Before you give the patches for devkit8000, I > struggle for it for a long time. I don't know how to porting for a specific > board, what knowledge should I have to generate patches for devkit8000 if > you don't give it? Oh i cheated on that one and didn't really do any work, those were the patches merged in 2.6.36-rc's for the devkit8000.. from git i did: git format-patch -18 arch/arm/mach-omap2/board-devkit8000.c and only the first 11 are appropriate, as 12-16 are bits from the omap merge for 2.6.36.. btw, can you do Chen and I a favor... I need a complete boot log for comparison on a working devkit8000.. Using cutecom or a serial terminal that logs to a file.. Start logging.. Power up board Stop u-boot: type "printenv" reboot the board wait till login prompt shows up. un power board stop logging pastebin the file.. Regards, -- Robert Nelson http://www.rcn-ee.com/ ------------------------------------------------------------------------------ _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
