From: Clemens Ladisch <clemens@ladisch.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Monty Montgomery <xiphmont@gmail.com>,
Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: fix multiple eMagic 6|2m regressions introduced in 2.6.27
Date: Tue, 24 Nov 2009 10:52:58 +0100 [thread overview]
Message-ID: <4B0BACFA.90801@ladisch.de> (raw)
In-Reply-To: <1259055721.29729.277.camel@macbook.infradead.org>
David Woodhouse wrote:
> Where did the new firmware come from?
Sorry, I snipped that part of Monty's mail:
> > 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. In fact, it is
> > loading an exact copy of the bistream firmware file that belongs to
> > the emi26 driver rather than the firmware that previously belonged to
> > the emi62. A new firmware/emi62/bitstream.HEX file generated from the
> > old driver's header corrects the problem and the 6|2 works as it did
> > before.
> >
> > Note that the current firmware/emi62/bitstream.HEX mistakenly
> > identifies itself as:
> >
> > // VERSION= 1.0.0.191
> > // DATE= 2002oct28
> >
> > ...this is incorrect and apparently cut out of the old emi62 driver's
> > firmware header and pasted onto the other firmware file.
next prev parent reply other threads:[~2009-11-24 9:52 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
2009-11-24 9:35 ` Monty Montgomery
2009-11-24 9:42 ` David Woodhouse
2009-11-24 9:52 ` Clemens Ladisch [this message]
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=4B0BACFA.90801@ladisch.de \
--to=clemens@ladisch.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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