From: Andrey Konovalov <andreyknvl@google.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
Nazime Hande Harputluoglu <handeharputlu@google.com>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: /dev/sequencer descriptions
Date: Mon, 27 Jul 2020 20:05:12 +0200 [thread overview]
Message-ID: <CAAeHK+wu3WvODwA_33uPDdFCtipeQWuitb_EDXOfDNO_RGYnvA@mail.gmail.com> (raw)
In-Reply-To: <s5hr1swj0p2.wl-tiwai@suse.de>
On Mon, Jul 27, 2020 at 8:02 PM Takashi Iwai <tiwai@suse.de> wrote:
>
> On Mon, 27 Jul 2020 19:47:54 +0200,
> Andrey Konovalov wrote:
> >
> > Hi Takashi,
> >
> > We're working on syzkaller descriptions for /dev/sequencer [1], but
> > have some troubles understanding its functionality. The main question
> > is: is sound/synth/emux/ code reachable when tested in a VM (we're
> > using QEMU with -soundhw all), or does it require some specific
> > hardware to be present?
>
> It's for Creative SoundBlaster EMU chips, and it needs the specific
> hardware that isn't emulated, so far.
>
> > In our setup (with Debian Stretch userspace image) we have
> > /dev/sequencer with SNDRV_MINOR_OSS_SEQUENCER and /dev/sequencer2 with
> > SNDRV_MINOR_OSS_MUSIC. For the former, there are no synth devices as
> > reported by SNDCTL_SEQ_NRSYNTHS. For the latter, synth devices are
> > there, but the load_patch() callback is not reachable as this check
> > [2] fails.
> >
> > Is that code impossible to test in a VM at all? Or are there some
> > specific kernel options/drivers that need to be enabled?
>
> Another possible device supporting the OSS sequencer is the old FM
> OPL3. But it seems also not properly implemented in QEMU (I see only
> OPL2), unfortunately.
OK, got it, thank you!
prev parent reply other threads:[~2020-07-27 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 17:47 /dev/sequencer descriptions Andrey Konovalov
2020-07-27 18:02 ` Takashi Iwai
2020-07-27 18:05 ` Andrey Konovalov [this message]
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=CAAeHK+wu3WvODwA_33uPDdFCtipeQWuitb_EDXOfDNO_RGYnvA@mail.gmail.com \
--to=andreyknvl@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=handeharputlu@google.com \
--cc=syzkaller@googlegroups.com \
--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.