From: "Petr Vandrovec Ing. VTEI" <VANDROVE@vc.cvut.cz>
To: Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: matroxfb, anybody? (More details...)
Date: Mon, 1 Feb 1999 18:32:25 MET-1 [thread overview]
Message-ID: <1F394C253DD@vcnet.vc.cvut.cz> (raw)
On 1 Feb 99 at 18:15, Geert Uytterhoeven wrote:
> > So, attached patch adds back that matrox_init is called unless you
> > specify `video=matrox:off' on command line. In this case, matrox can
> > be still initialized through offb. If you specify `video=matrox:disabled',
> > driver will be unavailable for offb too.
> Which does not help if you have 2 Matrox boards, due to the single static
> `initialized' variable.
No problem because of driver initializes ALL matroxes once matrox_init is
called, regardless of device_node contents (behavior is determined by
video=matrox:dev:X parameter).
> > Also, driver still does not use device_node passed to driver by offb
> > because of no-one told me what I can expect in that variable... Driver
> You can find the PCI base addresses in there (look at atyfb_of_init() for an
> example).
Unless `register_pci_region' is here, I think that I stay with current
behavior. I'm too lazy to add skipping of already registered devices
into matrox_init().
Petr Vandrovec
vandrove@vc.cvut.cz
[[ 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 18:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-01 18:32 Petr Vandrovec Ing. VTEI [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-02 12:53 matroxfb, anybody? (More details...) Petr Vandrovec Ing. VTEI
1999-02-04 5:49 ` dhiltgen@toocool.calpoly.edu
1999-02-04 22:52 ` Takashi Oe
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 12:51 Petr Vandrovec Ing. VTEI
1999-02-01 12:08 ` 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
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=1F394C253DD@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--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 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).