Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: raoul@shuttle.de (Raoul Borenius)
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Raoul Borenius <raoul@shuttle.de>,
	linux-mips@oss.sgi.com, devfs@oss.sgi.com
Subject: Re: broken devfs-support in SGI Zilog8530 serial driver
Date: Sat, 30 Mar 2002 14:28:56 +0100	[thread overview]
Message-ID: <20020330132856.GA24305@bunny.shuttle.de> (raw)
In-Reply-To: <20020329233559.A31160@dea.linux-mips.net>

Hi Ralf,

On Fri, Mar 29, 2002 at 11:35:59PM -0800, Ralf Baechle wrote:
> On Fri, Mar 29, 2002 at 11:32:44AM +0100, Raoul Borenius wrote:
> 
> > I'm not sure if this is a devfs or mips problem so I'm sending it
> > to both lists.
> > 
> > I just compiled my own mips-kernel from oss.sgi.com:/cvs to get
> > devfs-support. Unfortunately there seems to be a problem with the
> > serial-driver at least in the linux_2_4 branch:
> > 
> > SGI Zilog8530 serial driver version 1.00
> > devfs_register(ttyS): could not append to parent, err: -17
> > devfs_register(cua): could not append to parent, err: -17
> 
> At this time we don't even claim to have proper devfs support in the
> Indy serial drivers ...

But it would be nice to have ;-)

Especially because you only need the small change pointed out by
Russell Coker:

--- sgiserial.c.orig    Sat Mar 30 10:51:03 2002
+++ sgiserial.c Sat Mar 30 10:54:28 2002
@@ -1875,7 +1875,11 @@
        
        memset(&serial_driver, 0, sizeof(struct tty_driver));
        serial_driver.magic = TTY_DRIVER_MAGIC;
+#ifdef CONFIG_DEVFS_FS
+       serial_driver.name = "tts/%d";
+#else
        serial_driver.name = "ttyS";
+#endif
        serial_driver.major = TTY_MAJOR;
        serial_driver.minor_start = 64;
        serial_driver.num = NUM_CHANNELS;
@@ -1911,7 +1915,11 @@
         * major number and the subtype code.
         */
        callout_driver = serial_driver;
+#ifdef CONFIG_DEVFS_FS
+       callout_driver.name = "cua/%d";
+#else
        callout_driver.name = "cua";
+#endif
        callout_driver.major = TTYAUX_MAJOR;
        callout_driver.subtype = SERIAL_TYPE_CALLOUT;

It works for my Indy and I just love devfs. All other drivers used
on my box also work fine with devfs (sound, watchdog, rtc etc.).

Regards

Raoul

  reply	other threads:[~2002-03-30 13:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-29 10:32 broken devfs-support in SGI Zilog8530 serial driver Raoul Borenius
2002-03-29 11:01 ` Borsenkow Andrej
2002-03-29 13:26   ` Raoul Borenius
2002-03-29 13:38     ` Russell Coker
2002-03-29 13:38       ` Russell Coker
2002-03-30  7:35 ` Ralf Baechle
2002-03-30 13:28   ` Raoul Borenius [this message]
2002-03-30 20:18     ` Ralf Baechle
2002-03-31 15:00     ` Raoul Borenius
2002-03-31 22:15       ` Ralf Baechle
2002-04-01 19:29       ` Florian Lohoff
2002-04-01 22:16         ` Ralf Baechle

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=20020330132856.GA24305@bunny.shuttle.de \
    --to=raoul@shuttle.de \
    --cc=devfs@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.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