All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Barr <andrew.james.barr@gmail.com>
To: openembedded-devel@openembedded.org
Subject: Re: Nokia 770, GPE, Angstrom
Date: Thu, 11 Jan 2007 12:37:02 -0500	[thread overview]
Message-ID: <1168537022.8701.10.camel@localhost> (raw)
In-Reply-To: <1168532784.21840.4.camel@localhost>

On Thu, 2007-01-11 at 11:26 -0500, Andrew J. Barr wrote:
> Hi,
> 
> I have flashed my Nokia 770 with a self-built rootfs using
> "angstrom-2007.1" as the DISTRO and "nokia770" as the MACHINE. Target
> was 'gpe-image', branch was org.openembedded.dev. I flashed it using
> Nokia's version 3 flasher:
> 
> ./flasher-3.0 -f -k zImage -r rootfs.bin
> 
> I applied the patch to sysvinit mentioned here[0].
> 
> It goes successfully. The device starts up to the Nokia logo (NOLO
> bootloader I assume) but the screen fades to white. According to the
> document linked below, the initial startup takes a while. Am I just
> being impatient or am I doing something wrong? I notice there's no
> initfs built by OE, not sure if this is needed.

It does not boot after about half hour. I think I know why:

I forgot that I had hacked the nokia770 build to use plain
xserver-kdrive instead of xserver-kdrive-omap. This is because it does
not build; the configure script fails because it is missing the
pkg-config file xextensions.pc. Searching the ML archives I see
pre-modular-X stuff has been removed from OE. Does updated, plain Kdrive
support the OMAP / Nokia 770 graphics or do I need to figure out how to
build (or file a bug against) the old Xomap server to run OE on my 770?

Regards,
Andrew Barr

> Regards,
> Andrew Barr
> 
> [0] http://downloads.kernelconcepts.de/maemo-oe.txt



  reply	other threads:[~2007-01-11 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11 16:26 Nokia 770, GPE, Angstrom Andrew J. Barr
2007-01-11 17:37 ` Andrew Barr [this message]
2007-01-11 17:51   ` 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=1168537022.8701.10.camel@localhost \
    --to=andrew.james.barr@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.