From: Tony Lindgren <tony@atomide.com>
To: Nathan Monson <nmonson@gmail.com>
Cc: Paul Walmsley <paul@pwsan.com>,
"Woodruff, Richard" <r-woodruff2@ti.com>,
"linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>,
"TK, Pratheesh Gangadhar" <pratheesh@ti.com>,
Rick Bronson <rick@efn.org>
Subject: Re: omapfb: help from userspace
Date: Thu, 16 Oct 2008 15:52:23 -0700 [thread overview]
Message-ID: <20081016225222.GA15820@atomide.com> (raw)
In-Reply-To: <e5e6ade50810161515h6c050ab2k1657e1e3a12edd6c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
* Nathan Monson <nmonson@gmail.com> [081016 15:15]:
> On Thu, Oct 16, 2008 at 3:10 PM, Tony Lindgren <tony@atomide.com> wrote:
> > No.. And I also got some -33 errors here too :( So back to the drawing
> > board.
> >
> > Could you post step by step instructions on how you can reproduce your
> > problem?
>
> I'm running the DSP Bridge patches in my kernel. I got them set up
> using this guide:
> http://elinux.org/BeagleBoard/DSP_Howto
>
> That guide also points to some sample binaries, including 'ping.out',
> which is a simple round-trip test between the DSP and ARM.
>
> To reproduce, I do this:
> 1) Boot kernel with mem=122m
> 2) modprobe bridgedriver phys_mempool_base=0x87a00000
> phys_mempool_size=0x600000
> base_img=/home/root/dsp/ddspbase_tiomap3430.dof64P
> 3) while true; do ./ping.out; done
>
> This ALWAYS reproduces within seconds.
>
> If the DSP patches are too much work to get set up, I've also heard
> that people can reproduce this issue by playing movie files with
> mplayer on Angstrom.
Thanks, I'll set that up when I get a chance.
Meanwhile, here's one more patch for you to test if you have a chance.
Maybe also do a power off for few seconds before booting with this
just in case.
If this still does not help, then we'll use the strongly ordered patch
for now, and tag v2.6.27-omap1 tomorrow. Then we can continue debugging
the issue until we fully understand it.
Tony
[-- Attachment #2: intc-write-readback.patch --]
[-- Type: text/x-diff, Size: 347 bytes --]
--- a/arch/arm/mach-omap2/irq.c
+++ b/arch/arm/mach-omap2/irq.c
@@ -53,6 +53,7 @@ static struct omap_irq_bank {
static void intc_bank_write_reg(u32 val, struct omap_irq_bank *bank, u16 reg)
{
__raw_writel(val, bank->base_reg + reg);
+ __raw_readl(bank->base_reg + reg);
}
static u32 intc_bank_read_reg(struct omap_irq_bank *bank, u16 reg)
next prev parent reply other threads:[~2008-10-16 22:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 18:36 omapfb: help from userspace Nathan Monson
2008-10-08 20:21 ` Nathan Monson
2008-10-08 20:37 ` Woodruff, Richard
2008-10-09 6:20 ` TK, Pratheesh Gangadhar
2008-10-09 12:43 ` Tony Lindgren
2008-10-09 17:55 ` Nathan Monson
2008-10-15 11:57 ` Paul Walmsley
2008-10-15 12:04 ` Lauri Leukkunen
2008-10-16 6:49 ` Nathan Monson
2008-10-16 20:57 ` Tony Lindgren
2008-10-16 22:07 ` Nathan Monson
2008-10-16 22:10 ` Tony Lindgren
2008-10-16 22:15 ` Nathan Monson
2008-10-16 22:52 ` Tony Lindgren [this message]
2008-10-16 22:59 ` Tony Lindgren
2008-10-16 23:02 ` Tony Lindgren
2008-10-16 23:20 ` Nathan Monson
2008-10-16 23:24 ` Tony Lindgren
2008-10-17 0:17 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2008-09-15 14:38 Felipe Contreras
2008-09-15 20:24 ` Felipe Contreras
2008-09-15 20:46 ` Måns Rullgård
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=20081016225222.GA15820@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=nmonson@gmail.com \
--cc=paul@pwsan.com \
--cc=pratheesh@ti.com \
--cc=r-woodruff2@ti.com \
--cc=rick@efn.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