linux-mips
[Top] [All Lists]

RE: Problem in the usage of mmap command(in directFB)

To: "kaka" <share.kt@gmail.com>, <linux-mips@linux-mips.org>, <uclinux-dev@uclinux.org>, <celinux-dev@tree.celinuxforum.org>, <linux-fbdev-users@lists.sourceforge.net>
Subject: RE: Problem in the usage of mmap command(in directFB)
From: "Kaz Kylheku" <kaz@zeugmasystems.com>
Date: Thu, 29 Nov 2007 17:51:26 -0800
Cc: <directfb-users@directfb.org>, <directfb-dev@directfb.org>
In-reply-to: <eea8a9c90711282148g67ec85e0q9decd3e0e1f4325f@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
Thread-index: AcgyS8v5FiRvVoKyQbWDSyssetYbmgApcpzA
Thread-topic: Problem in the usage of mmap command(in directFB)
Dear Aptly-Named User, 

The first clue you need to get is that you shouldn't send MIME-encoded,
HTML crap to open source mailing lists. 

Repeatedly sending the same question to half a dozen mailing lists won't
solve your problem. (Everyone heard you the first N times already, and
it's unlikely that anyone new signed up within the last week who can
magically fix the failing mmap cll for you.

You have a 100% reproducible problem: no timing dependencies or race
conditions. Everytime you make the call with more than a certain size,
you nicely get this predictable EINVAL result. 

You have the source code to everything; you can add debug printk calls
anywhere you want and rebuild the kernel. If there are multiple places
that can produce an -EINVAL return value, you can precisely identify
which one is doing it.

Golly, gee, lucky you! This is like the software equivalent of taking a
shot against a wide-open net: just kick the ball!

What is missing?

<Prev in Thread] Current Thread [Next in Thread>