From: Tony Lindgren <tony@atomide.com>
To: Anand Gadiyar <gadiyar@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
"Cousson, Benoit" <b-cousson@ti.com>
Subject: Re: linux-next 20101115 fails to boot on zoom3
Date: Mon, 15 Nov 2010 09:34:16 -0800 [thread overview]
Message-ID: <20101115173415.GI9264@atomide.com> (raw)
In-Reply-To: <4CE135B0.8070405@ti.com>
* Anand Gadiyar <gadiyar@ti.com> [101115 05:19]:
> Hi all,
>
> Linux-next as of 20101115 fails to boot up on a zoom3. earlyprintk throws
> the following crash.
>
> [ 0.000000] MUX: Add partition: #1: core, flags: 0
> [ 0.000000] Unable to handle kernel paging request at virtual address 01000268
I'll merge the following fix into Benoit's patch. Looks like hese patches
need still a bit more testing :)
Regards,
Tony
From: Tony Lindgren <tony@atomide.com>
Date: Mon, 15 Nov 2010 09:30:11 -0800
Subject: [PATCH] omap: mux: Fix omap_mux_write_array
Otherwise we can get:
MUX: Add partition: #1: core, flags: 0
Unable to handle kernel paging request at virtual address 01000268
Also fix a cosmetic issue in omap_mux_init while.
Signed-off-by: Tony Lindgren <tony@atomide.com>
--- a/arch/arm/mach-omap2/mux.c
+++ b/arch/arm/mach-omap2/mux.c
@@ -796,7 +796,7 @@ static void omap_mux_init_signals(struct omap_mux_partition *partition,
struct omap_board_mux *board_mux)
{
omap_mux_set_cmdline_signals();
- omap_mux_write_array(partition->base, board_mux);
+ omap_mux_write_array(partition, board_mux);
}
#else
@@ -816,7 +816,7 @@ static void omap_mux_init_signals(struct omap_mux_partition *partition,
static u32 mux_partitions_cnt;
-int __init omap_mux_init(const char * name, u32 flags,
+int __init omap_mux_init(const char *name, u32 flags,
u32 mux_pbase, u32 mux_size,
struct omap_mux *superset,
struct omap_mux *package_subset,
prev parent reply other threads:[~2010-11-15 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 13:29 linux-next 20101115 fails to boot on zoom3 Anand Gadiyar
2010-11-15 17:34 ` 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=20101115173415.GI9264@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.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 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.