Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: Grant Grundler <grundler@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] a500.out16
Date: Thu, 2 Nov 2000 11:30:47 +0000	[thread overview]
Message-ID: <20001102113047.J32715@linuxcare.com> (raw)
In-Reply-To: <20001102104306.F32715@linuxcare.com>; from rhirst@linuxcare.com on Thu, Nov 02, 2000 at 10:43:06AM +0000

On Thu, Nov 02, 2000 at 10:43:06AM +0000, Richard Hirst wrote:
> On Thu, Nov 02, 2000 at 12:21:36AM -0800, Grant Grundler wrote:
> > Hi Richard (et al),
> > I finally think I understand how pcibios_align_resource() is used...
> > that definitely was the problem. Everything on A500 but PCI-PCI bridge
> > seems to be assigned I/O port and MMIO addresses correctly.
> > 
> > I'll look at tulip code tomorrow to see why it's not happy.
> 
> I fixed tulip_core.c to report what it means, which gave me
> 
> tulip: MMIO resource (0x400@0xfffffffff8020000) unavailable, aborting
> 
> Note sym53c8xx.c doesn't seem to bother with request_mem_region(), so
> maybe request_mem_region() is just broken.

It is broken because of the following line in kernel/resource.c:

struct resource iomem_resource = { "PCI mem", 0x00000000, 0xffffffff, IORESOURCE_MEM };

'end' needs to be rather higher than 0xffffffff on 64 bit.  I changed it to

struct resource iomem_resource = { "PCI mem", 0x00000000, ~0, IORESOURCE_MEM };

and it works.  I havn't committed that 'fix' though.

Richard

  reply	other threads:[~2000-11-02 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02  8:21 [parisc-linux] a500.out16 Grant Grundler
2000-11-02 10:43 ` Richard Hirst
2000-11-02 11:30   ` Richard Hirst [this message]
2000-11-02 12:01     ` Matthew Wilcox
2000-11-02 16:42       ` Grant Grundler
2000-11-02 12:07   ` Richard Hirst
2000-11-02 10:48 ` Richard Hirst
2000-11-02 16:12   ` Grant Grundler

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=20001102113047.J32715@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.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