mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: IDE - sensible probing for PCI systems
Date: Tue, 21 Jun 2005 19:46:29 +0100	[thread overview]
Message-ID: <1119379587.3325.182.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61L.0506211535100.17779@blysk.ds.pg.gda.pl>

>  How is the range defined -- is there a way for us to find it?  I'd assume 
> in the absence of a PCI-ISA or PCI-EISA bridge all I/O port addresses 
> belong to PCI.  Otherwise the usual rule of "(addr & 0x300) == 0" applies.  
> Perhaps with the addition of "(addr & ~0xff) != 0" for safety as junk I/O 
> is often not recorded properly in BARs, sigh...

No the low addresses belong to the chipset and motherboard. There is
also magic then for video and IDE legacy port ranges. I suspect your
mips boxen might be a lot cleaner than the PC world.

Alan


  reply	other threads:[~2005-06-21 18:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 12:23 Alan Cox
2005-06-21 13:42 ` Maciej W. Rozycki
2005-06-21 14:12   ` Alan Cox
2005-06-21 15:10     ` Maciej W. Rozycki
2005-06-21 18:46       ` Alan Cox [this message]
2005-06-23 18:22         ` Maciej W. Rozycki
2005-06-23 22:48           ` Alan Cox
2005-06-24 11:52             ` Maciej W. Rozycki
2005-06-24 22:41               ` Jeff Garzik
2005-06-27 14:18                 ` Maciej W. Rozycki
2005-06-27 20:31                   ` Bill Davidsen
2005-06-25 12:32               ` Alan Cox
2005-06-27 14:55                 ` Maciej W. Rozycki
2005-06-27 16:24                   ` Russell King
2005-06-27 19:54                   ` Alan Cox

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=1119379587.3325.182.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.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

Powered by JetHome