linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: JosephChan@via.com.tw
Cc: geert@linux-m68k.org, akpm@linux-foundation.org,
	linux-fbdev-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/13] viafb: iface.c, iface.h, ioctl.c, ioctl.h
Date: Mon, 30 Jun 2008 21:52:11 +0200	[thread overview]
Message-ID: <4869396B.8060401@gmail.com> (raw)
In-Reply-To: <C80EF34A3D2E494DBAF9AC29C7AE4EB8074E7804@exchtp03.taipei.via.com.tw>

> diff -Nur a/drivers/video/via/ioctl.h b/drivers/video/via/ioctl.h
> --- a/drivers/video/via/ioctl.h	1970-01-01 08:00:00.000000000 +0800
> +++ b/drivers/video/via/ioctl.h	2008-06-30 08:53:33.000000000 +0800
> @@ -0,0 +1,212 @@
[...]
> +struct device_t {
> +	unsigned short crt:1;
> +	unsigned short dvi:1;
> +	unsigned short lcd:1;
> +	unsigned short samm:1;
> +	unsigned short primary_dev;
> +
> +	unsigned short lcd_dsp_cent:1;
> +	unsigned char lcd_panel_id;
> +	unsigned char lcd_mode:1;
> +
> +	unsigned short xres, yres;
> +	unsigned short xres1, yres1;
> +	unsigned short refresh;
> +	unsigned short bpp;
> +	unsigned short refresh1;
> +	unsigned short bpp1;
> +	unsigned short sequence;
> +
> +	unsigned short epia_dvi:1;
> +	unsigned short lcd_dual_edge:1;
> +	unsigned short bus_width;
> +	unsigned short lcd2:1;
> +};

Bitfields suck (and generate ugly code).

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

  parent reply	other threads:[~2008-06-30 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30  7:26 [PATCH 7/13] viafb: iface.c, iface.h, ioctl.c, ioctl.h JosephChan
2008-06-30  9:39 ` Alan Cox
2008-07-01  1:20   ` JosephChan
2008-07-01  7:59     ` Alan Cox
2008-06-30 19:52 ` Jiri Slaby [this message]
2008-08-08 10:15 ` [PATCH 7/13 v2] " JosephChan

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=4869396B.8060401@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=JosephChan@via.com.tw \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --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 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).