linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Donald White" <dbwhite@asu.edu>
To: "linux-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Question about porting VxWorks driver
Date: Thu, 03 Apr 2003 01:11:18 -0700	[thread overview]
Message-ID: <3E8BECA6.6060709@asu.edu> (raw)


I am porting a Vxworks driver for an encryption chip from Vxworks to Linux on a
cutom MPC860 board.  The Linux is HHL 2.0.  The driver communicates with the chip
through chip registers and shared memory buffers.  The VxWorks driver set the system
memory cache policy to writethrough.  I am using ioremap for the chip registers and
consistent_alloc for the shared buffers.  This all works fine.  Now for my questions.

Is this the right approach for me to take?  Does Linux support designating memory
regions for writethrough caching?  If it does, should I use it rather than doing
what I am doing?

Thanks,

Don


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-04-03  8:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03  8:11 Donald White [this message]
2003-04-03 15:27 ` Question about porting VxWorks driver Dan Malek
2003-04-03 15:41 ` Vladimir Gurevich

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=3E8BECA6.6060709@asu.edu \
    --to=dbwhite@asu.edu \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).