From: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
To: meta-ti@yoctoproject.org
Subject: Re: Building for TI 8148 EVM
Date: Tue, 25 Oct 2011 14:32:59 +0200 [thread overview]
Message-ID: <4EA6AC7B.90809@ts.fujitsu.com> (raw)
In-Reply-To: <20111024183727.GF9156@denix.org>
Am 24.10.2011 20:37, schrieb Denys Dmytriyenko:
>> In the mean time you should be able to get around it by doing 'bitbake
>> mesa-dri' manually.
>
> Yep, I can confirm this issue. I had it fixed locally by adding mesa-dri to
> DEPENDS in xorg-xserver... Didn't have time to submit either a patch or a
> bugreport though.
Ok, with all the hints from this thread I was able to build an image.
Testing on my DM8148 EVM wasn't that much of a success, image boots to
console, but is lacking of the required (question: what do I need for
this EVM, anyone from TI can tell me?) xorg-modules. /etc/X11/xorg.conf
tries to load an intel driver which is definitely out of range for this
board. :-)
How can I see from the logs what xserver/xorg-components were built and
how can I add the missing ones?
TIA
Rainer
--
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE
Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany
Telephone: +49-821-804-3321
Telefax: +49-821-804-2131
Mail: mailto:Rainer.Koenig@ts.fujitsu.com
Internet ts.fujtsu.com
Company Details ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2011-10-25 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 9:07 Building for TI 8148 EVM Rainer Koenig
2011-10-21 9:14 ` Koen Kooi
2011-10-24 8:48 ` Rainer Koenig
2011-10-24 8:58 ` Koen Kooi
2011-10-24 9:05 ` Rainer Koenig
2011-10-24 9:20 ` Koen Kooi
2011-10-24 11:22 ` Koen Kooi
2011-10-24 18:37 ` Denys Dmytriyenko
2011-10-25 12:32 ` Rainer Koenig [this message]
2011-10-25 15:39 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA6AC7B.90809@ts.fujitsu.com \
--to=rainer.koenig@ts.fujitsu.com \
--cc=meta-ti@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.