public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: Philip Balister <philip@balister.org>,
	OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: Recent git kernels and OSK
Date: Tue, 03 Oct 2006 15:55:17 +0200	[thread overview]
Message-ID: <45226BC5.9050201@gmail.com> (raw)
In-Reply-To: <4521941B.2020102@balister.org>

Philip Balister wrote:
> I just built a kernel from today's git repo and tried booting it on my 
> OSK. The boot hung after uncompressing the kernel at the "Starting 
> kernel ..." message.
> 
> Has anyone successfully booted a recent git kernel on the OSK?

Just checked it. Seems that recent git on OSK is really 
broken. Enabling lowlevel debug last thing I get is kernel 
command line output [3]. On my last working kernel next 
output would be clock stuff [2]

My last update some days ago including "Menelaus: Fix 
voltage values for VMEM" [1] was okay. So anything between 
this patch and now is the bad one.

Any ideas?

Cheers

Dirk

[1] 
http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=8f321b52ea97a59e8471904b2e2c32438618c6be

[2]
Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x2813 ARM_CKCTL: 0x150f
Clocking rate (xtal/DPLL1/MPU): 12.0/192.0/192.0 MHz
...

[3] Recent git with lowlevel debug enabled on OSK:

5>Linux version 2.6.18-omap1 (dirk@asterix) (gcc version 
4.1.0) #2 PREEMPT Tue Oct 3 15:40:42 CEST 2006
CPU: ARM926EJ-S [41069263] revision 3 (ARMv5TEJ), cr=00053177
Machine: TI-OSK
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 8192
<7>  DMA zone: 8192 pages, LIFO batch:1
OMAP1611b revision 2 handled as 16xx id: 68058c80eb071005
<6>SRAM: Mapped pa 0x20000000 to va 0xd0000000 size: 0x100000
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 
128 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 
64 sets
Built 1 zonelists.  Total pages: 8192
<5>Kernel command line: mem=32M console=tty0 
console=ttyS0,115200 initrd=0x10400000,8M root=/dev/ram0 rw

  parent reply	other threads:[~2006-10-03 13:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02 22:35 Recent git kernels and OSK Philip Balister
2006-10-02 23:29 ` David Brownell
2006-10-03 13:55 ` Dirk Behme [this message]
2006-10-03 15:24   ` Dirk Behme
2006-10-04  9:03     ` Dirk Behme
     [not found]       ` <4523892B.3000505@balister.org>
2006-10-04 13:27         ` Dirk Behme
2006-10-06  9:58       ` Dirk Behme

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=45226BC5.9050201@gmail.com \
    --to=dirk.behme@googlemail.com \
    --cc=Linux-omap-open-source@linux.omap.com \
    --cc=philip@balister.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