From: Geoffroy Stevenne <geof@hellea.com>
To: linux-mtd@lists.infradead.org
Subject: Re: writing new BBRAM driver
Date: Mon, 16 Dec 2002 13:54:14 +0100 [thread overview]
Message-ID: <20021216135414.6d72949c.geof@hellea.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0212161057400.28011-100000@www.optixsoft.de>
Hi,
On Mon, 16 Dec 2002 11:14:41 +0100 (MET)
Tobias Otto-Adamczak <toa@indakom.de> wrote:
> Alex Pavloff, 2002-12-13, 15:45h:
>
> > Hi there folks. I've written the struct mtd_info functions for a
> > 128KB BBRAM driver for my companies new board. It's horribly
> > simple, as most of it is actually done by a gate array on the board,
> > so from kernel land its just poking ioports. Easy stuff.
Great! If it works with the versalogic board it will be tested
here with a 512KB BBRAM. Of course I'll provide maximum feedback
(maybe patches if any required). Thanks!
--
Geoffroy
next prev parent reply other threads:[~2002-12-16 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 23:45 writing new BBRAM driver Alex Pavloff
2002-12-16 10:14 ` Tobias Otto-Adamczak
2002-12-16 12:54 ` Geoffroy Stevenne [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-16 22:33 Alex Pavloff
2002-12-17 9:12 ` Jörn Engel
2002-12-17 9:49 ` Tobias Otto-Adamczak
2002-12-20 1:14 Alex Pavloff
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=20021216135414.6d72949c.geof@hellea.com \
--to=geof@hellea.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