From: Mike Frysinger <vapier@gentoo.org>
To: linux-sh@vger.kernel.org
Subject: Re: Busybox and automatic module loading
Date: Wed, 09 Jan 2008 19:21:27 +0000 [thread overview]
Message-ID: <200801091421.28128.vapier@gentoo.org> (raw)
In-Reply-To: <1199495386.12780.3.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]
On Wednesday 09 January 2008, Adrian McMenamin wrote:
> On Wed, 2008-01-09 at 12:54 -0500, Mike Frysinger wrote:
> > On Wednesday 09 January 2008, Adrian McMenamin wrote:
> > > 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.
> >
> > i'd just build everything into the kernel except for the module you're
> > developing ... a lot simpler that way
>
> Why? I'm not sure I follow what you mean.
because then there is no question of whether you loaded things properly ...
they're built into the kernel, end of story
> > > > > 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?
> >
> > make sure you turn off version stuff: --with-versioned=no
>
> Is this for alsa-lib or something else?
yes, for alsa-lib ... if you try to use symbol versioning with alsa-lib under
uClibc (since uClibc does not handle symbol versioning information), it wont
work properly
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2008-01-09 19:21 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
2008-01-09 17:54 ` Mike Frysinger
2008-01-09 18:56 ` Adrian McMenamin
2008-01-09 19:21 ` Mike Frysinger [this message]
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=200801091421.28128.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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 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.