linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/5200: make BestComm gen_bd microcode exchangeable
Date: Sat, 03 Oct 2009 15:50:12 +0200	[thread overview]
Message-ID: <1254577821.3331.0@antares> (raw)
In-Reply-To: <20091003094417.GA24206@pengutronix.de> (from w.sang@pengutronix.de on Sat Oct  3 11:44:17 2009)

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

Hi Wolfram:

Am 03.10.09 11:44 schrieb(en) Wolfram Sang:
> you wrote your own microcode? :)

I modified the bcom_gen_bd_rx_task for a LPB peripheral as to perform  
Endianess swapping during the transfer (works meanwhile :-).    
Modifying the standard kernel code for testing seemed to be the wrong  
approach for me, so I wrote that patch...

If possible, I would also like to have a crc32 calculation performed by  
BestComm, but unfortunately there is no documentation and Freescale  
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!

> approach looks ok to me in general, but this patch is line-wrapped.

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?)?  Or is '3676 in general not acceptable for patches?

[snip]
> spaces instead of tabs
[snip]
> Two empty lines.

Thanks - will submit a fixed patch next week, stay tuned...

Cheers, Albrecht.


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...

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-10-03 13:50 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ß [this message]
2009-10-03 14:40     ` Wolfram Sang
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=1254577821.3331.0@antares \
    --to=albrecht.dress@arcor.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=w.sang@pengutronix.de \
    /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).