From: "Petr Vandrovec Ing. VTEI" <VANDROVE@vc.cvut.cz>
To: Owen Waller <O.Waller@ee.qub.ac.uk>
Cc: dhiltgen@toocool.itslab.calpoly.edu, mlan@cpu.lu,
Geert.Uytterhoeven@cs.kuleuven.ac.be,
linuxppc-dev@lists.linuxppc.org
Subject: Re: matroxfb, anybody? (More details...)
Date: Mon, 1 Feb 1999 12:51:40 MET-1 [thread overview]
Message-ID: <1EDE67B39D1@vcnet.vc.cvut.cz> (raw)
On 1 Feb 99 at 11:35, Owen Waller wrote:
> > (my PReP does not have OF and I never saw it...) If you uncommented #define
> > above, be sure that you commented out complement part from
> > drivers/video/offb.c - otherwise matroxfb can be initialized twice, thus
> > you'll get two fb's per one hardware :-(
> Is there any way that this could be changed? I don't need my internal
> video (control) to work, but I'd rather have it and the matrox compiled
> into the one kernel without a hack. Unless Geert you know some way of
> "fudging" an non-OF card into the OF device tree? OR Petr could you
> possibly work in a #define construct so that Daniel's "hack" became
> official? (mind you neither of these are very general solutions).
There is a problem. What if you HAVE matrox in OF ? Of course,
I remove this #ifdef from driver and add some variable to ensure, that
driver will be initialized only once... And if matroxfb is not your primary
head, you can, as temporary solution, compile it as module. It should
work without problems then.
> Also does anybody know how this situation changes if you use BootX to boot
> (I don't so I can't comment on this). Would BootX map the mystique from
As I do not have anything with OF around here, tell me what you want
and I'll do it...
Petr Vandrovec
vandrove@vc.cvut.cz
P.S.: I'm not on the list, so please CC me...
P.P.S.: Should not I remove whole #ifdef CONFIG_FB_OF from driver?
Is there anybody who uses this additional feature?
[[ 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. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1999-02-01 12:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-01 12:51 Petr Vandrovec Ing. VTEI [this message]
1999-02-01 12:08 ` matroxfb, anybody? (More details...) Geert Uytterhoeven
1999-02-01 16:30 ` Owen Waller
1999-02-01 16:18 ` Geert Uytterhoeven
1999-02-01 19:14 ` Benjamin Herrenschmidt
1999-02-01 20:30 ` Owen Waller
1999-02-02 15:04 ` Owen Waller
-- strict thread matches above, loose matches on Subject: below --
1999-02-02 12:53 Petr Vandrovec Ing. VTEI
1999-02-04 5:49 ` dhiltgen@toocool.calpoly.edu
1999-02-04 22:52 ` Takashi Oe
1999-02-01 18:32 Petr Vandrovec Ing. VTEI
1999-02-01 17:38 Petr Vandrovec Ing. VTEI
1999-02-01 17:15 ` Geert Uytterhoeven
1999-02-01 20:32 ` Owen Waller
1999-02-01 15:55 Benjamin Herrenschmidt
1999-02-01 16:25 ` Geert Uytterhoeven
1999-02-02 15:10 ` Owen Waller
1999-02-02 20:03 ` Geert Uytterhoeven
1999-02-01 10:34 Petr Vandrovec Ing. VTEI
1999-02-01 10:04 ` Geert Uytterhoeven
1999-02-01 12:35 ` Owen Waller
1999-02-02 10:37 ` dhiltgen@toocool.calpoly.edu
1999-01-30 10:00 matroxfb, anybody? dhiltgen@toocool.calpoly.edu
1999-01-30 15:32 ` Owen Waller
1999-01-30 23:34 ` matroxfb, anybody? (More details...) dhiltgen@toocool.calpoly.edu
1999-01-31 9:38 ` Gerd Knorr
1999-01-31 14:24 ` Geert Uytterhoeven
1999-02-06 15:22 ` Gerd Knorr
1999-01-31 14:36 ` 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=1EDE67B39D1@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=O.Waller@ee.qub.ac.uk \
--cc=dhiltgen@toocool.itslab.calpoly.edu \
--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 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).