From: Daniel Jacobowitz <drow@false.org>
To: Michel Lanners <mlan@cpu.lu>
Cc: geert@linux-m68k.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: aty128 and offb and linux-2.3.99pre6
Date: Mon, 24 Apr 2000 15:07:52 -0400 [thread overview]
Message-ID: <20000424150752.A25359@drow.res.cmu.edu> (raw)
In-Reply-To: <200004240651.IAA00313@piglet.grunz.lu>; from mlan@cpu.lu on Mon, Apr 24, 2000 at 08:51:12AM +0200
On Mon, Apr 24, 2000 at 08:51:12AM +0200, Michel Lanners wrote:
> control is only PCI-based with some abstractions.... It can, however,
> be made to look entirely like a PCI device, if you can avoid poking at
> it afterwards.
>
> I have patches for control anyway (adding it to the PCI device chain,
> precisely); so I might try and implement the changes for control. Or
> are you already working on this, Dan?
I've been too busy with Debian to touch controlfb lately; patches would
be appreciated.
Also, what is the current state of your memory testing? Or was that
not you?
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-24 19:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-19 14:29 aty128 and offb and linux-2.3.99pre6 Chas Williams
2000-04-19 17:45 ` Nelson Abramson
2000-04-19 18:11 ` Kevin B. Hendricks
2000-04-19 20:55 ` Geert Uytterhoeven
2000-04-19 23:07 ` Martin Costabel
2000-04-24 6:51 ` Michel Lanners
2000-04-24 13:31 ` Geert Uytterhoeven
2000-04-24 15:16 ` Chas Williams
2000-04-24 18:10 ` Geert Uytterhoeven
2000-04-24 20:09 ` Chas Williams
2000-04-24 21:05 ` Michel Lanners
2000-04-25 9:52 ` Geert Uytterhoeven
2000-04-24 19:07 ` Daniel Jacobowitz [this message]
2000-04-24 21:11 ` Michel Lanners
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=20000424150752.A25359@drow.res.cmu.edu \
--to=drow@false.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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).