Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Dr Nicholas J Bailey <nicholas.bailey@glasgow.ac.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: usb-usx2y: playback fails with Tascam US122 on	kernel 3.14
Date: Thu, 21 Aug 2014 18:16:51 +0200	[thread overview]
Message-ID: <s5hr409akcs.wl-tiwai@suse.de> (raw)
In-Reply-To: <13813163.9xG9j8aSFS@arial>

At Thu, 21 Aug 2014 17:14:04 +0100,
Dr Nicholas J Bailey wrote:
> 
> On Thursday 21 August 2014 09:02:44 you wrote:
> > At Wed, 20 Aug 2014 18:50:21 +0100,
> > 
> > Dr Nicholas J Bailey wrote:
> > > ...
> > > So the thing is, I can't make any stock kernel work on my Debian laptop,
> > > which means there aren't two points between which to bisect.
> > > 
> > > That's all I've got time for at the moment. I'll append the notes I made
> > > yesterday and today while the builds and tests were going on, just in case
> > > they are any help. At least I have a kernel (3.10.11) that works for now,
> > > but unless somebody who really knows what they are doing is going on the
> > > case, it looks like its just a matter of time before I'll be buying a
> > > whole bunch of new audio interfaces. We have at least 4 or 5 of these
> > > Tascam US-122 boxes, and use them quite a lot, so I am nervously
> > > fingering my wallet... :(
> > Try to build 3.10.11 from linux-stable tree manually and see whether
> > it works.  If yes, there must be a fix between 3.10 and 3.10.11, and
> > you can bisect it easily.
> > 
> > If the manual built 3.10.11 kernel doesn't work, it's most likely a
> > kernel config issue, assuming that Debian doesn't put so many own
> > kernel patches (especially for the sound stuff).
> > 
> > 
> > Takashi
> 
> OK, I don't understand git very well. When I first cloned the kernel repo, I 
> did git tag -l, and I'd swear that there were only tags of the form 
> v<major>.<minor>(-rc[0-9]+)? but now I give the same command again I get tags 
> like v<major>.<minor>.<subminor>(-rc[0-9]+)? That's why I tried to build 3.10 
> and 3.11.

It depends where you clone the git repo from.  If you cloned from
linux-stable tree, it should have contained all 3.10.x stuff.  If you
cloned from Linus tree, it contains only the initial 3.10 and
3.10-rc*, but no 3.10.x stable.


Takashi

      reply	other threads:[~2014-08-21 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 14:51 usb-usx2y: playback fails with Tascam US122 on kernel 3.14 Dr Nicholas J Bailey
2014-08-06 16:43 ` Dr Nicholas J Bailey
2014-08-06 16:45   ` Dr Nicholas J Bailey
2014-08-06 17:19   ` Daniel Mack
2014-08-08  6:13     ` Takashi Iwai
2014-08-20 17:50     ` Dr Nicholas J Bailey
2014-08-21  7:02       ` Takashi Iwai
2014-08-21 16:14         ` Dr Nicholas J Bailey
2014-08-21 16:16           ` Takashi Iwai [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=s5hr409akcs.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=nicholas.bailey@glasgow.ac.uk \
    /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