All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Altenberg <jan.altenberg@linutronix.de>
To: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	"Antonino A. Daplas" <adaplas@gmail.com>,
	Andrew Victor <andrew@sanpeople.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Haavard Skinnemoen <hskinnemoen@atmel.com>,
	Patrice Vilchez <patrice.vilchez@rfo.atmel.com>
Subject: Re: [Linux-fbdev-devel] [PATCH] atmel_lcdfb: AT91/AT32 LCD Controller framebuffer driver
Date: Fri, 18 May 2007 20:05:31 +0200	[thread overview]
Message-ID: <1179511541.3811.16.camel@bender> (raw)
In-Reply-To: <4641E1E2.6040808@rfo.atmel.com>

Hi Nicolas,

> +	info->fix.line_length = info->var.xres_virtual * (info->var.bits_per_pixel / 8);

line_length will always be 0 for bits_per_pixel < 8.

	Jan

  reply	other threads:[~2007-05-18 18:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 14:11 [PATCH] atmel_lcdfb: AT91/AT32 LCD Controller framebuffer driver Nicolas Ferre
2007-05-07 16:01 ` [RFC] AVR32: Implement platform hooks for atmel_lcdfb driver Haavard Skinnemoen
2007-05-07 21:40 ` [Linux-fbdev-devel] [PATCH] atmel_lcdfb: AT91/AT32 LCD Controller framebuffer driver Antonino A. Daplas
2007-05-08 17:26   ` Haavard Skinnemoen
2007-05-08 17:26     ` [Linux-fbdev-devel] " Haavard Skinnemoen
2007-05-09 14:59   ` Nicolas Ferre
2007-05-18 18:05     ` Jan Altenberg [this message]
2007-06-12 11:27       ` [PATCH] atmel_lcdfb: Fix wrong line_length calculation Haavard Skinnemoen
2007-06-15  8:49         ` Nicolas Ferre
2007-06-15  8:49           ` Nicolas Ferre
2007-05-09 14:59   ` [PATCH] atmel_lcdfb: AT91/AT32 LCDController framebuffer driver Nicolas Ferre
2007-05-09 14:59     ` [Linux-fbdev-devel] " Nicolas Ferre

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=1179511541.3811.16.camel@bender \
    --to=jan.altenberg@linutronix.de \
    --cc=adaplas@gmail.com \
    --cc=andrew@sanpeople.com \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@rfo.atmel.com \
    --cc=patrice.vilchez@rfo.atmel.com \
    /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.