[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

"Theodore Y. Ts'o": Re: continuing setserial problems


------- Forwarded Message

Return-Path: root@burrito.onshore.com
Delivery-Date: Mon, 05 Jul 1999 22:24:42 -0400
Received: from root by burrito with local (Exim 2.11 #1 (Debian))
	id 111KuX-00006i-00; Mon, 5 Jul 1999 22:24:41 -0400
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [])
	by queso.onshore.com (8.9.2/8.9.2/Debian/GNU) with SMTP id TAA30096
	for <adam@onshore.com>; Fri, 2 Jul 1999 19:43:06 -0500 (CDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id UAA11266; Fri, 2 Jul 1999 20:43:34 -0400
Date: Fri, 2 Jul 1999 20:43:34 -0400
Message-Id: <199907030043.UAA11266@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Adam Di Carlo <adam@onshore.com>
CC: Gordon Russell <gor@dcs.napier.ac.uk>
cc: davem@vger.rutgers.edu
In-reply-to: Adam Di Carlo's message of 02 Jul 1999 00:38:00 -0400,
Subject: Re: continuing setserial problems
Address: 1 Amherst St., Cambridge, MA 02139
Phone: (617) 253-8091
X-UIDL: b49f080861e0936ebc16b1d00cb3fac5
Status: RO
Lines: 41
Sender: root <root@burrito.onshore.com>

   From: Adam Di Carlo <adam@onshore.com>
   Date: 02 Jul 1999 00:38:00 -0400

   Using setserial 2.15 with kernel 2.2.x on the Sun4u architecture, I
   get failure:

    # setserial /dev/ttyS0
    sys32_ioctl: Unknown cmd fd(3) cmd(0000541e) arg(effffc20)
    Cannot get serial info: Invalid argument

   Is setserial's functionality just not supported in the Sparc64 Linux

   A knowledgable Debian sparc64 person, Steve Dunham, wrote:

   |  I always assumed it wasn't needed (and disabled it).  The error
   | message that you included above will only come from the sparc64
   | kernel.  (It is from the code in
   | arch/sparc64/kernel/{ioctl,sys_sparc32}.c which translates the
   | arguments of 32-bit system calls into 64-bit system calls.)
   | Since it is unhandled, either: it's not used on the sparc, or they
   | didn't get around to adding it.

   Mr Tso, do you know if this is a sparc64 kernel bug?

Well, I'm not really an expert on how things work on the sparc64

Are they using drivers/char/serial.c?  They may not be.... I'd be
surprised if the my serial driver works on the Sparc64 w/o
modification, and I haven't seen any Sparc 64 specific modifications.
Maybe if the sparc64 hardware has ISA hardware compatibility.... but
that would be surprising, since the ISA bus is *junk*.

If they are, then the serial ioctls really should be supported, and it's
a bug.  But I'm not sure this is the case.

David Miller would know, I think.  Dave?

						- Ted

------- End of Forwarded Message

Reply to: