Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001376]: ens1370 gameport module stupidity
Date: Sun, 23 Jul 2006 19:36:03 +0200	[thread overview]
Message-ID: <577b5ee1540e88acea76a8bc5b6810dc@bugtrack.alsa-project.org> (raw)


The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1376> 
======================================================================
Reported By:                Hetfield
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   1376
Category:                   PCI - ens1370
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     resolved
Distribution:               
Kernel Version:             
Resolution:                 won't fix
Fixed in Version:           
======================================================================
Date Submitted:             08-29-2005 11:59 CEST
Last Modified:              07-23-2006 19:36 CEST
======================================================================
Summary:                    ens1370 gameport module stupidity
Description: 
hi.

situation:
i have ens1370 built-in kernel and gameport too.
i have the lilo cmd line snd_ens1370.joystick=1 to enable gameport.
works perfectly.

the problem is if i add gameport as module.
the gameport command fails, and i can't use gameport.
this can be even normal..but the problem is i can't no more enable
gameport on audio card.

i checked the /sys and /proc fs to check a settable value. no luck
this forces gameport to be a module, only if snd is module (i can pass
values via modprobe)
and forces to be built-in if snd is built-in.

can be gameport init added via proc/sys or a specific alsa tool?

Thanks




======================================================================

----------------------------------------------------------------------
 Adrian Bunk - 07-23-06 19:36 
----------------------------------------------------------------------
This can't be easily done.

The solution is to simply build the gameport support statically into the
kernel if this driver is compiled statically.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
08-29-05 11:59 Hetfield       New Issue                                    
07-23-06 19:36 Adrian Bunk    Note Added: 0011203                          
07-23-06 19:36 Adrian Bunk    Status                   new => resolved     
07-23-06 19:36 Adrian Bunk    Resolution               open => won't fix   
======================================================================



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

             reply	other threads:[~2006-07-23 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-23 17:36 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-29  9:59 [ALSA - driver 0001376]: ens1370 gameport module stupidity bugtrack

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=577b5ee1540e88acea76a8bc5b6810dc@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox