Re: ioctl number 0xF3

From: Francois Romieu (
Date: 05/24/04

  • Next message: Adrian Bunk: "[patch] John A. Martin no longer maintains the CREDITS file"
    Date:	Mon, 24 May 2004 01:39:30 +0200
    To: Thomas Winischhofer <>

    Thomas Winischhofer <> :
    > The interface I intend to use matches the one the X driver has (using
    > the Xv extension as an ioctl replacement) and will be documented. Since
    > I develope both the SiS kernel framebuffer driver as well as the SiS X
    > driver this will reduce duplicate code and ensures good cooperation.
    > Furthermore, there could be a common library for both the framebuffer and X.

    As you apparently manage the utility, you are at the first place to handle
    the incompatibilities as well. Fine :o)

    > Hm. Were the matrox folks asked for a "clear interface" in advance when
    > they started using the 'n' ioctls? Am I too polite? ;)

    Nonononono. It is just a bit optimistic to hope for an instant solution
    here if there has not been one so far on the xfree/friends side. Imo
    there are some grey areas:
    - what does the common part need;
    - who can/want/will do the dirty work.
    Looking at the code, there is no instant answer and things won't be set
    in stone today. The best you can do is to minimize the pain in the future:
    use as few ioctls as possible so that you can control/verify the changes
    of interface trough a single point and design this interface so that it
    takes into account that things will change. No silver bullet.

    > sisfb uses a few ioctls already, as an extension to the generic fb
    > related ioctls. (Although the version currently in mainline 2.4 is not
    > in any way 32/64 bit safe, and neiter is the mainline 2.6 version yet as
    > regards the obviously required ioctl32 emulation stuff - investigating
    > this at the moment).

    Consider reusing these ? It may be a bit academic as you control the main
    utility anyway.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

  • Next message: Adrian Bunk: "[patch] John A. Martin no longer maintains the CREDITS file"

    Relevant Pages

    • Re: ioctl number 0xF3
      ... I didn't mean that as any sort of insult. ... people telling me "implement a generic interface". ... driver and want the users of this driver to have some sort of comfort. ... intended ioctls already implemented. ...
    • RE: Digi Neo 8: linux-2.6.12_r2 jsm driver
      ... Oh, keep in mind, the ioctls are not new. ... Subject: Digi Neo 8: linux-2.6.12_r2 jsm driver ... as the extended features added special ioctls ... , then this interface needs ...
    • Re: ioctls, etc. (was Re: [PATCH 1/4] sas: add flag for locally attached PHYs)
      ... > ioctls represent the most direct, ... > potentially a few levels down a driver stack. ... sysfs, since its normal ASCII ... This entirely depends on the interface you define. ...
    • RE: [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b7).
      ... > I didn't see any comments about Christoph's patches, so is it OK if I ... the driver now, ... IOCTLs were mainly used and built upon due the platform agnostic ... use the platform's IOCTL interface with the QLogic ...
    • Re: Linux Firewall/LoadBalancer
      ... The bonding driver originally came from Donald Becker's beowulf patches for ... Build kernel with the bonding driver ... "Bonding driver support" in the "Network device support" section. ... so the bonding driver will automatically load when the bond0 interface is ...