From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: adaplas@pol.net
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
James Simmons <jsimmons@infradead.org>
Subject: Re: [PATCH]: rivafb DDC2/I2C
Date: Tue, 13 Jan 2004 09:50:12 +1100 [thread overview]
Message-ID: <1073947811.763.175.camel@gaston> (raw)
In-Reply-To: <1110.203.177.116.240.1073919544.squirrel@webmail.po.com>
On Tue, 2004-01-13 at 01:59, Antonino A. Daplas wrote:
> Hi,
>
> Attached is a patch against linux-2.6.1 + fbdev.diff. (It's another big
> patch so it's zipped).
>
Sounds nice (according to your description at least :)
I won't have time to try it on my side much during this week
(linuxconf.au), nor to adapt radeonfb to the changes at least
until I'm back.
James: Are you still around ? Got my previous set of patches ?
I think it's time to start feeding Andrew (though I'd rather
add the FB_ACTIVATE_FIND first, but that can always get in later
if we really want it).
Note that I reproduced cases of console resize via stty blowing
up in accel_clear_margins on an x86, I think that's unrelated to
the changes I did though, but I haven't figured out what's going
on exactly yet. It blows up after the resize, apparently in a
call to fbcon_switch()...
Ben.
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
next prev parent reply other threads:[~2004-01-12 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 14:59 [PATCH]: rivafb DDC2/I2C Antonino A. Daplas
2004-01-12 22:50 ` Benjamin Herrenschmidt [this message]
2004-01-12 23:24 ` James Simmons
[not found] ` <20040112173853.GA2176@dreamland.darkstar.lan>
2004-01-13 1:09 ` Antonino A. Daplas
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=1073947811.763.175.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=adaplas@pol.net \
--cc=jsimmons@infradead.org \
--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).