linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <florian@openwrt.org>
To: Hector Martin <hector@marcansoft.com>
Cc: mbizon@freebox.fr, linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: BCM63xx merge progress
Date: Wed, 2 Dec 2009 11:16:01 +0100	[thread overview]
Message-ID: <200912021116.01290.florian@openwrt.org> (raw)
In-Reply-To: <4B15D4E7.6060707@marcansoft.com>

On Wednesday 02 December 2009 03:45:59 Hector Martin wrote:
> Maxime Bizon wrote:
> > On Wed, 2009-12-02 at 01:25 +0100, Hector Martin wrote:
> >> Well, there's a commit (4059ddb4) that claims to "Add USB OHCI support",
> >> yet it only adds a #include to ohci-hcd.c and a few .h bits. The actual
> >> ohci-bcm63xx.c is missing, which means the OHCI driver probably won't
> >> even compile. It's also missing the relevant platform device stuff in
> >
> > I cannot find this commit in linus' tree nor linux-mips master, where
> > does it come from ?
> 
> Okay, nevermind, that was a screwup by me. At some point one of my
> OpenWRT patch test commits made its way onto the wrong local branch, and
> I didn't notice where it lived. Oops. (This commit was meant to be
> incomplete, it comes straight from the OpenWRT patch). I think I found
> the mips-bcm63xx (proper) patch, tried to search for it on my local
> repo, and this thing popped up and I didn't look at it closely enough.
> This is what I get for trying to work at 4am.
> 
> I take back the 'broken' then, we're just left with 'incomplete'. Makes
> quite a bit more sense now, sorry for the confusion.
> 
> > The remaining two patches that were not merged in 2.6.32 are on top of
> > this tree: http://www.linux-mips.org/git?p=linux-bcm63xx.git
> >
> > They should apply with little difficulty on current upstream kernel and
> > besides the *_be stuffs that need to be cleaned up, they were ACKed by
> > the usb maintainer.
> 
> Cool, I'll see about applying them and working off of that. Thanks for
> the confirmation.
> 
> FWIW, I'm trying to reverse engineer Broadcom's DSL driver, which I hope
> will be useful so we can finally have a properly working OpenWRT
> firmware for DSL routers based on this firmware.

Good luck :)
-- 
WBR, Florian

  reply	other threads:[~2009-12-02 10:16 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
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 [this message]
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=200912021116.01290.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 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).