From: Adrian McMenamin <adrian@newgolddream.dyndns.info>
To: linux-sh@vger.kernel.org
Subject: Re: Busybox and automatic module loading
Date: Tue, 08 Jan 2008 20:49:40 +0000 [thread overview]
Message-ID: <1199825380.6232.11.camel@localhost.localdomain> (raw)
In-Reply-To: <1199495386.12780.3.camel@localhost.localdomain>
On Tue, 2008-01-08 at 00:57 -0500, Mike Frysinger wrote:
> On Friday 04 January 2008, Adrian McMenamin wrote:
> > I am struggling to get alsa (userland) to work on my Dreamcast - the
> > kernel side works nicely when using oss emulation but I cannot get the
> > pure alsa stuff - which relies on the alsa-lib - to work at all.
> >
> > I *think* this is due to not being able to configure the modules
> > automatically and I cannot figureout any way to get Busybox to do this -
> > eg neither /etc/modules or /etc/modules.conf appear to be handled.
> >
> > I suppose I could hack the init in some way to fix this, but I wonder if
> > someone here has had this problem and knows how to get round it?
>
> you still having troubles with the userspace alsa stuff ?
Yes. I think I've more or less convinced people I am building the thing
properly now, but it still won't work as alsa.
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!
I could try to debug alsa-lib but even its creators admit it's pretty
hard to digest.
next prev parent reply other threads:[~2008-01-08 20:49 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 [this message]
2008-01-09 0:38 ` Mike Frysinger
2008-01-09 7:59 ` Adrian McMenamin
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=1199825380.6232.11.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