From: Jeff Garzik <garzik@havoc.gtf.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SIOCDEVICE ?
Date: Sat, 2 Feb 2002 18:57:44 -0500 [thread overview]
Message-ID: <20020202185744.B1740@havoc.gtf.org> (raw)
In-Reply-To: <200201311304.FAA00344@adam.yggdrasil.com> <20020131181241.A3524@fafner.intra.cogenit.fr> <m3665iqhqn.fsf@defiant.pm.waw.pl> <20020202154424.A5845@fafner.intra.cogenit.fr> <m3wuxvofvf.fsf@defiant.pm.waw.pl>
In-Reply-To: <m3wuxvofvf.fsf@defiant.pm.waw.pl>; from khc@pm.waw.pl on Sat, Feb 02, 2002 at 08:14:44PM +0100
On Sat, Feb 02, 2002 at 08:14:44PM +0100, Krzysztof Halasa wrote:
> Francois Romieu <romieu@cogenit.fr> writes:
>
> > Your patch doesn't apply against 2.5.3. I did a quick update and noticed the
> > patch is the sole user of SIOCDEVICE (with dscc4) and SIOCDEVPRIVATE.
>
> SIOCDEVICE, yes. That's my attempt to create an ioctl interface for
> controlling devices. It's defined by the hdlc patch, discussed about
> a year (?) ago here. Yes, I think I should post a note here.
This too seems way too generic for including in the kernel.
> A new patch which applies to 2.5.3 is in the usual place:
> ftp://ftp.pm.waw.pl/pub/linux/hdlc/
> This is what I want included in base kernel.
What data is passed through the following structure?
Untyped data has the same problems as I listed for SIOCDEVPRIVATE:
> struct if_settings
> {
> unsigned int type; /* Type of physical device or protocol */
> unsigned int data_length; /* device/protocol data length */
> void * data; /* pointer to data, ignored if length = 0 */
> };
Regards,
Jeff
next prev parent reply other threads:[~2002-02-02 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 13:04 linux-2.4.3/drivers/net/wan/dscc4.c does not compile Adam J. Richter
2002-01-31 17:12 ` Francois Romieu
2002-01-31 22:26 ` Krzysztof Halasa
2002-02-02 14:44 ` SIOCDEVICE ? Francois Romieu
2002-02-02 19:14 ` Krzysztof Halasa
2002-02-02 23:57 ` Jeff Garzik [this message]
2002-02-02 20:43 ` Jeff Garzik
2002-02-02 22:18 ` Francois Romieu
2002-02-03 0:40 ` Alan Cox
2002-02-03 14:19 ` Francois Romieu
2002-02-03 1:44 ` Krzysztof Halasa
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=20020202185744.B1740@havoc.gtf.org \
--to=garzik@havoc.gtf.org \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®