From: Florian Fainelli <florian@openwrt.org>
To: Maxime Bizon <mbizon@freebox.fr>
Cc: ralf@linux-mips.org, netdev@vger.kernel.org,
afleming@freescale.com, jgarzik@pobox.com,
linux-usb@vger.kernel.org, dbrownell@users.sourceforge.net,
linux-pcmcia@lists.infradead.org, linux-serial@vger.kernel.org,
linux-mips@linux-mips.org
Subject: Re: [PATCH/RFC v1 00/12] Support for Broadcom 63xx SOCs
Date: Wed, 22 Oct 2008 15:58:23 +0200 [thread overview]
Message-ID: <200810221558.27338.florian@openwrt.org> (raw)
In-Reply-To: <1224382022-24173-1-git-send-email-mbizon@freebox.fr>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
Hello,
Le Sunday 19 October 2008 04:07:02 Maxime Bizon, vous avez écrit :
> CPUs supported are 6348 and 6358. Support is provided for integrated
> UART, USB OHCI and EHCI, PCI controller, ethernet MAC & PHY and
> PCMCIA/Cardbus controller.
I got some pending patches on top of yours to add support for earlier : 6338
and 6345, as well as newer revisions of the SoC : 6368 and 6816.
Additionnaly, the cable version (BCM3348/BCM3349) should be fairly well
supported now, for which I need to have a serious try.
I prefer you get some feedback on your patches first before submitting my
changes.
--
Best regards, Florian Fainelli
Email : florian@openwrt.org
http://openwrt.org
-------------------------------
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-22 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 2:07 [PATCH/RFC v1 00/12] Support for Broadcom 63xx SOCs Maxime Bizon
2008-10-22 13:58 ` Florian Fainelli [this message]
2008-11-25 17:44 ` Florian Fainelli
2008-11-25 17:44 ` Florian Fainelli
2008-10-26 11:26 ` Ralf Baechle
2008-10-26 12:24 ` Florian Fainelli
2008-10-26 12:24 ` Florian Fainelli
2008-10-26 12:34 ` Ralf Baechle
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=200810221558.27338.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=afleming@freescale.com \
--cc=dbrownell@users.sourceforge.net \
--cc=jgarzik@pobox.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mbizon@freebox.fr \
--cc=netdev@vger.kernel.org \
--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.