Stallion EasyIO and devfs

Stallion EasyIO and devfs

[Donald Thompson]

I've got a stallion EasyIO PCI 4 port card running on kernel 2.4.4.
Loading the stallion.o module does not seem to create the proper device files
for me using devfs.

Upon loading the module I get the following devices created:

/dev/ttyE
/dev/cue
/dev/staliomem/0
/dev/staliomem/1
/dev/staliomem/2
/dev/staliomem/3

I don't get /dev/ttyE0 through /dev/ttyE3 or /dev/ttyE/0 through
/dev/ttyE/3, which is what I believe should be happening.

I can make the devices using the mkdevnods script from the ata 5.5.0
stallion driver package, and sure enough ttyE0 through ttyE3 work as
expected. I can setup the devices at boot so I'm not dead in the water
with it.

Heres the output from /proc/pci regarding the card:
  Bus  0, device  20, function  0:
    Communication controller: Stallion Technologies, Inc. EasyIO (rev 1).
      IRQ 9.
      I/O at 0xf480 [0xf4ff].
      I/O at 0xf800 [0xf87f].

I'm using devfsd 1.3.11 on an up to date debian sid machine.

-Don

Re: Stallion EasyIO and devfs

[Richard Gooch]

Donald Thompson writes:
> I've got a stallion EasyIO PCI 4 port card running on kernel 2.4.4.
> Loading the stallion.o module does not seem to create the proper device files
> for me using devfs.
> 
> Upon loading the module I get the following devices created:
> 
> /dev/ttyE
> /dev/cue
> /dev/staliomem/0
> /dev/staliomem/1
> /dev/staliomem/2
> /dev/staliomem/3
> 
> I don't get /dev/ttyE0 through /dev/ttyE3 or /dev/ttyE/0 through
> /dev/ttyE/3, which is what I believe should be happening.

Please apply the following patch to drivers/char/stallion.c and let me
know if that helps.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

--- stallion.c~	Fri Mar  2 14:12:07 2001
+++ stallion.c	Mon Jul 30 21:08:34 2001
@@ -139,8 +139,13 @@
 static char	*stl_drvtitle = "Stallion Multiport Serial Driver";
 static char	*stl_drvname = "stallion";
 static char	*stl_drvversion = "5.6.0";
+#ifdef CONFIG_DEVFS_FS
+static char	*stl_serialname = "ttyE/%d";
+static char	*stl_calloutname = "cue/%d";
+#else
 static char	*stl_serialname = "ttyE";
 static char	*stl_calloutname = "cue";
+#endif
 
 static struct tty_driver	stl_serial;
 static struct tty_driver	stl_callout;

Re: Stallion EasyIO and devfs

[Donald Thompson]

Works correctly. Didn't patch properly into 2.4.7 properly, think it
just
had the wrong line numbers. But patching it in by hand was no problem.
I'm 
missing compatability symlinks, so that I get links from /dev/ttyE/* to 
/dev/ttyE*, but thats another problem.

-Don

Richard Gooch wrote:
> 
> Donald Thompson writes:
> > I've got a stallion EasyIO PCI 4 port card running on kernel 2.4.4.
> > Loading the stallion.o module does not seem to create the proper device files
> > for me using devfs.
> >
> > Upon loading the module I get the following devices created:
> >
> > /dev/ttyE
> > /dev/cue
> > /dev/staliomem/0
> > /dev/staliomem/1
> > /dev/staliomem/2
> > /dev/staliomem/3
> >
> > I don't get /dev/ttyE0 through /dev/ttyE3 or /dev/ttyE/0 through
> > /dev/ttyE/3, which is what I believe should be happening.
> 
> Please apply the following patch to drivers/char/stallion.c and let me
> know if that helps.
> 
>                                 Regards,
> 
>                                         Richard....
> Permanent: rgooch@atnf.csiro.au
> Current:   rgooch@ras.ucalgary.ca
> 
> --- stallion.c~ Fri Mar  2 14:12:07 2001
> +++ stallion.c  Mon Jul 30 21:08:34 2001
> @@ -139,8 +139,13 @@
>  static char    *stl_drvtitle = "Stallion Multiport Serial Driver";
>  static char    *stl_drvname = "stallion";
>  static char    *stl_drvversion = "5.6.0";
> +#ifdef CONFIG_DEVFS_FS
> +static char    *stl_serialname = "ttyE/%d";
> +static char    *stl_calloutname = "cue/%d";
> +#else
>  static char    *stl_serialname = "ttyE";
>  static char    *stl_calloutname = "cue";
> +#endif
> 
>  static struct tty_driver       stl_serial;
>  static struct tty_driver       stl_callout;

Re: Stallion EasyIO and devfs

[Donald Thompson]

devfsd and the compatability links work correctly as of 2.4.8 with the
patch you provided.

This is quite possibly user error and not a kernel issue, but it seems
pppd 2.4.1 breaks once I've got the stallion card under devfsd with
compatability links.

mgetty runs on device lets say, /dev/ttyE2 (symlink to /dev/ttyE/2), and
passes off incoming connections to pppd. I'm expecting pppd is gonna want
to look at /etc/ppp/options.ttyE2, but its not.

If I change stallion.c at around line 145 from:
static char     *stl_serialname = "ttyE/%d";

To:
static char     *stl_serialname = "ttyE%d";

so that the real device becomes /dev/ttyE2 rather than a symlink to
/dev/ttyE/2 pppd starts looking at the correct options file.

pppd seems to be able to handle the compatability symlinks just fine on
/dev/ttyS* devices and find the proper ppp options file to look at. So I'm
guessing they've got a hack to handle devfsd standard serial ports, or I'm
doing something wrong somewhere.

-Don

On Sun, 12 Aug 2001, Richard Gooch wrote:

> Donald Thompson writes:
> > Works correctly. Didn't patch properly into 2.4.7 properly, think it
> > just
> > had the wrong line numbers. But patching it in by hand was no problem.
> > I'm
> > missing compatability symlinks, so that I get links from /dev/ttyE/* to
> > /dev/ttyE*, but thats another problem.
>
> The current version of devfsd (1.3.14) should provide them. Note that
> the kernel patch and devfsd will probably be changed again, but the
> compatibility names should stay the same.
>
> 				Regards,
>
> 					Richard....
> Permanent: rgooch@atnf.csiro.au
> Current:   rgooch@ras.ucalgary.ca
>

Re: Stallion EasyIO and devfs

[Richard Gooch]

Donald Thompson writes:
> devfsd and the compatability links work correctly as of 2.4.8 with the
> patch you provided.
> 
> This is quite possibly user error and not a kernel issue, but it seems
> pppd 2.4.1 breaks once I've got the stallion card under devfsd with
> compatability links.
> 
> mgetty runs on device lets say, /dev/ttyE2 (symlink to /dev/ttyE/2), and
> passes off incoming connections to pppd. I'm expecting pppd is gonna want
> to look at /etc/ppp/options.ttyE2, but its not.
> 
> If I change stallion.c at around line 145 from:
> static char     *stl_serialname = "ttyE/%d";
> 
> To:
> static char     *stl_serialname = "ttyE%d";
> 
> so that the real device becomes /dev/ttyE2 rather than a symlink to
> /dev/ttyE/2 pppd starts looking at the correct options file.

The recent versions of devfsd expect the Stallion devices to have the
name tts/E%d, so this suggests that you are running a virgin
kernel. So grab devfs-patch-v187 and devfsd-v1.3.17 (or later) and try
again. If you still have problems, run strace and analyse the result.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca