public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: green <greenfreedom10@gmail.com>
Cc: 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 11:14:58 -0500	[thread overview]
Message-ID: <4530c67662adea689bad79e193a9323a@felipebalbi.com> (raw)
In-Reply-To: <20080515140914.GA30594@swansys>



On Thu, 15 May 2008 09:09:14 -0500, green <greenfreedom10@gmail.com> wrote:
> Hello, I am trying to run Debian Sid on a Nokia N810.  I have tried
several
> 
> different kernel sources and lots of different configs without seeing
> anything 
> but the NOKIA splash screen.  Therefore, my current goal has been reduced
> to 
> simply booting a kernel and seeing some text output from it so I know it
> is at 
> least attempting to boot.  Once I've succeeded in that I'll continue
> toward my 
> ultimate goal of running Debian Sid.
> 
> 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 have used these three different kernel sources with two results.
>  maemo 2008 kernel
>   http://repository.maemo.org/pool/maemo4.0.1/free/k/kernel-source-rx-34/
>  2.6.25-omap1
>   http://www.muru.com/linux/omap/patches/patch-2.6.25-omap1.bz2
>  2.6.26-rc2-omap1 with muru.com N810 patches
>   http://source.mvista.com/git/?p=linux-omap-2.6.git
>   http://www.muru.com/linux/n8x0/n8x0-2008-05-12.tar.gz
> 
> Always, one of these two happens after I flash the compiled zImage:
>  - The NOKIA splash screen is displayed for about 20 seconds and then the
> N810 
> powers off.
>  - The splash screen is shown for <1 second and the device resets (loop);
> I 
> have to remove the battery.

flasher --enable-rd-mode --set-rd-flags=serial-console,no-lifeguard-reset
-f

> 
> I have enabled CONFIG_FRAMEBUFFER_CONSOLE and disabled 
> CONFIG_FB_OMAP_MANUAL_UPDATE.  The last config I've tried (with 
> linux-2.6.26-rc2-omap1 +N810) is attached.
> 
> I'm using gcc 4.3.0-4 and binutils 2.18.1~cvs20080103-4 in Debian Sid.
> 
> I have enable R&D mode on the N810 and disabled the lifeguard-reset flag.
> 
> One of the N810 patches from muru.com changes the N810 machine number to
> 5555; 
> I've tried both that and the 1548, on the assumption that perhaps a
> bootloader 
> update has fixed the machine number.
> 
> I've used 'make n800_defconfig' (2.6.26-rc2-omap1 +N810) and changed only
> the 
> default cmdline without success.  Also I've used 'make
> nokia_2420_defconfig' 
> with the maemo kernel.

try also
flasher --set-root-device mmc

> 
> Note that the initfs, X-Loader, NOLO secondary bootloader, and NOLO cold 
> flasher ("2nd") images are all from the 
> RX-44_2008SE_2.2007.51-3_PR_COMBINED_MR0_ARM.bin maemo FIASCO (I guess)
> image.  
> The rootfs is probably from an older one (I never updated it) but I'm
> assuming 
> that the rootfs doesn't matter anyway.
> 
> Please ask for any more information that might be helpful.
> 
> Oh, and one more question that I ought to know the answer to by now:
> Is it okay to do 'make zImage', then change the config, then 'make
zImage'
> 
> again without doing a 'make clean', so long as nothing in the source has
> been 
> changed?  That saves a lot of time.

Yes, it's ok. ;-)

-- 
Best Regards,

Felipe Balbi
http://felipebalbi.com
me@felipebalbi.com


  reply	other threads:[~2008-05-15 16:15 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 [this message]
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
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=4530c67662adea689bad79e193a9323a@felipebalbi.com \
    --to=me@felipebalbi.com \
    --cc=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