From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: Chuck Hast <wchast@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-hams@vger.kernel.org, Marc Schneider <macke@macke.org>
Subject: Re: [PATCH] SMP fix for 6pack driver
Date: Tue, 5 Jul 2005 19:12:22 +0100 [thread overview]
Message-ID: <20050705181222.GB18772@linux-mips.org> (raw)
In-Reply-To: <620c905705070509063b3f65fb@mail.gmail.com>
On Tue, Jul 05, 2005 at 12:06:41PM -0400, Chuck Hast wrote:
> Ralf,
> What is lacking that would allow 6pack TNC's to be daisy chained?
> By doing so we would be able to use a single serial port to support
> multiple TNC's I have the documentation on how to wire the hardware
> and that is no big deal.
Well, by the time I was writing that driver I didn't have a 6pack TNC
at all, so I wrote a 6pack TNC emulator that is capable of simulating
a single TNC. I still don't have multiple TNCs, unfortunately, so I'm
planning on extending that emulator for my work :-)
You could try EB6EBU's m6pack which is an application level solution
to the problem. I'm undecieded, maybe it's even preferable over a kernel
solution.
> I have USB running on a laptop, it works well most of the time but
> at times when the machine boots one or other ports generates the
> "trying to synch tnc" message. The serial port always works.
>
> I think that at times the USB part is slow to get totally initialized so
> I have gone in and added sleeps to slow things down a bit at init.
Mine seems to be ok as long as the machine survives plugging in the
USB device and open()ing the device file. Never really looked into it,
blaming the driver for now.
> > (For dare devils, attaching a remote 6pack TNC via for example ssh sort
> > of works also ;-)
> >
>
> Ahh a subversive TNC to spy on a remote network???
It's a strategy that allows attaching the TNC to any UNIX machine,
even without AX.25 support. It's a hack but I was playing with it
for a while when I ran out of interfaces.
73 de DL5RB op Ralf
--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
next prev parent reply other threads:[~2005-07-05 18:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 17:30 [PATCH] SMP fix for 6pack driver Ralf Baechle
2005-07-05 10:45 ` Chuck Hast
2005-07-05 15:53 ` Ralf Baechle DL5RB
2005-07-05 16:06 ` Chuck Hast
2005-07-05 18:12 ` Ralf Baechle DL5RB [this message]
2005-07-05 22:39 ` Bill Vodall
2005-07-07 10:46 ` Ralf Baechle DL5RB
2005-07-08 20:15 ` SMP fix for mkiss driver ? Bernard Pidoux
2005-07-09 16:51 ` mkiss driver patch applied ? Bernard Pidoux
2005-07-09 23:13 ` Stephen
2005-07-10 12:41 ` Bernard Pidoux
2005-07-11 15:55 ` Ralf Baechle DL5RB
2005-07-05 15:26 ` [stable] [PATCH] SMP fix for 6pack driver Chris Wright
2005-07-05 16:23 ` Ralf Baechle DL5RB
2005-07-05 16:26 ` Chris Wright
2005-07-31 5:07 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-08-28 20:46 Iñaki Arenaza
2005-09-01 11:45 ` Ralf Baechle DL5RB
2005-09-01 12:47 ` Chuck Hast
2005-09-01 15:35 ` Ralf Baechle DL5RB
2005-09-01 20:16 ` Chuck Hast
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050705181222.GB18772@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jgarzik@pobox.com \
--cc=linux-hams@vger.kernel.org \
--cc=macke@macke.org \
--cc=wchast@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).