alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: alsa-devel@alsa-project.org, ramkromberg@mail.com
Subject: Re: Can someone verify support for "AzTech Sound	Galaxy Nova 16 Extra II-3D - using AZT-2316/R Chipset -	FCC-ID:I38-MMSN846" ?
Date: Thu, 17 May 2007 01:35:59 +0200	[thread overview]
Message-ID: <464B955F.3030508@gmail.com> (raw)
In-Reply-To: <20070515101259.GS5690@sygehus.dk>

On 05/15/2007 12:12 PM, Rask Ingemann Lambertsen wrote:

> On Tue, May 15, 2007 at 12:22:03AM +0200, Rene Herman wrote:
>  
>> As said. If you execute this as root it should enable the card. You can 
>> pick the base address (the one JMPB0 is set to) with "-p 0x220|0x240". 
>> Default is 0x200 if you don't specify one.
>              ^^^^^
>    0x220 or 0x240?

0x220.

> Do you think there is any point in trying any of this configuration stuff
> on an NXPro?

Probably not. The oldest Sound Galaxy I have is a NX Pro 16 (I38-MMSN803) 
and I haven't yet tested on that either. That one does have an EEPROM but 
the jumper doesn't select between EEPROM and software but between EEPROM and 
  "factory setting" which probably implies it's not software configurable.

(other than by writing to the EEPROM and rebooting the card with the jumper 
set to EEPROM; writing to the EEPROM is yet another fun little project for a 
future HWDEP interface in the driver but it's not an important feature).

Does your NX Pro have an EEPROM? It should be a small 8-pin chip marked with 
something close to "X24C00", near a clock chip and probably near an Intel 
8051 microcontroller. And does it have a jumper that sounds like it has 
anything to do with things?

>> 		return EXIT_FAILURE;
>> 	}
>>
>> 	return EXIT_SUCCESS;
> 
>    It is not often that I see other people use standards compliant return
> values from main().

0 and !0 are as standards compliant... :-)

Rene.

  reply	other threads:[~2007-05-16 23:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 10:17 Can someone verify support for "AzTech Sound Galaxy Nova 16 Extra II-3D - using AZT-2316/R Chipset - FCC-ID:I38-MMSN846" ? ramkromberg
2007-05-13 11:00 ` j t
2007-05-14  9:07 ` Rask Ingemann Lambertsen
2007-05-14 21:53 ` Rene Herman
2007-05-14 22:22   ` Rene Herman
2007-05-14 22:25     ` Rene Herman
2007-05-15 10:12     ` Rask Ingemann Lambertsen
2007-05-16 23:35       ` Rene Herman [this message]
2007-05-17 13:08         ` Rask Ingemann Lambertsen
2007-05-19  2:55           ` Rene Herman
2007-05-20 12:23             ` Rask Ingemann Lambertsen
2007-05-23 20:03               ` Can someone verify support for Rene Herman
2007-05-15 10:16   ` Can someone verify support for "AzTech Sound Galaxy Nova 16 Extra II-3D - using AZT-2316/R Chipset - FCC-ID:I38-MMSN846" ? Rask Ingemann Lambertsen
2007-05-16 23:47     ` Rene Herman
  -- strict thread matches above, loose matches on Subject: below --
2007-05-17  8:48 ramkromberg
2007-05-17  9:22 ` Rene Herman
2007-05-15  8:50 ramkromberg
2007-05-16 23:23 ` Rene Herman
2007-05-14 13:21 ramkromberg
2007-05-14 14:53 ` Rene Herman
2007-05-11 16:44 ramkromberg
2007-05-11 21:42 ` Rene Herman
2007-05-10 20:57 ramkromberg
2007-05-10 21:06 ` Rene Herman
2007-05-10 18:24 ramkromberg
2007-05-07  5:46 ramkromberg
2007-05-07 20:51 ` Rene Herman
2007-05-10 14:56   ` Rene Herman

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=464B955F.3030508@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ramkromberg@mail.com \
    --cc=rask@sygehus.dk \
    /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;
as well as URLs for NNTP newsgroup(s).