From: "Randy.Dunlap" <rddunlap@osdl.org>
To: James Simmons <jsimmons@infradead.org>
Cc: alex@foogod.com, linux-fbdev-devel@lists.sourceforge.net,
geert@linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH] neofb patches
Date: Fri, 23 Apr 2004 20:15:36 -0700 [thread overview]
Message-ID: <20040423201536.6aefe7ad.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0404232241260.5826-100000@phoenix.infradead.org>
On Sat, 24 Apr 2004 00:00:23 +0100 (BST) James Simmons <jsimmons@infradead.org> wrote:
|
| > Ok, I've got everything except the blanking patch (which isn't finished
| > anyway) converted to apply cleanly to James' patched driver source.
| > Everything works fine on my laptop as far as I can tell. Additional
| > feedback is welcome.
| >
| > I've put up a web page for the patches. They can be found at
| > http://www.foogod.com/~alex/neofb/
|
| Got it. I merged your patches. I also did a few fixes. The code had issues
| with non byte align images, i.e sparc 12x22 fonts. Now it works. I posted
| at
|
| http://phoenix.infradead.org:~/jsimmons/neofb.diff.gz
|
| This is against the latest kernel.
Hi James,
I think it would help a bit if someone could load
http://phoenix.infradead.org/~jsimmons/ in a web browser
and be able to see a list of files/patches/etc there
instead of having to know an exact file name to grab.
--
~Randy
next prev parent reply other threads:[~2004-04-24 3:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56202.64.139.3.221.1082702638.squirrel@www.foogod.com>
2004-04-23 23:00 ` James Simmons
2004-04-24 3:15 ` Randy.Dunlap [this message]
2004-04-24 7:08 ` Alex Stewart
2004-04-25 3:10 ` James Simmons
2004-04-25 3:09 ` James Simmons
2004-04-24 17:29 ` Alex Stewart
2004-04-25 0:55 ` 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=20040423201536.6aefe7ad.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=alex@foogod.com \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.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
all inboxes | Powered by JetHome®