All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Hast <wchast@gmail.com>
To: Ralf Baechle DL5RB <ralf@linux-mips.org>
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 12:06:41 -0400	[thread overview]
Message-ID: <620c905705070509063b3f65fb@mail.gmail.com> (raw)
In-Reply-To: <20050705155301.GM5171@linux-mips.org>

On 7/5/05, Ralf Baechle DL5RB <ralf@linux-mips.org> wrote:
> On Tue, Jul 05, 2005 at 04:45:56AM -0600, Chuck Hast wrote:
> 
> > Does 6pack still only handle 1 tnc under Linux or have you got it to do
> > a ring of TNC's like the DOS one does? Sure would like to see that on
> > Linux, would cut cost for us where we have multiple TNC's and want to
> > use a simple machine.
> 
> Such a limitation has never existed as far as I can tell; the sole
> limitation is to a single TNC per RS-232 interface.  Daisy chaining
> multiple TNCs per interface is still not supported.  If you run out
> of serial interfaces using for example USB serial interfaces should
> work just fine.
> 
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.

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.



> (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???



-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."

  reply	other threads:[~2005-07-05 16:06 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 [this message]
2005-07-05 18:12       ` Ralf Baechle DL5RB
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=620c905705070509063b3f65fb@mail.gmail.com \
    --to=wchast@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=macke@macke.org \
    --cc=ralf@linux-mips.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.