All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Blechmann <tim@klingt.org>
To: LKML <linux-kernel@vger.kernel.org>, alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>, Brian Gerst <brgerst@gmail.com>
Subject: [bisected] lx6464es fails to open a second time
Date: Tue, 22 Nov 2011 01:00:39 +0100	[thread overview]
Message-ID: <2428359.JOQWRg64O4@moka> (raw)

hi all, especially brian and takashi,

some time ago, i've been developing the driver for the lx6464es ethersound 
sound card, which has been included into the kernel for some time. however i 
haven't been able to use it in kernels after 2.6.33.

today, i was able to bisect the issue and the first bad commit is:

commit 6175ddf06b6172046a329e3abfd9c901a43efd2e
Author: Brian Gerst <brgerst@gmail.com>
Date:   Fri Feb 5 09:37:07 2010 -0500

    x86: Clean up mem*io functions.
    
    Iomem has no special significance on x86.  Use the standard mem*
    functions instead of trying to call other versions.  Some fixups
    are needed to match the function prototypes.
    
    Signed-off-by: Brian Gerst <brgerst@gmail.com>
    LKML-Reference: <1265380629-3212-6-git-send-email-brgerst@gmail.com>
    Signed-off-by: H. Peter Anvin <hpa@zytor.com>


the problem was: the sound card could only be started once, but i haven't been 
able to start it a second time, probably because the driver doesn't shut down 
the device correctly.

the communication with the device is done by passing simple commands via 
memcpy_fromio and memcpy_toio (compare sound/pci/lx6464es/lx_core.c, lines 75 
to 99). any idea, what is going wrong there?

thanks, tim

WARNING: multiple messages have this Message-ID (diff)
From: Tim Blechmann <tim@klingt.org>
To: LKML <linux-kernel@vger.kernel.org>, alsa-devel@alsa-project.org
Cc: Brian Gerst <brgerst@gmail.com>, Takashi Iwai <tiwai@suse.de>
Subject: [bisected] lx6464es fails to open a second time
Date: Tue, 22 Nov 2011 01:00:39 +0100	[thread overview]
Message-ID: <2428359.JOQWRg64O4@moka> (raw)

hi all, especially brian and takashi,

some time ago, i've been developing the driver for the lx6464es ethersound 
sound card, which has been included into the kernel for some time. however i 
haven't been able to use it in kernels after 2.6.33.

today, i was able to bisect the issue and the first bad commit is:

commit 6175ddf06b6172046a329e3abfd9c901a43efd2e
Author: Brian Gerst <brgerst@gmail.com>
Date:   Fri Feb 5 09:37:07 2010 -0500

    x86: Clean up mem*io functions.
    
    Iomem has no special significance on x86.  Use the standard mem*
    functions instead of trying to call other versions.  Some fixups
    are needed to match the function prototypes.
    
    Signed-off-by: Brian Gerst <brgerst@gmail.com>
    LKML-Reference: <1265380629-3212-6-git-send-email-brgerst@gmail.com>
    Signed-off-by: H. Peter Anvin <hpa@zytor.com>


the problem was: the sound card could only be started once, but i haven't been 
able to start it a second time, probably because the driver doesn't shut down 
the device correctly.

the communication with the device is done by passing simple commands via 
memcpy_fromio and memcpy_toio (compare sound/pci/lx6464es/lx_core.c, lines 75 
to 99). any idea, what is going wrong there?

thanks, tim


             reply	other threads:[~2011-11-22  0:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  0:00 Tim Blechmann [this message]
2011-11-22  0:00 ` [bisected] lx6464es fails to open a second time Tim Blechmann
2011-11-22  7:42 ` Clemens Ladisch
2011-11-22  7:42   ` [alsa-devel] " Clemens Ladisch
2011-11-22 10:17   ` Tim Blechmann
2011-11-22 10:17     ` [alsa-devel] " Tim Blechmann
2011-11-22 10:26     ` Takashi Iwai
2011-11-22 10:26       ` [alsa-devel] " Takashi Iwai

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=2428359.JOQWRg64O4@moka \
    --to=tim@klingt.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=brgerst@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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.