From: Monty Montgomery <xiphmont@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Clemens Ladisch <clemens@ladisch.de>,
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 05:14:29 -0500 [thread overview]
Message-ID: <806dafc20911240214x13838c9bma939c4a07ea25a82@mail.gmail.com> (raw)
In-Reply-To: <1259055721.29729.277.camel@macbook.infradead.org>
> Where did the new firmware come from?
It is the firmware as originally appeared in in Tapio's original out
of tree driver in 2002-ish, was committed to the tree in 2.6.12, and
remained unchanged until it was removed in the firmware cleanup in
2.6.27. The firmware header at that time held the bitstream, loader
and SPIDF/MIDI firmware images all in one header file. In 2.6.27,
they were all split back out into their original ihex sources but this
operation seems to have been botched. I wrote a quick script to
redump the data from the original header back into ihex format as I
couldn't locate the original ihex files Tapio apparently originally
worked from (the comments and partial original ihex inclusion in
Tapio's header are admittedly confusing and apparently led the
cleaner-upper astray).
Monty
next prev parent reply other threads:[~2009-11-24 10:14 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
2009-11-24 9:52 ` Clemens Ladisch
2009-11-24 10:14 ` Monty Montgomery [this message]
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=806dafc20911240214x13838c9bma939c4a07ea25a82@mail.gmail.com \
--to=xiphmont@gmail.com \
--cc=akpm@osdl.org \
--cc=clemens@ladisch.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=retroeffective@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®