linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: Benjamin Herrenschmidt <bh40@calva.net>,
	Kostas Gewrgiou <gewrgiou@imbc.gr>,
	Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: dual head r128
Date: Thu, 12 Oct 2000 12:40:17 -0400	[thread overview]
Message-ID: <200010121640.MAA06292@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Gabriel Paubert <paubert@iram.es> of "Thu, 12 Oct 2000 17:49:22 +0200." <Pine.HPX.4.10.10010121719150.16113-100000@gra-ux1.iram.es>


>>>>> Gabriel Paubert writes:

>> On the kernel side, one of the PCI IO busses will be mapped to ISA. What
>> I'll do is basically to change the kernel inb/outb functions to do
>> something like
>>
>> if (addr < 64k)
>> do_io(isa_io_base + addr)
>> else
>> do_io(addr)

Gabriel> No please, is there anybody bloat-conscious on this damned list ? Burying
Gabriel> more and more code inside each {in,out}[bwl] is not the solution.

Gabriel> Just define a macro ISA_PORT or something like this and update the kernel
Gabriel> to replace all the in/out to fixed ports to do in/out(ISA_PORT(n)). If you
Gabriel> don't do it you'll get a nice panic so you'll find all the places quite
Gabriel> fast.

	Yes, it is very important to avoid adding many layers of branches
to the code if anyone cares about performance.

David

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

  reply	other threads:[~2000-10-12 16:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-11 18:17 dual head r128 Josh Huber
2000-10-11 18:43 ` Michel Dänzer
2000-10-11 18:52   ` Josh Huber
2000-10-11 19:04     ` Tom Rini
2000-10-11 19:09     ` Michel Dänzer
2000-10-11 19:26       ` Josh Huber
2000-10-11 22:48         ` Michel Dänzer
2000-10-13 17:16           ` Josh Huber
2000-10-12 13:09     ` Kostas Gewrgiou
2000-10-12 15:13       ` Benjamin Herrenschmidt
2000-10-12 15:49         ` Gabriel Paubert
2000-10-12 16:40           ` David Edelsohn [this message]
2000-10-17  0:12           ` Paul Mackerras
2000-10-17  5:56             ` Michel Lanners
2000-10-17 10:41             ` Benjamin Herrenschmidt
2000-10-17 13:45               ` Geert Uytterhoeven
2000-10-17 17:17                 ` Benjamin Herrenschmidt
2000-10-12 16:44         ` Kostas Gewrgiou
2000-10-11 21:01 ` Gabriel Paubert
  -- strict thread matches above, loose matches on Subject: below --
2000-10-12 13:41 Hendricks, Kevin
2000-10-12 14:10 ` Kostas Gewrgiou
2000-10-12 14:30 Hendricks, Kevin
2000-10-12 16:11 ` Kostas Gewrgiou
2000-10-12 17:22   ` Michel Dänzer
2000-10-12 17:44     ` Kostas Gewrgiou
2000-10-12 21:25       ` Michel Dänzer
2000-10-13 15:26         ` Kostas Gewrgiou
2000-10-13 16:21       ` Geert Uytterhoeven
2000-10-12 16:25 Hendricks, Kevin
     [not found] <200010121619.TAA27476@ns0.imbc.gr>
2000-10-12 17:08 ` Kostas Gewrgiou
     [not found] <19340906102959.14429@192.168.1.2>
2000-10-12 17:57 ` Gabriel Paubert
     [not found] <Pine.LNX.4.10.10010132302530.381-100000@cassiopeia.home>
2000-10-13 21:36 ` Benjamin Herrenschmidt
2000-10-13 21:47   ` Michel Lanners
2000-10-14 10:13     ` Benjamin Herrenschmidt
2000-10-14 10:21   ` 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=200010121640.MAA06292@mal-ach.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=bh40@calva.net \
    --cc=gewrgiou@imbc.gr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /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).