[Coco] two other things..

[Chuck Youse]

Actually, I was intending separate cards;

1. An FDC card
2. An IDE controller (maybe.  kinda pointless, my proto FDCs have IDE on
them for _me_, and other folks have IDE controllers out there, Cloud-9
e.g.)
3. Dual UART card
4. Ethernet card

C.

On Wed, 2008-07-09 at 15:45 -0400, mike delyea wrote:
> Yes that sounds really useful.  If I'm correct you would have a floppy
> controller, an IDE controller, ethernet and at least 1 serial port on
> the card?  Yes, I'd really be interested in something like that.
> 
> On Wed, Jul 9, 2008 at 3:35 PM, Chuck Youse
> <cyouse at serialtechnologies.com> wrote:
> > .. on the drawing board, if anyone's interested in what I have coming
> > up.
> >
> > 1. Well, I need to respin the FDC.  Couple of changes required.
> > 2. A 10baseT ethernet interface w/ IP stack for NitrOS-9;
> > 3. A dual 16550-compatible UART card.
> >
> > Hardware-wise, #2 and #3 are both easy.  Software-wise, #3 will be a
> > breeze.  #2 will be tough because I'll need to write a new file manager
> > and such.
> >
> > But I really think the only thing that makes using NitrOS-9 today
> > somewhat problematic is its lack of Ethernet/IP support.  I could
> > _totally_ use it as a workstation if it were networked.  And no, SLIP
> > doesn't count (too slow!).
> >
> > For those who are dubious, no, TCP/IP isn't terribly difficult to
> > implement -- TCP can be tricky when your aim is high throughput, but I'm
> > not aiming at that.  We're talking limited window sizes here.
> >
> > C.
> >
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> >
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco