From: ing. Federico Fuga <fuga@studiofuga.com>
To: buildroot@busybox.net
Subject: [Buildroot] Alsa problem with arm 2.6.23.1 and uclibc
Date: Fri, 16 Nov 2007 17:50:44 +0100 [thread overview]
Message-ID: <473DCA64.3060505@studiofuga.com> (raw)
In-Reply-To: <473D82AE.5040907@promwad.com>
Hi Ivan,
which kernel version and kernel headers are you using? Mine are 2.6.23.1
and 2.6.23, but now I am trying to move the kernel headers to 2.6.21
(Angstrom linux works without problems, but are based on different
kernel headers).
uclibc I am using are 0.9.29, alsa 1.0.14.
The failing ioctl is identical both in the working (Angstrom) and not
working versions, and since the kernel is the same (really the same!) I
am thinking that is only a problem between the "glue" of uclibc and
kernel...
I'll keep you informed.
Regards,
ing. Federico Fuga
(sorry for the duplicate mail!)
Ivan Kuten ha scritto:
> > Hi Federico!
> >
> > I'm observing the same problem with ALSA as you.
> >
> >
>
>> >> ioctl(4, USBDEVFS_CONTROL, 0xbef809cc) = 0
>> >> ioctl(4, UI_DEV_CREATE, 0xbef80ab0) = 0
>> >> ioctl(4, USBDEVFS_CONNECTINFO, 0xbef80634) = 0
>> >> ioctl(4, USBDEVFS_HUB_PORTINFO, 0xbef80748) = -1 ENOTTY (Inappropriate
>> >> ioctl for device)
>> >>
>>
> >
> > Think these lines are key to understanding what the problem is.
> >
> > Regards,
> > Ivan
> >
> >
> >
>
prev parent reply other threads:[~2007-11-16 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 10:27 [Buildroot] Alsa problem with arm 2.6.23.1 and uclibc ing. Federico Fuga
2007-11-16 11:44 ` Ivan Kuten
2007-11-16 16:50 ` ing. Federico Fuga [this message]
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=473DCA64.3060505@studiofuga.com \
--to=fuga@studiofuga.com \
--cc=buildroot@busybox.net \
/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