All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Dänzer <daenzer@relog.ch>
To: Kostas Gewrgiou <gewrgiou@imbc.gr>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: XFree 4.0 dual monitor on AGP G4
Date: Wed, 26 Apr 2000 16:16:36 +0200	[thread overview]
Message-ID: <3906FA44.2EBD53FA@relog.ch> (raw)
In-Reply-To: Pine.LNX.4.21.0004261635150.27506-100000@idd-01.imbc.gr


Kostas Gewrgiou wrote:

> the second r128 will never be able to pick the right device
> (/dev/fb1 here) the BusID line is more or less ignored in the fbdev
> case so the second driver will open /dev/fb0 which will result
> in a kernel crash.

Doesn't r128 support the "fbdev" option to specify the framebuffer device?

Here's the important code from the glint driver:


	for (i = 0; i < numDevSections; i++) {
 	    dev = xf86FindOptionValue(devSections[i]->options,"fbdev");
 	    if (devSections[i]->busID) {
 		xf86ParsePciBusString(devSections[i]->busID,&bus,&device,&func);
 		if (!xf86CheckPciSlot(bus,device,func))
 		    continue;
 	    }
 	    if (fbdevHWProbe(NULL,dev,&name)) {
 		ScrnInfoPtr pScrn;

  				/* Check for pm2fb */
 		if (strcmp(name,"Permedia2")) continue;
 		foundScreen = TRUE;
 		pScrn = NULL;

 		if (devSections[i]->busID) {
 		    /* XXX what about when there's no busID set? */
 		    int entity;
 		    entity = xf86ClaimPciSlot(bus,device,func,drv,
 					      0,devSections[i],
 					      TRUE);
 		    pScrn = xf86ConfigPciEntity(pScrn,0,entity,
 						      NULL,RES_SHARED_VGA,
 						      NULL,NULL,NULL,NULL);
 		    if (pScrn)
  			xf86DrvMsg(pScrn->scrnIndex, X_CONFIG,
  				   "claimed PCI slot %d:%d:%d\n",bus,device,func);
 		} else {



Michel

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

  reply	other threads:[~2000-04-26 14:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-24  6:16 XFree 4.0 dual monitor on AGP G4 W. Taylor Holliday
2000-04-25 11:23 ` Michel Dänzer
2000-04-25  9:27   ` W. Taylor Holliday
2000-04-25 16:51     ` Michel Dänzer
2000-04-25 18:30       ` W. Taylor Holliday
2000-04-26 12:26         ` Michel Dänzer
2000-04-26 13:54           ` Kostas Gewrgiou
2000-04-26 14:16             ` Michel Dänzer [this message]
2000-04-26 16:53             ` Ryuichi Oikawa
2000-04-26 17:02               ` Michel Dänzer
2000-04-28 16:37                 ` Ryuichi Oikawa
2000-04-25 17:22     ` Michael Schmitz
  -- strict thread matches above, loose matches on Subject: below --
2000-04-26 19:45 W. Taylor Holliday
2000-04-27 11:10 ` Michel Dänzer
2000-04-27 13:35   ` Kostas Gewrgiou
2000-04-27 13:57     ` Kostas Gewrgiou
2000-04-27 15:23     ` Michel Dänzer
2000-04-26 19:51 W. Taylor Holliday
2000-04-26 20:05 ` Michael Schmitz
2000-04-26 22:54 W. Taylor Holliday
2000-04-27 13:14 ` Geert Uytterhoeven
2000-04-28  0:42 W. Taylor Holliday
2000-04-28  6:06 ` Michel Dänzer
2000-04-28  0:51 W. Taylor Holliday
2000-04-28  6:09 ` Michel Dänzer
2000-04-28  7:47   ` Michael Schmitz

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=3906FA44.2EBD53FA@relog.ch \
    --to=daenzer@relog.ch \
    --cc=daenzerm@student.ethz.ch \
    --cc=gewrgiou@imbc.gr \
    --cc=linuxppc-dev@lists.linuxppc.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 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.