linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Takashi Oe <toe@unlserve.unl.edu>
Cc: David Riley <happyoscar42@usa.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: BootX enhancement request
Date: Wed, 25 Aug 1999 22:29:35 -0400	[thread overview]
Message-ID: <19990825222935.A20023@them.org> (raw)
In-Reply-To: <Pine.A41.3.96LJ1.1b7.990825194557.72736C-100000@unlserve.unl.edu>; from Takashi Oe on Wed, Aug 25, 1999 at 07:49:34PM -0500


On Wed, Aug 25, 1999 at 07:49:34PM -0500, Takashi Oe wrote:
> 
> On Tue, 24 Aug 1999, David Riley wrote:
> 
> > Some of the drivers don't do video=xxxx.  I know controlfb doesn't.  Is there
> > a _good_ reason for this, or does controlfb just not like me?
> 
> It's probably a simple oversight.  Last I checked,
> controlfb does have the necessary code for "video=...", while
> drivers/video/fbmem.c lacks an entry for controlfb to actually activate
> the code.

Translation - I'm being far too lazy.  I have some other work for the
controlfb underway, and I'm hoping to make some progress.

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-08-26  2:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-24  8:56 BootX enhancement request Benjamin Herrenschmidt
1999-08-25  3:12 ` David Riley
1999-08-26  0:49   ` Takashi Oe
1999-08-26  2:29     ` Daniel Jacobowitz [this message]
1999-08-26  8:39     ` Geert Uytterhoeven
1999-08-26 15:15       ` David Riley
  -- strict thread matches above, loose matches on Subject: below --
1999-08-24  9:02 Benjamin Herrenschmidt
1999-08-24 12:56 ` Geert Uytterhoeven
1999-08-24 13:05   ` Benjamin Herrenschmidt
1999-08-25  4:26   ` Paul Mackerras
1999-08-25  8:46     ` Geert Uytterhoeven
1999-08-27  6:33   ` Tom Rini
1999-08-27  9:20     ` Benjamin Herrenschmidt
1999-08-28 11:27       ` Geert Uytterhoeven
1999-08-24 17:43 ` David A. Gatwood
1999-08-24 18:21   ` Benjamin Herrenschmidt
1999-08-27  5:46     ` brad allison
1999-08-22 20:20 Kevin Puetz
1999-08-18 14:33 Is someone working on HFS+ support ? Benjamin Herrenschmidt
1999-08-22 17:45 ` BootX enhancement request brad allison
1999-08-23 13:52   ` Mike Lambert
1999-08-23 16:00   ` Robert Shaw
1999-08-23 20:16     ` brad allison
1999-08-23 20:27       ` Tom Rini
1999-08-23 20:40         ` Robert Shaw
1999-08-23 21:23           ` brad allison
1999-08-23 20:56         ` Jerry Quinn
1999-08-23 21:10           ` David A. Gatwood
1999-08-23 21:27           ` Peter Chang
1999-08-24  4:52           ` Tom Rini
1999-08-23 21:36         ` anthony tong
1999-08-24  4:35           ` Paul Mackerras
1999-08-23 20:29       ` Robert Shaw

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=19990825222935.A20023@them.org \
    --to=drow@false.org \
    --cc=happyoscar42@usa.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=toe@unlserve.unl.edu \
    /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).