From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.236.97.9 with SMTP id s9mr9568177yhf.43.1409460869988; Sat, 30 Aug 2014 21:54:29 -0700 (PDT) X-Received: by 10.140.27.140 with SMTP id 12mr2088qgx.19.1409460869941; Sat, 30 Aug 2014 21:54:29 -0700 (PDT) Path: border1.nntp.dca1.giganews.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!i13no4551059qae.1!news-out.google.com!q8ni3qal.1!nntp.google.com!i13no4551057qae.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 30 Aug 2014 21:54:29 -0700 (PDT) In-Reply-To: <929e9226-e4aa-474e-843c-68ed800eefad@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=92.109.179.4; posting-account=uePmQwoAAADTqdMkQ5mqQNa8zVpjxCa1 NNTP-Posting-Host: 92.109.179.4 References: <60a42dc6-d8d0-4432-ae5a-86de18b82840@googlegroups.com> <5kkrv9hejn2qhdckkeo8lidkbh3bkme1gn@4ax.com> <5b91313c-acf9-4a6e-b157-6ba7c8021567@googlegroups.com> <0513ad07-6fbe-463a-be6f-097cd5113f52@googlegroups.com> <4f1ec65a-d66a-40bf-a0d6-278fde206e70@googlegroups.com> <1cjwzr30b24xy.11kpydntxhfo5$.dlg@40tude.net> <929e9226-e4aa-474e-843c-68ed800eefad@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <5b5583ca-c7b2-40be-9090-6253f0514db5@googlegroups.com> Subject: Re: STM32F4 Discovery, communication and libraries From: gvdschoot@gmail.com Injection-Date: Sun, 31 Aug 2014 04:54:29 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: number.nntp.dca.giganews.com comp.lang.ada:188761 Date: 2014-08-30T21:54:29-07:00 List-Id: On Friday, August 29, 2014 6:47:52 PM UTC+2, Roy Emmerich wrote: >=20 > My requirements for dynamic behaviour don't extend so far as to be plug a= nd play ready. What I do want, being a modular hardware platform, is to def= ine, in a configuration file, which hardware modules are plugged into which= socket. At start up the supervisor will read this file and instantiate the= relevant software modules. That looks a lot like MINIX 3. A microkernel where the user can very easy c= onfigure and run drivers. http://www.minix3.org/other/reliability.html Another benefit is that with a microkernel communication between drivers an= d the kernel is standardized. It is relatively easy to create new drivers. = I don't know if you can use Ada. NetBSD rump also looks like that. https://www.usenix.org/legacy/event/usenix09/tech/full_papers/kantee/kantee= _html/