mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: alex.buell@tahallah.demon.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [sparc] Weird ioctl() bug in 2.2.19 (fwd)
Date: Wed, 31 Oct 2001 10:32:41 -0800 (PST)	[thread overview]
Message-ID: <20011031.103241.45747017.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110311827530.19987-100000@tahallah.demon.co.uk>
In-Reply-To: <20011031.092954.115906622.davem@redhat.com> <Pine.LNX.4.33.0110311827530.19987-100000@tahallah.demon.co.uk>

   From: Alex Buell <alex.buell@tahallah.demon.co.uk>
   Date: Wed, 31 Oct 2001 18:28:28 +0000 (GMT)

   On Wed, 31 Oct 2001, David S. Miller wrote:
   
   >   cp src/linux/include/linux/soundcard.h /usr/include/linux/soundcard.h
   
   Unfortunately, these files are identical, which is why it is so strange!

I'm pretty sure the ioctl numbers are wrong, and that is what
is causing the problem.

Print out from your app the ioctl number it uses (you've done
this already) and have the kernel do similar.  If they are different
you know that at least I was on the right track.

It's easy to figure out some value in the kernel without even
rebooting, just add to like some source file:

int foo = IOCTL_VALUE_I_WANT;

Then do "make drivers/sbus/audio/whatever.s"
and look at the assembler file for the value it
ended up using :-)

Franks a lot,
David S. Miller
davem@redhat.com

  parent reply	other threads:[~2001-10-31 18:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-31 10:41 Alex Buell
2001-10-31 17:29 ` David S. Miller
2001-10-31 18:28   ` Alex Buell
2001-10-31 18:32   ` David S. Miller [this message]
2001-10-31 20:00     ` Alex Buell
2001-11-01  3:52     ` Paul Mackerras
2001-11-01 13:19       ` Alex Buell
2001-11-01 16:00         ` Peter Jones
2001-11-01 16:21           ` Alex Buell
2001-11-01 16:27             ` Peter Jones
2001-11-01 19:28               ` Alex Buell

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=20011031.103241.45747017.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=alex.buell@tahallah.demon.co.uk \
    --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®