From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Conflict bluetooth and soundcard
Date: Wed, 22 Dec 2004 10:41:57 +0100 [thread overview]
Message-ID: <200412221041.57016.cijoml@volny.cz> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAosiAEZOtxUiHqgChZUVmh8KAAAAQAAAAklRz+OMPMEe49ORKn91EJAEAAAAA@t-online.de>
Compile and use LATEST vanilla kernel 2.6.10-rc3 and let us know about
success.
We NEVER give help to users using vendor kernels.
Michal
Dne st 22. prosince 2004 10:27 Peter K. Martin napsal(a):
> Hi Marcel,
> again thanks a lot for your help. The problem of the bt-connection to the
> accesspoint seems to be solved. I have a littel additional question. There
> seems to be a confict between dmabt and the soundcard. When the soundcard
> is correctly installed, dmabt give the massage can't access bt-device. Then
> I reboot linux with the bootoption ACPI=oldboot --> dmabt works without any
> message and I'm able to reinstall the soundcard by YaST. But the next boot
> without bootoption give the same result, so I can use either dmabt or
> soundcard, They seem to use the same irq or dma-channel. How is this to be
> changed for dmabt???
>
> Regards
> Peter
-------------------------------------------------------
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/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-12-22 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 9:27 Conflict bluetooth and soundcard Peter K. Martin
2004-12-22 9:41 ` Michal Semler [this message]
2004-12-22 10:49 ` AW: [Bluez-users] " Peter K. Martin
2004-12-22 11:12 ` Michal Semler
2004-12-22 12:57 ` Marcel Holtmann
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=200412221041.57016.cijoml@volny.cz \
--to=cijoml@volny.cz \
--cc=bluez-users@lists.sourceforge.net \
/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