From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Huajun Li <huajun.li.lee@gmail.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
acho@novell.com, linux-kernel@vger.kernel.org,
lud <linux-usb@vger.kernel.org>,
usb-storage@lists.one-eyed-alien.net,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Linux 3.0: broken ums_eneub6250
Date: Sat, 30 Jul 2011 08:15:23 +0200 [thread overview]
Message-ID: <4E33A17B.2050008@01019freenet.de> (raw)
In-Reply-To: <CA+v9cxbKKxPg29q5Jr3Lf+JOrdQeYhrPqFm4TtK9=c1Xoq3CUw@mail.gmail.com>
Hi Huajun,
Huajun Li schrieb:
> Hi Dunlap and all, The root cause may be the firmware of ENE card
> reader is not integrated yet. You known, after the codes merged from
> staging/keucr into usb-storage, its HEX formated firmware codes were
> removed, and they should go to firmware tree.
>
> Currently, acho@novell.com toke efforts to get these firmware
> license and pushed the patch to dwmw2@infradead.org, I thinks the
> patch is pending now.
>
> Yes, the perfect way to fix the issue is waiting the firmware patch
> applied soon, but to make your card work at once, I think you could
> get a copy of the firmware patch from acho@novell.com. :)
What's the name of the firmware file? I think, there is a repository
somewhere, where I could just get it? Any hints?
Thanks,
Andreas
next prev parent reply other threads:[~2011-07-30 6:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 16:14 Linux 3.0: broken ums_eneub6250 Andreas Hartmann
2011-07-30 1:14 ` Randy Dunlap
2011-07-30 2:50 ` Huajun Li
2011-07-30 6:15 ` Andreas Hartmann [this message]
[not found] <hjXX6-Ee-55@gated-at.bofh.it>
[not found] ` <hk6nE-6kT-5@gated-at.bofh.it>
[not found] ` <hk7Wq-mZ-1@gated-at.bofh.it>
2011-08-07 18:39 ` Andreas Hartmann
2011-08-08 4:22 ` Greg KH
2011-08-08 8:16 ` Andreas Hartmann
2011-08-08 15:33 ` Greg KH
2011-08-08 19:25 ` Andreas Hartmann
2011-08-09 3:39 ` Greg KH
2011-08-10 12:05 ` Andreas Hartmann
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=4E33A17B.2050008@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=acho@novell.com \
--cc=dwmw2@infradead.org \
--cc=huajun.li.lee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=usb-storage@lists.one-eyed-alien.net \
/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