All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: beagleboard@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [beagleboard] Diff between Linux-2.6.27-omap1-dirty and Linux-2.6.27-omap1 ?
Date: Mon, 3 Nov 2008 13:04:59 -0800	[thread overview]
Message-ID: <20081103210458.GD28924@atomide.com> (raw)
In-Reply-To: <d82e647a0810312125q1e4760c4t6690d69e04b5c7b6@mail.gmail.com>

* Ming Lei <tom.leiming@gmail.com> [081031 21:26]:
> I also have this problem, even git-tree is not dirty.
> Why?

Looks like you've hit the ptebits problem.. See the arm-linux-kernel
mailing list archive or linux-omap list today for an experimental
patch to fix it.

Tony

> 
> Thanks!
> ------------------------------------------------------------
> Texas Instruments X-Loader 1.41
> Starting OS Bootloader...
> 
> 
> U-Boot 1.3.3 (Jul 10 2008 - 16:33:09)
> 
> OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
> OMAP3 Beagle Board + LPDDR/NAND
> DRAM:  128 MB
> NAND:  256 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Audio Tone on Speakers  ... complete
> Hit any key to stop autoboot:  0
> OMAP3 beagleboard.org #
> OMAP3 beagleboard.org #
> OMAP3 beagleboard.org # printenv
> bootargs=console=ttyS2,115200n8 ramdisk_size=8192 root=/dev/ram0 rw
> rootfstype=ext2 initrd=0x81600000f
> bootcmd=mmcinit;fatload mmc 0 0x80300000 uImage;fatload mmc 0
> 0x81600000 rd-ext2.bin;bootm 0x80300000
> stdin=serial
> stdout=serial
> stderr=serial
> 
> Environment size: 257/131068 bytes
> OMAP3 beagleboard.org # mmcinit;fatload mmc 0 0x80300000 ui3;bootm 0x80300000
> reading ui3
> 
> 1723104 bytes read
> ## Booting kernel from Legacy Image at 80300000 ...
>    Image Name:   Linux-2.6.28-rc2-omap1-05147-g82
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    1723040 Bytes =  1.6 MB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
> 
> Starting kernel ...
> 
> Uncompressing Linux...................................................................................
> 
> 
> 
> 
> 2008/10/31 Shivdas Gujare <shivdas.tech@gmail.com>:
> >
> > Hi All,
> >
> > I am working on testing Linux-2.6.27 omap kernel on beagle board.
> >
> > I cloned kernel from
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
> >
> > and checked out to tag v2.6.27-omap1, I loaded kernel on beagle board,
> > and was able to boot properly like....
> >
> > OMAP3 beagleboard.org # bootm 0x80300000
> > ## Booting kernel from Legacy Image at 80300000 ...
> >   Image Name:   Linux-2.6.27-omap1
> >   Image Type:   ARM Linux Kernel Image (uncompressed)
> >   Data Size:    1614320 Bytes =  1.5 MB
> >   Load Address: 80008000
> >   Entry Point:  80008000
> >   Verifying Checksum ... OK
> >   Loading Kernel Image ... OK
> > OK
> >
> > Now, I done some operations, like checkout to master, checkout to
> > v2.6.26-omap1 and v2.6.25-omap1, loaded corresponding uImages to
> > beagle board
> > and was able to boot board every time.
> >
> > After this, I again checkout to v2.6.27-omap1, compiled and loaded
> > uImage to beagleboard
> > But this time I am not able to boot the board.
> > and Got the message like
> >
> > OMAP3 beagleboard.org # bootm 0x80300000
> > ## Booting kernel from Legacy Image at 80300000 ...
> >   Image Name:   Linux-2.6.27-omap1-dirty
> >   Image Type:   ARM Linux Kernel Image (uncompressed)
> >   Data Size:    1669176 Bytes =  1.6 MB
> >   Load Address: 80008000
> >   Entry Point:  80008000
> >   Verifying Checksum ... OK
> >   Loading Kernel Image ... OK
> > OK
> >
> > Starting kernel ...
> >
> > Uncompressing Linux...........................................................................................................
> > done, booting the kernel.
> >
> > and it, stucks at here..
> >
> > Here, the only difference I observed is "Image Name:
> > Linux-2.6.27-omap1" and "Image Name:   Linux-2.6.27-omap1-dirty",
> > where uImage with second Image name is not booting.
> >
> > I think, I have done something wrong here, while compilation and checkout.
> >
> > I just want to know in what cases "-dirty" is appended to linux kernel
> > Image Names or anything I done wrong?
> >
> > Thanks for your Helps.
> >
> > Regards,
> > Shivdas
> >
> > --~--~---------~--~----~------------~-------~--~----~
> > You received this message because you are subscribed to the Google Groups "Beagle Board" group.
> > To post to this group, send email to discussion@beagleboard.org.
> > To unsubscribe from this group, send email to beagleboard-unsubscribe@beagleboard.org
> > For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en
> > -~----------~----~----~----~------~----~------~--~---
> >
> >
> 
> 
> 
> -- 
> Lei Ming
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

      reply	other threads:[~2008-11-03 21:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 13:08 Diff between Linux-2.6.27-omap1-dirty and Linux-2.6.27-omap1 ? Shivdas Gujare
2008-10-31 13:35 ` Alan Jenkins
2008-11-01  4:25 ` [beagleboard] " Ming Lei
2008-11-03 21:04   ` Tony Lindgren [this message]

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=20081103210458.GD28924@atomide.com \
    --to=tony@atomide.com \
    --cc=beagleboard@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.leiming@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 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.