All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: fso-console-image problems
Date: Fri, 02 Dec 2011 14:08:07 +0000	[thread overview]
Message-ID: <4ED8DBC7.6080708@googlemail.com> (raw)
In-Reply-To: <201112021120.17762.GNUtoo@no-log.org>



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).

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).

> 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...




  reply	other threads:[~2011-12-02 14:15 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 [this message]
2011-12-02 14:52     ` Martin Jansa
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=4ED8DBC7.6080708@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=GNUtoo@no-log.org \
    --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.