From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, Richard Purdie <rpurdie@rpsys.net>
Subject: Re: Behaviour change of /dev/fb0?
Date: Sat, 15 Apr 2006 08:53:21 +0800 [thread overview]
Message-ID: <44404401.3030702@gmail.com> (raw)
In-Reply-To: <1145009768.6179.7.camel@localhost.localdomain>
Richard Purdie wrote:
> Ignoring whether this is a good idea or not, under 2.6.15 you could run
>
> dd if=/dev/zero of=/dev/fb0
>
> which would clear the framebuffer. It would end up saying "dd: /dev/fb0:
> No space left on device".
>
> Under 2.6.16 (and a recent git kernel), the same command clears the
> screen but then hangs. Was the change in behaviour intentional?
>
> I've noticed this on a couple of ARM based Zaurus handhelds under both
> w100fb and pxafb.
>
After reading 'man 2 read' more thoroughly, I've adjusted fb_write()'s
return codes appropriately. Can you try this patch and let me know if it
fixes your problem.
Tony
fbdev: Fix return error of fb_write()
- return -EFBIG if file offset is past the maximum allowable offset
- return -EFBIG and write to end of framebuffer if size is bigger than the
framebuffer length
- return -ENOSPC and write to end of framebuffer if size is bigger than the
framebuffer length - file offset
Signed-off-by: Antonino Daplas <adaplas@pol.net>
---
drivers/video/fbmem.c | 12 +++++++++---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/drivers/video/fbmem.c b/drivers/video/fbmem.c
index 944855b..8a643bf 100644
--- a/drivers/video/fbmem.c
+++ b/drivers/video/fbmem.c
@@ -669,13 +669,19 @@ fb_write(struct file *file, const char _
total_size = info->fix.smem_len;
if (p > total_size)
- return 0;
+ return -EFBIG;
- if (count >= total_size)
+ if (count >= total_size) {
+ err = -EFBIG;
count = total_size;
+ }
+
+ if (count + p > total_size) {
+ if (!err)
+ err = -ENOSPC;
- if (count + p > total_size)
count = total_size - p;
+ }
buffer = kmalloc((count > PAGE_SIZE) ? PAGE_SIZE : count,
GFP_KERNEL);
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-04-15 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 10:16 Behaviour change of /dev/fb0? Richard Purdie
2006-04-14 23:29 ` [Linux-fbdev-devel] " Antonino A. Daplas
2006-04-15 0:13 ` Richard Purdie
2006-04-15 0:53 ` Antonino A. Daplas [this message]
2006-04-15 4:31 ` Andrew Morton
2006-04-15 5:38 ` [PATCH] fbdev: Fix return error of fb_write Antonino A. Daplas
2006-04-17 14:45 ` Richard Purdie
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=44404401.3030702@gmail.com \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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;
as well as URLs for NNTP newsgroup(s).