Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: patch for sysfs in the cyclades driver
Date: Wed, 3 Nov 2004 14:20:39 -0600
Message-ID: <71A17D6448EC0140B44BCEB8CD0DA36E04B9D81C@minimail.digi.com>
Thread-Topic: patch for sysfs in the cyclades driver
Thread-Index: AcTB4Db/dWj2VOolS6Ov2E4ZZlm1bgAALCag
From: "Kilau, Scott" <Scott_Kilau@digi.com>
To: "Greg KH" <greg@kroah.com>
Cc: <germano.barreiro@cyclades.com>, <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1193
Lines: 34

> > Maybe we can allow a "custom" name to be sent into the
> > tty_register_device() call?  Like add another option parameter
called
> > "custom_name" that if non-NULL, is used instead of the derived name?

> Why?  What would you call it that would be any different from what we
> use today?  I guess I don't understand why you don't like the kernel
> names.

> greg k-h

Well, tty name compatibly reasons with a couple of our drivers.

Most of our new Linux users for a couple of our older products are
coming
from a specific different OS who are adamant that we keep the tty names
the way they were used to under that OS.

Also, I can see some oddball products out there that might need
only 1 tty out there.

Instead of forcing "ttyoddball0" for the name, it would
be nice to let the driver use "ttyoddball", or whatever it wanted.

In fact, it would be similar to the existing entries for "console" and
"ptmx"...

Scott Kilau
Digi International
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/