linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: geert@linux-m68k.org
Cc: linuxppc-dev@lists.linuxppc.org, drow@false.org
Subject: Re: aty128 and offb and linux-2.3.99pre6
Date: Mon, 24 Apr 2000 08:51:12 +0200 (CEST)	[thread overview]
Message-ID: <200004240651.IAA00313@piglet.grunz.lu> (raw)
In-Reply-To: <Pine.LNX.4.10.10004192247200.436-100000@cassiopeia.home>


Hi all,

On  19 Apr, this message from Geert Uytterhoeven echoed through cyberspace:
> What about other frame buffer devices, like e.g. matroxfb? Does it still work
> after this patch? If yes, we can get rid of matrox_of_init() as well.

It does work... but it changes the order my fbs are detected. Grrr....
;-)

> I'd really like to get rid of all these:
>
>     s3triofb_init_of()
>     imsttfb_of_init()
>     chips_of_init()
>     matrox_of_init()
>     control_of_init()
>     valkyrie_of_init()
>     platinum_of_init()
>     clgen_of_init()
>
> These are all PCI based, so they can be found using PCI probing and marked
> busy using PCI resource management.

control is only PCI-based with some abstractions.... It can, however,
be made to look entirely like a PCI device, if you can avoid poking at
it afterwards.

I have patches for control anyway (adding it to the PCI device chain,
precisely); so I might try and implement the changes for control. Or
are you already working on this, Dan?

Cheers


Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


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

  parent reply	other threads:[~2000-04-24  6:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-19 14:29 aty128 and offb and linux-2.3.99pre6 Chas Williams
2000-04-19 17:45 ` Nelson Abramson
2000-04-19 18:11   ` Kevin B. Hendricks
2000-04-19 20:55 ` Geert Uytterhoeven
2000-04-19 23:07   ` Martin Costabel
2000-04-24  6:51   ` Michel Lanners [this message]
2000-04-24 13:31     ` Geert Uytterhoeven
2000-04-24 15:16     ` Chas Williams
2000-04-24 18:10       ` Geert Uytterhoeven
2000-04-24 20:09         ` Chas Williams
2000-04-24 21:05         ` Michel Lanners
2000-04-25  9:52           ` Geert Uytterhoeven
2000-04-24 19:07     ` Daniel Jacobowitz
2000-04-24 21:11       ` Michel Lanners

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=200004240651.IAA00313@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=drow@false.org \
    --cc=geert@linux-m68k.org \
    --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).