From: Florian Fainelli <florian@openwrt.org>
To: Hector Martin <hector@marcansoft.com>
Cc: Maxime Bizon <mbizon@freebox.fr>,
linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: BCM63xx merge progress
Date: Wed, 2 Dec 2009 00:05:06 +0100 [thread overview]
Message-ID: <200912020005.07407.florian@openwrt.org> (raw)
In-Reply-To: <4B15974E.1060505@marcansoft.com>
Hello Hector,
Le mardi 1 décembre 2009 23:23:10, Hector Martin a écrit :
> 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.
Everything that Maxime sent is, or will be merged either in 2.6.32 or in
2.6.33, that includes:
- arch/mips/bcm63xx (will be in 2.6.32)
- USB driver bits (2.6.33)
- Ethernet MAC driver bits (2.6.32)
- Ethernet PHY driver bits (2.6.32)
- UART driver (2.6.32)
- PCMCIA support (2.6.32)
>
> 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.
We maintain a couple of different patches for OpenWrt, specifically the mtd
partition parser since we provide images, so the box should boot from Flash.
That driver is not in a mergable state at the moment. There is also a embryon
of a SPI driver and a watchdog driver, which I will probably submit once
cleaned up.
>
> Please let me know what your thoughts are, and whether I should proceed
> and work on this myself or whether you have other plans.
>
My plans are currently to maintain the bcm63xx board code and drivers in a
working state for the community, probably not much.
--
Best regards, Florian Fainelli
Email: florian@openwrt.org
Web: http://openwrt.org
IRC: [florian] on irc.freenode.net
-------------------------------
next prev parent reply other threads:[~2009-12-01 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 22:23 BCM63xx merge progress Hector Martin
2009-12-01 23:05 ` Florian Fainelli [this message]
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=200912020005.07407.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=hector@marcansoft.com \
--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 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.