From: Michel Lanners <mlan@cpu.lu>
To: Geert.Uytterhoeven@sonycom.com
Cc: bh40@calva.net, linuxppc-dev@lists.linuxppc.org
Subject: Re: busmaster/latency for video
Date: Mon, 11 Oct 1999 20:12:06 +0200 (CEST) [thread overview]
Message-ID: <199910111812.UAA00352@piglet.cpu.lu> (raw)
In-Reply-To: <Pine.GSO.4.10.9910110828450.9144-100000@dandelion.sonytel.be>
On 11 Oct, this message from Geert Uytterhoeven echoed through cyberspace:
> On Fri, 8 Oct 1999, Michel Lanners wrote:
>> OF itself doesn't enable any memory or IO region; it's the
>> device-specific init code (which might be on-board for PCI cards, or in
>> OF for motherboard devices).
>>
>> There are, however, a few things OF does for _every_ PCI device, among
>> which enabling bus mastering and assigning memory and/or IO resources.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> assigning some memory and/or IO resources? Or is this only the case in the
> Longtrail-OF-which-is-better-than-Apple-OF-except-maybe-for-assigning-resources
> case?
Hm, my 7600's OF version 1.05 assigns memory and IO regions for two
boards that don't have any OF code: a Matrox Millenium I and a Promise
Ultra/66 IDE controller. Never had any problem in that area..
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/
prev parent reply other threads:[~1999-10-11 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 5:54 busmaster/latency for video Ryan Nielsen
1999-10-07 13:50 ` Michel Lanners
1999-10-07 14:06 ` Geert Uytterhoeven
1999-10-07 19:13 ` Michel Lanners
1999-10-08 9:19 ` Geert Uytterhoeven
1999-10-08 10:18 ` Benjamin Herrenschmidt
1999-10-08 17:59 ` Michel Lanners
1999-10-11 6:30 ` Geert Uytterhoeven
1999-10-11 18:12 ` Michel Lanners [this message]
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=199910111812.UAA00352@piglet.cpu.lu \
--to=mlan@cpu.lu \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=bh40@calva.net \
--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).