From: Federico Fuga <f.fuga@people.it>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Inappropriate ioctl for device on alsalib with uclibc and arm platform
Date: Tue, 20 Nov 2007 17:51:22 +0100 [thread overview]
Message-ID: <4743108A.7050409@people.it> (raw)
In-Reply-To: <s5hbq9pggs3.wl%tiwai@suse.de>
Takashi Iwai ha scritto:
> At Mon, 19 Nov 2007 16:21:39 +0100,
> Federico Fuga wrote:
> # alsactl restore
> alsactl: set_control:1159: Cannot write control '2:0:0:Speaker Playback
> Volume:0' : Inappropriate ioctl for device
>
> while traceing with strace I see that:
>
> open("/usr/lib/libasound.so.2", O_RDONLY) = 4
> fstat(4, {st_mode=S_IFREG|0755, st_size=716844, ...}) = 0
> close(4) = 0
> open("/dev/snd/controlC0", O_RDONLY) = 4
> close(4) = 0
> open("/dev/snd/controlC0", O_RDWR) = 4
> ioctl(4, USBDEVFS_CONTROL, 0xbeab09ec) = 0
> ioctl(4, UI_DEV_CREATE, 0xbeab0ad0) = 0
> ioctl(4, USBDEVFS_CONNECTINFO, 0xbeab0654) = 0
> ioctl(4, USBDEVFS_HUB_PORTINFO, 0xbeab0768) = -1 ENOTTY (Inappropriate
>
>
> Looks like the definition of SNDRV_CTL_ICOTL_ELEM_WRITE doesn't match
> with the user-space and the kernel, most likely the size of struct
> snd_ctl_elem_value. This might be a word alignment issue.
>
>
Hi Takashi,
thank you for your response. I have tracked the problem to the kernel
space and found exactly what you say (structure size). I didn't think
about word alignment, I will try by changeing the gcc options.
Do you think I should look at the cross compiler or at the parameters
passed to gcc while compiling the alsa library?
Thank you very much.
Federico
next prev parent reply other threads:[~2007-11-20 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 15:21 Inappropriate ioctl for device on alsalib with uclibc and arm platform Federico Fuga
2007-11-20 13:58 ` Takashi Iwai
2007-11-20 16:51 ` Federico Fuga [this message]
2007-11-21 10:11 ` Takashi Iwai
2007-11-23 17:49 ` Federico Fuga
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=4743108A.7050409@people.it \
--to=f.fuga@people.it \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.