From: Dirk Behme <dirk.behme@googlemail.com>
To: "Sideleau, Scott R" <srs@WPI.EDU>
Cc: OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1
Date: Fri, 06 Oct 2006 21:30:56 +0200 [thread overview]
Message-ID: <4526AEF0.4000005@gmail.com> (raw)
In-Reply-To: <CC7B089C59ED6841BAE28F1EA69A8543873730@EXCHDB.admin.wpi.edu>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
Sideleau, Scott R wrote:
> ## Booting image at 00100000 ...
> Image Name: OE
> Image Type: ARM Linux Kernel Image (gzip compressed)
> Data Size: 1065210 Bytes = 1 MB
> Load Address: 10c08000
> Entry Point: 10c08000
> Verifying Checksum ... OK
> Uncompressing Kernel Image ... OK
I wonder about the adresses used here. Do you followed
http://oskfordummies.hp.infoseek.co.jp/howto/flash_kernel.html
?
I would assume kernel at 0x40000 and start address/entry
point at 0x10008000. E.g.:
## Checking image at 00040000 ...
Image Name: Linux-2.6.11-omap1
Image Type: ARM Linux Kernel Image (umcompressed)
Data Size: 1159328 Bytes = 1.1 MB
Load Address: 10008000
Entry Point: 10008000
Veryfying Checksum ... OK
> Any ideas? Any and all help/direction is appreciated.
For debugging, enable
Kernel hacking -> Kernel debugging -> Kernel low-level
debugging functions
(and temporarily apply patch in attachment, seems to be
necessary to work low level debugging properly).
Dirk
[-- Attachment #2: temp_low_level_debug_patch.txt --]
[-- Type: text/plain, Size: 872 bytes --]
--- ./arch/arm/plat-omap/clock.c_orig 2006-10-06 21:16:49.000000000 +0200
+++ ./arch/arm/plat-omap/clock.c 2006-10-06 21:17:03.000000000 +0200
@@ -135,7 +135,7 @@ void clk_disable(struct clk *clk)
return;
spin_lock_irqsave(&clockfw_lock, flags);
- BUG_ON(clk->usecount == 0);
+ //BUG_ON(clk->usecount == 0);
if (arch_clock->clk_disable)
arch_clock->clk_disable(clk);
spin_unlock_irqrestore(&clockfw_lock, flags);
--- ./arch/arm/mach-omap1/clock.c_orig 2006-10-06 21:18:57.000000000 +0200
+++ ./arch/arm/mach-omap1/clock.c 2006-10-06 21:16:21.000000000 +0200
@@ -651,7 +651,7 @@ int __init omap1_clk_init(void)
/* USB_REQ_EN will be disabled later if necessary (usb_dc_ck) */
reg = omap_readw(SOFT_REQ_REG) & (1 << 4);
- omap_writew(reg, SOFT_REQ_REG);
+ //omap_writew(reg, SOFT_REQ_REG);
if (!cpu_is_omap15xx())
omap_writew(0, SOFT_REQ_REG2);
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-10-06 19:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 9:58 [PATCH] ARM: OMAP: Make OMAP1 work again Dirk Behme
2006-10-06 10:21 ` Bug? - OSK Frame Buffer Support in Kernel 2.6.18-omap1 Sideleau, Scott R
2006-10-06 10:43 ` Dirk Behme
2006-10-06 16:13 ` Sideleau, Scott R
2006-10-06 19:05 ` Can't Boot " Sideleau, Scott R
2006-10-06 19:30 ` Dirk Behme [this message]
2006-10-06 12:49 ` [PATCH] ARM: OMAP: Make OMAP1 work again Tony Lindgren
[not found] <CC7B089C59ED6841BAE28F1EA69A8543873731@EXCHDB.admin.wpi.edu>
2006-10-06 20:38 ` Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1 Sideleau, Scott R
2006-10-07 10:52 ` Jonathan McDowell
[not found] <45274A7A.4000707@gmail.com>
2006-10-07 15:01 ` Sideleau, Scott R
2006-10-07 15:09 ` Sideleau, Scott R
2006-10-07 17:02 ` Sideleau, Scott R
2006-10-08 12:31 ` Sideleau, Scott R
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=4526AEF0.4000005@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=srs@WPI.EDU \
/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.