You do need to know that vesa fb has lower performance On 6/1/09, Dhananjay Joshi <[email protected]> wrote: > On Mon, Jun 1, 2009 at 9:39 PM, Yi Sun <[email protected]> wrote: > >> >> Two choices: >> 1. use fb driver for intel 82q35 (I don't know which driver it is) >> 2. usb vesa fb driver >> On Mon, 2009-06-01 at 19:51 +0530, Dhananjay Joshi wrote: >> > >> > >> > On Mon, Jun 1, 2009 at 8:27 AM, Yi Sun <[email protected]> wrote: >> > >> > Try to use VESA driver first to see if you can boot. >> > >> > On Sat, 2009-05-30 at 23:22 -0700, dhananjay wrote: >> > > I have built android x86 cupcake. i am trying to bring it on >> > my x86 >> > > desktop pc.after booting it was showing some issues >> > related to >> > > framebuffer >> > > so to fix them i built 3 new kernel modules as follows >> > > intelfb.ko >> > > i915.ko >> > > i2c-.....ko >> > > as per latest instructions available on x86-wiki and >> > modified >> > > corresponding >> > > Android.mk as well as init.rc to accumulate these >> > changes. >> > > when i tried to boot again, it is showing following >> > error >> > > >> > > "sh:can't access tty; job control turned off >> > > EGl_bad_surface. >> > > and couldnt launch gui.i'm getting shell prompt but >> > that too >> > > screen is flickering continuously. >> > > >> > > does anybody knows is this framebuffer problem or >> > anything else? >> > > can anybody point me where do i find correct >> > patch ,for x86 desktop >> > > framebuffer >> > > driver. >> > > and also in the source tree inside >> > vendor/asus/eee_701/modules/ >> > > drm_patches dir >> > > what this patches are all about? are these intel fb >> > driver patches ? >> > > and i need to patch kernel before building ? >> > > does anybody knows about this drm_patch dir? >> > > >> > > > >> > >> > >> > Hi >> > here is my lspci output >> > 00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM >> > Controller (rev 02) >> > 2 00:02.0 VGA compatible controller: Intel Corporation 82Q35 >> > Express Integrated Graphics Controller (rev 02) >> > 3 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 >> > Family) USB UHCI Controller #4 (rev 02) >> > 4 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 >> > Family) USB UHCI Controller #5 (rev 02) >> > 5 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 >> > Family) USB2 EHCI Controller #2 (rev 02) >> > 6 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 >> > Family) HD Audio Controller (rev 02) >> > 7 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) >> > PCI Express Port 1 (rev 02) >> > 8 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) >> > PCI Express Port 2 (rev 02) >> > 9 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) >> > PCI Express Port 3 (rev 02) >> > 10 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) >> > PCI Express Port 6 (rev 02) >> > 11 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 >> > Family) USB UHCI Controller #1 (rev 02) >> > 12 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 >> > Family) USB UHCI Controller #2 (rev 02) >> > 13 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 >> > Family) USB UHCI Controller #3 (rev 02) >> > 14 00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 >> > Family) USB UHCI Controller #6 (rev 02) >> > 15 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 >> > Family) USB2 EHCI Controller #1 (rev 02) >> > 16 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge >> > (rev 92) >> > 17 00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC >> > Interface Controller (rev 02) >> > 18 00:1f.2 IDE interface: Intel Corporation 82801IB (ICH9) 2 >> > port SATA IDE Controller (rev 02) >> > 19 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) >> > SMBus Controller (rev 02) >> > 20 00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 >> > Family) 2 port SATA IDE Controller (rev 02) >> > 21 02:00.0 IDE interface: Marvell Technology Group Ltd. >> > 88SE6121 SATA II Controller (rev b2) >> > 22 03:00.0 Ethernet controller: Marvell Technology Group Ltd. >> > 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) >> > >> > and m using vesafb driver. >> > >> > Regrads, >> > Dhananjay >> > >> > >> > > >> > >> >> >> > >> Hi > thnaks yi/luca > correct selection of vesa fb driver for desktop solved my issue. > m able to see android launcher on my desktop. > thanx for your support. > > Regards, > DJ > > > >
--~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
