From: Tony Lindgren <tony@atomide.com>
To: Arnaud Patard <arnaud.patard@rtp-net.org>,
Toshihiro Kobayashi <toshihiro.kobayashi@nokia.com>,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] dsp: don't use registered_fb[1]
Date: Fri, 26 Jan 2007 13:51:24 -0800 [thread overview]
Message-ID: <20070126215123.GL29286@atomide.com> (raw)
In-Reply-To: <85ac0lg239.fsf@orfeo.duckcorp.org>
* Arnaud Patard <arnaud.patard@rtp-net.org> [070114 05:45]:
>
> According to dsp_fbexport(), the dsp code handles only the first
> registered framebuffer, so using registered_fb[1] in mbox_fbctl_upd is
> wrong. registered_fb[0] must be used instead.
> This code has also the side effect to oops the kernel as
> registered_fb[1] is null and omapfb_update_window_async doesn't handle
> this case. The fix for omapfb_update_window_async is sent in an other
> mail.
>
>
> Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
> ---
> ---
> arch/arm/plat-omap/dsp/dsp_mem.c | 2 1 + 1 - 0 !
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-omap-2.6/arch/arm/plat-omap/dsp/dsp_mem.c
> ===================================================================
> --- linux-omap-2.6.orig/arch/arm/plat-omap/dsp/dsp_mem.c 2007-01-14 14:10:26.000000000 +0100
> +++ linux-omap-2.6/arch/arm/plat-omap/dsp/dsp_mem.c 2007-01-14 14:10:37.000000000 +0100
> @@ -2052,7 +2052,7 @@ void mbox_fbctl_upd(void)
> return;
> }
> //printk("calling omapfb_update_window_async()\n");
> - omapfb_update_window_async(registered_fb[1], &win, fbupd_cb, NULL);
> + omapfb_update_window_async(registered_fb[0], &win, fbupd_cb, NULL);
> }
>
> #else /* CONFIG_FB_OMAP_LCDC_EXTERNAL */
Toshihiro and Hiroshi, can you ack this one?
Regards,
Tony
next prev parent reply other threads:[~2007-01-26 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 13:38 [PATCH] dsp: don't use registered_fb[1] Arnaud Patard
2007-01-26 21:51 ` Tony Lindgren [this message]
2007-01-28 5:13 ` Hiroshi DOYU
2007-01-31 18:58 ` Tony Lindgren
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=20070126215123.GL29286@atomide.com \
--to=tony@atomide.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=arnaud.patard@rtp-net.org \
--cc=linux-omap-open-source@linux.omap.com \
--cc=toshihiro.kobayashi@nokia.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