From mboxrd@z Thu Jan 1 00:00:00 1970 References: <4F687917.5040305@yahoo.fr> <2579e8.2258e2ff.jYph.mx@tumtum.plumbweb.net> <7F3B0E1A-1629-40B3-8A9B-872E85B580DB@gmail.com> In-Reply-To: <7F3B0E1A-1629-40B3-8A9B-872E85B580DB@gmail.com> Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=us-ascii Message-Id: <355ACE61-8887-4EB6-912E-75F7AFDC296F@bitblocks.com> Content-Transfer-Encoding: quoted-printable From: Bakul Shah Date: Sun, 22 Apr 2012 14:30:37 -0700 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] nice terminal... Topicbox-Message-UUID: 7a7fd906-ead7-11e9-9d60-3106f5b1d025 On Apr 22, 2012, at 8:47 AM, Jeffrey Green wrote: > I'm assuming the proprietary stuff that is the hurdle here is a ROM based b= oot sequence (and language). I would think that the ARM processor architectu= re is standard. If so about the ROM, is the general public completely in the= dark about it? There are is a binary containing the code that runs on the GPU; this is load= ed by the boot loader on the GPU. Then there are libGLES.so and friends that= link with your openGL ES Linux app. Not much different from what NVidia doe= s. The "kernel" is also booted by the GPU. In some ways this is simpler. To a= llow kernel choice at run time, the GPU loaded "kernel" could be 9load or gr= ub or something.=20 Linux driver to talk to the GPU is open source & CPU-GPU message types to im= plement a dumb frame buffer are documented so getting up /dev/draw shouldn't= be hard. There is a schematic for the board and a separate spec for peripherals - GPI= O, UART, PWM, etc etc. So a port should be no worse than to other ARM based SBCs. And once a port i= s done, you can have a ready to run SDHC card - no more fighting with instal= ling plan9!