linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Tobler <toa@pop.agri.ch>
To: mlan@cpu.lu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2940UW & 2.4.0-test-ac7 PCI probs
Date: Tue, 06 Jun 2000 14:57:37 +0200	[thread overview]
Message-ID: <393CF541.4E4D88B7@pop.agri.ch> (raw)
In-Reply-To: 200006061136.NAA01541@piglet.grunz.lu


Hi,

Michel Lanners wrote:
> >   for root[0:ffffffff] min[1000] size[100]
> >   got res[1000:10ff] for resource 0
>
> This must be the conflicting resource, but it gets an equally-wrong new
> address :-(( In fact, the PCI resource code still misses a patch to make
> the correct resources available to the resource allocation code (so that
> IO regions can be taken out of the IO region of the correct PCI bus..)
>
> I'm still working on that part ;-)

Thanks!

>
> So if the SCSI driver actually uses the IO region, it will most
> certainly not work....

How do I find that out?

Below it says I/O ports unassigned and it works. (2399p9)

00:0e.0 SCSI storage controller: Adaptec AIC-7881U
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr-
Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 8 min, 8 max, 32 set, cache line size 08
        Interrupt: pin A routed to IRQ 24
        Region 0: I/O ports at <unassigned>
        Region 1: Memory at 80801000 (32-bit, non-prefetchable)

Andreas

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

  reply	other threads:[~2000-06-06 12:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-05 15:56 2940UW & 2.4.0-test-ac7 PCI probs Andreas Tobler
2000-06-05 20:39 ` Michel Lanners
2000-06-06  6:37   ` Geert Uytterhoeven
2000-06-06  6:48   ` Andreas Tobler
2000-06-06 11:36     ` Michel Lanners
2000-06-06 12:57       ` Andreas Tobler [this message]
2000-06-07  5:57         ` Michel Lanners

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=393CF541.4E4D88B7@pop.agri.ch \
    --to=toa@pop.agri.ch \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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).