public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessio Sangalli <alesan@manoweb.com>
To: Ben Dooks <ben-linux@fluff.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Driver for tightly coupled memory
Date: Tue, 16 Sep 2008 10:39:11 -0700	[thread overview]
Message-ID: <48CFEF3F.5040901@manoweb.com> (raw)
In-Reply-To: <20080916093513.GF1916@fluff.org.uk>

Ben Dooks wrote:

> This isn't the right list to be discussing this on, try looking for
> linux-arm-kernel instead. It will get your question to the attention
> of more people knowledgable about the ARM specifics.

I disagree, something like a TCM can very well be present in any
architecture, after all it's some kind of fast memory mapped to an
address, nothing special from a software point of view. I will ask on
the ARM mailing list however.


> IIRC, there's no current support for using TCMs.

I think I will write a module that implements a software FIFO. One
function to allocate a FIFO n words deep, a "push" and a "pop" and
similar. The calling module will have to setup the FIFO and use it
probably in ISRs or similar (the policy will totally remain in the
caller module). Any comments on such approach?

bye
Alessio

  reply	other threads:[~2008-09-16 17:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15 20:35 Driver for tightly coupled memory Alessio Sangalli
2008-09-16  9:35 ` Ben Dooks
2008-09-16 17:39   ` Alessio Sangalli [this message]
2008-09-16 22:27     ` Ben Nizette
2008-09-16 22:49       ` Alessio Sangalli
2008-09-16 23:04         ` Ben Nizette
2008-09-16 23:52           ` Alessio Sangalli
2008-09-17  2:42         ` Valdis.Kletnieks
2008-09-17  5:27           ` Alessio Sangalli
2008-09-17  5:39             ` Valdis.Kletnieks
2008-09-17  5:55               ` Alessio Sangalli

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=48CFEF3F.5040901@manoweb.com \
    --to=alesan@manoweb.com \
    --cc=ben-linux@fluff.org \
    --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