From: Sacha Varma <sacha@ssl.co.uk>
To: Ani Joshi <ajoshi@shell.unixbox.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PCI compatibility
Date: Thu, 20 Jul 2000 15:33:49 +0100 [thread overview]
Message-ID: <39770DCD.B7F1C6FE@ssl.co.uk> (raw)
In-Reply-To: Pine.LNX.4.10.10007200653360.21977-100000@shell.unixbox.com
Thanks to all for the responses.
Ani Joshi wrote:
>
> On Wed, 19 Jul 2000, Sacha Varma wrote:
>
> > It's quite terse but states that PCI cards that need to be active on boot
> > (video cards) will generally not work, and cards that don't generally will.
> >
> > I'm just curious (I was wondering why there was no support for various nifty
> > non-AGP PC graphics cards, and also why the PC USB card I installed yesterday
> > works fine under MacOS) but
>
> Video cards do not need to be active 'on boot' (if you mean upon powerup)
> to work in linux. If there is no OF rom you will ofcourse not see any
> display until Linux initializes the display.
So... does this mean that as far as hardware is concerned there is nothing to prevent me from using any old PCI graphics card in a (non-AGP?) mac so long as linux has drivers for it?
Where in the kernel source is the bit where it initialises the display (is this a per-host-architecture thing, per-video-chipset thing, or a generic PCI thing)?
> If you have problems with
> devices not 'talking' then try enabling IO and MEM access, as they were
> probably not turned on.
As I say, I'm just curious, I'm not having any problems, nor (clearly) do I know much about PCI! But where would one enable these?
--
sacha varma : system simulation ltd : +44 (0) 20 7836 7406
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-20 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 15:21 PCI compatibility Sacha Varma
2000-07-20 13:56 ` Ani Joshi
2000-07-20 14:33 ` Sacha Varma [this message]
2000-07-20 15:13 ` Ani Joshi
2000-07-20 15:49 ` Michael Schmitz
2000-07-20 15:53 ` Benjamin Herrenschmidt
2000-07-20 16:00 ` Ani Joshi
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=39770DCD.B7F1C6FE@ssl.co.uk \
--to=sacha@ssl.co.uk \
--cc=ajoshi@shell.unixbox.com \
--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).