public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Cc: linux-omap@vger.kernel.org
Subject: Re: N810: latest linux-omap-2.6.git master
Date: Wed, 13 May 2009 12:12:19 +0300	[thread overview]
Message-ID: <20090513121219.43206b03.jhnikula@gmail.com> (raw)
In-Reply-To: <200905121818.13785.luke@dashjr.org>

On Tue, 12 May 2009 18:18:13 -0500
Luke Dashjr <luke@dashjr.org> wrote:

> > For me mmc is working. I'm booting through the modified initfs with
> > official major number 179 for /dev/mmcblk* device nodes.
> 
> Modified initfs? Is there something needed beyond copying the
> filesystem's modules?
> 
Actually I'm not using modules from initfs at all nor updating them but
I have compiled the ext2 in so that initfs can mount the ext2 formatted
root from mmc (flasher --set-root-device=mmc).

This device node update to initfs is required since Maemo 2.6.21
kernel & initfs are using major number 254 for mmcblk whereas newer
kernels are using 179.

I basically copied initfs from running system or fiasco image, I don't
remember, modified it on desktop and then created new jffs2 image out
of it. That can be then flashed with "flasher -f -n initfs.jffs2".

I think it would be possible to boot modified initfs also from another
mmc partition so that initfs on NAND can be intact.


-- 
Jarkko

  reply	other threads:[~2009-05-13  9:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-09 22:45 N810: latest linux-omap-2.6.git master Luke-Jr
2009-05-12  7:06 ` Jarkko Nikula
2009-05-12 23:18   ` Luke Dashjr
2009-05-13  9:12     ` Jarkko Nikula [this message]
2009-05-19  5:09       ` Luke-Jr
2009-05-19  6:42         ` Jarkko Nikula
2009-05-19 17:15           ` Tony Lindgren
2009-05-20 14:11             ` Kalle Valo
2009-05-20 15:13               ` Tony Lindgren
2009-05-20 19:05                 ` Jarkko Nikula
2009-05-20 21:29                   ` Max Filippov
2009-05-20 19:11                 ` Kalle Valo
2009-05-23  3:41                 ` green
2009-05-20 22:07         ` Max Filippov

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=20090513121219.43206b03.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=luke@dashjr.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