From: Adrian McMenamin <adrian@newgolddream.dyndns.info>
To: linux-sh@vger.kernel.org
Subject: Re: Busybox and automatic module loading
Date: Wed, 09 Jan 2008 07:59:17 +0000 [thread overview]
Message-ID: <1199865557.6393.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1199495386.12780.3.camel@localhost.localdomain>
On Tue, 2008-01-08 at 19:38 -0500, Mike Frysinger wrote:
> On Tuesday 08 January 2008, Adrian McMenamin wrote:
> > On Tue, 2008-01-08 at 00:57 -0500, Mike Frysinger wrote:
>
> are you generating the device nodes by hand or relying on something else ?
> mdev currently will not place the device nodes in a subdir as would be
> required by alsa-lib.
No, I'm using udev. The module loading stuff was not the issue I'm sure
anyway. And the OSS emulation appears to work perfectly.
>
> > Maybe something wrong with my driver, (though oss emulation works very
> > well), but nobody is being very communicative. I don't think there is
> > much cross compiling of alsa going on out there!
>
> are you using uClibc or glibc ? we're cross-compiling alsa-lib for
> Blackfin/uClibc and it seems to be working for us. our drivers are varying
> degrees of working, but that is a driver problem ;)
>
uClibc. I suppose my issue might be driver related, but if so nobody can
point me as to where. And, as I say, the OSS emulation works.
Maybe you could point me to the configure script you are using?
> > I could try to debug alsa-lib but even its creators admit it's pretty
> > hard to digest.
>
> so it is
> -mike
next prev parent reply other threads:[~2008-01-09 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 1:09 Busybox and automatic module loading Adrian McMenamin
2008-01-05 1:24 ` Mike Frysinger
2008-01-05 12:47 ` Adrian McMenamin
2008-01-08 5:57 ` Mike Frysinger
2008-01-08 20:49 ` Adrian McMenamin
2008-01-09 0:38 ` Mike Frysinger
2008-01-09 7:59 ` Adrian McMenamin [this message]
2008-01-09 17:54 ` Mike Frysinger
2008-01-09 18:56 ` Adrian McMenamin
2008-01-09 19:21 ` Mike Frysinger
2008-01-09 20:55 ` Adrian McMenamin
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=1199865557.6393.2.camel@localhost.localdomain \
--to=adrian@newgolddream.dyndns.info \
--cc=linux-sh@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