All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Utley <jerutley@gmail.com>
To: linux-hams@vger.kernel.org
Subject: Re: mkiss, udev and kernel 2.6
Date: Thu, 11 Nov 2004 20:59:42 -0800	[thread overview]
Message-ID: <d5d4185b0411112059129ce996@mail.gmail.com> (raw)
In-Reply-To: <000601c4c852$79768360$07001aac@adminqn>

As I said in my original message to Bernard, it's not a hard thing. 
First, you have to make sure that BSD PTY support is in your kernel. 
Then, in your bootscripts, before you run the mkiss command to set up
the dual port TNC, create the 4 legacy PTY nodes into the /dev
filesystem.  You can find the correct major/minor numbers to use by
looking at devices.txt in the kernel source Doucmentation directory,
or looking at an old distro that has them set up already.  You'll need
4 device nodes:

/dev/ptyp0 - character device, major number 2, minor number 0
/dev/ptyp1 - character device, major number 2, minor number 1
/dev/ttyp0 - character device, major 3, minor 0
/dev/ttyp1 - character device, major 3, minor 1

Then, your mkiss command will look something like this:

mkiss -s 9600 /dev/ttyS0 /dev/ptyp0 /dev/ptyp1

and your kissattach commands will reference /dev/ttyp0 and /dev/ttyp1.
 On my Kam, when configured this way, /dev/ttyp0 ends up the VHF port,
and /dev/ttyp1 the HF port.

Hope this helps!

Jeremy, NW7JU (ex KF3EL)


On Thu, 11 Nov 2004 16:56:40 -0800, AA6QN <aa6qn@pacbell.net> wrote:
> I ported my Linux over to Gentoo and started off with devfs. I did try udev
> and it did not work for me. So, back to devfs and things are working once
> again. Let us know if you get it running.
> 
> 73,John AA6QN
> 
> 
> 
> -----Original Message-----
> From: linux-hams-owner@vger.kernel.org
> [mailto:linux-hams-owner@vger.kernel.org] On Behalf Of Bernard Pidoux
> Sent: Tuesday, November 02, 2004 8:49 AM
> To: unlisted-recipients:; no To-header on input
> Cc: linux-hams@vger.kernel.org
> Subject: mkiss, udev and kernel 2.6
> 
> Hi,
> 
> Does someone have an experience with mkiss and udev in 2.6 kernel ?
> 
> I need to use mkiss-kissattach to drive a dual port TNC 1200/9600 KPC9612.
> 
> However I don't see how to set up a master-slave pseudo tty system with
> udev.
> 
> Actually, I went through by instructing the kernel to load devfs at boot
> (append="devfs=mount... " in lilo.conf.
> 
> But Is there any other solution with udev alone (without devfs) ?
> 
> 73 de Bernard, f6bvp
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2004-11-12  4:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29 18:36 [PATCH 2.6] convert netrom to module_param Stephen Hemminger
2004-07-29 23:02 ` David S. Miller
2004-11-02 16:48 ` mkiss, udev and kernel 2.6 Bernard Pidoux
2004-11-12  0:56   ` AA6QN
2004-11-12  4:59     ` Jeremy Utley [this message]
2005-03-13 23:25     ` Bernard Pidoux
2005-03-20 23:38       ` AX25 udev pseudo tty support Bernard Pidoux
2004-11-02 17:34 ` xfbb ports and kernel 2.6.8 Bernard Pidoux

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=d5d4185b0411112059129ce996@mail.gmail.com \
    --to=jerutley@gmail.com \
    --cc=linux-hams@vger.kernel.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.