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 0000428]: unresolved symbols in snd-pcm.ko on alpha linux-2.6.7
Date: Mon, 22 Nov 2004 14:48:10 +0100	[thread overview]
Message-ID: <ed44bdd478b6dfa5556dec93ab6fa9da@bugtrack.alsa-project.org> (raw)


The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=428> 
======================================================================
Reported By:                svetljo
Assigned To:                perex
======================================================================
Project:                    ALSA - driver
Issue ID:                   428
Category:                   0_compilation problem_!!!
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     closed
Distribution:               Mandrake cooker
Kernel Version:             2.6.7
Resolution:                 unable to duplicate
Fixed in Version:           
======================================================================
Date Submitted:             08-06-2004 21:15 CEST
Last Modified:              11-22-2004 14:48 CET
======================================================================
Summary:                    unresolved symbols in snd-pcm.ko on alpha
linux-2.6.7
Description: 
trying to compile latest alsa driver 1.0.6-rc1
results in unresolved symbols at module link time
in snd-pcm.ko

gcc-3.4 , linux-2.6.7

here is the message:
*** Warning: "__ioremap" [sound/core/snd-pcm.ko] undefined!
*** Warning: "virt_to_phys" [sound/core/snd-pcm.ko] undefined!

which results in unusable alsa drivers
======================================================================

----------------------------------------------------------------------
 svetljo - 08-13-04 14:40 
----------------------------------------------------------------------
general /*probably stupid */ question

why don't you use remap_page_range instead of io_remap_page_range 
wouldn't this solve the problem

----------------------------------------------------------------------
 perex - 10-22-04 16:49 
----------------------------------------------------------------------
Please, reopen if this bug still exists with 1.0.7rc2..

Issue History
Date Modified  Username       Field                    Change              
======================================================================
08-06-04 21:15 svetljo        New Issue                                    
08-06-04 21:15 svetljo        Distribution              => Mandrake cooker 
08-06-04 21:15 svetljo        Kernel Version            => 2.6.7           
08-11-04 19:31 svetljo        Issue Monitored: svetljo                     
08-12-04 11:09 svetljo        Note Added: 0001552                          
08-12-04 11:35 perex          Note Added: 0001553                          
08-12-04 11:42 svetljo        Note Added: 0001554                          
08-12-04 11:54 perex          Note Added: 0001555                          
08-12-04 12:06 svetljo        Note Added: 0001556                          
08-12-04 12:45 svetljo        Note Added: 0001557                          
08-12-04 14:07 svetljo        Note Added: 0001558                          
08-13-04 14:40 svetljo        Note Added: 0001563                          
10-22-04 16:49 perex          Status                   assigned => resolved
10-22-04 16:49 perex          Resolution               open => unable to
duplicate
10-22-04 16:49 perex          Note Added: 0002249                          
11-22-04 14:48 tiwai          Status                   resolved => closed  
======================================================================




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

             reply	other threads:[~2004-11-22 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 13:48 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-22 14:49 [ALSA - driver 0000428]: unresolved symbols in snd-pcm.ko on alpha linux-2.6.7 bugtrack
2004-08-13 12:40 bugtrack
2004-08-12 12:07 bugtrack
2004-08-12 10:45 bugtrack
2004-08-12 10:06 bugtrack
2004-08-12  9:54 bugtrack
2004-08-12  9:42 bugtrack
2004-08-12  9:35 bugtrack
2004-08-12  9:09 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=ed44bdd478b6dfa5556dec93ab6fa9da@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