All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dino <dino@e4a.it>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Umaintained drivers
Date: Tue, 28 Feb 2006 12:05:36 +0100	[thread overview]
Message-ID: <1141124736.44042e805a63f@mail.e4a.it> (raw)

>>
>> Hi,
>>     i'm having a lot of problems with my cs46xx card because no replay
>> to my questions/bugs from the manteiner. So is this driver dead? Is
>> there a manteiner for it? How many drivers are actually unmanteined?
>
>The problem is, as usual, no developers have this card.
>So, debugging a model-specific problem is pretty difficult in general
>although the driver itself is maintained in a certain level,
>i.e. adapting the mainstream and following API changes.
>
>Takashi

Thanks for your replay.
Ok but i'm a developer and i have that card, so i can do something by myself.
But i need documentation, a lot of documentation (please don't tell me that
there is only the source code) and a feedback from any author of the driver
should be very appreciated.

bye,
   Dino



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642

             reply	other threads:[~2006-02-28 11:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 11:05 Dino [this message]
2006-03-03 18:08 ` Re: Umaintained drivers Takashi Iwai
2006-03-03 21:45   ` Rene Herman
  -- strict thread matches above, loose matches on Subject: below --
2006-02-19 14:32 Dino Puller
2006-02-21 15:29 ` 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=1141124736.44042e805a63f@mail.e4a.it \
    --to=dino@e4a.it \
    --cc=alsa-devel@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 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.