From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: fso-console-image problems
Date: Fri, 2 Dec 2011 15:52:56 +0100 [thread overview]
Message-ID: <20111202145256.GD3770@jama.jama.net> (raw)
In-Reply-To: <4ED8DBC7.6080708@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 2535 bytes --]
On Fri, Dec 02, 2011 at 02:08:07PM +0000, Mr Dash Four wrote:
>
>
> Denis 'GNUtoo' Carikli wrote:
> > What are you using?
> > SHR-core or openembedded classic?
> >
> Don't know if I am honest - there is a (very good) wiki page I have been
> following to build this ->
> http://www.openembedded.org/wiki/Getting_started. I presume it is
> openembedded classic since I downloaded all the stuff from that page
> (git://github.com/openembedded/openembedded.git is the repository used).
So yes this is OE-classic.
For building SHR you should follow SHR instructions:
http://wiki.shr-project.org/trac/wiki/Building%20SHR
Where are instructions for building from OE-classic as well as new
layers, but with htcdream there is problem in oe-core, see this thread:
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/010993.html
> As I indicated earlier, I successfully built the shr-image (GUI-based) -
> it boots up OK on my smartphone, but I have no luck whatsoever with the
> console (i.e. just cli) images - I tried two: "console-image" and
> "fso-console-image", both unsuccessful (they do build, but my smartphone
> is having problems booting up properly with these).
I'm not familiar with htcdream, but this looks like some problem with kernel fb
driver, you can try to boot shr-image, setup ssh access and then
shutdown xserver (with /etc/init.d/xserver-nodm stop) to see if you get
console login (check inittab if it's starting getty there) and also try
other vts with chvt.
If it works you can prepare console-image with right
/etc/network/interfaces to be able to ssh in as soon as it boots and
then debug those stripes over ssh too.
Well if you can get serial console to htcdream then it would be even
easier.
> > If you are using shr-core you need to fix that file:
> > openembedded-core/meta/conf/machine/include/arm/arch-armv6.inc
> > to include support for armv6-novfp and add a tune file for the CPU of the
> > htcdream and then require that cpu tune file in the htcdream machine recipe.
> >
> I don't know whether I would need this. I also discovered yesterday that
> there is another openembedded git repository on freesmartphone.org
> (git://git.freesmartphone.org/openembedded.git), but not sure whether
> this is the same as the one I have been using...
This is usually used only by FSO people without R/W access to OE git to
prepare some changes.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2011-12-02 14:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 1:57 fso-console-image problems Mr Dash Four
2011-12-02 10:20 ` Denis 'GNUtoo' Carikli
2011-12-02 14:08 ` Mr Dash Four
2011-12-02 14:52 ` Martin Jansa [this message]
2011-12-02 15:12 ` Mr Dash Four
2011-12-02 15:46 ` Martin Jansa
2011-12-02 16:20 ` Mr Dash Four
2011-12-02 16:25 ` Martin Jansa
2011-12-02 17:27 ` Denis 'GNUtoo' Carikli
2011-12-02 17:42 ` Mr Dash Four
2011-12-02 20:06 ` Mr Dash Four
2011-12-02 22:24 ` Denis 'GNUtoo' Carikli
2011-12-02 23:35 ` Mr Dash Four
2011-12-02 23:50 ` Mr Dash Four
2011-12-03 9:46 ` Denis 'GNUtoo' Carikli
2011-12-03 16:37 ` Mr Dash Four
2011-12-03 16:52 ` Martin Jansa
2011-12-03 17:47 ` Mr Dash Four
2011-12-03 18:03 ` Martin Jansa
2011-12-03 18:35 ` Mr Dash Four
2011-12-04 12:39 ` Mr Dash Four
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=20111202145256.GD3770@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.