public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Joel Coltoff <joel@wmi.com>
To: linux-mtd@lists.infradead.org
Subject: Question on configuring for a MIPS processor
Date: Tue, 17 Oct 2006 17:36:17 +0000	[thread overview]
Message-ID: <45351491.7070207@wmi.com> (raw)

Hi,

First let me apologize if this is in the archive. I've checked
a bit and didn't see it. I'm a bit surprised that it isn't.

We are running, for the moment, a bit of a hack. We are using
a 2.4.18 kernel that has been updated to support a subset of
the intel 28F256P30 strataflash. It seems to be working. In
the meantime, work goes on doing a board support package for
2.6.17.

The problem we are facing is that our flash runs from
0x1f000000 - 0x21000000. Since we are running on a MIPS we've
got boot code at 0x1fc000000 which sort of gets in the way. There's
other stuff that fills memory up to 0x20000000. I've got no problem
having /dev/mtdb0 use the space from the start of flash up to
0x1fc00000. What I'd like to be able to do is use the rest of
the flash. I'm reasonable certain it would be foolish to treat the
memory as 2 devices. Should I use fdisk to create my flash drives?
Is there another way to handle this?

If I do use fdisk what make sense for heads/sectors/cylinders?
In theory, fdisk seems like the best way to go. What I mean
by that is do I want my sector size to be 128K. I really don't
know how the code works when only part of a sector gets updated.

Thanks for your help,
  - Joel

                 reply	other threads:[~2006-10-17 17:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=45351491.7070207@wmi.com \
    --to=joel@wmi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox