linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wang Jian <lark@linux.net.cn>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: mpc8541 pci1 ioport allocation address space problem
Date: Tue, 23 Sep 2008 22:24:54 +0800	[thread overview]
Message-ID: <48D8FC36.9080407@linux.net.cn> (raw)
In-Reply-To: <1222062464.12085.25.camel@pasglop>

Confirmed.

I had this patch and 2 fixes on dts applied simultaneously, and the board
works. I thought this patch was necessary.

I reverted this patch and tried again, the board still works. Thanks for
your insight.

Anyway, the io port read from /proc/ioports is misleading, so I wish it
can be changed a little.


Regards

Benjamin Herrenschmidt wrote:
> This is expected and should work. Depending on the relative
> physical addresses of IO space and the order in which the bridges are
> discovered, the bridge IO ports will look at either positive or negative
> values. This should be fine, as port numbers are supposed to be 32 bits
> and in-kernel arithmetic should do the right thing... I suppose unless a
> driver stores those in a 64 bits integer and doesn't sign extend.
> 
> I would like to change that whole thing to something more similar to
> 64 bits where I reserve a portion of the address space for IO ports,
> though address space on 32 bits platforms is scarce, but nothing I have
> time to toy with right now.
> 
> Cheers,
> Ben. 
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 
> 

  reply	other threads:[~2008-09-23 14:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-20 11:16 mpc8541 pci1 ioport allocation address space problem Wang Jian
2008-09-21  1:19 ` Wang Jian
2008-09-23  6:55   ` Benjamin Herrenschmidt
2008-09-22  5:47 ` Benjamin Herrenschmidt
2008-09-23 14:24   ` Wang Jian [this message]
2008-09-23 21:16     ` Benjamin Herrenschmidt

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=48D8FC36.9080407@linux.net.cn \
    --to=lark@linux.net.cn \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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).