Bug 5182 - [Beagleboard xM]X can not startup with 3.10 kernel
Summary: [Beagleboard xM]X can not startup with 3.10 kernel
Status: RESOLVED WONTFIX
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-yocto (show other bugs)
Version: 1.5
Hardware: Beagleboard arm
: Medium+ normal
Target Milestone: 1.5.1
Assignee: Liming Wang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-09-13 09:51 UTC by Yi Zhao
Modified: 2014-03-13 15:14 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
xorg.0.log (6.18 KB, text/x-log)
2013-09-13 09:51 UTC, Yi Zhao 		no flags Details
A sato build fix provided as a small layer. (580 bytes, application/x-gtar-compressed)
2014-03-02 03:55 UTC, Kevin Cribbs 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2013-09-13 09:51:38 UTC 
Created attachment 1495 [details]
xorg.0.log

Image location: http://autobuilder.yoctoproject.org/pub/releases/1.5_M5.rc1/
Git rev: master/566ca1e4769b4ec7e3f6c6a98bb817db2221cf82

The X can not start up with 1.5 M5 rc1 build.
There is no /dev/fb device.

u-boot args:
setenv bootcmd 'mmc rescan; fatload mmc 0:1 0x80300000 zImage; bootz 0x80300000'
setenv bootargs 'console=tty0 console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootwait rootfstype=ext3 ro'
boot
Comment 1 Yi Zhao 2013-11-22 06:09:32 UTC 
This issue still happens on 1.6 20131119 build.
git rev: master/215dab864e7cf74394840621ad0754db593708f1
Comment 2 Bruce Ashfield 2013-11-22 16:28:58 UTC 
I unfortunately don't have a display to test this with, so we'll hunt for someone
that can look at the issue. We are also switching to the beagleboneblack, so
this bug will likely be closed as part of that switch.
Comment 3 Yi Zhao 2013-12-19 09:02:58 UTC 
This issue still exists in 1.5.1 rc2:
Comment 4 Kevin Cribbs 2014-02-28 15:14:42 UTC 
When I tested a recent build (poky-6a708c3edb5da3d73730eaf21d8c6c4f79972e9d) with a Beagleboard XM, the display worked after enabling CONFIG_PANEL_TFP410 in the kernel configuration. The display was connected to the DVI-D output. I have also confirmed this change worked with a platform using the same processor and LCD (but an older 3.10 build). Because the original bug report included the boot args, this is the cat /proc/cmdline output: console=tty0 console=ttyO2,115200n8 debug consoleblank=0 mpurate=auto buddy=none camera=none vram=16M omapfb.mode=dvi:hd720 omapfb.vram=0:8M,1:4M,2:4M omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
Comment 5 Kevin Cribbs 2014-03-02 03:55:41 UTC 
Created attachment 1790 [details]
A sato build fix provided as a small layer.

A sato build fix provided as a small layer.
Comment 6 Yi Zhao 2014-03-04 08:47:11 UTC 
(In reply to comment #5)
> Created attachment 1790 [details]
> A sato build fix provided as a small layer.
> 
> A sato build fix provided as a small layer.

Thanks, Kevin.

I tested it with poky/5ab9d7e28f987fba8bab03bb7851c263f746c208 . After enabled Device Drivers -> Graphics support -> OMAP2+ Display Subsystem support -> OMAP2/3 Display Device Drivers -> TFP410 DPI-to-DVI chip , the display worked without problems.
Comment 7 Darren Hart 2014-03-13 15:14:39 UTC 
This BSP will be replaced with one for the BeagleBone Black. For Beagleboard xM support, the TI BSP should be used instead of this one. Closing as will not fix.