All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: ramkromberg@mail.com
Cc: alsa-devel@alsa-project.org
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 11:22:56 +0200	[thread overview]
Message-ID: <464C1EF0.2080809@gmail.com> (raw)
In-Reply-To: <20070517084847.550D91CE303@ws1-6.us4.outblaze.com>

On 05/17/2007 10:48 AM, ramkromberg@mail.com wrote:

> Yes, its like you said Rene, sb8 works although the sound is distorted 
> and the module can't be removed...
> Later I can modprobe sgalaxy too, and the sound works without a hitch.

Okay, don't know what the trouble is with that distortion (if you haven't 
set the volumes to 100, that is) but not too important right now.

> Also since now I can compile some code - your "eeprom.c" compiles and 
> works - I'm available for further testing...

I might want you to test some mode-resetting code later; will be sure to ask 
if needed.

> I also noticed that the binary you sent was 506kb while my compilation 
> is 9kb, maybe you sent an early/later version with some additional 
> includes for verbose ?
> I compiled it with "gcc -W -Wall -o eeprom eeprom.c" like you said (on 
> my xubuntu 7.04 with build-essentials deb package installed).

Now try it with "gcc -static -W -Wall -o eeprom eeprom.c". I compiled the 
binary I provided with that "-static" flag which means the program includes 
all library code directly inside the binary and doesn't link to the library 
code you already have on your system.

I did this to avoid any version problems that may exist between different 
distributions. Essentially you're only guaranteed that a dynamic executable 
will work on the system on which it was compiled (rather, on a system with 
the same versions of the libraries installed as on the system on which it 
was compiled). In this case the program only links to the system C library 
and did nothing weird so it wasn't much of an issue, but I don't even want 
to deal with any _possible_ problems of that nature...

Yes, with a normal (ie, dynamic) link that 9k is correct.

Rene.

  reply	other threads:[~2007-05-17  9:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17  8:48 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-17  9:22 ` Rene Herman [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-13 10:17 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
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-15 10:16   ` Rask Ingemann Lambertsen
2007-05-16 23:47     ` 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=464C1EF0.2080809@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ramkromberg@mail.com \
    /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.