public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Binarus <lists@binarus.de>
To: kvm@vger.kernel.org
Subject: Re: Fritz!Card, MSIs and virtual machines
Date: Sun, 29 Jan 2012 07:56:11 +0100	[thread overview]
Message-ID: <4F24ED8B.8050209@binarus.de> (raw)
In-Reply-To: <4F0AD455.8070707@siemens.com>

> There are patches in the queue to enable legacy interrupt sharing for
> PCI 2.3 compliant devices at least. But I bet the Fritz hardware
> predates even this (just like my Fritz!Card DSL v2).

Thank you very much for this hint. Do you know when these will be out?

Does anybody know about a PCI ISDN card which is PCI 2.3 compliant?

> Emulating an ISDN adapter could be fairly complicated, specifically if
> the interface the binary Windows driver expects is not well documented.
> Even for Linux-on-Linux, i.e. when you can debug both host and guest
> properly, this will be quite some work (just check the driver code of
> some popular ISDN adapters Linux supports).
> 
> And it may turn out to be timing sensitive, e.g. for fax services.
> Emulation will happen in user space, i.e. in still fairly
> undeterministic QEMU hands, while device path through mostly happens in
> kernel space under KVM control.

I also think that it's not a good idea to solve the problem that way.

Perhaps there is such a thing like a USB ISDN adapter. We then could pass the USB port which this adapter is attached to to the virtual machine. But even if I am able to find such a device, I doubt that our fax system supports it. Nevertheless, there are chances that it works.

Regards,

Peter

P.S. Thanks for bothering with our exotic problem!


  reply	other threads:[~2012-01-29  6:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07 17:52 Fritz!Card, MSIs and virtual machines Binarus
2012-01-08 16:51 ` Andreas Färber
2012-01-29  7:09   ` Binarus
2012-01-09 11:49 ` Jan Kiszka
2012-01-29  6:56   ` Binarus [this message]
2012-08-16 17:21     ` rm

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=4F24ED8B.8050209@binarus.de \
    --to=lists@binarus.de \
    --cc=kvm@vger.kernel.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