All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>
Cc: Thomas Charbonnel <thomas@undata.org>,
	Tim Blechmann <TimBlechmann@gmx.net>,
	alsa-devel@lists.sourceforge.net
Subject: Re: Hammerfall (hdsp) initialization problem
Date: Fri, 30 Jul 2004 15:01:52 +0200	[thread overview]
Message-ID: <s5hbrhxps1r.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hllh54dm0.wl@alsa2.suse.de>

At Tue, 27 Jul 2004 18:30:15 +0200,
I wrote:
> 
> At Tue, 27 Jul 2004 12:07:06 -0400,
> Jean-Marc Valin wrote:
> > 
> > > The problem is that you have to know the PCI pointer to call
> > > dma_alloc_coherent() correctly beforehand.  Otherwise you'll get only
> > > ZONE_DMA under 16MB region.
> > 
> > Still, there must be *something* that can be done, no? What are other
> > OSs doing about that? I mean, the card manual doesn't say "if you insert
> > this card after boot, it won't work", so I don't see why ALSA
> > fundamentally couldn't support hot-plugging cards.
> 
> Of course hotplug is supported (how can you read above in such a way?)
> The question is only the memory preallocation for the cardbus device.
> 
> hdsp driver and/or memalloc.c should be changed to handle properly the
> buffer preservation after replugging.  Most likely the pci device
> pointer is changed after replug.  Can anyone check whether pci_dev
> pointer is changed at each time?

Ok, I now simplified the middle layer code for buffer allocation.
Now the HDSP buffer should be preserved during replugging and the same
buffer should be reused.

I don't attach here the patch since it's a relatively massive change.
Please check the cvs tree later after sync'ed.
(Or wait for 1.0.6-rc release, scheduled soon later)


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com

  parent reply	other threads:[~2004-07-30 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 18:32 Hammerfall (hdsp) initialization problem Jean-Marc Valin
2004-07-24  8:05 ` Tim Blechmann
2004-07-25  5:48   ` Jean-Marc Valin
2004-07-25 11:16     ` Thomas Charbonnel
2004-07-27 13:47       ` Takashi Iwai
2004-07-27 16:07         ` Jean-Marc Valin
2004-07-27 16:30           ` Takashi Iwai
2004-07-27 19:26             ` Paul Davis
2004-07-30 13:01             ` Takashi Iwai [this message]
2004-07-27 13:43     ` 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=s5hbrhxps1r.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=Jean-Marc.Valin@USherbrooke.ca \
    --cc=TimBlechmann@gmx.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=thomas@undata.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 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.