From: David Woodhouse <dwmw2@infradead.org>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Monty Montgomery <xiphmont@gmail.com>,
Linux kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Der Mickster <retroeffective@gmail.com>
Subject: Re: PATCH: fix multiple eMagic 6|2m regressions introduced in 2.6.27
Date: Tue, 24 Nov 2009 09:42:01 +0000 [thread overview]
Message-ID: <1259055721.29729.277.camel@macbook.infradead.org> (raw)
In-Reply-To: <4B0BA71B.8040800@ladisch.de>
On Tue, 2009-11-24 at 10:27 +0100, Clemens Ladisch wrote:
>
> > 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.
Where did the new firmware come from?
I think the best option at this point is to remove it from the firmware/
directory and add the new one to the linux-firmware.git repository.
--
dwmw2
next prev parent reply other threads:[~2009-11-24 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 8:54 Monty Montgomery
2009-11-24 8:59 ` Monty Montgomery
2009-11-24 9:27 ` Clemens Ladisch
2009-11-24 9:35 ` Monty Montgomery
2009-11-24 9:42 ` David Woodhouse [this message]
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=1259055721.29729.277.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=clemens@ladisch.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®