Linux Sound subsystem development
 help / color / mirror / Atom feed
* solo-1 chip
@ 1999-03-05 21:07 Dan Boger
  1999-03-11  6:10 ` Bill Nottingham
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: Dan Boger @ 1999-03-05 21:07 UTC (permalink / raw)
  To: linux-sound

Hi,

  Anyone have any luck configuring kernel 2.2.2 to work with the
solo-1 chip (on the motherboard)? I can get it to work with the sb
driver, but only in 8-bit mode.  WSS driver seems to be able to access 
it, but I can't think of a way to figure out the IRQ/DMA for it.

Any ideas?

Thanks

  Dan

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: solo-1 chip
  1999-03-05 21:07 solo-1 chip Dan Boger
@ 1999-03-11  6:10 ` Bill Nottingham
  1999-03-11 17:09 ` Thomas Sailer
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: Bill Nottingham @ 1999-03-11  6:10 UTC (permalink / raw)
  To: linux-sound

Dan Boger (dan@giccs.georgetown.edu) said: 
>   Anyone have any luck configuring kernel 2.2.2 to work with the
> solo-1 chip (on the motherboard)? I can get it to work with the sb
> driver, but only in 8-bit mode.  WSS driver seems to be able to access 
> it, but I can't think of a way to figure out the IRQ/DMA for it.

To get native ESS Solo support ATM, you'd either have to use the
2.2.*-ac patches (ftp.linux.org.uk:/pub/linux/alan/2.2), or ALSA
(http://alsa.jcu.cz/)

Bill

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: solo-1 chip
  1999-03-05 21:07 solo-1 chip Dan Boger
  1999-03-11  6:10 ` Bill Nottingham
@ 1999-03-11 17:09 ` Thomas Sailer
  1999-03-11 18:21 ` Dan Boger
  1999-03-12  0:05 ` Cornelius Creedon
  3 siblings, 0 replies; 5+ messages in thread
From: Thomas Sailer @ 1999-03-11 17:09 UTC (permalink / raw)
  To: linux-sound

Bill Nottingham wrote:

> To get native ESS Solo support ATM, you'd either have to use the
> 2.2.*-ac patches (ftp.linux.org.uk:/pub/linux/alan/2.2), or ALSA
> (http://alsa.jcu.cz/)

AFAIK, the -ac - patches contain initialisation code for the
ESS Maestro2, not the Solo. 

And the ALSA driver only supports playback at the moment.

Tom

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: solo-1 chip
  1999-03-05 21:07 solo-1 chip Dan Boger
  1999-03-11  6:10 ` Bill Nottingham
  1999-03-11 17:09 ` Thomas Sailer
@ 1999-03-11 18:21 ` Dan Boger
  1999-03-12  0:05 ` Cornelius Creedon
  3 siblings, 0 replies; 5+ messages in thread
From: Dan Boger @ 1999-03-11 18:21 UTC (permalink / raw)
  To: linux-sound

On Thu, 11 Mar 1999 01:10:13 -0500 Bill Nottingham <notting@redhat.com> wrote
 concerning 'Re: solo-1 chip':
> 
> To get native ESS Solo support ATM, you'd either have to use the
> 2.2.*-ac patches (ftp.linux.org.uk:/pub/linux/alan/2.2), or ALSA
> (http://alsa.jcu.cz/)

Great!  So I download the alsa driver install it.  But when I try to
modprobe it says that the device is already in use.  I look at
proc/modules, it did load a bunch of stuff, but still no sound.  Do I
need to edit my /etc/conf.modules for options?  The solo1 isn't
mentioned in any of the documents - how do I know the name of the
options?

Thanks,

  Dan

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: solo-1 chip
  1999-03-05 21:07 solo-1 chip Dan Boger
                   ` (2 preceding siblings ...)
  1999-03-11 18:21 ` Dan Boger
@ 1999-03-12  0:05 ` Cornelius Creedon
  3 siblings, 0 replies; 5+ messages in thread
From: Cornelius Creedon @ 1999-03-12  0:05 UTC (permalink / raw)
  To: linux-sound

On Thu, 11 Mar 1999, Dan Boger wrote:

> On Thu, 11 Mar 1999 01:10:13 -0500 Bill Nottingham <notting@redhat.com> wrote
>  concerning 'Re: solo-1 chip':
> > 
> > To get native ESS Solo support ATM, you'd either have to use the
> > 2.2.*-ac patches (ftp.linux.org.uk:/pub/linux/alan/2.2), or ALSA
> > (http://alsa.jcu.cz/)
> 
> Great!  So I download the alsa driver install it.  But when I try to
> modprobe it says that the device is already in use.  I look at

i have seen this error when trying to load the sb module and it seemed to
happen simply because i did not specify enough or the right options.

> proc/modules, it did load a bunch of stuff, but still no sound.  Do I
> need to edit my /etc/conf.modules for options?  The solo1 isn't
> mentioned in any of the documents - how do I know the name of the
> options?

i believe the names of the options are uniform, at least the generic ones.
try io=0x... irq=... dma1=... and such.

you can supply these on the command line, until you get it working, then
put the right values into your conf.modules
ie 'modprobe ess-solo irq=x io=0xwhatever ...'

-cc

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~1999-03-12  0:05 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-03-05 21:07 solo-1 chip Dan Boger
1999-03-11  6:10 ` Bill Nottingham
1999-03-11 17:09 ` Thomas Sailer
1999-03-11 18:21 ` Dan Boger
1999-03-12  0:05 ` Cornelius Creedon

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox