All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Grill <kgrill@chello.at>
To: alsa-devel@alsa-project.org
Subject: emi62 (may be slightly off-topic)
Date: Tue, 12 Feb 2013 09:17:54 +0100	[thread overview]
Message-ID: <1360657074.2790.71.camel@chello084112006029.chello.at> (raw)
In-Reply-To: <4D894196.4040002@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 865 bytes --]

Hi all,
I'm not quite sure if this is really on-topic as the emi62 loader is not
in alsa-driver. On the other hand, the patch is small (changing only two
bytes in the sources, one in  the binary - as a matter of fact, I fixed
the driver for myself by directly patching the binary), so I'll attach
it here (against the alsa-kernel tree). The driver has been broken since
kernel 2.6.27 (http://xiphmont.livejournal.com/46858.html).
BTW, the firmware for both the 6|2m and the 2|6 in the alsa-firmware
package are in the wrong format (the kernel drivers don't work with raw
binaries but with the binary ihex .fw format), and it is installed in
the wrong place. This may create some confusion - it did so for me. As
the mainstream linux kernel already contains the proper firmware, it
might be the best solution to remove the emi_26_62 stuff altogether.

Regards
Karl


[-- Attachment #2: 0001-emi62-fix.patch --]
[-- Type: text/x-patch, Size: 863 bytes --]

>From 850dfc9bd36b4d76d3bd4279028dd74bc3d7e170 Mon Sep 17 00:00:00 2001
From: Karl Grill <kgrill@chello.at>
Date: Sun, 10 Feb 2013 20:27:25 +0100
Subject: [PATCH] emi62-fix
 fix firmware loading for emi6|2m (was broken since 2.6.27)


Signed-off-by: Karl Grill <kgrill@chello.at>
---
 drivers/usb/misc/emi62.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/usb/misc/emi62.c b/drivers/usb/misc/emi62.c
index ae794b9..4e94b60 100644
--- a/drivers/usb/misc/emi62.c
+++ b/drivers/usb/misc/emi62.c
@@ -197,7 +197,7 @@ static int emi62_load_firmware (struct usb_device *dev)
 		if (INTERNAL_RAM(be32_to_cpu(rec->addr))) {
 			err = emi62_writememory(dev, be32_to_cpu(rec->addr),
 						rec->data, be16_to_cpu(rec->len),
-						ANCHOR_LOAD_EXTERNAL);
+						ANCHOR_LOAD_INTERNAL);
 			if (err < 0)
 				goto wraperr;
 		}
-- 
1.7.2.5


[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2013-02-12  7:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 14:12 how to create alsa nodes? loody
2011-03-17 14:26 ` Clemens Ladisch
2011-03-18  9:03   ` loody
2011-03-23  0:40     ` Connecting a codec to an i2c codec driver Steve Calfee
2011-03-23 11:07       ` Mark Brown
2011-03-23 13:22         ` Steve Calfee
2011-03-23 13:30           ` Mark Brown
2011-03-24 19:56             ` Steve Calfee
2011-03-25 11:43               ` Mark Brown
2013-02-12  8:17       ` Karl Grill [this message]
2013-02-15 14:44         ` emi62 (may be slightly off-topic) Takashi Iwai
2013-02-15 15:28           ` Monty Montgomery
2013-02-15 15:37             ` Monty Montgomery
2013-02-15 16:07               ` Takashi Iwai
2013-02-15 16:14                 ` Monty Montgomery
2013-02-15 16:26                   ` Takashi Iwai
2013-12-11  0:04                     ` Monty Montgomery
2013-12-11 14:34                       ` Takashi Iwai
2013-12-12  7:32                         ` Monty Montgomery
2013-12-12 17:11                           ` Takashi Iwai

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=1360657074.2790.71.camel@chello084112006029.chello.at \
    --to=kgrill@chello.at \
    --cc=alsa-devel@alsa-project.org \
    /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.