public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "David Härdeman" <david@2gen.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IBM Thinkpad G41 PCMCIA problems
Date: Sun, 20 Feb 2005 10:19:02 +0000	[thread overview]
Message-ID: <20050220101902.B9509@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050220095211.GB12738@hardeman.nu>; from david@2gen.com on Sun, Feb 20, 2005 at 10:52:12AM +0100

On Sun, Feb 20, 2005 at 10:52:12AM +0100, David Härdeman wrote:
> e820 map:
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
>  BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000ce000 - 00000000000d0000 (reserved)
>  BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 000000000f6f0000 (usable)
>  BIOS-e820: 000000000f6f0000 - 000000000f700000 (reserved)
>  BIOS-e820: 000000000f700000 - 000000003f6f0000 (usable)
>  BIOS-e820: 000000003f6f0000 - 000000003f6f8000 (ACPI data)
>  BIOS-e820: 000000003f6f8000 - 000000003f6fa000 (ACPI NVS)
>  BIOS-e820: 000000003f700000 - 0000000040000000 (reserved)
>  BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved)
> 118MB HIGHMEM available.
> 896MB LOWMEM available.
> 
> Is the hole between 0x36f6fa000 and 0x3f700000?

Looks like it.

> And what would be the proper way of fixing it (assuming that IBM won't 
> issue a fixed BIOS)?

Try passing:

	reserve=0x3f6fa000,0x6000

to the kernel.

-- 
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

  reply	other threads:[~2005-02-20 10:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-20  9:22 IBM Thinkpad G41 PCMCIA problems David Härdeman
2005-02-20  9:26 ` Russell King
2005-02-20  9:52   ` David Härdeman
2005-02-20 10:19     ` Russell King [this message]
2005-02-20 10:57       ` David Härdeman
2005-02-20 10:20     ` Dominik Brodowski
2005-02-20 10:25       ` Russell King
     [not found] <3zVzJ-1GD-5@gated-at.bofh.it>
     [not found] ` <3zVzM-1GD-17@gated-at.bofh.it>
     [not found]   ` <3zW2R-1Yl-15@gated-at.bofh.it>
     [not found]     ` <3zWvU-2tS-25@gated-at.bofh.it>
     [not found]       ` <3zWYX-2Ob-23@gated-at.bofh.it>
2005-02-21  9:49         ` Bjørn Mork

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=20050220101902.B9509@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=david@2gen.com \
    --cc=linux-kernel@vger.kernel.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