From: Johannes Erdfelt <johannes@erdfelt.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Mike Jadon <mikej@umem.com>, linux-kernel@vger.kernel.org
Subject: Re: PCI NVRAM Memory Card
Date: Fri, 10 Aug 2001 12:47:15 -0400 [thread overview]
Message-ID: <20010810124715.F1575@sventech.com> (raw)
In-Reply-To: <5.1.0.14.0.20010622101907.03ac21b0@192.168.0.5> <m17kwctghx.fsf@frodo.biederman.org> <20010810114011.X3126@sventech.com> <m1snezswqb.fsf@frodo.biederman.org>
In-Reply-To: <m1snezswqb.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Fri, Aug 10, 2001 at 10:31:08AM -0600
On Fri, Aug 10, 2001, Eric W. Biederman <ebiederm@xmission.com> wrote:
> Johannes Erdfelt <johannes@erdfelt.com> writes:
>
> > On Fri, Aug 10, 2001, Eric W. Biederman <ebiederm@xmission.com> wrote:
> > > Mike Jadon <mikej@umem.com> writes:
> > >
> > > > My company has released a PCI NVRAM memory card but we haven't developed a
> > Linux
> >
> > > >
> > > > driver for it yet. We want the driver to be open to developers to build
> > upon.
> >
> > > > Is there a specific path we should follow with this being our goal?
> > >
> > > You might want to check out the development of the mtd subsystem.
> > > http://www.linux-mtd.infradead.org/
> > >
> > > This is probably what you want to write a driver for for your NVRAM PCI card.
> >
> > Not really.
> >
> > In their case, it's a bunch of standard SDRAM on a PCI card with a
> > battery backup. It's not flash.
> >
> > A block device is all that's needed.
>
> O.k. that make sense, NVRAM has so many meanings... It still might
> make sense to support things like JFFS, and friends, though. So the
> reference isn't totally wasted.
As a block device, anything is available to be used :)
> Somehow I missed the reference to a description of what kind of
> hardware is being discussed. I wonder if the card can do DMA.
> Without bus mastering it looks tricky to get burts over the PCI bus,
> which would intern mean the card would be relatively slow. And for
> things like keeping a journal for your filesystem generally the faster
> the better. Being able to get 128MB/s would be pretty cool.
It can do DMA, even scatter gather. It's 64 bit too. It's pretty nice.
JE
next prev parent reply other threads:[~2001-08-10 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 19:30 PCI NVRAM Memory Card Mike Jadon
2001-08-08 19:49 ` Ignacio Vazquez-Abrams
2001-08-08 19:54 ` Nicholas Knight
2001-08-08 21:08 ` H. Peter Anvin
2001-08-10 9:24 ` Eric W. Biederman
2001-08-10 15:40 ` Johannes Erdfelt
2001-08-10 16:31 ` Eric W. Biederman
2001-08-10 16:47 ` Johannes Erdfelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-08 22:14 Jesse Pollard
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=20010810124715.F1575@sventech.com \
--to=johannes@erdfelt.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikej@umem.com \
/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