lkml.org 
[lkml]   [2004]   [Nov]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Problem with ioctl command TCGETS
    Miklos Szeredi wrote:
    >>>>Think read(2)/write(2). We already have several barfbags too many,
    >>>>and that includes both ioctl() and setsockopt(). We are stuck with
    >>>>them for compatibility reasons, but why the hell would we need yet
    >>>>another one?
    >>>
    >>>You can't replace either ioctl() or setsockopt() with read/write can
    >>>you? Both of them set out-of-band information on file descriptors.
    >>
    >>Out-of-band == should be on a separate channel...
    >
    >
    > Tell me how? E.g. how would you set/get sound stream parameters if
    > not with ioctl()?
    >

    Maybe using sysfs? /sys/device/cdrom/param ?
    But then you'd have to open another file :(

    And what about somethink like:
    cdrom_fd = open("/dev/cdrom", O_RDWR)
    cdrom_param_fd = get_param_fd(cdrom_fd) /* a new syscall */
    Now read/write to this param fd.
    And two new entries in the struct file_operations:
    write_param([same args as write])
    read_param([same args as read])

    tom
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 14:08    [W:4.819 / U:0.000 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site