All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jared Hulbert <jaredeh@gmail.com>
To: "JobHunts02@aol.com" <JobHunts02@aol.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Flash with boot blocks in kernel 2.4
Date: Thu, 26 May 2005 11:02:49 -0700	[thread overview]
Message-ID: <6934efce05052611026685ab6f@mail.gmail.com> (raw)
In-Reply-To: <197.3f3af727.2fbed9f0@aol.com>

On 5/19/05, JobHunts02@aol.com <JobHunts02@aol.com> wrote:
> I am working with kernel 2.4 on a board with two flash chips that have boot
> blocks, Intel Advanced Boot Block Flash Memory (28F320C3).  I just read that
> "the 2.4 CFI code handles only devices with uniform eraseblock size -- not the
> devices with 'boot blocks'. Current CVS fixes that for AMD chips, and it's
> trivial to do the same for Intel chips, now it's been done once," according to the
> MTD project leader.
> 
> Does anyone know where on the web I can find these "trivial" changes for
> Intel chips?
> 
> Thank you.
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 

Newer MTD rev's fix this.  Back porting a new MTD should help you.

FYI - I don't think JFFS2 can span boot blocks and regular block,
though now that I think of it I've never tried.  Anybody know if
that's true or not?

      reply	other threads:[~2005-05-26 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20  6:13 Flash with boot blocks in kernel 2.4 JobHunts02
2005-05-26 18:02 ` Jared Hulbert [this message]

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=6934efce05052611026685ab6f@mail.gmail.com \
    --to=jaredeh@gmail.com \
    --cc=JobHunts02@aol.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 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.