At 9:50 AM -0700 10/3/02, Derek Brans wrote:
>> Once you've done it you realize that there is a lot of hardware out 
>> there,
>> like wireless cards, cameras, drives, etc. Hardware specs for these
>> devices are often unavailable to developers because the vendors 
>> typically
>> supply their own device drivers for the standard OS's. So even if you
>> have the time to write your own device drivers, you may lack the
>> necessary documentation.
>
>Is there a compromise between "Squeak on bare hardware" and running 
>Squeak as a process on some other operating system?  What about writing 
>a version of Squeak to operate on a kernel that already exists and is 
>being ported to many platforms?
>Derek

I think building on an OS kernel (such as OSKit, as Tim mentioned) is a
great approach. It gives you excellent control all the way down, but you
can share device driver code with others working on that kernel.

Like Tim, I thought someone out there was doing exactly this. If so, I'd
love to know how it works out.

I'm amazed at the work Luciano's group is doing. Wow!!

	-- John