Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrus Harmon <cyrus@bobobeach.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [PATCH] add Steinberg UR44 USB Audio Interface support to quirks-table
Date: Thu, 06 Nov 2014 08:54:26 -0800	[thread overview]
Message-ID: <545BA7C2.5010402@bobobeach.com> (raw)
In-Reply-To: <s5hmw841dh2.wl-tiwai@suse.de>

That's what I was looking for!

Thanks!

On 11/06/2014 08:49 AM, Takashi Iwai wrote:
> At Thu, 06 Nov 2014 08:05:43 -0800,
> Cyrus Harmon wrote:
>>
>> On a somewhat related note, is there a way to apply changes to things
>> in, say, sound/usb and compile/install those changes without a few
>> kernel rebuild/install? Or, even better, without a reboot? Would
>> certainly shorting the debug cycle time for me. In this case I'm
>> interested in finding out what quirk->type is when it gets to
>> snd_usb_create_quirk as it looks like the function in the quirk_funcs
>> table that gets called here produces the first suspect error. Adding a
>> dev_info, followed by a kernel rebuild, reinstall, reboot (and the fact
>> that my broken nvidia drivers require reinstalling the video driver
>> every time I install a new kernel) makes for a tedious process!
> It's a standard procedure, something like...
>
> 	% mkdir /somewhere
> 	% cd /somewhere
> 	% cp -a /there/linux/sound .
> 	% patch -p1 < your-usb.patch
> 	% make -C /lib/modules/`uname -r`/build M=$PWD/sound/usb
> 	% su
> 	# make -C /lib/modules/`uname -r`/build M=$PWD/sound/usb modules_install
> 	# modprobe -r snd-usb-audio
> 	# modprobe snd-usb-audio
>
>
> Takashi

  reply	other threads:[~2014-11-06 16:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-09 18:12 [PATCH] add Steinberg UR44 USB Audio Interface support to quirks-table Cyrus Harmon
2014-03-10  9:42 ` Takashi Iwai
2014-03-10 12:07 ` Clemens Ladisch
2014-03-10 15:26   ` Cyrus Harmon
2014-03-10 15:30     ` Takashi Iwai
2014-03-10 15:40     ` Clemens Ladisch
2014-03-11  6:33       ` Cyrus Harmon
2014-03-11  8:31         ` Clemens Ladisch
2014-03-11  9:30           ` Cyrus Harmon
2014-03-17 16:29           ` Cyrus Harmon
2014-11-04  0:36             ` Cyrus Harmon
2014-11-04  6:28               ` Takashi Iwai
2014-11-04  8:55                 ` Cyrus Harmon
2014-11-05 23:14                   ` Takashi Iwai
2014-11-06  4:39                     ` Cyrus Harmon
2014-11-06  5:28                       ` Vlad Catoi
2014-11-06  5:32                         ` Cyrus Harmon
2014-11-06 13:46                           ` Vlad Catoi
2014-11-04  8:59               ` Clemens Ladisch
2014-11-04  9:00             ` Clemens Ladisch
2014-11-05 18:16               ` Cyrus Harmon
2014-11-05 21:17                 ` Clemens Ladisch
2014-11-06  5:47                   ` Cyrus Harmon
2014-11-15 13:00                     ` Clemens Ladisch
2015-02-03  7:14                       ` Cyrus Harmon
2014-11-06 16:05                   ` Cyrus Harmon
2014-11-06 16:49                     ` Takashi Iwai
2014-11-06 16:54                       ` Cyrus Harmon [this message]
2014-11-08  4:24                         ` Vlad Catoi
2014-11-08  4:25                         ` Vlad Catoi
2015-02-03  6:56                       ` Cyrus Harmon
2015-02-03  9:02                         ` Takashi Iwai
2014-11-06 17:32                     ` Clemens Ladisch
  -- strict thread matches above, loose matches on Subject: below --
2014-03-10 15:37 Cyrus Harmon

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=545BA7C2.5010402@bobobeach.com \
    --to=cyrus@bobobeach.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox