Android port for beagle(OMAP3530)- Code Released

Jay,

JayBird wrote:

Hi Rupesh,

I went through the build process again:)  Overall, I was able create a
working system; however, it wasn't perfect.

I was able to build the 2.6.25 kernel with no problems.  I haven't
tried the 2.6.27 branch yet; however, I think I will have some time
tomorrow to try it out.  I was also able to build  Android (haven't
tried cupcake yet) with your patches; however, ALSA fails (See error
below).  As a result, I had to remove that option from my
BoardConfig.mk.  Note, I did apply the Alsa_sound.patch.

As I built the system, I took some notes.  Below is list of changes
that you may want to integrate in your build instructions:

1. If one wants to cut-and-paste the patch commands, either the patch
files need to be re-named to match the text, or the text modified to
reflect the patch file names (i.e qwerty.kl.patch should be
Qwerty.patch)

2. May want to add

      $ make

    in the Compile Build

3. In the Alsa_sound section, you ask the user to apply the patches,
but give the incorrect Root Dir.  I think you it may flow better if re-
work it a little:

                1 - $ cd ~
                2 - Clone alsa-lib from
                         $ git clone git://android.git.kernel.org/platform/external/alsa-lib.git
                3 - Clone ALSA based libaudio
                         $ git clone git://android.git.kernel.org/platform/hardware/alsa_sound.git
                 4 - Apply following patches to build
                         Root DIR : alsa_sound
                         Media:alsa_sound.patch
                         $ patch -p1 <  Alsa_sound.patch

                  5- Change directory to the root "Android_build"
                         $ cd Android_build
                  6 - Add ALSA audio support to the board config file
and comment our generic audio support.
                        $ vim Android_build/build/target/board/generic/
BoardConfig.mk
                                 add BOARD_USES_ALSA_AUDIO := true
                                 #BOARD_USES_GENERIC_AUDIO := true
                  7 - Copy ALSA support supporting code from steps 3
and 4 above
                               $cp -a ~/alsa-lib  external
                               $cp -a ~/alsa_sound hardware

4. I think the instructions in the Ownership section are incorrect.
The following seem to work for me.

                  1. Do the following as either root or use sudo
                         $ cd ~/Android_rfs
                         $ chown -R root.root *
                         $ chmod -R 777 system/user/keychars

If I compile Andorid with ALSA support, I get the following error:

target arm C++: libaudio <= hardware/alsa_sound/AudioHardwareStub.cpp
hardware/alsa_sound/AudioHardwareStub.cpp: In member function 'virtual
android::AudioStreamOut* android::AudioHardwareStub::openOutputStream
(int, int, uint32_t, android::status_t*)':
hardware/alsa_sound/AudioHardwareStub.cpp:52: error: cannot allocate
an object of abstract type 'android::AudioStreamOutStub'
hardware/alsa_sound/AudioHardwareStub.h:30: note:   because the
following virtual functions are pure within
'android::AudioStreamOutStub':
hardware/libhardware/include/hardware/AudioHardwareInterface.h:88:
note: 	virtual android::status_t android::AudioStreamOut::standby()
make: *** [out/target/product/generic/obj/SHARED_LIBRARIES/
libaudio_intermediates/AudioHardwareStub.o] Error 1
jayw@Rubicon:~/Android/beagleboard/mydroid$

  

Have you synced you Android build with latest code. Patches mentioned in wiki are working with latest code drop. There have been quiet few changes related to sound in HAL. Also we are working on 2.6.27 kernel branch, as all development is moved to it and we expect all code base to work with 2.6.27 branch.
I will look at rest of your suggestions soon.

Regards,

Jay,
JayBird wrote:

Hey Rupesh,

I grab the beagle.android-2.6.27 branch for the kernel, and it appears
the omap3_beagle_android_defconfig file is a diff file.  Did you check
in the right file?

  

Please check now. lots of patches are making life miserable. :slight_smile:

Regards,

Hi,
Thanks for the reply. i tried what you asked, and i think your right
about the LCD not being initialised. When i try the 'cat file > /dev/
fb0' nothing appears on screen.
zygote is running and a bunch of other stuff too (listed below). After
a brief scan over the logcat, i didnt notice anything that stood out.
Ill keep trying, maybe with a different monitor and/or cable.
Will keep you updated

# ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 284 192 c00a8520 0000c58c S /init
root 2 0 0 0 c006389c 00000000 S kthreadd
root 3 2 0 0 c0055ac4 00000000 S ksoftirqd/0
root 4 2 0 0 c0075d80 00000000 S watchdog/0
root 5 2 0 0 c0060ad0 00000000 S events/0
root 6 2 0 0 c0060ad0 00000000 S khelper
root 12 2 0 0 c0060ad0 00000000 S suspend
root 74 2 0 0 c0060ad0 00000000 S kblockd/0
root 84 2 0 0 c0060ad0 00000000 S twl4030-irqchip
root 85 2 0 0 c01b8910 00000000 S twl4030-irq
root 95 2 0 0 c0060ad0 00000000 S ksuspend_usbd
root 101 2 0 0 c01dcb38 00000000 S khubd
root 113 2 0 0 c0060ad0 00000000 S kmmcd
root 128 2 0 0 c0060ad0 00000000 S kondemand/0
root 136 2 0 0 c0080ed8 00000000 S pdflush
root 137 2 0 0 c0080ed8 00000000 S pdflush
root 138 2 0 0 c00847b4 00000000 S kswapd0
root 140 2 0 0 c0060ad0 00000000 S aio/0
root 141 2 0 0 c0060ad0 00000000 S nfsiod
root 317 2 0 0 c01d356c 00000000 S mtdblockd
root 367 2 0 0 c0060ad0 00000000 S rpciod/0
root 372 2 0 0 c02059a4 00000000 S mmcqd
root 629 1 740 332 c00534f8 afe0d0fc S /system/bin/sh
system 630 1 812 268 c01b60c8 afe0c35c S /system/bin/
servicemanager
root 632 1 1848 368 ffffffff afe0ccec S /system/bin/
mountd
root 633 1 668 268 c024a848 afe0ccec S /system/bin/
debuggerd
radio 634 1 3276 616 ffffffff afe0c9cc S /system/bin/rild
root 635 1 44824 5628 c00796c0 ad05b2d8 D zygote
media 636 1 18232 3840 ffffffff afe0c35c S /system/bin/
mediaserver
bluetooth 638 1 1168 568 c00a8520 afe0d2cc S /system/bin/dbus-
daemon
root 640 1 804 276 c024a848 afe0ccec S /system/bin/
installd
root 641 1 1272 124 ffffffff 0000e774 S /sbin/adbd
root 651 629 888 344 00000000 afe0c0bc R ps

Rupesh,


This could be silly but how can one play mp3 files on android i did the steps on your site

mount -t vfat /dev/mmcblk0p1 /sdcard
$setprop EXTERNAL_STORAGE_STATE mounted
$am broadcast -a android.intent.action.MEDIA_MOUNTED --ez read-only false -d  file:///sdcard

then i get

Broadcasting: Intent { action=android.intent.action.MEDIA_MOUNTED data=file:///sdcard (has extras) }

the card is getting mounted but the music app is not able to search any music.

Vishal,
Copy *.mp3 file on vfat formatted partition on SD card. (/dev/mmcblk0p1) , mount partition on RFS.
$mount -t vfat /dev/mmcblk0p1 /sdcard
Follow rest of commands as stated on wiki page.

Regards,

Jay,
We have incorporated most of your suggestions, Please check wiki and let me know your feedback.

Thanks,

JayBird wrote:

No need to worry, its working now. It was a dodgy HDMI-DVI cable i was
using.
The original uImage didnt work with my keyboard/mouse setup at all.
After compiling my own uImage, it works (kinda).
Keeps moaning about softkeys and certain keys dont work like back etc.
(so when im in setting or something, i cant exit to main screen, so
have to restart). probably the weird keyboard ive got. (i tried to do
the qwerty.patch also)
Thanks for the help!

You can look in /system/xbin and there are a bunch of debugging
tools. There is one called getevent or evtest or something like that,
and if you run it, you will see the keycodes dump to the screen. You
can use that info to modify qwerty.kl

Also, there are some settings you can change from the ui (either under
settings or developer tools) that allows the red power button (end on
keyboard) return to the home screen rather than blanking the screen.

I found that to work better than the home key.

-Howard

Jay,
JayBird wrote:

Hi Rupesh,

I did a repo sync on my cupcake branch, and I'm still have problems
with the ALSA.  Could you be more specific on what I need to do to
sync up my Android environment?

  

We tested ALSA patches on master branch and not on cupcake, as it is a development branch and stable features of cupcake are merged regularly with master.

ie.working with a branch obtained by:-
$ repo init -u git://android.git.kernel.org/platform/manifest.git
$ repo sync

and NOT working with a branch obtained by:-
$ repo init -u git://android.git.kernel.org/platform/manifest.git -b cupcake
$ repo sync

Are you facing problems with master branch ? We have compiled build successfully with ALSA patches on master branch.
You can try cleaning build and recompiling or take fresh build and try again, we have observed that sometimes if you repo sync precompiled build, then it do not get compiled unless you clean it.

$make clobber → cleans build
$repo sync
$make

Regards,

Hi all,
I have a couple of doubts on adding the patch for BB to the android
baseline.

1. I have downloaded the latest baseline from the android git
following the instructions in the page
http://source.android.com/download.
can anybody tell me which is the version of kernel that gets
downloaded after this?
From some of the posts I guess it might be 2.6.27. I would like to
confirm on that so that I can take the appropriate branch from the
patch as well.

2. Is there a file in the kernel source that stores the version
number? Can someone tell me which would that file be in case it
exists?

Thank you in advance,
Regards
Kozak

Kozak,

kozak wrote:

Hi all,
I have a couple of doubts on adding the patch for BB to the android
baseline.

1. I have downloaded the latest baseline from the android git
following the instructions in the page
http://source.android.com/download.
can anybody tell me which is the version of kernel that gets
downloaded after this?
  

2.6.27

From some of the posts I guess it might be 2.6.27. I would like to
confirm on that so that I can take the appropriate branch from the
patch as well.

2. Is there a file in the kernel source that stores the version
number? Can someone tell me which would that file be in case it
exists?

Check first 3 lines of following file:-
android_build/kernel/Makefile

Regards,

Hi, all:
When doing the porting Android port for beagle, some problem happens like below:
step1: successully Getting Android build from http://source.android.com/download,
problem met: a lots time lost to communication with the downloading
website. solution is just repeating repo sync. After downloading, make succesully.
step2: Apply tls & gl wrapper patch given below to Android build
No problem with applying the patch for gl wrapper but problem met with applying the patch for tls and it gives error info: tls.h file not available. just skip. This is not solved.
Does anybody know how to fix this? Thanks a lot.

step 3 do ALSA Support.
do substep 1-7 good.
in substep 8: Compile build, when make, it gives lots of error info,
don’t know how to fix?
Anybody can help me? The error info is pasted below
Thank you very much in advance.
Frank

build/core/main.mk:180: implicitly installing apns-conf_sdk.xml
target arm C++: libaudio <= hardware/alsa_sound/AudioHardwareInterface.cpp
In file included from hardware/alsa_sound/AudioHardwareInterface.cpp:27:
hardware/alsa_sound/AudioHardwareStub.h:24:40: error: hardware/AudioHardwareBase.h: No such file or directory
In file included from hardware/alsa_sound/AudioHardwareInterface.cpp:27:
hardware/alsa_sound/AudioHardwareStub.h:30: error: expected class-name before ‘{’ token
hardware/alsa_sound/AudioHardwareStub.h:40: error: expected ‘,’ or ‘…’ before ‘<’ token
hardware/alsa_sound/AudioHardwareStub.h:40: error: ISO C++ forbids declaration of ‘Vector’ with no type
hardware/alsa_sound/AudioHardwareStub.h: In member function ‘virtual int android::AudioStreamOutStub::format() const’:
hardware/alsa_sound/AudioHardwareStub.h:36: error: ‘AudioSystem’ has not been declared
hardware/alsa_sound/AudioHardwareStub.h: At global scope:
hardware/alsa_sound/AudioHardwareStub.h:43: error: expected class-name before ‘{’ token
hardware/alsa_sound/AudioHardwareStub.h:52: error: expected ‘,’ or ‘…’ before ‘<’ token
hardware/alsa_sound/AudioHardwareStub.h:52: error: ISO C++ forbids declaration of ‘Vector’ with no type
hardware/alsa_sound/AudioHardwareStub.h: In member function ‘virtual int android::AudioStreamInStub::format() const’:
hardware/alsa_sound/AudioHardwareStub.h:49: error: ‘AudioSystem’ has not been declared
hardware/alsa_sound/AudioHardwareStub.h: At global scope:
hardware/alsa_sound/AudioHardwareStub.h:57: error: expected class-name before ‘{’ token
hardware/alsa_sound/AudioHardwareStub.h:74: error: ISO C++ forbids declaration of ‘AudioStreamOut’ with no type
hardware/alsa_sound/AudioHardwareStub.h:74: error: ‘AudioStreamOut’ declared as a ‘virtual’ field
hardware/alsa_sound/AudioHardwareStub.h:74: error: expected ‘;’ before ‘’ token
hardware/alsa_sound/AudioHardwareStub.h:80: error: ISO C++ forbids declaration of ‘AudioStreamIn’ with no type
hardware/alsa_sound/AudioHardwareStub.h:80: error: ‘AudioStreamIn’ declared as a ‘virtual’ field
hardware/alsa_sound/AudioHardwareStub.h:80: error: expected ‘;’ before '
’ token
hardware/alsa_sound/AudioHardwareStub.h:88: error: expected ‘,’ or ‘…’ before ‘<’ token
hardware/alsa_sound/AudioHardwareStub.h:88: error: ISO C++ forbids declaration of ‘Vector’ with no type
hardware/alsa_sound/AudioHardwareStub.h:92: error: expected ‘,’ or ‘…’ before ‘<’ token
hardware/alsa_sound/AudioHardwareStub.h:92: error: ISO C++ forbids declaration of ‘Vector’ with no type
In file included from hardware/alsa_sound/AudioHardwareInterface.cpp:28:
hardware/alsa_sound/AudioHardwareALSA.h:116: error: ‘Mutex’ does not name a type
hardware/alsa_sound/AudioHardwareALSA.h:130: error: expected class-name before ‘,’ token
hardware/alsa_sound/AudioHardwareALSA.h:163: error: expected ‘,’ or ‘…’ before ‘<’ token
hardware/alsa_sound/AudioHardwareALSA.h:163: error: ISO C++ forbids declaration of ‘Vector’ with no type
hardware/alsa_sound/AudioHardwareALSA.h:179: error: expected class-name before ‘,’ token
hardware/alsa_sound/AudioHardwareALSA.h:213: error: expected ‘,’ or ‘…’ before ‘<’ token
hardware/alsa_sound/AudioHardwareALSA.h:213: error: ISO C++ forbids declaration of ‘Vector’ with no type
hardware/alsa_sound/AudioHardwareALSA.h:228: error: expected class-name before ‘{’ token
hardware/alsa_sound/AudioHardwareALSA.h:260: error: ISO C++ forbids declaration of ‘AudioStreamOut’ with no type
hardware/alsa_sound/AudioHardwareALSA.h:260: error: ‘AudioStreamOut’ declared as a ‘virtual’ field
hardware/alsa_sound/AudioHardwareALSA.h:260: error: expected ‘;’ before ‘’ token
hardware/alsa_sound/AudioHardwareALSA.h:267: error: ISO C++ forbids declaration of ‘AudioStreamIn’ with no type
hardware/alsa_sound/AudioHardwareALSA.h:267: error: ‘AudioStreamIn’ declared as a ‘virtual’ field
hardware/alsa_sound/AudioHardwareALSA.h:267: error: expected ‘;’ before '
’ token
hardware/alsa_sound/AudioHardwareALSA.h:282: error: expected ‘,’ or ‘…’ before ‘<’ token
hardware/alsa_sound/AudioHardwareALSA.h:282: error: ISO C++ forbids declaration of ‘Vector’ with no type
hardware/alsa_sound/AudioHardwareALSA.h:292: error: ‘Mutex’ does not name a type
hardware/alsa_sound/AudioHardwareInterface.cpp:88: error: expected constructor, destructor, or type conversion before ‘*’ token
hardware/alsa_sound/AudioHardwareInterface.cpp:236: error: expected `}’ at end of input
make: *** [out/target/product/generic/obj/SHARED_LIBRARIES/libaudio_intermediates/AudioHardwareInterface.o] Error 1
|

Frank,
There have been changes in android code base recently, File “libc/include/sys/tls.h” no more exist in build. Also they are modifying audio interface in HAL layer, due to which ALSA is broken in latest build. We are looking into it, and will update about it soon.
By that time you can try using pre-build binaries which we have compiled against older android build.
Regards, frank zhu wrote:

Hi, all:
When doing the porting Android port for beagle, some problem happens like below:
step1: successully Getting Android build from http://source.android.com/download,
problem met: a lots time lost to communication with the downloading
website. solution is just repeating repo sync. After downloading, make succesully.
step2: Apply tls & gl wrapper patch given below to Android build
No problem with applying the patch for gl wrapper but problem met with applying the patch for tls and it gives error info: tls.h file not available. just skip. This is not solved.
Does anybody know how to fix this? Thanks a lot.

step 3 do ALSA Support.
do substep 1-7 good.
in substep 8: Compile
build, when make, it gives lots of error info,
don't know how to fix?
Anybody can help me? The error info is pasted below
Thank you very much in advance.
Frank

build/core/main.mk:180: implicitly installing apns-conf_sdk.xml
target arm C++: libaudio <= hardware/alsa_sound/AudioHardwareInterface.cpp
In file included from hardware/alsa_sound/AudioHardwareInterface.cpp:27:
hardware/alsa_sound/AudioHardwareStub.h:24:40: error: hardware/AudioHardwareBase.h: No such file or directory
In file included from hardware/alsa_sound/AudioHardwareInterface.cpp:27:
hardware/alsa_sound/AudioHardwareStub.h:30: error: expected class-name before '{' token
hardware/alsa_sound/AudioHardwareStub.h:40: error: expected ',' or '...' before '<' token
hardware/alsa_sound/AudioHardwareStub.h:40: error: ISO C++ forbids declaration of 'Vector' with no
type
hardware/alsa_sound/AudioHardwareStub.h: In member function 'virtual int android::AudioStreamOutStub::format() const':
hardware/alsa_sound/AudioHardwareStub.h:36: error: 'AudioSystem' has not been declared
hardware/alsa_sound/AudioHardwareStub.h: At global scope:
hardware/alsa_sound/AudioHardwareStub.h:43: error: expected class-name before '{' token
hardware/alsa_sound/AudioHardwareStub.h:52: error: expected ',' or '...' before '<' token
hardware/alsa_sound/AudioHardwareStub.h:52: error: ISO C++ forbids declaration of 'Vector' with no type
hardware/alsa_sound/AudioHardwareStub.h: In member function 'virtual int android::AudioStreamInStub::format() const':
hardware/alsa_sound/AudioHardwareStub.h:49: error: 'AudioSystem' has not been declared
hardware/alsa_sound/AudioHardwareStub.h: At global scope:
hardware/alsa_sound/AudioHardwareStub.h:57: error: expected class-name before '{'
token
hardware/alsa_sound/AudioHardwareStub.h:74: error: ISO C++ forbids declaration of 'AudioStreamOut' with no type
hardware/alsa_sound/AudioHardwareStub.h:74: error: 'AudioStreamOut' declared as a 'virtual' field
hardware/alsa_sound/AudioHardwareStub.h:74: error: expected ';' before '*' token
hardware/alsa_sound/AudioHardwareStub.h:80: error: ISO C++ forbids declaration of 'AudioStreamIn' with no type
hardware/alsa_sound/AudioHardwareStub.h:80: error: 'AudioStreamIn' declared as a 'virtual' field
hardware/alsa_sound/AudioHardwareStub.h:80: error: expected ';' before '*' token
hardware/alsa_sound/AudioHardwareStub.h:88: error: expected ',' or '...' before '<' token
hardware/alsa_sound/AudioHardwareStub.h:88: error: ISO C++ forbids declaration of 'Vector' with no type
hardware/alsa_sound/AudioHardwareStub.h:92: error: expected ',' or '...' before '<' token
hardware/alsa_sound/AudioHardwareStub.h:92: error: ISO C++
forbids declaration of 'Vector' with no type
In file included from hardware/alsa_sound/AudioHardwareInterface.cpp:28:
hardware/alsa_sound/AudioHardwareALSA.h:116: error: 'Mutex' does not name a type
hardware/alsa_sound/AudioHardwareALSA.h:130: error: expected class-name before ',' token
hardware/alsa_sound/AudioHardwareALSA.h:163: error: expected ',' or '...' before '<' token
hardware/alsa_sound/AudioHardwareALSA.h:163: error: ISO C++ forbids declaration of 'Vector' with no type
hardware/alsa_sound/AudioHardwareALSA.h:179: error: expected class-name before ',' token
hardware/alsa_sound/AudioHardwareALSA.h:213: error: expected ',' or '...' before '<' token
hardware/alsa_sound/AudioHardwareALSA.h:213: error: ISO C++ forbids declaration of 'Vector' with no type
hardware/alsa_sound/AudioHardwareALSA.h:228: error: expected class-name before '{' token
hardware/alsa_sound/AudioHardwareALSA.h:260: error: ISO C++ forbids
declaration of 'AudioStreamOut' with no type
hardware/alsa_sound/AudioHardwareALSA.h:260: error: 'AudioStreamOut' declared as a 'virtual' field
hardware/alsa_sound/AudioHardwareALSA.h:260: error: expected ';' before '*' token
hardware/alsa_sound/AudioHardwareALSA.h:267: error: ISO C++ forbids declaration of 'AudioStreamIn' with no type
hardware/alsa_sound/AudioHardwareALSA.h:267: error: 'AudioStreamIn' declared as a 'virtual' field
hardware/alsa_sound/AudioHardwareALSA.h:267: error: expected ';' before '*' token
hardware/alsa_sound/AudioHardwareALSA.h:282: error: expected ',' or '...' before '<' token
hardware/alsa_sound/AudioHardwareALSA.h:282: error: ISO C++ forbids declaration of 'Vector' with no type
hardware/alsa_sound/AudioHardwareALSA.h:292: error: 'Mutex' does not name a type
hardware/alsa_sound/AudioHardwareInterface.cpp:88: error: expected constructor, destructor, or type conversion before '*'
token
hardware/alsa_sound/AudioHardwareInterface.cpp:236: error: expected `}' at end of input
make: *** [out/target/product/generic/obj/SHARED_LIBRARIES/libaudio_intermediates/AudioHardwareInterface.o] Error 1

Hi Rupesh,

i follow the Android Porting Guide to Beagle Board (checkout the
2.6.27 kernel source) to port Android on my Beagle Board.

After all the things are done, I copy the uImage and root file system
to different separations (fat32/ext3) in a SD card.
Then use this SD card to boot the Beagle Board. Following is my boot
arguments:

console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2 video=omapfb:mode:
1024x768@60 init=/init rootfstype=ext3 rw rootdelay=1 nohz=off

mmcinit; fatload mmc 0 0x80300000 uImage; bootm 0x80300000

The teraterm console will display much information, but the LCD can
not show anything which said that it is it is out of the range.
(Neither Android booting screen nor Android robot are shown)

It seems that the "video=omapfb:mode:1024x768@60" does not work.
(After booting, I can access the file system via teraterm console.)

How can I fix this problem to show Android main screen on my LCD?
(When typing the booting arguments, the beagleboard.org LOGO is shown
correctly on LCD)

BTW, I found a Linux OMAP repository that adds a list of common video
modes and allows one to be selected with video=omapfb:mode:name on the
command line.
Check here: http://git.mansr.com/?p=linux-omap;a=commitdiff;h=80fe5350fcb8feeae2db01b0173c39077b656ecf
The source code on embinux git seems not add this function?
Hope this will help you.

Sincerely,
Ken

Ken,

wrote: Try out with We have tested it with video=omapfb:mode:1280x720@50. It is working for us. I am not expert to comment about whether “video=omapfb:mode:1024x768@60” is supported in our code base. But i definitely find support for this mode present. Please check. Regards,

Frank,
We have fixed step 2. ie.
step2: Apply tls & gl wrapper patch given below to Android build

Now you can apply both patches successfully. We have tested it against todays build. While we are still looking into ALSA issue.
Please let me know if you are still facing problems with step2.

Regards,
Rupesh Gujare wrote:

Hi,
  I also meet the lcd problem when I boot the android binary from
embinux.
  The LCD monitor OSD show the message "Out of Range", I tried another
resolution
and
  H/V sync frequency, but the problem still exist.

I compile the kernel 2.6.27 patched from embinux by myself,
and open the "Bootup logo" config, I cannot see penguin icon at
booting,
but i can see the beagleboard logo at u-boot.
I think the lcd driver doesn't match my lcd screen, is that right?
My both LCDs (17", 19") have the smae problem.
I check the lcd driver (lcd_omap3beagle.c, omapfb_main.c, dispc.c)
and
have no idea to modify it. Any suggestion is appreciated.

PS: the boot argument is as following:
setenv bootargs console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2
video=omapfb:mode:1280x720@50 init=/init rootfstype=ext2 rw
rootdelay=1 nohz=off

Hi Rupesh,

Thanks for your suggestion.

Finally I solve the problem after connecting the beagle board to
another LCD without chaning any configurations.

It seems that the old LCD (CMV CT-726D) does not support the output
signal or something.
When connecting to a new LCD (BenQ E2200HD), everything works fine.
(video=omapfb:mode:1024x768@50 is OK)

I have no idea about how to choose a suitable LCD.
Maybe Vincent Liang need to find another LCD that support the output
signal.

Best Regards,
Ken