All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Updegraff <dave@cray.com>
To: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Physically mapped FLASH
Date: Wed, 22 Aug 2001 08:32:28 -0500	[thread overview]
Message-ID: <3B83B46C.8030805@cray.com> (raw)
In-Reply-To: 20010822134155.4105@mailhost.mipsys.com


Hi.

Is there a reason why the physical-mapping setup (drivers/mtd/maps/physmap.c)
is coded to ONLY talk to CFI chips?  For example I have some 405gp things
that have AMD Flash chips that are physically mapped to the top of memory
and could be driven by the algorithms in drivers/mtd/chips/amd_flash.c.

I've patched it and it appears to work ok; is it a bad idea?  is it good idea?
Any interest in incorporating in?

--
Dave Updegraff / dave@cray.com / 218-525-1154


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

  reply	other threads:[~2001-08-22 13:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 10:22 status of linuxppc_2_4_devel for ppc405gp Stefan Roese
2001-08-22 12:30 ` Kenneth Johansson
2001-08-22 16:10   ` Dan Malek
2001-08-22 22:29     ` Phillip Lougher
2001-08-22 22:48       ` Dan Malek
2001-08-22 13:41 ` Benjamin Herrenschmidt
2001-08-22 13:32   ` David Updegraff [this message]
2001-08-22 10:32     ` Physically mapped FLASH Matt Porter
2001-08-22 16:06   ` status of linuxppc_2_4_devel for ppc405gp Dan Malek
     [not found]     ` <3B83E474.5B906F13@mvista.com>
2001-08-22 19:31       ` Dan Malek
2001-08-22 20:04     ` Benjamin Herrenschmidt
2001-08-23  0:40       ` David Gibson
2001-08-23  7:41         ` Benjamin Herrenschmidt
2001-08-23 11:08           ` Benjamin Herrenschmidt
2001-08-24  1:41             ` David Gibson
2001-08-24  5:06               ` Dan Malek
2001-08-24  6:03                 ` David Gibson
2001-08-24 10:28                 ` Benjamin Herrenschmidt
2001-08-25  2:53                   ` Dan Malek

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=3B83B46C.8030805@cray.com \
    --to=dave@cray.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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.