linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kronos <kronos@kronoz.cjb.net>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: tdfx & multiple voodoo cards : supposed to work ?
Date: Wed, 29 Oct 2003 21:25:44 +0100	[thread overview]
Message-ID: <20031029202544.GA8953@dreamland.darkstar.lan> (raw)
In-Reply-To: <20031029195627.GA13626@iliana>

Il Wed, Oct 29, 2003 at 08:56:27PM +0100, Sven Luther ha scritto: 
> On Wed, Oct 29, 2003 at 07:25:32PM +0100, Kronos wrote:
> > Il Wed, Oct 29, 2003 at 10:36:53AM +0100, Sven Luther ha scritto: 
> > > Hello,
> > > 
> > > I have had a report of someone trying to use two voodoo cards on a
> > > pegasos/ppc motherboard, and it freezing the kernel (2.4.22 kernel)
> > > 
> > > Is the tdfx fbdev supposed to be able to handle dual card setups, or not ?
> > 
> > No, the driver has a statically allocated fb_info. It will blow up.
> 
> Ok, thought so, i am not sure though.

BTW, looking  at 2.6 it  seems that the  driver will work  with multiple
cards.  Static vars have been removed so this problem is solved. I'm not
sure that the  driver itself can handle more than  one card though. Give
it a try.

Luca
-- 
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
"New processes are created by other processes, just like new
 humans. New humans are created by other humans, of course,
 not by processes." -- Unix System Administration Handbook


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

  reply	other threads:[~2003-10-29 20:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-29  9:36 tdfx & multiple voodoo cards : supposed to work ? Sven Luther
2003-10-29 18:25 ` Kronos
2003-10-29 19:56   ` Sven Luther
2003-10-29 20:25     ` Kronos [this message]
2003-10-29 22:19       ` James Simmons
2003-10-30  6:49       ` tdfx & multiple voodoo cards : supposed to work ? + Mach64Gx question Sven Luther
2003-10-30  9:38         ` Geert Uytterhoeven
2003-10-30  9:56           ` Mach64Gx not working on pmac 9500 (Was : tdfx & multiple voodoo cards : supposed to work ? + Mach64Gx question.) Sven Luther
2003-10-30 18:27         ` tdfx & multiple voodoo cards : supposed to work ? + Mach64Gx question James Simmons
2003-10-30 18:31           ` Sven Luther
2003-10-30 18:45             ` James Simmons
2003-10-30 20:47               ` Geert Uytterhoeven
2003-10-30 20:31             ` Geert Uytterhoeven
2003-10-29 20:04   ` tdfx & multiple voodoo cards : supposed to work ? James Simmons
2003-10-30  9:15     ` Sven Luther
2003-10-30 11:32       ` Sven Luther
2003-10-30 18:27       ` James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2003-10-30 12:34 Richard Drummond
2003-10-30 12:48 ` Sven Luther
2003-10-30 18:42   ` James Simmons
2003-10-30 18:41 ` James Simmons
2003-10-30 14:03 Richard Drummond
2003-10-30 14:31 ` Sven Luther

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=20031029202544.GA8953@dreamland.darkstar.lan \
    --to=kronos@kronoz.cjb.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=sven.luther@wanadoo.fr \
    /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).