From: Russell King <rmk@arm.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Simmons <jsimmons@transvirtual.com>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [PATCH] fbdev updates.
Date: Fri, 5 Jul 2002 11:20:35 +0100 [thread overview]
Message-ID: <20020705112035.D23355@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.GSO.4.21.0207051138380.23857-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Fri, Jul 05, 2002 at 11:39:24AM +0200
On Fri, Jul 05, 2002 at 11:39:24AM +0200, Geert Uytterhoeven wrote:
> On Fri, 5 Jul 2002, Russell King wrote:
> > On Fri, Jul 05, 2002 at 10:53:35AM +0200, Geert Uytterhoeven wrote:
> > > If you have an `asymmetric' dual-head chipset (both heads are not independent,
> > > and/or have different capabilities), you'll have 2 info structures, with one
> > > shared par. So info and par cannot be combined.
> >
> > That may be true for such systems. I don't believe in imposing such
> > restrictions on drivers that can _never ever_ fall into that category.
>
> Then just store your par in your info.
Err, that's what I _am_ doing. However, James has converted my info to
a par and reordered some elements without any reason.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Bringing you mounds of caffeinated joy.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-05 10:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 17:48 [PATCH] fbdev updates James Simmons
2002-07-01 17:48 ` James Simmons
2002-07-02 13:33 ` Jani Monoses
2002-07-05 2:41 ` James Simmons
2002-07-03 23:03 ` Russell King
2002-07-05 4:05 ` James Simmons
2002-07-05 8:44 ` Russell King
2002-07-05 8:53 ` Geert Uytterhoeven
2002-07-05 9:09 ` Russell King
2002-07-05 9:39 ` Geert Uytterhoeven
2002-07-05 10:20 ` Russell King [this message]
2002-07-05 17:20 ` James Simmons
2002-07-05 17:16 ` James Simmons
2002-07-05 17:58 ` Russell King
2002-07-05 18:21 ` James Simmons
2002-07-05 18:27 ` Russell King
2002-07-05 17:14 ` James Simmons
2002-07-05 17:57 ` Russell King
2002-07-05 18:32 ` James Simmons
2002-07-05 18:39 ` Russell King
2002-07-05 19:00 ` James Simmons
2002-07-05 19:29 ` Ani Joshi
2002-07-05 19:32 ` James Simmons
2002-07-05 19:41 ` Russell King
2002-07-05 19:57 ` James Simmons
2002-07-05 19:53 ` Ani Joshi
2002-07-05 19:55 ` Ani Joshi
2002-07-05 19:58 ` James Simmons
2002-07-05 20:21 ` Ani Joshi
2002-07-05 20:09 ` James Simmons
2002-07-05 20:34 ` James Simmons
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=20020705112035.D23355@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=jsimmons@transvirtual.com \
--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 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.