From: David Frascone <dave@frascone.com>
To: linux-kernel@vger.kernel.org
Subject: Faking a memory map?
Date: Tue, 11 Feb 2003 18:21:15 -0600 [thread overview]
Message-ID: <20030212002115.GD26196@wolverine> (raw)
I'm trying to get an existing SDK (userland) for a PCI hardware device
to work across a different propriatary bit-banged interface.
The original device driver just mmaped the PCI registers / address
space into userland. (talk about lazy ;)
Anyway, the hardware I'm working with is *not* on the PCI bus, and
therefore not memory-mappable. So, I'm stuck with a complex driver
design (compared to the original), and rewriting the entire bottom of
the SDK.
So, I thought: Is there a way to cheat? Would it be possible for me
to *fake* the SDK out by memory mapping some RAM, and then reading /
writing to the ram after bit-banging the device.
I looked into it some, but I couldn't figure out how to get notified
when the region was read/written to (only when the page changed). So,
is it possible to do the (admitedly ugly) hack I'm attempting?
Thanks in advance,
-Dave
--
David Frascone
What garlic is to salad, insanity is to art.
next reply other threads:[~2003-02-12 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 0:21 David Frascone [this message]
2003-02-13 18:14 ` Faking a memory map? Jeremy Jackson
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=20030212002115.GD26196@wolverine \
--to=dave@frascone.com \
--cc=linux-kernel@vger.kernel.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