All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew McGregor <andrew@indranet.co.nz>
To: Vanja Hrustic <vanja@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: PCI problem with RICOH RL5C475 PCI/PCMCIA adapter, on 2.4.26
Date: Fri, 30 Apr 2004 00:12:06 +1200	[thread overview]
Message-ID: <816034775.1083283926@T400> (raw)
In-Reply-To: <20040428183325.2860bd95.vanja@pobox.com>



--On Wednesday, 28 April 2004 6:33 p.m. +0200 Vanja Hrustic 
<vanja@pobox.com> wrote:

> I have PCI-PCMCIA adapter (Ricoh RL5C475 based) in a desktop machine.
>
> Initially, I had problems making it work, but managed to get help on
> comp.os.linux.portable. Now, most of the cards work okay.
>
> However, I still have one wireless PCMCIA card (Prism GT based) which
> doesn't work, and was advised to post the problem here.
>
> Dave (from comp.os.linux.portable) said:
>
> "This part is a tricky one.  It is a bug in the kernel's PCI resource
> allocation code.  It tries to allocate CardBus memory resources from
> whatever memory ranges happened to be allocated for the bridge device
> by the BIOS at power-up time; but in this case, those memory windows
> are too small.  There isn't a simple fix for this and I don't have a
> good suggestion for what to do about it; you can report it on the
> linux-kernel mailing list."

Ok, so I see the same thing with a Ricoh PC104+ to Cardbus adaptor on a 
little industrial PC, except I'm using an Atheros-based wireless card 
instead.  I get this with 2.4.25:

01:00.0 Class 0200: 168c:0013 (rev 01)
        Subsystem: 1186:3202
        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Step
ping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort
- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 12
        Region 0: [virtual] Memory at d5120000 (32-bit, non-prefetchable) 
[size=
8K]
        Capabilities: [44] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=2 PME-


cs: cb_alloc(bus 1): vendor 0x168c, device 0x0013
PCI: Failed to allocate resource 0(d5120000-d5121fff) for 01:00.0
PCI: Enabling device 01:00.0 (0000 -> 0002)

Again, any assistance greatly appreciated, and I'll test any proposed 
patches.

Andrew


      reply	other threads:[~2004-04-29 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 16:33 PCI problem with RICOH RL5C475 PCI/PCMCIA adapter, on 2.4.26 Vanja Hrustic
2004-04-29 12:12 ` Andrew McGregor [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=816034775.1083283926@T400 \
    --to=andrew@indranet.co.nz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vanja@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.