Re: ioctl number 0xF3
From: Francois Romieu (romieu_at_fr.zoreil.com)
Date: 05/22/04
- Previous message: Sergey Vlasov: "Re: [PATCH] isofs meta-data beyond 4GB"
- In reply to: Thomas Winischhofer: "Re: ioctl number 0xF3"
- Next in thread: Thomas Winischhofer: "Re: ioctl number 0xF3"
- Reply: Thomas Winischhofer: "Re: ioctl number 0xF3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 22 May 2004 16:32:14 +0200 To: Thomas Winischhofer <thomas@winischhofer.net>
Thomas Winischhofer <thomas@winischhofer.net> :
[...]
> Don't get me wrong.. did you ever write a driver for graphics hardware?
He can surely tell when an egg stinks. However Arjan is not a chicken.
[...]
> Is 64 out of, what's that, 65536 too much to ask? Well, I could live
> with 32 as well...
Reserving a generous ioctl range without any clear interface will make
some people nervous. If you can not specify the interface now, try to
separate the generic/specific part of it and use sub-ioctl for the really
scary things as it will make the future life easier.
If you have some pointers to the existing code, that may help too.
-- Ueimor - 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/
- Previous message: Sergey Vlasov: "Re: [PATCH] isofs meta-data beyond 4GB"
- In reply to: Thomas Winischhofer: "Re: ioctl number 0xF3"
- Next in thread: Thomas Winischhofer: "Re: ioctl number 0xF3"
- Reply: Thomas Winischhofer: "Re: ioctl number 0xF3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|