All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederman@lnxi.com (Eric W. Biederman)
To: "Daniel Engström" <daniel@omicron.se>
Cc: robert@schwebel.de, linux-mtd@lists.infradead.org,
	"Klaus-D . Walter" <k.d.walter@t-online.de>
Subject: Re: MTD concat layer
Date: 13 Feb 2002 07:01:35 -0700	[thread overview]
Message-ID: <m3sn85pjk0.fsf@DLT.linuxnetworx.com> (raw)
In-Reply-To: <20020213143336.C26867@jupiter.omicron.se>

Daniel Engström <daniel@omicron.se> writes:

> On 2002.02.13 12:37 Robert Schwebel wrote:
> > The DNP has only one Intel 28F016F3 flash chip. Does anybody know
> > something about the reason why this strange layout for the BIOS was
> > chosen?
> 
> The realmode BIOS must reside at 0xf0000-0xfffff in system
> memory. Depending
> on which options the chipset offers to map the flash, the BIOS may have to
> be located in the middle of the flash device.

Hmm.  Except the BIOS starts executing at 0xfffffff0 in system memory,
so ROMS chips usually reside at 0xfff00000 - 0xffffffff.  Usually an
alias exists at 0xf0000-0xfffff is handy but not required.  (I
don't use it when I port LinuxBIOS to a new board).  But usually
0xf0000-0xfffff on x86 is surrounded by RAM so this does not appear to
be the reason.

Eric

  reply	other threads:[~2002-02-13 13:50 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 18:40 MTD concat layer Robert Kaiser
2002-02-13  7:56 ` Suspend Erase bug in cfi_cmdset0001.c Joakim Tjernlund
2002-02-14  8:17   ` Joakim Tjernlund
2002-02-13 11:00 ` MTD concat layer Joakim Tjernlund
2002-02-13 11:04   ` David Woodhouse
2002-02-13 11:34     ` Robert Kaiser
2002-02-13 11:37     ` Robert Schwebel
2002-02-13 13:33       ` Daniel Engström
2002-02-13 14:01         ` Eric W. Biederman [this message]
2002-02-15 15:58 ` David Woodhouse
2002-02-15 17:43   ` Robert Kaiser
2002-02-15 18:02     ` David Woodhouse
2002-02-15 18:40       ` Jörn Engel
2002-02-16 10:33         ` Robert Kaiser
2002-02-16 10:43       ` Robert Kaiser
2002-02-16 10:43         ` David Woodhouse
2002-02-16 11:03           ` Robert Kaiser
2002-02-16 11:08             ` David Woodhouse
2002-02-16 14:56             ` Brian J. Fox
2002-02-17 10:36               ` Robert Kaiser
2002-02-17 19:05                 ` Brian J. Fox
2002-02-18  8:48                   ` Robert Kaiser
2002-02-18  9:05                     ` David Woodhouse
2002-02-18 15:53                       ` Brian J. Fox
2002-02-18 17:01                         ` Robert Kaiser
2002-02-18 17:02                           ` David Woodhouse
2002-02-18 15:46                     ` Brian J. Fox
2002-02-20 14:28 ` Jonas Holmberg
2002-02-20 15:35   ` Robert Kaiser
2002-02-21 14:51     ` Jonas Holmberg
2002-02-26 11:32       ` Robert Kaiser
2002-03-06 13:37         ` Jonas Holmberg
2002-03-06 16:02           ` Robert Kaiser
  -- strict thread matches above, loose matches on Subject: below --
2002-02-14 11:14 Jonas Holmberg
2002-03-08 16:08 Robert Kaiser
2002-03-08 16:22 ` David Woodhouse

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=m3sn85pjk0.fsf@DLT.linuxnetworx.com \
    --to=ebiederman@lnxi.com \
    --cc=daniel@omicron.se \
    --cc=k.d.walter@t-online.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=robert@schwebel.de \
    /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.