All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Robert Schweikert <rschweikert@novell.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: LSB inclusion of ALSA
Date: Fri, 19 Jun 2009 15:43:24 +0200	[thread overview]
Message-ID: <4A3B95FC.4020404@ladisch.de> (raw)
In-Reply-To: <4A3B78F4.7000407@novell.com>

Robert Schweikert wrote:
> Clemens Ladisch wrote:
> > While many parts of the library can be tested without special hardware
> > (config, sequencer+MIDI, timers), the parts that are most likely to be
> > used (PCM, mixer) require at least some kernel driver and contain many
> > functions that are used to handle hardware differences.
> 
> Understood, but this is functional testing (current tests seem to cover
> this) and would required the appropriate hardware (a gazilion sound
> cards). LSB makes no guarantees that the drivers exist and have no bugs.
> LSB does strive to guarantee that a particular interface exists and
> behaves as specified.
> 
> So for interfaces that require a driver one could test that an
> appropriate error condition is returned if no driver exists, and we
> could test that no error condition is triggered when a dummy driver is
> connected. Correct?

Yes.

This would require that the test suite has the capability to load and
unload kernel modules.  Could this ever be a problem?


Best regards,
Clemens

      reply	other threads:[~2009-06-19 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 17:56 LSB inclusion of ALSA Robert Schweikert
2009-06-16 11:59 ` Clemens Ladisch
2009-06-17  8:16   ` Takashi Iwai
2009-06-17  8:52     ` Clemens Ladisch
2009-06-19 12:07       ` Robert Schweikert
2009-06-19 12:45       ` Theodore Tso
2009-06-19 13:43         ` Clemens Ladisch
2009-06-19 11:39   ` Robert Schweikert
2009-06-19 13:43     ` Clemens Ladisch [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=4A3B95FC.4020404@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=rschweikert@novell.com \
    /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.