Matthew N. Dodd wrote:
On Sat, 28 Aug 1999, Kris Kirby wrote:
Both. The problem is that you can't cram a signal moving at 10 Mbps
through a radio interface designed for 256K, even if it is bandwidth
limited to 256K. I'm hoping the 3C503 is ancient enough that I can slow
it down by
On Sun, 29 Aug 1999, Warner Losh wrote:
: I have some frequecy hopping radio modems that use the 82593 to get
: 256kbps or so...
Speaking of which, I'll give two free to someone that commits to
writing a driver for these beasts. It would be an excellent chance
for reverse engineering
hi, there!
On Mon, 30 Aug 1999, Matthew N. Dodd wrote:
: I have some frequecy hopping radio modems that use the 82593 to get
: 256kbps or so...
Speaking of which, I'll give two free to someone that commits to
writing a driver for these beasts. It would be an excellent chance
for
Matthew N. Dodd wrote:
On Sat, 28 Aug 1999, Kris Kirby wrote:
Both. The problem is that you can't cram a signal moving at 10 Mbps
through a radio interface designed for 256K, even if it is bandwidth
limited to 256K. I'm hoping the 3C503 is ancient enough that I can slow
it down by
In message pine.bsf.4.10.9908281545220.1358-100...@sasami.jurai.net Matthew
N. Dodd writes:
: On Sat, 28 Aug 1999, Kris Kirby wrote:
: Both. The problem is that you can't cram a signal moving at 10 Mbps
: through a radio interface designed for 256K, even if it is bandwidth
: limited to 256K.
: I have some frequecy hopping radio modems that use the 82593 to get
: 256kbps or so...
Speaking of which, I'll give two free to someone that commits to
writing a driver for these beasts. It would be an excellent chance
for reverse engineering skills to be honed. :-) I would prefer
On Sun, 29 Aug 1999, Warner Losh wrote:
: I have some frequecy hopping radio modems that use the 82593 to get
: 256kbps or so...
Speaking of which, I'll give two free to someone that commits to
writing a driver for these beasts. It would be an excellent chance
for reverse engineering
In message pine.bsf.4.10.9908300059590.1358-100...@sasami.jurai.net Matthew
N. Dodd writes:
: Of course, I'm assuming that your boards are compatible with the ARCnet
: standard programming interface...
Actually, no. They are Ethernet drivers with an underdocumented
interface.
Warner
To
hi, there!
On Mon, 30 Aug 1999, Matthew N. Dodd wrote:
: I have some frequecy hopping radio modems that use the 82593 to get
: 256kbps or so...
Speaking of which, I'll give two free to someone that commits to
writing a driver for these beasts. It would be an excellent chance
for
Well serial ports come free on all new computers ;)
You mean like the PC 2000 that _only_ comes with USB and for which you
will have to buy a USB-serial converter that might not handle the
signalling you had in mind? :-)
Nick
http://www.etla.net/~n_hibma/usb/usb.pl
--
e-Mail: [EMAIL
On Saturday, 28 August 1999 at 2:52:12 -0500, Kris Kirby wrote:
Daniel O'Connor wrote:
On 28-Aug-99 Kris Kirby wrote:
RS232? RS485? VERY cheap and the later is at least moderatly resistant to
noise
Noise shouldn't be an issue. It's going to be handling "clean" data. By
cheap, I mean $5
On 28-Aug-99 Greg Lehey wrote:
So what's wrong with PLIP? Last time I used it, I was getting about
50 kB/s out of it.
PLIP has a terrible CPU/speed ratio.. You have to busy wait while bashing the
parallel port which is just yech :(
---
Daniel O'Connor software and network engineer
for
Greg Lehey wrote:
I'm going to be building at least three of these units, assuming I get
the technical issues out of the way. So I'm looking at a cheap (hardware
and software) way of getting data in and out of a PC with IP support and
such. It just makes sense in my POV to use a NIC. It's
Daniel O'Connor wrote:
On 28-Aug-99 Kris Kirby wrote:
I'm going to be building at least three of these units, assuming I get
the technical issues out of the way. So I'm looking at a cheap (hardware
and software) way of getting data in and out of a PC with IP support and
such. It
On 28-Aug-99 Kris Kirby wrote:
Both. The problem is that you can't cram a signal moving at 10 Mbps
through a radio interface designed for 256K, even if it is bandwidth
limited to 256K. I'm hoping the 3C503 is ancient enough that I can slow
it down by yanking it's 20. MHz crystal
Both. The problem is that you can't cram a signal moving at 10 Mbps
through a radio interface designed for 256K, even if it is bandwidth
limited to 256K. I'm hoping the 3C503 is ancient enough that I can slow
it down by yanking it's 20. MHz crystal oscillator and feeding it a
lower
On Sat, 28 Aug 1999, Kris Kirby wrote:
Both. The problem is that you can't cram a signal moving at 10 Mbps
through a radio interface designed for 256K, even if it is bandwidth
limited to 256K. I'm hoping the 3C503 is ancient enough that I can slow
it down by yanking it's 20. MHz crystal
Matthew N. Dodd wrote:
On Fri, 27 Aug 1999, Kris Kirby wrote:
It's not a bandwidth issue; it's a speed issue. I'm trying to find an
extremely cheap way to get data in and out of a PC.
How about an I2C bus?
(Or is that -too- slow?)
I'll have to admit I'm totally ignorant of what this
Julian Elischer wrote:
plip?
Ideally, no. The ethernet card makes the data rather easy to handle into
other means (like a radio modem). It's already serialized, packetized,
has a MAC address for a link address, and it's easy to get seperate RX
and TX lines out of the card, even if it is
Daniel O'Connor wrote:
On 28-Aug-99 Kris Kirby wrote:
It's not a bandwidth issue; it's a speed issue. I'm trying to find an
extremely cheap way to get data in and out of a PC. I've got the
National Semiconductor application sheets for the 8392(?) and plan on
using one cut in half:
On 28-Aug-99 Kris Kirby wrote:
RS232? RS485? VERY cheap and the later is at least moderatly resistant to
noise
Noise shouldn't be an issue. It's going to be handling clean data. By
cheap, I mean $5 a pop or so. I've got a few 3C503s that I feel like
cutting into. I'm going to be bearing
USB?
http://www.activewire.com/ has a nice board that does I2C as well. With
a bit of plumbing you should be able to stream out 100kb a second.
Nick
On Fri, 27 Aug 1999, Julian Elischer wrote:
plip?
On Fri, 27 Aug 1999, Matthew N. Dodd wrote:
On Fri, 27 Aug 1999, Kris Kirby wrote:
Daniel O'Connor wrote:
On 28-Aug-99 Kris Kirby wrote:
RS232? RS485? VERY cheap and the later is at least moderatly resistant to
noise
Noise shouldn't be an issue. It's going to be handling clean data. By
cheap, I mean $5 a pop or so. I've got a few 3C503s that I feel like
cutting
Well serial ports come free on all new computers ;)
You mean like the PC 2000 that _only_ comes with USB and for which you
will have to buy a USB-serial converter that might not handle the
signalling you had in mind? :-)
Nick
http://www.etla.net/~n_hibma/usb/usb.pl
--
e-Mail: hi...@skylink.it
On Saturday, 28 August 1999 at 2:52:12 -0500, Kris Kirby wrote:
Daniel O'Connor wrote:
On 28-Aug-99 Kris Kirby wrote:
RS232? RS485? VERY cheap and the later is at least moderatly resistant to
noise
Noise shouldn't be an issue. It's going to be handling clean data. By
cheap, I mean $5 a
On 28-Aug-99 Greg Lehey wrote:
So what's wrong with PLIP? Last time I used it, I was getting about
50 kB/s out of it.
PLIP has a terrible CPU/speed ratio.. You have to busy wait while bashing the
parallel port which is just yech :(
---
Daniel O'Connor software and network engineer
for
Greg Lehey wrote:
I'm going to be building at least three of these units, assuming I get
the technical issues out of the way. So I'm looking at a cheap (hardware
and software) way of getting data in and out of a PC with IP support and
such. It just makes sense in my POV to use a NIC. It's
Daniel O'Connor wrote:
On 28-Aug-99 Kris Kirby wrote:
I'm going to be building at least three of these units, assuming I get
the technical issues out of the way. So I'm looking at a cheap (hardware
and software) way of getting data in and out of a PC with IP support and
such. It
On 28-Aug-99 Kris Kirby wrote:
Both. The problem is that you can't cram a signal moving at 10 Mbps
through a radio interface designed for 256K, even if it is bandwidth
limited to 256K. I'm hoping the 3C503 is ancient enough that I can slow
it down by yanking it's 20. MHz crystal
Both. The problem is that you can't cram a signal moving at 10 Mbps
through a radio interface designed for 256K, even if it is bandwidth
limited to 256K. I'm hoping the 3C503 is ancient enough that I can slow
it down by yanking it's 20. MHz crystal oscillator and feeding it a
lower
On Sat, 28 Aug 1999, Kris Kirby wrote:
Both. The problem is that you can't cram a signal moving at 10 Mbps
through a radio interface designed for 256K, even if it is bandwidth
limited to 256K. I'm hoping the 3C503 is ancient enough that I can slow
it down by yanking it's 20. MHz crystal
On Fri, 27 Aug 1999, Kris Kirby wrote:
I know there are drivers for the WaveLan card, but I'm looking at going
even slower (256Kb!).
Why do you wnat to do this? If for bandwidht limiting you need look no
further than 'dummynet'.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E |
Matthew N. Dodd wrote:
On Fri, 27 Aug 1999, Kris Kirby wrote:
I know there are drivers for the WaveLan card, but I'm looking at going
even slower (256Kb!).
Why do you wnat to do this? If for bandwidht limiting you need look no
further than 'dummynet'.
It's not a bandwidth issue; it's
On Fri, 27 Aug 1999, Kris Kirby wrote:
It's not a bandwidth issue; it's a speed issue. I'm trying to find an
extremely cheap way to get data in and out of a PC.
How about an I2C bus?
(Or is that -too- slow?)
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
|
plip?
On Fri, 27 Aug 1999, Matthew N. Dodd wrote:
On Fri, 27 Aug 1999, Kris Kirby wrote:
It's not a bandwidth issue; it's a speed issue. I'm trying to find an
extremely cheap way to get data in and out of a PC.
How about an I2C bus?
(Or is that -too- slow?)
--
| Matthew N. Dodd
On 28-Aug-99 Kris Kirby wrote:
It's not a bandwidth issue; it's a speed issue. I'm trying to find an
extremely cheap way to get data in and out of a PC. I've got the
National Semiconductor application sheets for the 8392(?) and plan on
using one "cut in half": Half duplex, but split into
Matthew N. Dodd wrote:
On Fri, 27 Aug 1999, Kris Kirby wrote:
It's not a bandwidth issue; it's a speed issue. I'm trying to find an
extremely cheap way to get data in and out of a PC.
How about an I2C bus?
(Or is that -too- slow?)
I'll have to admit I'm totally ignorant of what this
Julian Elischer wrote:
plip?
Ideally, no. The ethernet card makes the data rather easy to handle into
other means (like a radio modem). It's already serialized, packetized,
has a MAC address for a link address, and it's easy to get seperate RX
and TX lines out of the card, even if it is
Daniel O'Connor wrote:
On 28-Aug-99 Kris Kirby wrote:
It's not a bandwidth issue; it's a speed issue. I'm trying to find an
extremely cheap way to get data in and out of a PC. I've got the
National Semiconductor application sheets for the 8392(?) and plan on
using one "cut in
On 28-Aug-99 Kris Kirby wrote:
RS232? RS485? VERY cheap and the later is at least moderatly resistant to
noise
Noise shouldn't be an issue. It's going to be handling "clean" data. By
cheap, I mean $5 a pop or so. I've got a few 3C503s that I feel like
cutting into. I'm going to be
On Fri, 27 Aug 1999, Kris Kirby wrote:
I know there are drivers for the WaveLan card, but I'm looking at going
even slower (256Kb!).
Why do you wnat to do this? If for bandwidht limiting you need look no
further than 'dummynet'.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E |
Matthew N. Dodd wrote:
On Fri, 27 Aug 1999, Kris Kirby wrote:
I know there are drivers for the WaveLan card, but I'm looking at going
even slower (256Kb!).
Why do you wnat to do this? If for bandwidht limiting you need look no
further than 'dummynet'.
It's not a bandwidth issue; it's
On Fri, 27 Aug 1999, Kris Kirby wrote:
It's not a bandwidth issue; it's a speed issue. I'm trying to find an
extremely cheap way to get data in and out of a PC.
How about an I2C bus?
(Or is that -too- slow?)
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
|
plip?
On Fri, 27 Aug 1999, Matthew N. Dodd wrote:
On Fri, 27 Aug 1999, Kris Kirby wrote:
It's not a bandwidth issue; it's a speed issue. I'm trying to find an
extremely cheap way to get data in and out of a PC.
How about an I2C bus?
(Or is that -too- slow?)
--
| Matthew N. Dodd
On 28-Aug-99 Kris Kirby wrote:
It's not a bandwidth issue; it's a speed issue. I'm trying to find an
extremely cheap way to get data in and out of a PC. I've got the
National Semiconductor application sheets for the 8392(?) and plan on
using one cut in half: Half duplex, but split into
The WaveLan card suddenly comes to mind...
Are the ethernet drivers time dependent? If I take a ethernet card
[ed(4)] and change the crystal for something slower, assuming I can
still get the card to work correctly (albiet slower) will it still
interact properly with the ed(4) driver, or do I
The WaveLan card suddenly comes to mind...
Are the ethernet drivers time dependent? If I take a ethernet card
[ed(4)] and change the crystal for something slower, assuming I can
still get the card to work correctly (albiet slower) will it still
interact properly with the ed(4) driver, or do I
47 matches
Mail list logo
