linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: How to support SDIO wifi/bt in DT
Date: Thu, 16 Jan 2014 20:03:45 +0000	[thread overview]
Message-ID: <20140116200345.GZ15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOesGMjZzwuOvt3iV+CDXZr5-hWvay_xaO-RH5syB1D-zGVu+A@mail.gmail.com>

On Thu, Jan 16, 2014 at 12:00:47PM -0800, Olof Johansson wrote:
> On Thu, Jan 16, 2014 at 11:58 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Thu, Jan 16, 2014 at 09:15:17AM -0800, Olof Johansson wrote:
> >> We've dealt with it with local code in our tree for Chrome OS, and I
> >> suspect everyone else has too. It's definitely time to solve
> >> generically.
> >
> > As there's no code for any Cubox-i or Hummingboard (they're both purely
> > DT), what this means is that the answer to Wifi/BT support in mainline is
> > that this is "impossible at the moment"...
> >
> > I guess this is becoming a higher priority issue which really needs to be
> > solved somehow. :)
> 
> I'm looking at it right now actually, might as well sort it out while
> people are paying attention. Patches a little later today unless I get
> distrac^Winterrupted. :)

I'll look forward to them, but I may not be able to do much more this
evening.

-- 
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up.  Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".

  reply	other threads:[~2014-01-16 20:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 13:36 How to support SDIO wifi/bt in DT Russell King - ARM Linux
2014-01-16 13:51 ` Chen-Yu Tsai
2014-01-16 14:02 ` Arnd Bergmann
2014-01-16 17:15   ` Olof Johansson
2014-01-16 19:58     ` Russell King - ARM Linux
2014-01-16 20:00       ` Olof Johansson
2014-01-16 20:03         ` Russell King - ARM Linux [this message]
2014-01-17  9:39         ` Alexandre Belloni
2014-01-17 10:06           ` Chen-Yu Tsai
2014-01-17 10:14             ` Alexandre Belloni
2014-01-17 10:44           ` Andrew Lunn
2014-02-05 17:11             ` Mark Brown
2014-01-16 21:46     ` Arnd Bergmann
2014-01-16 21:52       ` Olof Johansson
2014-01-16 22:14       ` Marcel Holtmann
2014-01-17  3:08     ` Nicolas Pitre
2014-01-17 14:47       ` Arnd Bergmann
2014-01-17 15:14       ` Rob Herring
2014-01-17 16:58         ` Nicolas Pitre
2014-01-19 19:29           ` Olof Johansson
2014-01-19 20:28             ` Arnd Bergmann
2014-01-19 23:26               ` Olof Johansson
2014-01-19 23:09             ` Alexandre Belloni
2014-01-19 23:30               ` Olof Johansson
2014-01-20  3:57                 ` Olof Johansson
2014-01-17  9:02     ` Alexandre Belloni
2014-01-17  9:38       ` Nicolas Ferre
2014-01-16 14:08 ` Alexandre Belloni
2014-01-16 14:34   ` Russell King - ARM Linux

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=20140116200345.GZ15937@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).