From: Thomas Gleixner <tglx@linutronix.de>
To: Geoffroy Stevenne <geof@hellea.com>, linux-mtd@lists.infradead.org
Cc: jch@hellea.be
Subject: Re: bbram access problems
Date: Thu, 12 Dec 2002 15:40:43 +0100 [thread overview]
Message-ID: <200212121540.43586.tglx@linutronix.de> (raw)
In-Reply-To: <20021212140546.3607a3e0.geof@hellea.com>
On Thursday 12 December 2002 14:05, Geoffroy Stevenne wrote:
> Hi,
>
> We're trying to use BBRAM on a VersaLogic VSBC-6 m-b. We use the slram
> driver and the 2.4.18 kernel. The problem is that we can't acces the
> entire memory of the BBRAM, just the first 64k page.
>
> Other problem: we added to our lilo.conf:
>
> append="slram=BBRAM,0xE0000,+0x10000"
>
> We can write to the BBRAM but we noticed data corruption (not write
> operation was done) in this address range. Is there a way to lock this
> memory area? Is this the right thing to do?
>
> What we need is to mount a filesystem on the entire BBRAM, not just the
> first 64k. I can (and wish to) provide more information, test changes,
> report bugs, etc. I can read and understand C code but I don't feel
> competent in writing drivers on my own.
from slram.c
NOTE:
With slram it's only possible to map a contigous memory region.
So you can't access it with slram, as the BBSRAM is a device with paged
access. All you have to do, is copy slram.c to bbram.c and add an additional
parameter, which tells the driver the number of pages.available. Then modify
the erase / read / write functions to do the page selection depending on the
address you have to access.
If you think this is out of your league, then hope, that somebody does this
for you sometimes, or ask one of the experts to help you for a little fee
immidiately :)
--
Thomas
____________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2002-12-12 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 13:05 bbram access problems Geoffroy Stevenne
2002-12-12 13:45 ` Jörn Engel
2002-12-12 14:09 ` Tobias Otto-Adamczak
2002-12-12 15:09 ` Jörn Engel
2002-12-12 13:54 ` Tobias Otto-Adamczak
2002-12-12 14:40 ` Thomas Gleixner [this message]
2002-12-13 11:50 ` Geoffroy Stevenne
2002-12-13 13:35 ` Geoffroy Stevenne
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=200212121540.43586.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=geof@hellea.com \
--cc=jch@hellea.be \
--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