Re: Sharing ioctls between char and net device

Jan Kasprzak (Jan.Kasprzak@eunet.cz)
Thu, 15 Oct 1998 15:08:14 +0200 (CEST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Chris Johnson: "Re: APC, Your company is making a mistake!"
Previous message: Mike A. Harris: "Re: APC, Your company is making a mistake!"
In reply to: Alan Cox: "Re: Sharing ioctls between char and net device"

: > device or as the network interface. I have written an user-space utility
: > for downloading firmware, resetting the card, querying the hardware
: > type etc. I would like to allow this user-space utility work both
: > via the ioctl on the character device and via the ioctl on the
: > network socket.
:
: Is it a char device for the purposes of being a serial port or just for being
: able to control it ?
:
At present it serves for control purposes only (downloading the
firmware, etc), but I want to extend it to a generic character device
(probably not a tty device, but a plain character device).

: If its solely for control and command then the wanrouter layer has a notion
: of this already putting things in /proc files.

Do you mean something like this?

cat fimware0123.bin >/proc/mydev/firmware
echo start_firmware 0x0400 >/proc/mydev/command

It sounds interesting, but I don't think I want yet
another controlling interface.

Another option (needing a big rewrite of my driver)
is to make a syncppp/hdlc layer working as some kind of a "line
discipline" over a generic character device.

-Yenya

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Chris Johnson: "Re: APC, Your company is making a mistake!"
Previous message: Mike A. Harris: "Re: APC, Your company is making a mistake!"
In reply to: Alan Cox: "Re: Sharing ioctls between char and net device"