All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: "Linux-Mtd" <linux-mtd@lists.infradead.org>
Subject: FW: Re: mapping of boot loader offset
Date: Fri, 12 Apr 2002 11:47:48 +0200	[thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJOECDCEAA.Stephan.Linke@epygi.de> (raw)

> -----Original Message-----
> From: Stephan Linke [mailto:Stephan.Linke@epygi.de]
> Sent: Donnerstag, 11. April 2002 18:50
> To: Tino Keitel
> Cc: Linux-Mtd-Admin           <---------- :o) oops
> Subject: RE: mapping of boot loader offset
> 
> 
> Hi!
> 
> You may probably fix it by using the mapping file for your mtd 
> driver. I mean the stuff placed in drivers/mtd/maps.
> 
> Here you have the chance to manipulate the addresses of the flash 
> access. You have to call the real access function of the actual 
> flash driver. So you could simply check the offset of the access 
> and if its above the "magic" address of your boot loader you 
> could add an additional offset. That's it. I didn't do that yet 
> and I think it's not the basic intantion of that mapping files. 
> (I think they should be used to split up flash areas, not to 
> connect them.) But I think it could work.
> 
> Maybe someone else has an "official" idea ;-). If not...
> 
> Regards, Stephan
> 
> > -----Original Message-----
> > From: linux-mtd-admin@lists.infradead.org
> > [mailto:linux-mtd-admin@lists.infradead.org]On Behalf Of Tino Keitel
> > Sent: Donnerstag, 11. April 2002 16:30
> > To: linux-mtd@lists.infradead.org
> > Subject: mapping of boot loader offset
> > 
> > 
> > Hi folks,
> > 
> > I wonder what to do if a processor looks for its BIOS/loader at a 
> > specified
> > address that is somewhere in the middle of a flash chip. The same 
> > chip will
> > contain one JFFS2. The boot loader area will have to be mapped 
> out of the
> > file system. Is there already something that MTD can do for me?
> > 
> > Regards,
> > Tino
> > 
> > -- 
> > tino.keitel@innominate.com
> > dipl.-inf.                        Innominate Security Technologies AG
> > software engineer                                   networking people
> > tel: +49.30.6392-3308                      http://www.innominate.com/
> > 
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/
> > 

                 reply	other threads:[~2002-04-12  9:47 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=FCEAKDJJAPHPLJFINDAJOECDCEAA.Stephan.Linke@epygi.de \
    --to=stephan.linke@epygi.de \
    --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.