From: David Woodhouse <dwmw2@infradead.org>
To: Fredrik Noring <noring@nocrew.org>
Cc: "Jaswinder Singh" <jaswinder@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Lars Brinkhoff" <lars@nocrew.org>,
"Tomas Skäre" <tomas@nocrew.org>
Subject: Re: [PATCH] dsp56k: use request_firmware
Date: Thu, 10 Jul 2008 09:53:39 +0100 [thread overview]
Message-ID: <1215680019.11567.242.camel@pmac.infradead.org> (raw)
In-Reply-To: <CFF38114-82BA-4A35-B378-8D0A5628E560@nocrew.org>
On Thu, 2008-07-10 at 09:38 +0200, Fredrik Noring wrote:
> Hi David,
>
> 9 jul 2008 kl. 15.05 skrev David Woodhouse:
> > It is in fact identical. Disassembly with the tools found on
> > sourceforge
> > was fun, since they have endianness bugs, don't recognise the 'JMP'
> > which was the first instruction, and need each 3-byte instruction in
> > the
> > binary to be prefixed with a zero byte to make it 4 bytes. But after
> > sorting that out and going through it instruction by instruction, it
> > really does seem to match.
>
> Heh. Amazing.
>
> [ I think the code can be simplified: It currently copies itself to a
> high program memory location, but this is not necessary because DSP
> soft reset was never implemented (the reset would have been trapped by
> the code, in order to load a new program). The driver instead power-
> cycles the DSP every time a new program is loaded. ]
I did wonder about that. But since we can't test, we're not going to
touch. Better to keep the assembler code which precisely matches the
known-good binary.
--
dwmw2
prev parent reply other threads:[~2008-07-10 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 10:24 Jaswinder Singh
2008-07-06 13:36 ` Fredrik Noring
2008-07-06 15:13 ` Jaswinder Singh
2008-07-06 15:36 ` Fredrik Noring
2008-07-06 15:38 ` Jaswinder Singh
2008-07-06 16:54 ` David Woodhouse
2008-07-06 18:29 ` Fredrik Noring
2008-07-09 13:05 ` David Woodhouse
2008-07-10 7:38 ` Fredrik Noring
2008-07-10 8:53 ` David Woodhouse [this message]
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=1215680019.11567.242.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jaswinder@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernelnewbies@nl.linux.org \
--cc=lars@nocrew.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noring@nocrew.org \
--cc=tomas@nocrew.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 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®