All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Behaviour change of /dev/fb0?
Date: Fri, 14 Apr 2006 11:16:08 +0100	[thread overview]
Message-ID: <1145009768.6179.7.camel@localhost.localdomain> (raw)

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.

Richard



-------------------------------------------------------
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

WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <rpurdie@rpsys.net>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Behaviour change of /dev/fb0?
Date: Fri, 14 Apr 2006 11:16:08 +0100	[thread overview]
Message-ID: <1145009768.6179.7.camel@localhost.localdomain> (raw)

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.

Richard


             reply	other threads:[~2006-04-14 10:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 10:16 Richard Purdie [this message]
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
2006-04-15  0:53   ` [Linux-fbdev-devel] " Antonino A. Daplas
2006-04-15  4:31   ` Andrew Morton
2006-04-15  4:31     ` [Linux-fbdev-devel] " Andrew Morton
2006-04-15  5:38     ` [PATCH] fbdev: Fix return error of fb_write Antonino A. Daplas
2006-04-15  5:38       ` Antonino A. Daplas
2006-04-17 14:45       ` Richard Purdie
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=1145009768.6179.7.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@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.