All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Dänzer <daenzer@relog.ch>
To: mlan@cpu.lu
Cc: ajoshi@shell.unixbox.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [patch] VRAM detection in controlfb
Date: Mon, 05 Jun 2000 14:59:16 +0200	[thread overview]
Message-ID: <393BA424.2E608C4@relog.ch> (raw)
In-Reply-To: 200006041356.PAA00976@piglet.grunz.lu


Michel Lanners wrote:

> 1. What do the vc: and map: options do?

map: maps framebuffer devices to VCs. E.g. I use

	video=pm2fb:... video=amifb:... video=map:000011

So pm2fb is fb0 and amifb fb1, and VCs 1-4 are handled by pm2fb while 5 and
six are handled by amifb. Hope you get the idea.


> 2. Why can you specify more options after 'scrollback:', separated with
>    a ',', but not after the 'map:' option (no other options possible),

I guess it doesn't make sense to mix map: with device specific options because
it affects all devices.

>    whereas you can have more options following 'vc:', but without a
>    separator?

If only I knew what vc: is for :)


Michel


--
...and that is how we know the Earth to be banana-shaped.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-06-05 12:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-31 22:43 [patch] VRAM detection in controlfb Michel Lanners
2000-06-01  0:57 ` Takashi Oe
2000-06-03  6:28   ` Michel Lanners
2000-06-03  7:13     ` Takashi Oe
2000-06-03  7:30       ` Geert Uytterhoeven
2000-06-03  8:49         ` Michel Dänzer
2000-06-03  9:22           ` Geert Uytterhoeven
2000-06-06 19:25             ` Michael Schmitz
2000-06-06 21:52               ` Michel Lanners
2000-06-03  7:38     ` Geert Uytterhoeven
2000-06-05  6:01       ` Michel Lanners
2000-06-04  0:09     ` Daniel Jacobowitz
2000-06-04  0:31       ` Ani Joshi
2000-06-04 13:55         ` Michel Lanners
2000-06-05 12:59           ` Michel Dänzer [this message]
2000-06-03  9:16 ` Franz Sirl
2000-06-04  7:09   ` Michel Lanners
2000-06-04 15:08     ` Tony Mantler
2000-06-04 17:48       ` Daniel Jacobowitz
2000-06-05  5:48         ` Michel Lanners
2000-06-05 12:40           ` Tony Mantler
2000-06-05 13:51             ` Michel Lanners
2000-06-05 14:15               ` Geert Uytterhoeven
2000-06-05 23:49                 ` Tony Mantler
2000-06-06  5:15                 ` Timothy A. Seufert
2000-06-06 19:49             ` Michael Schmitz
2000-06-06 21:58               ` Michel Lanners
2000-06-07  7:59                 ` Geert Uytterhoeven
     [not found] <20000607233456Z.roikawa@rr.iij4u.or.jp>
2000-06-07 15:10 ` Geert Uytterhoeven
2000-06-07 15:20   ` Michael Schmitz
2000-06-07 15:41     ` Geert Uytterhoeven
2000-06-07 15:58   ` Ryuichi Oikawa
2000-06-07 19:11     ` Geert Uytterhoeven

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=393BA424.2E608C4@relog.ch \
    --to=daenzer@relog.ch \
    --cc=ajoshi@shell.unixbox.com \
    --cc=daenzerm@student.ethz.ch \
    --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 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.