From: Belisko Marek <marek.belisko@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: 2.6.38 not booting on sbc8100 (aka devkit8000)
Date: Fri, 25 Mar 2011 08:57:04 +0100 [thread overview]
Message-ID: <AANLkTimdQKo40r9FzhHe94uAF28qGLcf5_5ZzcOrJuTA@mail.gmail.com> (raw)
In-Reply-To: <20110324190030.GW2811@atomide.com>
On Thu, Mar 24, 2011 at 8:00 PM, Tony Lindgren <tony@atomide.com> wrote:
> * Belisko Marek <marek.belisko@gmail.com> [110324 08:18]:
>> On Thu, Mar 24, 2011 at 4:18 PM, Tony Lindgren <tony@atomide.com> wrote:
>>
>> > * Belisko Marek <marek.belisko@gmail.com> [110324 02:50]:
>> > > Hi,
>> > >
>> > > Try to run 2.6.38 on my sbc8100
>> > > (use mach-type for devkit8000 because boards are similar) board but
>> > > when u-boot load it to ram I see just:
>> > > ## Booting kernel from Legacy Image at 80300000 ...
>> > > Image Name: Linux-2.6.38-06570-g79c21b4
>> > > Image Type: ARM Linux Kernel Image (uncompressed)
>> > > Data Size: 2967164 Bytes = 2.8 MB
>> > > Load Address: 80008000
>> > > Entry Point: 80008000
>> > > Verifying Checksum ... OK
>> > > Loading Kernel Image ... OK
>> > > OK
>> > > Starting kernel ...
>> > >
>> > > I have changed bootargs to: bootargs=console=ttyO2,115200n8 doesn't
>> > > help. Any ideas what could be checked?
>> >
>> > Can you enable DEBUG_LL and EARLY_PRINTK in your .config
>> > and add earlyprintk to your cmdline? Then you should see
>> > what goes wrong.
>> >
>> Forgot to mention. I already test this options but result is same like I
>> report in
>> first email.
>
> Maybe add some printk statements to start_kernel function in
> init/main.c and see if you get any output?
Add some printk to function you propose bu no output.
>
> Tony
>
regards,
marek
--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer
Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-25 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 9:52 2.6.38 not booting on sbc8100 (aka devkit8000) Belisko Marek
2011-03-24 15:18 ` Tony Lindgren
[not found] ` <AANLkTik8PW4ad2_4=UxzvL-V7HcpH0=dg-Un5NLkj6Yi@mail.gmail.com>
2011-03-24 19:00 ` Tony Lindgren
2011-03-25 7:13 ` Jarkko Nikula
2011-03-25 7:53 ` Belisko Marek
2011-04-08 7:00 ` Thomas Weber
2011-04-08 8:03 ` Belisko Marek
2011-04-08 7:25 ` Thomas Weber
2011-03-25 7:57 ` Belisko Marek [this message]
2011-03-25 8:27 ` Jarkko Nikula
2011-03-25 9:32 ` Belisko Marek
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=AANLkTimdQKo40r9FzhHe94uAF28qGLcf5_5ZzcOrJuTA@mail.gmail.com \
--to=marek.belisko@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).