All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Jones <pjones@redhat.com>
To: ultralinux@vger.kernel.org
Subject: Another Brute Force And Ignorance(tm) derived question...
Date: Mon, 12 Apr 1999 00:08:46 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-92387605531299@msgid-missing> (raw)

(Yeah, one of these days I'll actually learn something)

As I've said before, I'm attempting to get an es1371 going, and I'm
running into a couple of things that are perplexing me...  I've managed to
get it to compile in (obvious config.in patch), and with some patches
against es1371.c it doesn't even Oops anymore (these are getting merged in
to the main kernel, I think... Thomas Sailer sent them off to Alan
sometime last week), but I'm having some trouble after that, regarding how
the ioctl()'s work on sparc64...

It looks as if the switch(cmd){...} in sys32_ioctl() goes through, and if
it finds an ioctl() in its list, it runs it, and if not, it prints an
error.  But if I run, say, aumix, I get:

<4>sys32_ioctl: Unknown cmd fd(3) cmd(40044dfe) arg(0002563c)

I go to look what ioctl() it happened to send, and its doing

open("/dev/mixer", O_RDWR)              = 4
ioctl(4, SOUND_MIXER_READ_DEVMASK, 0x2563c) = -1 EINVAL (Invalid argument)

Which doesn't make sense to me, because SOUND_MIXER_READ_DEVMASK is in its
list, and is handled by es1371.c ...

Have I missed something obvious?

 -- Peter

"If people are good only because they fear punishment, and hope for reward,
then we are a sorry lot indeed."
		-- Einstein

             reply	other threads:[~1999-04-12  0:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-12  0:08 Peter Jones [this message]
1999-04-12  1:26 ` Another Brute Force And Ignorance(tm) derived question David Miller
1999-04-12  4:04 ` Peter Jones
1999-04-12  4:11 ` David Miller
1999-04-12  4:50 ` Peter Jones
1999-04-12  4:58 ` David Miller
1999-04-12  5:14 ` Jakub Jelinek
1999-04-12 12:46 ` Peter Jones
1999-04-12 13:22 ` Jakub Jelinek
1999-04-12 14:53 ` Peter Jones

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=marc-linux-ultrasparc-92387605531299@msgid-missing \
    --to=pjones@redhat.com \
    --cc=ultralinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.