All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Monty Montgomery <xiphmont@gmail.com>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Der Mickster <retroeffective@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: PATCH: fix multiple eMagic 6|2m regressions introduced in 2.6.27
Date: Tue, 24 Nov 2009 10:27:55 +0100	[thread overview]
Message-ID: <4B0BA71B.8040800@ladisch.de> (raw)
In-Reply-To: <806dafc20911240054p74bd4d67h97430a02ba86b468@mail.gmail.com>

Monty Montgomery wrote:
> The eMagic driver code cleanup from 2.6.26->2.6.27 introduces three
> new bugs that prevent the emi62 usb audio device from working.  2.6.31
> continues to be identically broken. Note that this is the 6|2, not the
> 2|6; the 2|6 works properly. The 6|2 does not function at all and will
> oops the kernel when plugged in.

This has been discussed in this thread:
http://lists.linuxaudio.org/pipermail/linux-audio-user/2009-November/064931.html

> Bug 1: a mirror of the loop termination bug that was fixed in the 2|6
> driver last January, causing a similar oops as the 2|6 did in 2.6.27.

My patch for this has already been picked up by akpm.

> Bug 2: the firmware load loop that is supposed to load the firmware
> section that sits in the device's RAM mistakenly uses
> ANCHOR_LOAD_EXTERNAL instead of ANCHOR_LOAD_INTERNAL, a bug from
> copy/pasting out of the preceeding loop.  This is clearly a regression
> from the 2.6.26 source which uses the proper target.
> 
> Bug 3: Fixing the first two problems prevents the oops and allows the
> USB stack to successfully allocate an endpoint without crashing the
> eMagic.  However, the eMagic crashes and lights its red INTERNAL ERROR
> led later as it tries to start up.  This problem can be traced to the
> linux/firmware/emi62/bistream.HEX file, which is loading different
> FPGA firmware as compared to the driver pre-2.6.27.
> [...]
> Due to the size of the patch (the replacement firmware file is 250kB),
> I've not attached it but rather stashed it at:
> 
> http://web.mit.edu/xiphmont/Public/emi/emi62.patch

I don't have much time; David, please handle this.


Clemens

  parent reply	other threads:[~2009-11-24  9:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24  8:54 PATCH: fix multiple eMagic 6|2m regressions introduced in 2.6.27 Monty Montgomery
2009-11-24  8:59 ` Monty Montgomery
2009-11-24  9:27 ` Clemens Ladisch [this message]
2009-11-24  9:35   ` Monty Montgomery
2009-11-24  9:42   ` David Woodhouse
2009-11-24  9:52     ` Clemens Ladisch
2009-11-24 10:14     ` Monty Montgomery
2012-04-17 20:45 ` a62m driver for lion alfie carroll

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=4B0BA71B.8040800@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=retroeffective@gmail.com \
    --cc=xiphmont@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 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.