From: Lars-Peter Clausen <lars@metafoo.de>
To: Graham Gower <graham.gower@gmail.com>
Cc: Florian Fainelli <florian@openwrt.org>,
Mirko Vogt <lists@nanl.de>,
linux-mips@linux-mips.org
Subject: Re: [PATCH 0/3] XBurst JZ4730 support
Date: Fri, 26 Feb 2010 02:51:00 +0100 [thread overview]
Message-ID: <4B872904.6070208@metafoo.de> (raw)
In-Reply-To: <6ec4247d1002251312h37f409bdp2384d7fcbddbb321@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
Graham Gower wrote:
> On 25 February 2010 18:22, Florian Fainelli <florian@openwrt.org> wrote:
>> Maybe you should work with the OpenWrt and qi-hardware guys to get the
jz4740
>> also merged in the same time?
>
> I've not seen any active attempt to get xburst code merged before and
> assumed there was no interest from others. I'm happy to be wrong on
> this.
I'm currently working on linux support for a few jz4740 hbased devices.
And it's definitely a goal get the code merged upstream once it is in
proper shape, but there is still some stuff that needs to be done.
Mostly documentation and smaller cleanups.
>
> My patch does not preclude adding jz4740 support. I don't have any of
> these devices however, so have only included code for the jz4730.
Unfortunately I don't have a jz4730 programmers manual to check so I
can't say for sure, but I guess there is quite some code that could be
shared between between both SoCS(and other jz47xx). I think we don't
want to do what Ingenic did with their codebase and copy 'n paste the
same file with minor modifications for each soc type.
You can find the patches (and files) adding jz4740 support to the
linux kernel at [1] and [2].
I suggest you take a look at it and see if we could use some of the
files(irq, gpio, dma, ...) for a common base between all jz47xx SoCs.
>
> -Graham
- - Lars
[1]
https://dev.openwrt.org/browser/trunk/target/linux/xburst/patches-2.6.32
[2] https://dev.openwrt.org/browser/trunk/target/linux/xburst/files-2.6.32
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkuHKQMACgkQBX4mSR26RiOGCgCdGzATziYC4wYLvz0HNhqwFOYi
OXAAn2mZx0e8qmqHtl+Vfm9vau9urpW+
=nIni
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-26 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 6:28 [PATCH 0/3] XBurst JZ4730 support Graham Gower
2010-02-25 6:29 ` [PATCH 1/3] Add " Graham Gower
2010-02-25 6:30 ` [PATCH 2/3] 8250: serial driver changes for XBurst SoCs Graham Gower
2010-02-25 6:31 ` [PATCH 3/3] net: add driver for JZ4730 ethernet controller Graham Gower
2010-02-25 7:52 ` [PATCH 0/3] XBurst JZ4730 support Florian Fainelli
2010-02-25 21:12 ` Graham Gower
2010-02-26 1:51 ` Lars-Peter Clausen [this message]
2010-02-26 3:34 ` Graham Gower
2010-02-26 11:41 ` blast_dcache32 problem with PREEMPT kernel Anoop P.A.
2010-02-26 11:41 ` Anoop P.A.
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=4B872904.6070208@metafoo.de \
--to=lars@metafoo.de \
--cc=florian@openwrt.org \
--cc=graham.gower@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=lists@nanl.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 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.