>Why is FireWire too much work? At the core, both Ethernet and
>FireWire are "simply" fast serial ports. (:
Having ethernet or firewire as serial ports on the Newton (i.e. with
the serial-port endpoint APIs) wouldn't be very useful and would be
painfully slow. Heh, imagine an ATA driver in NewtonScript :)
>"All" someone would have to do is write a FireWire driver as if it
>were an Ethernet driver, and voila, FireWire for the Newton!
Er, I don't think so.
>"All, he says," I hear you saying. Yes, I realize that nothing is
>that simple-- there are probably two totally different communication
>stacks involved
Yes, this is the main problem.
>As far as the power is concerned
The only problem with power is, I think, that it's going to suck
batteries pretty fast. I'm pretty sure that if it is plugged, the
Newton can provide enough power.
> >Hey, Paul? Correct me if I'm wrong!
You're right Laurent.
We could interface the FireWire driver with the ATA driver, though,
to use storage drives.
But the question is: is it really worth the effort or shouldn't we
work on other things? Personally, I'd prefer a driver for an
Airport-compatible card.
Paul
-- Home page: http://www.kallisys.com/ Newton-powered WebServer: http://newt.dyndns.org:8080/-- This is the Newtontalk mailinglist - http://www.newtontalk.net To unsubscribe or manage: visit the above link or mailto:newtontalk-request_at_newtontalk.net?Subject=unsubscribe
This archive was generated by hypermail 2.1.2 : Thu Nov 01 2001 - 10:02:38 EST