Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Harry Butterworth <heb1001@gmail.com>
Cc: Alsa-devel@alsa-project.org
Subject: Re: Creative X-Fi Titanium HD ctxfi bugs 5378 5218 4868
Date: Tue, 14 Jun 2011 07:38:06 +0200	[thread overview]
Message-ID: <s5hei2xdlc1.wl%tiwai@suse.de> (raw)
In-Reply-To: <s5hboy3f12c.wl%tiwai@suse.de>

At Sun, 12 Jun 2011 18:48:27 +0200,
Takashi Iwai wrote:
> 
> At Sat, 11 Jun 2011 18:25:36 +0800,
> Harry Butterworth wrote:
> > 
> > Hi,
> > 
> >     I have redone the patch against today's git repositories.
> > Creative have not yet got back to me about the PLL initialization.
> > Perhaps we can fix that later.
> > 
> >     I have only put the PCI ID in the pci_ids_compat.h.in file.  Is it
> > going to be necessary to add the PCI device ID somewhere in the kernel
> > tree to avoid breaking the kernel build?
> 
> Yes, include/linux/pci_ids.h is the place to change.
> But I can fix it by myself, too.
> 
> > 
> > > A few comment about the patch:
> > >
> > > - Instead of adding have_dedicated_mic and have_output_switch
> > >  callbacks in every place, I'd put some bit flags indicating the
> > >  capabilities, and set at the initialization appropriately.
> > 
> > I had a go at this in the patch 0002-ALSA...
> > 
> > > - A few easy coding-style issues; run scripts/checkpatch.pl and fix
> > >  the errors appropriately.
> > 
> > checkpatch now reports no errors.
> > 
> > I've only tested these changes with my Titanium HD card.  I don't have
> > any of the other X-Fi cards so I couldn't do any regression testing.
> > 
> > If there's anything else I need to do, please let me know.
> 
> I'm going to check patches in a more detail tomorrow.

Now both patches were applied to sound git tree.
Just minor fixes were applied in addition (coding-style issues in the
second patch and added the definition in include/linux/pci_ids.h in
the first patch).


thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2011-06-14  5:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30 13:22 Creative X-Fi Titanium HD ctxfi bugs 5378 5218 4868 Harry Butterworth
2011-06-03 15:44 ` Takashi Iwai
2011-06-11 10:35   ` Harry Butterworth
2011-06-11 10:39     ` Harry Butterworth
     [not found]   ` <BANLkTinovea9fE1Hxey83W+WAiYGBv600Q@mail.gmail.com>
2011-06-12 16:48     ` Takashi Iwai
2011-06-14  5:38       ` Takashi Iwai [this message]
2011-06-14  8:23         ` Harry Butterworth
2011-06-16  0:32           ` Harry Butterworth
2011-06-16  5:30             ` Takashi Iwai
2011-06-05  4:35 ` Marshall DeBerry
     [not found] <BANLkTikkMNPZ02ZmPtrJSmSEWi8nkfXsag@mail.gmail.com>
2011-06-03 12:26 ` Harry Butterworth

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=s5hei2xdlc1.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=Alsa-devel@alsa-project.org \
    --cc=heb1001@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox