well the socket is read only. no writes allowed.  one might be able to
adopt the rex methodology however to enable writes in a read only socket.

On Wed, Sep 20, 2017 at 5:39 PM, Douglas Quagliana <[email protected]>
wrote:

> I don't think there's a speed issue. They benchmarked the speed of the
> GPIO pins on a Raspberry Pi and they were able to toggle the output pins at
> 22 Megahertz using an optimized program written in C.  See
>
> http://codeandlife.com/2012/07/03/benchmarking-raspberry-pi-gpio-speed/
>
> The Model T's 8085 CPU is running way slower than 22 Megahertz.  I would
> think that there's plenty of time to read the GPIO pins, decode the
> address, set the data lines and flip the OE pin (or whatever else needs to
> be set).  No?
>
> I thought there might be an electrical incompatibility (wrong voltage,
> can't source/sink enough current) or something else that prevented a direct
> hookup between the GPIO pins and the option ROM pins.
>
> C'mon... Nobody even tried this yet?
>
> Douglas
>
> On Wed, Sep 20, 2017 at 10:03 AM, John R. Hogerhuis <[email protected]>
> wrote:
>
>> A raspberry pi cannot simulate a ROM chip as far as I know.
>>
>> Seems like it would be a speed issue.
>>
>> You could do interface a pi to serial port though, that has been done.
>>
>> -- John
>>
>
>

Reply via email to