mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
--
Daniel Savi
Nidelbadstrasse 6
8038 Zürich
daniel.s...@gaess.ch
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
olling the MX-1 itself).
I was wondering if the driver can be altered to include these additional
MIDI ports. And if this message is more apropriate for the dev list.
Cheers,
Daniel
___
Alsa-user mailing list
Alsa-user@lists.source
2016-08-24 9:15 GMT+02:00 Clemens Ladisch :
> Daniel wrote:
>> I have a problem for a long time with an USB audio and USB MIDI device
>> (DJ controller) that used to work flawlessly on a now very old
>> 3.0.0-12 kernel based (ubuntu studio) system but that crashes for any
&g
long end hopefully solve the problem. (I still have the old
working system installed when any system / configuration comparisons
could help).
Best regards,
Daniel
--
___
Alsa-user mail
On 08/22/2016 08:34 PM, Norman nolte wrote:
> On 08/22/2016 08:49 AM, Daniel Mack wrote:
>> On 07/19/2016 10:08 PM, Norman nolte wrote:
>>> Currently the patch is only activated for UD-H01 and other models
>>> sharing the same usb product id but it is possible t
le (git commit
> 7040b6d1febfdbd9c1595efb751d492cd2503f96). So first of all many thanks
> to Clemens Ladisch, Julien Benoist, Daniel Mack et al. who initially
> debugged the issue and patched the kernel.
>
> Unfortunately I still have problems which clicks and crackles even with
> patched kernels when playing dist
On 09/22/2015 09:03 PM, sypwex wrote:
> On Tue, Sep 22, 2015 at 2:17 PM, Daniel Mack wrote:
>>
>> Yes, this device only offers HID and DFU (for firmware updates), so
>> you'll have to parse the HID data it produces.
>>
>
> Ok, but device looks like p
HID data it produces. Use the hidraw interface
to get to the uncached information. Whether you can use an existing tool
to do that depends on what you want to achieve with this device.
In either case, there is no hardware MIDI port on this device, so the
firmware d
so this approach is definitely a dead end.
What does 'lsusb -v' show when you plug in the device?
Thanks,
Daniel
--
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
Hello,
I have a new laptop (Asus ROG G751JT) and I can't figure out, why the
headphone jack is not working.
I tried alsamixer (with sudo) and different options, but nothing helped.
So I tried to use the built-in speakers and they work well.
But if I run multiple programs, which can play sounds,
On Mon, Mar 9, 2015 at 8:07 AM, Daniel Smedegaard Buus
wrote:
> On Sun, Mar 8, 2015 at 10:59 PM, Bill Unruh wrote:
>> See www.theory.physics.ubc.ca/soundcard/resample.html
>
> Thank you for your input, Bill, and for the link, it'll be my breakfast read
> :)
>
That po
; AudioAlchemy 2.0). That's why I'd like to avoid to
introduce any :)
Thank you for your input, Bill, and for the link, it'll be my breakfast read :)
Daniel
> See www.theory.physics.ubc.ca/soundcard/resam
On Sun, Mar 8, 2015 at 8:59 PM, Clemens Ladisch wrote:
> Daniel Smedegaard Buus wrote:
>> I'd like to add a small delay to the 44.1 kHz output, and I've seen
>> some examples of introducing delays to a virtual device by using
>> lsdspa. However, according to LSDSPA
;.
I cannot use buffer_size and friends on the plug or the slave as
they're only valid for hw types...
Is there a way to do this?
Thanks in advance,
Daniel :)
My current .asoundrc:
# AKA Secret Rabbit Code resampler (best conversion, highest CPU utilization):
defaults.pcm.rate_convert
sable". Works at 48 kHz.
Is this a limitation or am I just doing it wrong? Hope I'm not being a
retard (more than usual, anyway).
I've added my conf below. Hope to hear from someone. Thank you :)
Daniel
~/.asoundrc:
defaults.pcm.rate_converter "samplerate_best"
ther you see a sane pattern with usbmon. If you can, tracing
the data on I2S is also a useful way that would show you whether the USB
stack in your device does the right thing.
Daniel
--
Meet PCI DSS 3.0 Compliance Requirem
On 08/15/2014 05:25 PM, Lionel wrote:
> Thanks Daniel!
You're welcome!
> I decided to ask the vendor to fix the bug in the firmware. Do I have
> any expectation of success?
Probably not. Most audio hardware vendors don't care about Linux.
> What should be the best way to
Hi,
On 08/15/2014 04:00 PM, Lionel wrote:
> Hi Daniel. This is trace when i connect the midi controller.
Thanks. This one here is the setup packet followed by the answer, which
is the device descriptor:
> 8801cbae2a80 1534946150 S Ci:2:000:0 s 80 06 0100 0040 64 <
>
tor is garbled.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/usb/usbmon.txt
Thanks,
Daniel
--
___
Alsa-user mailing list
Alsa-user@lists.
it did before? What's the suspected relation between the
firmware and the issue you're seeing?
Daniel
--
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
ws
> system between the device and the vendor's device driver.
>
> Then to apply a patch to ALSA enabling the necessary signals - but
> perhaps that is beyond the remit of ALSA?
Exactly. You can use usbmon to trace USB packets under Linux, see
Documentation/usb/usbmon.txt. That also
On 06/12/2014 12:14 AM, je...@web.de wrote:
> I just updated to kernel 3.15.0. Expectedly as with RC8 there is no change.
>
> Daniel, what makes you think, the 'midi3' node causes the warning? The
> warning appears not only for 'midi3' (and 'dmmidi3
our only connected midi device? IOW - are there any *before* you plug
in the USB device? How many after?
And how many midi devices does the device expose? I'm puzzled by the
'midi3' node that causes the warning
ume this issue goes away if you build the kernel
without OSS emulation support? Try SOUND_OSS=n as a first step.
Thanks,
Daniel
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases"
, the information which clock source that is
could be helpful.
> The alsa-info.sh is at
>
> http://www.alsa-project.org/db/?f=f8b4a9c6a4280a0d8b6d5237989f77e93fb82afc
We should really teach alsa-info.sh to dump the 'lsusb -v' output as well :)
Best regards,
Daniel
--
n try to make sense of the content. The goal is to create a Linux
driver that speaks the same protocol, and implements the ALSA interface
on the other side. The existing ul122 driver might be worth reusing, as
it probably has the right skeleton in pla
On 05/20/2014 12:08 AM, jean-noël chardron wrote:
>
> Also, I the sound card is a high-speed USB device, so you certainly need
> ehci_hcd. Which error did you see?
>
>
> Daniel
>
> t seems that there is a constraint on the usb.. the driver is only in
>
d
ehci_hcd. Which error did you see?
Daniel
--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalabilit
rder to fix it.
Daniel
--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Seleni
On 05/14/2014 03:03 AM, Masaru Nomiya wrote:
> Daniel Mack has written:
>> if ((chip->usb_id == USB_ID(0x0644, 0x8038) || /* TEAC UD-H01 */
>> chip->usb_id == USB_ID(0x0644, 0x8043)) && /* TEAC UD-501 */
>> ep->syncmaxsize == 4) {
>
USB_ID(0x0644, 0x8043)) && /* TEAC UD-501 */
ep->syncmaxsize == 4) {
printk(KERN_ERR "XXX %s():%d\n", __func__, __LINE__);
ep->udh01_fb_quirk = 1;
}
Then check for "XXX" in the logs when you plug in the device.
Daniel
---
On 05/13/2014 11:55 AM, Masaru Nomiya wrote:
> Daniel Mack has written:
>
>> It is related, but the code relies on the boolean variable
>> sender->udh01_fb_quirk which should be set for you device by the patch I
>> sent you. You could add this line inside this i
On 05/12/2014 10:15 AM, Masaru Nomiya wrote:
> Daniel Mack has written:
>> Yes. If the quirk doesn't work for you, the device needs some other
>> workaround than the UD-H01.
>
> Is this not related?
>
> [...]
> if (unlikely(sender->udh01_fb_quirk))
concerning loading snd-usb-audio with nrpacks option?
Yes, this parameter has been removed by a patch which reworks the packet
size calculation logic.
For details, see commit 976b6c064:
https://git.kernel.org/cgit/linux/kernel
On 05/11/2014 06:57 AM, Masaru Nomiya wrote:
> In the Message;
>
> Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
> Message-ID : <536e5f58.4020...@zonque.org>
> Date & Time: Sat, 10 May 2014 19:18:16 +0200
>
> Daniel Mack has written:
the patch yesterday; it should show up in the next
>>> stable kernel.
>
>> FYI, your patch also addresses some playback issues I have experienced
>> with another device - TEAC AI-501DA - which shares the same USB-ID.
>
> Unfortunately, still sounds distor
nd as I said - you should
first manage to use the device with aplay.
This is just a hint on where to continue debugging. I'll be 'away from
keyboard' for a good week from now on. I'll catch up on this once I'm back!
Thanks,
Daniel
---
other audio sink.
If you see the device with 'aplay -l' or in /proc/asound/cards, JACK and
PA should be able to pick them up just fine. ALSA itself already works
as expected at this point.
Are there any messages in dmesg when you plug in the device?
Thanks,
Daniel
Momentary freq = 192006 Hz (0x18.0030)
which is ~0.003% off. However, in contrast to my tests yesterday, I now
have occasional clicks with --buffer-size=256 as well.
Daniel
--
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
On 04/04/2014 08:54 AM, jul...@benoist.name wrote:
> On 04/03/2014 11:16 AM, Daniel Mack wrote:
>> ... 16bit, so things don't work for you in 192k/16bit, right?
>
> Well, it's not like I had experienced a lot with it, but the few times I
> tried 16/192, I didn'
On 04/03/2014 08:31 PM, Anders Genell wrote:
> 3 apr 2014 kl. 17:54 skrev Daniel Mack :
> Thanks!
>
> I might be able to set up an old laptop I have laying around with
> e.g. Debian and with a VirtualBox running XP SP3.
Ok. If you do, please take captures of the traffic t
without the patch is 'play' from the sox
> package.
I think we're facing two different issues here, as Andrea reported
problems with kernel 3.11, while the patch in question made it for 3.12.
Andrea, could you also try to play the file I posted above? I'd
end my card.
I think a good first step would be to trace the communication between
the driver and the card using a software analyzer. Either on the Windows
side, or on Linux with usbmon, together with a VM such as VirtualBox.
It might be worth the effort, the hardware actually looks quit
On 04/03/2014 11:07 AM, eloib-nnx wrote:
> So , my question is:
>
> Anyone sucess to install babyface in Linux ?
>
> Ps: Why Class compliant work on ipad and not works in Linx ;(
What exactly doesn't work for you? What does 'aplay -l'
Hi Julien,
On 04/02/2014 10:12 AM, jul...@benoist.name wrote:
> On 03/31/2014 12:02 PM, Daniel Mack wrote:
>> If you're really certain about this, and if you can rule out all other
>> components than the kernel, please do a git bisect to find which commit
>> causes thi
[Cc Takashi, maybe he can help]
On 03/28/2014 01:07 PM, Frank Zacharias wrote:
> Hi,
>
> I made a mistake and bought a sound card without looking first if it's
> supported by alsa ("c-media chip? that wont be a problem..."). The
> obvious question is wether it can be supported.
>
> The one I b
ped, but in order to fix
drivers for broken hardware, you'll need to dive into the system a
little deeper than usual.
Best regards,
Daniel
--
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
quot;hw" plugin with aplay. By default, the
"plughw" plugin will kick in and do the format conversion on the fly.
Daniel
--
___
Alsa-user mailing list
Alsa-user@
the device needs some quirks to go into the mode you tested in under
Windows. For that, you'd need to sniff the communication on the wire and
reverse-engineer what the Windows driver does:
http://wiki.wireshark.org/CaptureSetup/USB
HTH,
Daniel
---
ion and control pedal data into your software, and swap
> patches via BOSS TONE STUDIO.
Did you try to record anything from the device (arecord)?
Daniel
--
Managing the Performance of Cloud-Based Applications
Take ad
On 02/18/2014 05:27 PM, Mfdpro Mei wrote:
> 2014-02-18 13:13 GMT-03:00 Daniel Mack :
>> What does 'aplay -l' and 'cat /proc/asound/cards' say? How did you test
>> the audio output?
>
> I tried to test it using "aplay -vv ", but it didn'
erface driver snd-usb-audio
>
>
> Do you have any idea of what is happening?
What does 'aplay -l' and 'cat /proc/asound/cards' say? How did you test
the audio output?
Daniel
--
Managing the P
ses, the most significant byte should be in a
low range. If it isn't, there's a byte shift in the stream.
I could also image a timing issue during initialization, but that's all
just speculating for
3.12 or 3.13. There is some new code
in there to automatically detect USB cards with Roland chipsets and make
them work without explicit quirks table entries.
Best regards,
Daniel
--
Managing the Performance of Cloud-Based Appl
s some issues a far as the Fast Track Pro is
> concerned:
Which kernel version are you using? Also, please provide the output of
'lsusb -v'. Are there any relevant kernel messages when you start the
stream?
Thanks,
Daniel
On 01/30/2014 01:12 AM, ChaosEsque Team wrote:
> Why doesn't OSS emulation allow mixing. I got old OSS aps still blocking
> /dev/dsp.
> Comon, please do the code to allow mixing like alsa apps.
> It's been years and years.
Go troll some other list please.
---
On 01/14/2014 06:09 AM, Dennis New wrote:
> On Fri, 10 Jan 2014 10:16:07 -0500, Dennis New wrote:
>> On Sun, 05 Jan 2014 18:08:40 +0000, Daniel Mack wrote:
>>> Dennis New wrote:
>>>> For the past many linux kernels,
>>>
>>> Can you spot the last ker
ing and stopping the stream might be a good start.
Also, as stated above, please do test on a different machine. Ruling out the
host controller would be a crucial step.
Thanks,
Daniel
--
Rapidly troubleshoot problems
Some newer devices (like Asus T100TA) are using a Realtek ALC5642 chip.
It looks like ALSA does not yet support this chip and I also see that
Realtek does not yet have a datasheet on their site. Any news/thoughts
concerning support for it?
Thanks
--
ing will be replace hardcoded device name for hw:MPD3 and
> adjusting defines either for 64fs or 128fs DSD input file.
Yes, we need more testers around here, and support for more devices. If
you can have a look at this, that'd be much appreciated :)
Thanks,
Daniel
-
rmware.c:223 6fire: error requesting ezusb firmware
> 6fire/dmx6firel2.ihx.
Here's your problem. You have to provide a firmware image for this
device to work.
In order to help others, please edit the ALSA wiki and add th
might be the Windows driver
does something beyond the UAC standard to kick off the stream.
Quite frankly, I don't really know why this device doesn't work for you.
Ideally, you'd be able to trace the USB communication on both Windows
and Linux, and compare them. I don't know if
On 12/18/2013 06:42 PM, Bill Unruh wrote:
> On Wed, 18 Dec 2013, Daniel Mack wrote:
>
>>
>> What's the exact error that you get? What does
>>
>> 'aplay -Dhw:X -f cd /dev/urandom'
>>
>> do (you should hear pink noise @0dB, so beware!).
On 12/18/2013 10:58 AM, Michal Šmucr wrote:
> I'm sorry, i forgot to attach aplay output with hw and sw params
> during playback.
Ah, missed that. So you interrupted aplay with ^C? So it was running,
but you didn't hear a
comparing dumps and values at
> descriptors? I'll have another chance to test it more thoroughly and
> we will definitely write ticket to manufacturers support. But i would
> like to find out more about error we encountered, so i will be
s with different
> releases of snd-usb-audio module and do more thorough test of it, when
> i will have chance.
Alright.
Thanks,
Daniel
--
November Webinars for C, C++, Fortran Developers
Accelerate application
eo SPDIF and I2S I/Os with slightly
> different base firmware by XMOS, but except of one thread on XMOS
> forum i didn't find any information about compatibility with recent
> snd-usb-audio driver.
The driver doesn't know anything about XMOS
On 11/03/2013 11:05 AM, Jyrki Saarela wrote:
> On Sun, Nov 3, 2013 at 11:34 AM, Daniel Mack wrote:
>> If it's not listen in lsusb, it's not an ALSA problem. Are you
>> completely sure about that? Can you double-check with another machine maybe?
>>
>> Are th
aybe?
Are there any dmesg messages added when the device is plugged in?
Daniel
--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Dow
On 10/30/2013 07:01 PM, j...@vollbio.de wrote:
>> Gesendet: Mittwoch, 30. Oktober 2013 um 18:11 Uhr
>> Von: "Daniel Mack"
>> On 10/30/2013 02:42 PM, j...@vollbio.de wrote:
>>>> On 10/30/2013 11:39 AM, j...@vollbio.de wrote:
>>>>>> On 10/
host controller
has a general problem with isochronous transfers and such. If that works
fine, I guess someone needs to look into the usx2y driver.
Best regards,
Daniel
--
Android is increasing in popularity, but the ope
could be too long delays in usb-hcd interrupt handling.
We've recently fixed this by removing some code. Please try this patch:
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=a9d14bc0b188a822e42787d01e56c06fe9750162
Daniel
the kernel log show anything after that? (dmesg)
> I
> can imagine the Line "depends on X86 || PPC || ALPHA" was there for a
> reason...
I actually don't think so, but I haven't looked at the sources yet. It's
just a USB module, which should work on any p
On 10/26/2013 09:49 PM, Peter Bašista wrote:
> On Sat, Oct 26, 2013 at 9:46 PM, Daniel Mack wrote:
>> On 10/26/2013 09:42 PM, Peter Bašista wrote:
>>> You have asked whether this DAC works well in some other OS without
>>> some special drivers. The answer is, to t
anything, I
> will end up debugging the usb communication.
Forget about the map, the default should be fine. That has nothing to do
with the hardware, anyway.
Daniel
--
October Webinars: Code for Performance
Free Intel web
On 10/26/2013 09:17 PM, Daniel Mack wrote:
> On 10/26/2013 09:11 PM, Peter Bašista wrote:
>> $ amixer -c1 contents
>> numid=1,iface=PCM,name='Playback Channel Map'
>> ; type=INTEGER,access=rR--,values=2,min=0,max=36,step=0
>> : values=0,0
>&
On 10/26/2013 09:11 PM, Peter Bašista wrote:
> On Sat, Oct 26, 2013 at 9:00 PM, Daniel Mack wrote:
>> Which kernel is that? ('uname -a')
> Linux peter-P55A-UD4 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9
Ok, that's recent enought.
>> What about mixers? What d
ow much about that
> - I do not even know where to start. So, I have decided to try to ask here.
You can use the usbmon framework for that:
https://www.kernel.org/doc/Documentation/usb/usbmon.txt
Best regards,
Daniel
-
On 07.10.2013 18:46, Frank wrote:
> Recently I picked up a used usb tuner box (TvBox). The video works, but
> so far no sound. Should I have sound if the TvBox audio is working
> correctly.
Send the output of 'lsusb -v', pleas
irks-table.h with the following change
That device is most probably handled by a generic handler Clemens recently
added. Just try a recent 3.11 rc kernel and report if that helps.
If your distribution does not provide such a kernel image, you have to build it
from the git sour
Michael Goffioul wrote:
>On Thu, Aug 22, 2013 at 11:13 PM, Michael Goffioul <
>michael.goffi...@gmail.com> wrote:
>
>> On Thu, Aug 22, 2013 at 11:12 PM, Michael Goffioul <
>> michael.goffi...@gmail.com> wrote:
>>
>>> On Wed, Aug 21, 2013 at 2:20 AM
On 22.08.2013 10:47, john casey wrote:
> Daniel Mack gmail.com> writes:
>
>>> will get to the same non working state.
>>
>> Could you also post the output of "lsusb -v", please?
>>
>> Can you nail the lat
you nail the latest kernel version that worked for you?
Daniel
--
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resource
x kernel in version 3.11-rc5.
Daniel
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2%
1&redirs=1&profile=advanced
>
> Is it just that the documentation+matrix is not up-to-date?
Most probably, yes. I'm not aware of any automatic mechanism that
updates this page. It's a Wiki, and so it's everyone's call to augment it :)
Daniel
-
Hi Jeff,
On 11.07.2013 18:37, Jeff S wrote:
> On Thu, 7/11/13, Daniel Mack wrote:
>> I have added more files Dropbox:
>> https://www.dropbox.com/sh/eq9ed280i1kka4a/hSsAYhyRJ7
>
>> Your system signals an error code of -71, which is an internal USB
>> protocol er
On 11.07.2013 18:37, Jeff S wrote:
> On Thu, 7/11/13, Daniel Mack wrote:
>> Before analyzing anything else: is that PC you run Linux on
>> the same
>> that you use for your Windows tests? Is there any other
>> difference in
>> the setups, like USB hubs for i
Hi Jeff,
please do not top-post.
On 11.07.2013 05:44, Jeff S wrote:
> Thanks for the reply, Daniel.
>
> Yes, switching the Benchmark DAC2 from UAC 1.0 to 2.0 is done in
> hardware.
>
> No Mac OS X drivers or any other software needed to operate in UAC
> 1.0 or 2.0 modes.
&
th USB 1 and 2 modes are here:
> https://www.dropbox.com/sh/eq9ed280i1kka4a/hSsAYhyRJ7
Please also post the kernel messages generated by the driver probe. An
easy way to do this is running 'sudo dmesg -c' before and some seconds
after a device hotplug.
Best,
Daniel
whether there are any relevant mixer settings that need tweaking?
Daniel
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards
a MIDI header.
> 2) 2 other ports, one of which is called a control port which are
> probably internal to
> the SD-50 -- Under MacOSX the thing shows up as 3 MIDI In/Out ports --
> manual page 37.
I assume you installed a 3rd party driver for that?
Best,
Daniel
--
ository, and you can back-port the the quirks entry to
whatever kernel version you fancy. Just refer to the top-most commit in
my tree.
Thanks,
Daniel
--
How ServiceNow helps IT people transform IT departments:
1. A
which has a patch for
this device.
And in step 3, you can skip the optional second part, and also step 6 is
not necessary.
Please let me and the list know if that new kernel works for you.
Best,
Daniel
--
How ServiceNo
uhci_hcd
> Can I help someone to get this device going?
Please post the output of the following commands:
uname -a
cat /proc/asound/cards
lsusb -v
Best,
Daniel
--
How ServiceNow helps IT people transform IT
On 25.05.2013 18:18, Rafa Lafuente wrote:
>
>
>
> 2013/5/25 Daniel Mack mailto:zon...@gmail.com>>
>
> On 24.05.2013 10:33, Rafa Lafuente wrote:
> > Hi again, It seems still the same issue:
> >
> > $ cat /proc/asound/cards
> >
assword)
- plug in the device
- wait for 2 seconds
- run 'sudo dmesg -c' again and post the output of this last command
This will show any messages generated by the kernel when the driver
tries to handle the device.
Thanks,
Daniel
--
On 23.05.2013 15:00, Rafa Lafuente wrote:
> ah!
> I have not deleted the local directory.
> So I will run this command and then?
Then you run 'git pull origin snd-usb'
> follow wiki steps from 3 to 11 ?
Exactly.
And please do not top-
t;http://github.com/zonque/linux.git>
>
> ??
No, just "git pull origin snd-usb", nothing more. This will update your
current state to what's on the server.
If you already deleted your local directory, you can as well start over
and do e
On 23.05.2013 13:02, Clemens Ladisch wrote:
> Daniel Mack wrote:
>> git clone -b snd-usb git://github.com/zonque/linux.git
>
>> The device complies to the UAC1 standard but hides that fact with
>> proprietary descriptors.
>>
>> + {
>&
repository, which has a patch for
this device.
And in step 3, you can skip the optional second part, and also step 6 is
not necessary.
Please let me and the list know if that works for you.
Best,
Daniel
--
Try New R
1 - 100 of 386 matches
Mail list logo
