I have to support Jens since I think nex-Ax25 support is much better (and
what is done so far greatly proves that).
Have in mind we're talking about Ax25 for 2.5/2.6 kernels .. (or patched
2.2/2.4 of course) so compatibility issues are not that important.
On Wed, 26 Apr 2000, Tomi Manninen OH
On Wed, 9 Feb 2000, Joerg Reuter DL1BKE wrote:
> > - removed arbitration stuff from hdlcdrv.c & dependent drivers,
> >removed slottime+persistence, removed some (very old) kernel version
> >checks
> >removed kernel stuff from linux/include/linux/hdlcdrv.h, put it in
> >drivers/
On Mon, 7 Feb 2000, Robin Gilks wrote:
> On Mon, 07 Feb 2000, you wrote:
> > While playing around with hdlcdrv I came across two problems:
> >
> > Before arbitration was called by driver and when higher level decided to
> > transmit driver immediately keyed PTT. Now driver and DDI have separa
On Mon, 7 Feb 2000, Ing. Jose A. Amador wrote:
> Seems like reasons to consider upgrading the kernel sources...
New AX25 code itself is pretty stable. It is (sadly) quite rare to see
releasing of nearly complete code here. Problem is that some drivers are
not working yet and proc/ioctl interfac
While playing around with hdlcdrv I came across two problems:
Before arbitration was called by driver and when higher level decided to
transmit driver immediately keyed PTT. Now driver and DDI have separate
timers which results in DDI deciding to transmit BUT driver keying PTT
with some delay w
Kernel patch (includes my previous patch):
- removed arbitration stuff from hdlcdrv.c & dependent drivers,
removed slottime+persistence, removed some (very old) kernel version
checks
removed kernel stuff from linux/include/linux/hdlcdrv.h, put it in
drivers/net/hamradio/hdlcdrv.h
-
On Tue, 1 Feb 2000, Jens David wrote:
> > > We should start phase out "struct sockaddr_ax25" now, BTW. We're
> > > carrying this thing with us for too long now and I doubt any
> > > application still uses it. I don't know if it even works nowadays.
> > sockaddr_ax25 ?
> > Programs use full_socka
On Tue, 1 Feb 2000, Jens David wrote:
> John Ackermann wrote:
> > Not all hardware implementations need it, but there are at least some systems
> > where dropping the PTT immediately results in the tail end of the packet
> > (including the CRC and closing flag) to be chopped off.
>
> In fact pe
Hi ..
I wonder what is the real purpose of txtail.
All data has been TX'd so what is the purpose of waiting before releasing
PTT ?
Is it important for decoder or something ?
Omitting txtail would simplify drivers etc.
Jan
On Tue, 25 Jan 2000, Joerg Reuter DL1BKE wrote:
> And not on dev-hams, either.
I haven't noticed open subscribtion to dev-hams .. there are people who
are interrested. Maybe just welcome message with BIG statement that one
should not reply to things he doesn't understand or something would do .
--
Date: Mon, 17 Jan 2000 13:39:39 +0100 (CET)
From: Jan Wasserbauer <[EMAIL PROTECTED]>
To: Jens David <[EMAIL PROTECTED]>
Subject: Re: DG2FEF-AX.25 Patch for 2.2.14 available
Hello ..
Good that someone is taking care about new AX25, curent kernel-AX25 is
.. well .. really
On Wed, 19 Jan 2000, Joerg Reuter DL1BKE wrote:
> Hi,
> for some reason I didn't get the original message.
Was not to linux-hams ..
> > > - new SIOCAX25GETINFO - ax25_info_struct now includes information about
> > > VR,VS,VA,WINDOW,PACLEN so programs may get those information through
> > >
On Wed, 19 Jan 2000, Gerd wrote:
>
> So, I even was a little bit afraid if Slackware 7, which comes with 2.2.13,
> would run on my K6-2/400 with 64 MB RAM - but it does (I am still estonished).
>
I was running Slackware (4.0) on 386/33MHz/8MB RAM/100MB HDD
(with swap :) ) .. not very fast setup
Jose Angel Amador Fundora <[EMAIL PROTECTED]> wrote:
> I once made it work with ax25-utils, but that disk crashed and I have
> not been able to do it again. It makes changes in the kernel sources
> when you want to include kernel ax25 support.
Changes to kernel ? I have never noticed such thing.
Tomi Manninen <[EMAIL PROTECTED]> wrote:
> Anyway, there are two issues here. First: you say software has to be
> broken. Well, in my opinion the notion that a piece of software needs to
> know what happens underneath it (with 300ms granularity) is _completely_
> broken. Unless of course if the
"Karl F. Larsen" <[EMAIL PROTECTED]> wrote:
> Jan please re-organize your thoughts and send first your
> improvements to the ax25 software and then talk in another message about
> what's wrong with TNT. To my knowlege TNT is designed to work without the
> ax25-utils so that may be your pr
Jan Wasserbauer <[EMAIL PROTECTED]> wrote:
> > IMHO TNT is broken in this case. Why does it need to read it so often?
> TNT periodically reads channel status. I am trying to get it working using
> ioctl but can't find any way how to get number of unacked frames. Normal
> IMHO TNT is broken in this case. Why does it need to read it so often?
TNT periodically reads channel status. I am trying to get it working using
ioctl but can't find any way how to get number of unacked frames. Normally TNT
counts unacked frames using vs&va but those are not in ax25_info_struc
> On Tue, 7 Sep 1999, Cathryn Mataga http://junglevision.com wrote:
>
> > Yeah, I've been looking at the kernel source, and I'm trying to figure
...
> Ha! Thanks Cathryn, I think you found it!
>
> It seems the interface to getname has changed a bit. From that code I
> deduce that &len is now supp
Well .. I have just upgraded another machine to 2.2.12 .. and guess what ?
The same problem. It is similar setup using Slackware 4.0.
I can provide an account for someone who will (try to) fix that.
I tried to do something myself but was not very wise from kernel/libc sources.
Bye Jan
Hello ..
Is there any reason why linux/net/ax25/af_ax25.c - ax25_get_info()
disables interrupts ?
This causes problems with BayCom modem (and possibly others) since
its driver cannot receive interrupts from serial port while
something is reading /proc/net/ax25. TNT reads it every 300ms
which mak
Hi everyone on the list ..
Part of checklogin() function:
...
tv.tv_sec = 0;
tv.tv_usec = 0;
if (select (maxsock + 1, &rfds, NULL, NULL, &tv) <= 0)
return;
for (i = 0; i < listen_sock_num; i++)
{
if (!FD_ISSET (listen_sock[i], &rfds))
continue;
addrlen =
; Mike
Do you have IP adres assigned to your ax25 interfaces ?
I had similar problem because Linux tryes to route ethernet IP
traffic on radio (or it looks like that).
73s Jan
====
"Wasik" Jan Wasserbauer
23 matches
Mail list logo
