9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 C compiler for Xtensa CPUs
Date: Fri,  9 Aug 2019 15:51:22 -0700	[thread overview]
Message-ID: <B20074DE-3C06-4D57-AA2B-7A0F1295E99E@bitblocks.com> (raw)
In-Reply-To: <CAOw7k5i10arTZr3ovMvk8v1i5zodiPOKSHwS0CYNtY7R4jm35A@mail.gmail.com>

On Aug 9, 2019, at 2:34 PM, Charles Forsyth <charles.forsyth@gmail.com> wrote:
> 
> Since the resources are small if not tiny, a little systems analysis and design is probably needed, but it looks like a bit of fun, until the inevitable moment of "why am I here?".
> 
> On Fri, Aug 9, 2019 at 4:50 PM Charles Forsyth <charles.forsyth@gmail.com> wrote:
> The device I've got is ESP32-WROOM-32. None of the boards I've seen that use it bother with external memory,
> so memory is limited, especially the way it's partitioned.
> 
> On Fri, Aug 9, 2019 at 3:50 PM Charles Forsyth <charles.forsyth@gmail.com> wrote:
> The ESP32 has got several MMUs. The characteristics are different depending on the part that a given MMU accesses (flash, ROM, SRAM, external memory).
> Some things are accessed using Memory Protection Units instead, which control access by Process ID, but don't do mapping. Others including some of the SRAMs are accessed through
> an MMU that can do virtual to physical mapping. The MMUs for internal SRAM0 and 2 choose protection for a given physical page as none, one or all of PIDs 2 to 7, with the virtual address that
> maps to it. PIDs 0 and 1 can access everything. PID 0 can execute privileged instructions.
> A large chunk of SRAM (SRAM 1) has only Memory Protection and no translation. The external memory MMU is the most general (most conventional).

Thanks.

Not ideal for plan9 but it would be nice to have access to all its IO capabilities over 9p.


  parent reply	other threads:[~2019-08-09 22:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26  6:37 Cyber Fonic
2019-07-26 10:02 ` Rodrigo G. López
2019-07-26 10:30 ` Charles Forsyth
2019-07-26 12:04   ` Rodrigo G. López
2019-07-26 12:12   ` Cyber Fonic
2019-07-26 15:23   ` Charles Forsyth
2019-07-27  9:16     ` Anthony Martin
2019-07-27 11:10       ` Richard Miller
2019-07-27 16:29         ` Anthony Martin
2019-08-07  0:22   ` Charles Forsyth
2019-08-07  8:07     ` Lucio De Re
2019-08-09 14:17   ` Bakul Shah
2019-08-09 14:50     ` Charles Forsyth
2019-08-09 15:50       ` Charles Forsyth
2019-08-09 21:34         ` Charles Forsyth
2019-08-09 21:48           ` Shane Morris
2019-08-09 22:51           ` Bakul Shah [this message]
2019-08-09 22:53           ` Skip Tavakkolian
2019-08-10  9:09             ` Cyber Fonic
2019-08-10  9:15               ` Shane Morris
2019-08-10 16:18               ` Charles Forsyth
2019-08-11 18:59                 ` Lyndon Nerenberg
2019-08-18 14:10                 ` Charles Forsyth
2019-08-18 14:28                   ` Richard Miller
2019-08-19 11:51                   ` Cyber Fonic
2019-08-19 14:52                     ` [9fans] Plan 9 security Ethan Gardener
2019-08-20 13:13                       ` Cyber Fonic
2019-08-20 13:28                         ` Don A. Bailey
2019-08-23 18:45                           ` Ethan Gardener
2019-08-23 19:41                             ` Don Bailey
2019-07-26 13:16 [9fans] Plan 9 C compiler for Xtensa CPUs cinap_lenrek
2023-12-04 23:20 David Boddie

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=B20074DE-3C06-4D57-AA2B-7A0F1295E99E@bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /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).