linux-kernel - Re: Driver for tightly coupled memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Sep 2008 10:39:11 -0700
From:	Alessio Sangalli <alesan@...oweb.com>
To:	Ben Dooks <ben-linux@...ff.org>
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Driver for tightly coupled memory

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/