From: Wolfram Sang <w.sang@pengutronix.de>
To: "Albrecht Dreß" <albrecht.dress@arcor.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/5200: make BestComm gen_bd microcode exchangeable
Date: Sat, 3 Oct 2009 16:40:26 +0200 [thread overview]
Message-ID: <20091003144026.GA27519@pengutronix.de> (raw)
In-Reply-To: <1254577821.3331.0@antares>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
> doesn't give any support, so it's all trial and error and error and
> error... If you have any idea, pointers would be appreciated!
Sorry, I hardly know anything about the microcode. From what I know, it
shouldn't be much fun due to various bugs in the Bestcomm engine.
> I don't think so - the message body is a "format=flowed" (RFC 3676)
> text/plain part. Maybe your MUA doesn't display that format correctly
> (Outlook?)?
Hey! No need for insults! ;)
Have to check if my MUA (see headers) supports it. The archives seem to have
split it as well:
http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-October/076236.html
I recall a similar problem, where some archives had the patch correct and some
didn't.
> Or is '3676 in general not acceptable for patches?
Maybe. Could you try without next time, and we will see if it works better?
> P.S.: Did your mtd-ram/physmap_of patch you submitted a while ago make
> it into the stock kernel? I have some pending extra work (16-bit LPB
> RAM access) building on top of it...
Yup, since -rc1. (git log --grep=mtd-ram)
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-10-03 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 19:55 [PATCH] powerpc/5200: make BestComm gen_bd microcode exchangeable Albrecht Dreß
2009-10-03 9:44 ` Wolfram Sang
2009-10-03 13:50 ` Albrecht Dreß
2009-10-03 14:40 ` Wolfram Sang [this message]
2009-10-03 15:09 ` Albrecht Dreß
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=20091003144026.GA27519@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=albrecht.dress@arcor.de \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).