linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Richard Drummond <evilrich@rcdrummond.net>
Cc: Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Sven Luther <sven.luther@wanadoo.fr>
Subject: Re: tdfx & multiple voodoo cards : supposed to work ?
Date: Thu, 30 Oct 2003 13:48:35 +0100	[thread overview]
Message-ID: <20031030124835.GA7367@iliana> (raw)
In-Reply-To: <20031030123418.7005615CA9@mail03.powweb.com>

On Thu, Oct 30, 2003 at 12:34:15PM -0000, Richard Drummond wrote:
> Hi Sven
> 
> > BTW, what is the status of voodoo 4 & 5 with fbdev ? I get reports of
> > endianess problems, but this may also be related to XFree86, i will have
> > to investigate more.
> 
> Voodoo4/5 has a different method of byte-swizzling for big-endian hardware than the Voodoo3 - which isn't supported by the current tdxfb driver or by XFree86. I have been working on a fix for tdfxfb, and have had some success - but since I don't have any documentation, it's involved a lot of guess-work. I haven't looked at this for a while, but I could dig out the code again and supply a patch against what I have got so far.

Yep, that would be nice. I have already included a voodoo patch, but i
suppose it only works for the older voodoos. I have neither specs nor
hardware for them though.

> As to your other problem, I have two Voodoos working on my Mac with 2.6, so I would expect such a set-up to work on the Pegasos too. On PPC hardware, there should be no problem of conflicting VGA ports since the PCI sub-system can remap I/O ports on the PPC.

Mmm, that sounds nice. do you have OF based drivers for them in your
mac ? I need to port the pegasos patches to 2.6.x first though.

> Actually, there are one or two bugs in the tdfxfb driver which crop up when
> using multiple cards - but nothing too serious it would seem. Again, I've been meaning to submit a patch . . . (where does all the time go ;-)

:))

Friendly,

Sven Luther



-------------------------------------------------------
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-30 12:48 UTC|newest]

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

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=20031030124835.GA7367@iliana \
    --to=sven.luther@wanadoo.fr \
    --cc=evilrich@rcdrummond.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).