Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: ldavies@oz.agile.tv
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: Re: pci io remapping and ide_ioreg_t
Date: Tue, 20 Feb 2001 21:51:18 +0100	[thread overview]
Message-ID: <20010220215118.D2086@bacchus.dhis.org> (raw)
In-Reply-To: <3A91F56F.9020603@agile.tv>; from ldavies@agile.tv on Tue, Feb 20, 2001 at 02:41:19PM +1000

On Tue, Feb 20, 2001 at 02:41:19PM +1000, Liam Davies wrote:

> I have an old (2.0.x) ide driver that used to hard code the 
> hwif->io_ports up to the 0x100001f0-0x100001f7 range. This is now broken 
> in the 2.4 kernel since ide_ioreg_t has changed from unsigned long to 
> unsigned short.
> 
> What is the mechanism for reaching these ports now?

Consider this size of ide_ioreg_t a glitch; most current MIPS designs
have their IDE ports in outer space.  It shouldn't break anything, so
until somebody is going to cry I'll change it to unsigned long.

  Ralf

      parent reply	other threads:[~2001-02-20 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-20  4:41 pci io remapping and ide_ioreg_t Liam Davies
2001-02-20  8:52 ` Geert Uytterhoeven
2001-02-20 20:51 ` Ralf Baechle [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=20010220215118.D2086@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=ldavies@oz.agile.tv \
    --cc=linux-mips@oss.sgi.com \
    /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