public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>, Greg KH <gregkh@suse.de>
Subject: Re: IBM Thinkpad G41 PCMCIA problems [Was: Yenta TI: ... no PCI interrupts. Fish. Please report.]
Date: Sun, 20 Feb 2005 08:22:26 +0000	[thread overview]
Message-ID: <20050220082226.A7093@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1108863372.8413.158.camel@localhost.localdomain>; from rostedt@goodmis.org on Sat, Feb 19, 2005 at 08:36:12PM -0500

On Sat, Feb 19, 2005 at 08:36:12PM -0500, Steven Rostedt wrote:
> Linux version 2.6.10 (root@bilbo) (gcc version 3.3.5 (Debian 1:3.3.5-8)) #13 SMP Sat Feb 19 20:12:19 EST 2005
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
>  BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000d0000 - 00000000000d4000 (reserved)
>  BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 000000000f6f0000 (usable)
>  BIOS-e820: 000000000f6f0000 - 000000000f700000 (reserved)
>  BIOS-e820: 000000000f700000 - 000000003fef0000 (usable)
>  BIOS-e820: 000000003fef0000 - 000000003fef8000 (ACPI data)
>  BIOS-e820: 000000003fef8000 - 000000003fefa000 (ACPI NVS)
>  BIOS-e820: 000000003ff00000 - 0000000040000000 (reserved)

Your BIOS is broken.  You probably have 1GB of RAM which extends from
0x00000000 to 0x40000000.  However, there's a hole in the ACPI map
between 0x3fefa000 and 0x3ff00000.  This is where your Cardbus devices
are ending up:

> 3fefa000-3fefa3ff : 0000:00:1f.1
> 3fefb000-3fefbfff : 0000:02:01.0
>   3fefb000-3fefbfff : yenta_socket
> 3fefc000-3fefcfff : 0000:02:01.1
>   3fefc000-3fefcfff : yenta_socket

Changing the bridge type to non-transparent just means that we find
we can't allocate the bridge resources in this small window, so they
get moved elsewhere.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  parent reply	other threads:[~2005-02-20  8:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-20  0:22 IBM Thinkpad G41 PCMCIA problems [Was: Yenta TI: ... no PCI interrupts. Fish. Please report.] Steven Rostedt
2005-02-20  0:59 ` Linus Torvalds
2005-02-20  1:36   ` Steven Rostedt
2005-02-20  2:10     ` Linus Torvalds
2005-02-20  3:38       ` Steven Rostedt
2005-02-20  4:02         ` Linus Torvalds
2005-03-12  3:31           ` Adam Belay
2005-02-20  6:51         ` Linus Torvalds
2005-02-20  7:06           ` Linus Torvalds
2005-02-20 11:48           ` Steven Rostedt
2005-02-20  8:22     ` Russell King [this message]
2005-02-20 10:20       ` Russell King
2005-02-20 11:59         ` Steven Rostedt
2005-02-20 11:54       ` Steven Rostedt
2005-02-20 17:23       ` Linus Torvalds
2005-02-20 17:56         ` Linus Torvalds
2005-02-20 21:26           ` IBM Thinkpad G41 PCMCIA problems [Was: Yenta TI: ... no PCI David Härdeman
2005-02-21  4:19           ` IBM Thinkpad G41 PCMCIA problems [Was: Yenta TI: ... no PCI interrupts. Fish. Please report.] Steven Rostedt
2005-03-12  3:36         ` Adam Belay

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=20050220082226.A7093@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@osdl.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