From: Hector Martin <hector@marcansoft.com>
To: Maxime Bizon <mbizon@freebox.fr>, Florian Fainelli <florian@openwrt.org>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: BCM63xx merge progress
Date: Tue, 01 Dec 2009 23:23:10 +0100 [thread overview]
Message-ID: <4B15974E.1060505@marcansoft.com> (raw)
Hello, Maxime and Florian,
I saw that partial BCM63xx support has been merged into mainline. As I
am interested in developing a driver for this platform, I would like to
inquire as to the state of the remaining bits to merge. As it stands
now, the code merged into mainline is rather broken and incomplete.
I'll be happy to grab the code myself and get the patches in proper
merging order for mainline if nobody else is working / has time for it
at the moment, so I'm asking first.
I have a BCM63xx router and will be testing whatever I work on, both
compiling and running. My current reference is the OpenWRT patchset,
which is against an older kernel but seems to be working pretty well on
the actual hardware. I've also seen the linux-bcm63xx.git tree. Between
these I should be able to put together a decent set of commits that
cleanly apply onto current mainline.
Please let me know what your thoughts are, and whether I should proceed
and work on this myself or whether you have other plans.
--
Hector Martin (hector@marcansoft.com)
Public Key: http://www.marcansoft.com/marcan.asc
next reply other threads:[~2009-12-01 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 22:23 Hector Martin [this message]
2009-12-01 23:05 ` BCM63xx merge progress Florian Fainelli
2009-12-01 23:25 ` Maxime Bizon
2009-12-02 0:25 ` Hector Martin
2009-12-02 1:57 ` Maxime Bizon
2009-12-02 2:45 ` Hector Martin
2009-12-02 10:16 ` Florian Fainelli
2009-12-02 10:14 ` Florian Fainelli
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=4B15974E.1060505@marcansoft.com \
--to=hector@marcansoft.com \
--cc=florian@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=mbizon@freebox.fr \
--cc=ralf@linux-mips.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).