linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk
To: Jaya Kumar <jayakumar.lkml@gmail.com>
Cc: Eric Miao <eric.miao@marvell.com>,
	linux-fbdev-devel@lists.sourceforge.net,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [RFC 2.6.27 1/2] fbdev: add E-Ink Broadsheet controller support
Date: Sun, 21 Dec 2008 11:06:57 +0000	[thread overview]
Message-ID: <20081221110657.GA20251@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <12298571743158-git-send-email-jayakumar.lkml@gmail.com>

On Sun, Dec 21, 2008 at 06:59:34PM +0800, Jaya Kumar wrote:
> +static void broadsheetfb_dpy_update_pages(struct broadsheetfb_par *par,
> +						u16 y1, u16 y2)
> +{
> +	u16 args[5];
> +	unsigned char *buf = (unsigned char __force *)par->info->screen_base;

You shouldn't add __force inside drivers.

> +	videomemorysize = (DPY_W*DPY_H);
> +	videomemory = vmalloc(videomemorysize);
> +	if (!videomemory)
> +		goto err_fb_rel;
> +
> +	memset(videomemory, 0, videomemorysize);
> +
> +	info->screen_base = (char __force __iomem *)videomemory;

Ditto.

Also, using vmalloc for the backing store means this memory can't be
mmap()'d into userspace, which is a very common thing for framebuffer
using programs to do.  If mmap() is to be denied, then you should
provide a mmap implementation in the fb_ops structure.

------------------------------------------------------------------------------

  reply	other threads:[~2008-12-21 11:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-21 10:59 [RFC 2.6.27 1/2] fbdev: add E-Ink Broadsheet controller support Jaya Kumar
2008-12-21 11:06 ` linux [this message]
2008-12-21 11:12   ` Jaya Kumar
2008-12-21 11:15     ` linux
2008-12-21 14:58 ` Magnus Damm
2008-12-22  2:12   ` Magnus Damm
2008-12-24  4:30     ` Jaya Kumar
2009-01-02 21:24   ` Russell King - ARM Linux
2008-12-23 12:52 ` Geert Uytterhoeven
2008-12-24  4:22   ` Jaya Kumar

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=20081221110657.GA20251@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=eric.miao@marvell.com \
    --cc=geert@linux-m68k.org \
    --cc=jayakumar.lkml@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-fbdev-devel@lists.sourceforge.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).