From: Sven Luther <sven@powerlinux.fr>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, domen.puncer@telargo.com
Subject: Re: [PATCH v2 4/7] bestcomm: core bestcomm support for Freescale MPC5200
Date: Mon, 15 Oct 2007 08:12:47 +0200 [thread overview]
Message-ID: <20071015061246.GA25751@powerlinux.fr> (raw)
In-Reply-To: <fa686aa40710141423o69666b16pa7ce6851fa407d5e@mail.gmail.com>
On Sun, Oct 14, 2007 at 03:23:21PM -0600, Grant Likely wrote:
> On 10/14/07, Sven Luther <sven@powerlinux.fr> wrote:
> > On Sun, Oct 14, 2007 at 02:22:16PM -0600, Grant Likely wrote:
> > > On 10/14/07, Sven Luther <sven@powerlinux.fr> wrote:
> > > > On Sat, Oct 13, 2007 at 10:42:05PM -0600, Grant Likely wrote:
> > > > > From: Sylvain Munaut <tnt@246tNt.com>
> > > > >
> > > > > This patch adds support for the core of the BestComm API
> > > > > for the Freescale MPC5200(b). The BestComm engine is a
> > > > > microcode-controlled / tasks-based DMA used by several
> > > > > of the onchip devices.
> > > > >
> > > > > Setting up the tasks / memory allocation and all common
> > > > > low level functions are handled by this patch.
> > > > > The specifics details of each tasks and their microcode
> > > > > are split-out in separate patches.
> > > > >
> > > > > This is not the official API, but a much cleaner one.
> > > > > (hopefully)
> > > > >
> > > > > Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
> > > > > Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> > > >
> > > > Hi Grant, ...
> > > >
> > > > I am unsure if this is a regression with regard to Sylvain's patch, or
> > > > somethign else, but it is no more possible to build bestcomm modular :
> > >
> > > Hmmm, interesting. I'll try that out here this afternoon.
> >
> > Notice that domen said it was working, so it could have been a
> > mismanipulation on my part, or some problem with the debian patches.
> >
> > The older patchset with 2.6.23-rc6 worked fine though, and making the
> > main bestcomm module builtin solved the error messages. I did not spot
> > anything obvious when looking at the code.
>
> Yes, it is a regression. There had been a change to the Makefile.
> I've reverted it and it works fine now. I'll repost v3 shortly.
Ok, thanks.
Friendly,
Sven Luther
next prev parent reply other threads:[~2007-10-15 6:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 4:41 [PATCH v2 0/7] 2nd respin of bestcomm patches Grant Likely
2007-10-14 4:41 ` [PATCH v2 1/7] exports rheap symbol to modules Grant Likely
2007-10-14 4:41 ` [PATCH v2 2/7] rheap: Changes config mechanism Grant Likely
2007-10-15 13:43 ` Kumar Gala
2007-10-15 13:55 ` Grant Likely
2007-10-15 14:03 ` Kumar Gala
2007-10-15 14:06 ` Grant Likely
2007-10-15 14:53 ` Timur Tabi
2007-10-15 14:54 ` Kumar Gala
2007-10-15 14:54 ` Timur Tabi
2007-10-15 15:09 ` Grant Likely
2007-10-14 4:42 ` [PATCH v2 3/7] mpc52xx: Update mpc52xx_psc structure with B revision changes Grant Likely
2007-10-14 4:42 ` [PATCH v2 4/7] bestcomm: core bestcomm support for Freescale MPC5200 Grant Likely
2007-10-14 11:33 ` Sven Luther
2007-10-14 20:22 ` Grant Likely
2007-10-14 20:25 ` Sven Luther
2007-10-14 21:23 ` Grant Likely
2007-10-15 6:12 ` Sven Luther [this message]
2007-10-15 11:55 ` Matt Sealey
2007-10-15 14:04 ` Grant Likely
2007-10-15 20:53 ` Matt Sealey
2007-10-15 20:55 ` Matt Sealey
2007-10-15 21:06 ` Grant Likely
2007-10-16 13:21 ` tnt
2007-10-15 14:06 ` Kumar Gala
2007-10-15 14:20 ` Grant Likely
2007-10-15 14:39 ` Matt Sealey
2007-10-14 4:42 ` [PATCH v2 5/7] bestcomm: ATA task support Grant Likely
2007-10-14 4:42 ` [PATCH v2 6/7] bestcomm: FEC " Grant Likely
2007-10-14 4:42 ` [PATCH v2 7/7] bestcomm: GenBD " Grant Likely
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=20071015061246.GA25751@powerlinux.fr \
--to=sven@powerlinux.fr \
--cc=domen.puncer@telargo.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.