[PATCH/RFC v1 00/12] Support for Broadcom 63xx SOCs

[PATCH/RFC v1 00/12] Support for Broadcom 63xx SOCs

[Maxime Bizon]

[first try at patch series mailing, if you're in to/cc list by mistake
please tell me]


Hello everyone,

This is a set of patches that add support for the Broadcom 63xx series
of CPUs and  (some) integrated devices. These are  popular MIPS32 SOCs
found in a lot of DSL modems.

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.

Board support is still rough, each vendor seems to have its own way of
identifying the board  type in nvram, that's why  it will probably not
work out of  the box.  So DON'T FLASH IT BLINDLY  on your modem unless
you have a serial cable, prefer tftpboot/nfsroot for testing.

I used linux-mips git tree  master to generate theses patches, this is
probably  inappropriate considering  they  touch multiple  subsystems.
Since all patches  depends on first two of the series  I wonder how to
submit this properly for inclusion in one merge window (if that's even
do-able).

Patches are also available here in case they were too big:
http://88.191.35.171/bcm63xx/patches/linux-mips-bcm63xx/v1/


I would like to thank my company for letting me release this (hi
boss), and also Broadcom who gave its blessing.

Happy hacking !

-- 
Maxime

Re: [PATCH/RFC v1 00/12] Support for Broadcom 63xx SOCs

[Florian Fainelli]

[-- 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 --]

Re: [PATCH/RFC v1 00/12] Support for Broadcom 63xx SOCs

[Ralf Baechle]

On Sun, Oct 19, 2008 at 04:07:02AM +0200, Maxime Bizon wrote:

> [first try at patch series mailing, if you're in to/cc list by mistake
> please tell me]

In the Linux world people more complain about email they do not receive
than they receive unnecessarily.

Looks ok - the only thing that's a bit strange about this email is that
git-send-email which you seem to have used normally sends out all emails
as reply either to the one preceeding in the series or or the first of
all - but yours arrived without reply headers.

This means the receiver has to be careful to apply things in the right
order since the mail client probably will display them in the order of
arrival, if emails get reordered in transmission.

> This is a set of patches that add support for the Broadcom 63xx series
> of CPUs and  (some) integrated devices. These are  popular MIPS32 SOCs
> found in a lot of DSL modems.
> 
> 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.
> 
> Board support is still rough, each vendor seems to have its own way of
> identifying the board  type in nvram, that's why  it will probably not
> work out of  the box.  So DON'T FLASH IT BLINDLY  on your modem unless
> you have a serial cable, prefer tftpboot/nfsroot for testing.
> 
> I used linux-mips git tree  master to generate theses patches, this is
> probably  inappropriate considering  they  touch multiple  subsystems.
> Since all patches  depends on first two of the series  I wonder how to
> submit this properly for inclusion in one merge window (if that's even
> do-able).

As agreed earlier I've setup a git tree on linux-mips.org at
/pub/scm/linux-bcm63xx.git which also is visible on.
http://www.linux-mips.org/git.

If you want to send me any updates then it's also ok to send me a patch
relative to an earlier patch.  I'll then just fold it into that earlier
patch.

  Ralf

Re: [PATCH/RFC v1 00/12] Support for Broadcom 63xx SOCs

[Florian Fainelli]

Hey Ralf,

Le Sunday 26 October 2008 12:26:01 Ralf Baechle, vous avez écrit :
> As agreed earlier I've setup a git tree on linux-mips.org at
> /pub/scm/linux-bcm63xx.git which also is visible on.
> http://www.linux-mips.org/git.

Thank you very much ! The repository description needs fixing though 
(currently: description  Working Repository for integration of Routerboard 
532 patches.)
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH/RFC v1 00/12] Support for Broadcom 63xx SOCs

[Ralf Baechle]

On Sun, Oct 26, 2008 at 01:24:17PM +0100, Florian Fainelli wrote:

> Thank you very much ! The repository description needs fixing though 
> (currently: description  Working Repository for integration of Routerboard 
> 532 patches.)

Fixed.

  Ralf

Re: [PATCH/RFC v1 00/12] Support for Broadcom 63xx SOCs

[Florian Fainelli]

Hi again,

Le Wednesday 22 October 2008 15:58:23 Florian Fainelli, vous avez écrit :
> I prefer you get some feedback on your patches first before submitting my
> changes.

So the OpenWrt community did the following succesful tests :

- Inventel Livebox Pro (Need the OpenWrt patches plus some glue code to 
retrieve the MAC address) (6348)
- Neufbox 4 (6358)
- Comtrend CT536+ (6348)
- A custom design based on a BCM6348

There might be other successful reports as well.
-- 
Best regards, Florian Fainelli
Email : florian@openwrt.org
http://openwrt.org
-------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html