All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rainer Weikusat <rainer.weikusat@sncag.com>
To: D.A.Fedorov@inp.nsk.su
Cc: linux-mtd@lists.infradead.org
Subject: Re: starting address of mtd device
Date: Tue, 20 Jul 2004 11:22:26 +0800	[thread overview]
Message-ID: <87smbn747h.fsf@farside.sncag.com> (raw)
In-Reply-To: <Pine.SGI.4.10.10407192037090.204659-100000@Sky.inp.nsk.su> (Dmitry A. Fedorov's message of "Mon, 19 Jul 2004 21:01:13 +0700")

"Dmitry A. Fedorov" <D.A.Fedorov@inp.nsk.su> writes:
[...]

> Well, what about generic physmap board module?
> I can make patch.

I could provide you with one, if you wanted to use it (enables
configuration of arbitrarily mapped distinct flash chips via command
line, a sample looks like this:

CONFIG_CMDLINE="root=/dev/mtdblock2 physmap=phys_0:0x200000@0x2800000:2,phys_1:0x800000@0x2a00000:2 mtdparts=phys_0:128k(boot),-(root);phys_1:64k(top),8064k(main),64k(bottom)"

Patch is against 2.4.26-stock, but it should be reasonably to generic
to port it easily. I am actually using this with the board I am
working at the moment, and, except the fact that the *amdstd-functions
keep panicking my kernel (next work-step to do ;-), it seems to be
working fine.

  parent reply	other threads:[~2004-07-20  3:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 19:01 starting address of mtd device Mak Kar
2004-07-19 12:30 ` Josh Boyer
2004-07-19 12:49   ` Dmitry A. Fedorov
2004-07-19 13:28     ` Josh Boyer
2004-07-19 14:01       ` Dmitry A. Fedorov
2004-07-19 15:50         ` Josh Boyer
2004-07-21 12:32           ` Josh Boyer
2004-07-22  6:07             ` Dmitry A. Fedorov
2004-07-20  3:22         ` Rainer Weikusat [this message]
2004-07-20  4:07           ` Dmitry A. Fedorov
2004-07-19 21:55   ` Mak Kar

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=87smbn747h.fsf@farside.sncag.com \
    --to=rainer.weikusat@sncag.com \
    --cc=D.A.Fedorov@inp.nsk.su \
    --cc=linux-mtd@lists.infradead.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.