USB isn't crap. MS implimentation of USB is crap.
No,
it is crap to implement new IRQ-Eaters without any need.
There is nothing that could be done and it is not covered by
Ethernet or Firewire. So please stop USB : support FireWire and Ethernet
as FireWire is the Standard in the Video-Area
USB isn't crap. MS implimentation of USB is crap.
No,
it is crap to implement new IRQ-Eaters without any need.
There is nothing that could be done and it is not covered by
Ethernet or Firewire. So please stop USB : support FireWire and Ethernet
as FireWire is the Standard in the
Gareth Rowlands wrote:
It may be possible to mod the source of rip98d, so that its routes are
taken from a file other than /proc/net/route. You could then copy
proc/net/route
to this other file, censoring the unwanted contents via a script on
the way.
I prefeer the file option: you put
Dear All,
I found a problem on using soundmodem, it was not work and after rebuild the
kernel the steps are,
1. # insmod hdlcdrv (or modprobe hdlcdrv)
2. # insmod soundmodem mode="sbc:afsk1200" iobase=0x220 irq=5 dma=1
3. # sethdlc -p -i sm0 mode sbc:afsk1200 io 0x388 irq 10 dma 1
Gareth Rowlands wrote:
There isn't a simple way of stopping rip98d from advertising some routes,
unless they are non-44. routes when the -r option can be used, so that
only
Yes, I understand why: rip uses the kernel table as its storage for the
routes, as does *nos. Ok, good, that
I was just wondering what would it take to build a pager-like device
capable of receiving messages from the already deployed ax25
nodes and gateways all over the world?
Or is there anything like it already available?
In other words could we start an SMS over ax25 project?
regards,
"73" and
the only means of escape was the reset button, the oops was written to the
console but there is no trace of it in the system logs.
This renders a very big problem indeed for 2.2.x systems in remote
locations, imagen the effect _if_ an scc interface locks up, or any other
for that matter,
On 08-Jun-99 Karl Kramer wrote:
USB isn't crap. MS implimentation of USB is crap.
No,
it is crap to implement new IRQ-Eaters without any need.
There is nothing that could be done and it is not covered by
Ethernet or Firewire. So please stop USB : support FireWire and Ethernet
as
LOL,,, finally some Humor... Ip does quite well on Ethernet, and
How can I make KISS use IP?
On Tue, 8 Jun 1999, Tim Salo wrote:
Date: Tue, 08 Jun 1999 17:09:46 +0100 (BST)
From: Dirk Koopman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: USB TNC
[...]
Another
Yes, it has come full circle. Let's build a box with an ethernet
interface on one end and a radio port on the other. Wait a min.
I have one of those... it's a linux box configured with soundmodem
ports
:-)
When does the 10Mbps radio link kit (card and radio with sufficient
bandwidth) come
LOL,,, finally some Humor... Ip does quite well on Ethernet, and
How can I make KISS use IP?
Ditto...
If you have IP, why on Earth would you need KISS?
(As discussed on the TNC-TNG list circa 1993-94)
Mike N4CNW
___
Get Free
On 08-Jun-99 Tim Salo wrote:
Date:Tue, 08 Jun 1999 17:09:46 +0100 (BST)
From: Dirk Koopman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: USB TNC
[...]
Another argument for ethernet is that you can obtain perfectly servicable
10Mb ethernet interface chips for approx $5
On 08-Jun-99 Tim Salo wrote:
Date:Tue, 08 Jun 1999 17:09:46 +0100 (BST)
From: Dirk Koopman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: USB TNC
[...]
Another argument for ethernet is that you can obtain perfectly servicable
10Mb ethernet interface chips for approx $5
Date: Tue, 08 Jun 1999 20:42:34 +0100 (BST)
From: Dirk Koopman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: USB TNC
[...]
If you use Ethernet, perhaps you should use IP as well.
That way I could think about being able to use any Internet-connected
TNC in the
On Tue, 08 Jun 1999 14:34:19 +, [EMAIL PROTECTED] said:
Yes, I understand why: rip uses the kernel table as its storage for the
routes, as does *nos. Ok, good, that simplifies the program. There is
no way of doing a "route addprivate" in Linux ? Marking a route to not
to be exported.
On Tue, 8 Jun 1999, Tim Salo wrote:
If you use Ethernet, perhaps you should use IP as well.
I know of a guy, which have designed a small board with a 386, 1Mbyte
flash and ethernet onboard. It's designed for linux (It's called Linux In
A Board). Maybe it could be used for a new design? The
Hello Pat, hello all,
I have just remade a 2/0/36 kernel, and made some ax25 modules. When I
try to ifconfig the baycom, it gets an error. Here's the series:
root@linux1 [1]: setserial /dev/ttyS1 uart none
root@linux1 [2]: insmod hdlcdrv
root@linux1 [3]: insmod baycom mode="ser12*"
On Tue, Jun 08, 1999 at 02:51:29PM -0400, Patrick Ouellette wrote:
Yes, it has come full circle. Let's build a box with an ethernet
interface on one end and a radio port on the other. Wait a min.
I have one of those... it's a linux box configured with soundmodem
ports
Actually
I am sure that I am not the only guy who dials into an ISP and receives
an dynamic IP address for the outside interface with ipfwadm and running
Amateur tcpip applications. Aside from hand editing source and
destination address's each time the system kicks off, is there a better
mouse trap?
On Tue, Jun 08, 1999 at 02:21:21PM +, Gerd wrote:
May be you are right, maybe you are wrong. Anyway, Ethernet
could be a solution, too but it would not be easy to implement
either.
And: How do you make a usual TNC2, TNC3, Kamtronics, PK232
etc. Ethernet capable? For USB, there are
On Tue, Jun 08, 1999 at 05:09:46PM +0100, Dirk Koopman wrote:
Another potential problem is that Linus seems hellbent on adopting a dynamic
naming standard that changes devices as you add and take away devices on the
USB port. Now whilst I can see a sort of purist programmer's argument for
21 matches
Mail list logo
