Busybox and automatic module loading

Busybox and automatic module loading

[Adrian McMenamin]

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?

Adrian

Re: Busybox and automatic module loading

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 861 bytes --]

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?

it isnt busybox's job to load modules automatically and thus there is nothing 
in there for it.  then again, i dont see why it would matter ... just do 
`modprobe <the alsa driver>` and there's nothing else to be done.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

Re: Busybox and automatic module loading

[Adrian McMenamin]

On Fri, 2008-01-04 at 20:24 -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?
> 
> it isnt busybox's job to load modules automatically and thus there is nothing 
> in there for it.  then again, i dont see why it would matter ... just do 
> `modprobe <the alsa driver>` and there's nothing else to be done.

Well, obviously I can load the module manually - as that is how I get
the oss emulation to work.

ALSA seems to require various configuration settings to work and that is
what I am trying to get to work.

I took one of the init.d scripts on my x86 box, chopped it down slightly
and loaded that: now the modules load but the alias commands/settings
are all rejected: so more work needs to be done. 

Re: Busybox and automatic module loading

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

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 ?
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

Re: Busybox and automatic module loading

[Adrian McMenamin]

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.

Re: Busybox and automatic module loading

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]

On Tuesday 08 January 2008, Adrian McMenamin wrote:
> 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.

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.

> 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 ;)

> I could try to debug alsa-lib but even its creators admit it's pretty
> hard to digest.

so it is
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

Re: Busybox and automatic module loading

[Adrian McMenamin]

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

Re: Busybox and automatic module loading

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]

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

> > > 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
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

Re: Busybox and automatic module loading

[Adrian McMenamin]

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.

> > > > 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?

Adrian

Re: Busybox and automatic module loading

[Mike Frysinger]

[-- 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 --]

Re: Busybox and automatic module loading

[Adrian McMenamin]

On Wed, 2008-01-09 at 14:21 -0500, Mike Frysinger wrote:

> 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

You got my hopes there, but no, that's not it :(

Adrian