public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Mik Prog <mikprog@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: OMAP 5912: new kernel, how to create a new file system?
Date: Tue, 20 Nov 2007 16:41:46 -0500	[thread overview]
Message-ID: <4743549A.4070101@balister.org> (raw)
In-Reply-To: <6a7f58da0711200959u1481a90y5b50e9a5c5827c82@mail.gmail.com>

I have a replacement kernel (based on 2.6.22) and root file system here:

http://elinux.org/OSK#Files

Philip

Mik Prog wrote:
> Dear all,
> 
> I am an absolute beginner with OMAP and Linux (I am working on a OSK 5912).
> Apologies if some of my questions have already been answered. I do
> look on google first, but sometime even if the topic has been treated
> I don't clearly understand...
> 
> Here my case:
> 1. I wanted recompile the kernel image using arm-linux-gcc 3.4.1 (I
> got the kernel sources 2.6.20 and applied the patch
> patch-2.6.20-omap1)
> 2. then I enabled on omap_osk-5912_defconf the USB configuration
> 3. I built the kernel and formatted for u-boot.
> 4. I transferred that to OMAP using tftpboot
> 5. $ using uname -a I see that the kernel image is still the old one!
> 
> Do I need to update the root file system as well?
> How could I create my own root file system based on the kernel version
> I've compiled?
> 
> thanks for any help.
> Mik
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> 

  parent reply	other threads:[~2007-11-20 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 17:59 OMAP 5912: new kernel, how to create a new file system? Mik Prog
2007-11-20 18:24 ` Hunter, Jon
2007-11-20 21:41 ` Philip Balister [this message]
2008-01-10  9:49   ` Mik Prog

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=4743549A.4070101@balister.org \
    --to=philip@balister.org \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=mikprog@gmail.com \
    /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