public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: green <greenfreedom10@gmail.com>
To: Linux-OMAP List <linux-omap@vger.kernel.org>
Subject: Re: N810: linux-2.6.26-rc2-omap1 with muru.com N810 patches
Date: Thu, 15 May 2008 14:33:33 -0500	[thread overview]
Message-ID: <20080515193333.GA11713@swansys> (raw)
In-Reply-To: <20080515182840.GS8928@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 2313 bytes --]

On Thu, 2008.05.15, 136, Tony Lindgren wrote:
> * green <greenfreedom10@gmail.com> [080515 10:03]:
> > On Thu, 2008.05.15, 136, green wrote:
> > > I have built a Debian Sid armel chroot on the N810 and have compiled many 
> > > kernels in the chroot.  I send the kernels to the N810 using the flasher (-f 
> > > -k $IMAGE -R).
> > 
> > I've also built 2.6.26-rc2-omap1 (with muru.com N810 patches) on my amd64 
> > system using the gnueabi tools from emdebian.org.
> > 
> > gcc 4.3.0-4
> > binutils 2.18.1~cvs20080103-4
> > 
> > Same results.
> > >  - The NOKIA splash screen is displayed for about 20 seconds and then the N810 
> > > powers off.
> 
> Hmm, the patches I've posted should work fine to mount root from
> internal MMC card (assuming you have both cards inserted right now...)
> 
> You should see the white Nokia splash screen for few seconds, then
> the black framebuffer console with penguin.
> 
> I tarred up my n810 hacks to http://muru.com/linux/n8x0/ with the
> keyboard patches included.
> 
> Here's also a temporary test zImage:
> 
> http://muru.com/linux/n8x0/zImage-n8x0-2008-05-15
> 
> You can test that with:
> 
> $ flasher -k zImage-n8x0-2008-05-15 -l -b
> 
> I'll remove that zImage at some point soon because of my limited
> server bandwidth.. This zImage works with n810, and seemed to boot
> on n800 too.

Okay, I've got the zImage and updated patches; thanks.  This zImage does work, 
but fails to mount root device (maybe something I did wrong; I'll worry about 
that later).  Could you send the config you used?  Or maybe I'm doing 
something wrong when compiling.

I'm compiling on an amd64 system with the following packages (and their 
dependencies) from emdebian.org:
binutils-arm-linux-gnueabi 2.18.1~cvs20080103-4
cpp-4.3-arm-linux-gnueabi 4.3.0-4
g++-4.3-arm-linux-gnueabi 4.3.0-4
gcc-4.3-arm-linux-gnueabi 4.3.0-4

and in the Makefile:
CROSS_COMPILE   ?= arm-linux-gnueabi-

For now I'll try with the latest from linux-omap-2.6 with your patches.

> BTW, you need to disable rd mode with flasher --disable-rd-mode with
> the serial clock hack applied. Otherwise the boot won't complete. Or
> at least you should not have --set-rd-flags=serial-console set.

I don't have the serial-console flag set.


Thanks!

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-05-15 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 14:09 N810: linux-2.6.26-rc2-omap1 with muru.com N810 patches green
2008-05-15 16:14 ` Felipe Balbi
2008-05-15 18:19   ` green
2008-05-15 16:54 ` green
2008-05-15 18:28   ` Tony Lindgren
2008-05-15 19:33     ` green [this message]
2008-05-15 20:25       ` Tony Lindgren
2008-05-15 23:10         ` N810: linux-2.6.26-rc2-omap1 with muru.com N810 patches (success) green

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=20080515193333.GA11713@swansys \
    --to=greenfreedom10@gmail.com \
    --cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox