From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: Steve Sakoman <sakoman@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 3/4] HSMMC: Add support for the second controller
Date: Wed, 5 Nov 2008 19:32:11 -0800 [thread overview]
Message-ID: <20081106033210.GP21736@atomide.com> (raw)
In-Reply-To: <200811051554.24055.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [081105 15:54]:
> On Monday 03 November 2008, Steve Sakoman wrote:
> > >
> > > I used David's appended patch plus Tony's 4 HSMMC patches.
> > >
> > > I used version 8.73.7p3 of the Marvell SD8686 firmware and helper
> > > binaries and placed them in /lib/firmware.
> >
> > I just tried version 9.70.3p24 of the firmware & helper and have
> > confirmed that it also works.
>
> Ditto ... at least in terms of "iwlist scan" finding a decent set
> of networks. I think something probably should be done to keep
> that chip powered down when it's not in use; it's quite toasty.
> I'm not sure whether that issue comes from the libertas driver,
> the SDIO stack, or somewhere else (hsmmc glue).
>
>
> > This version is much more easily available from the Marvell site. Go to:
> >
> > http://www.marvell.com/drivers/search.do
> >
> > Select "Network Controller" for device type (it's the only choice),
> > and "Linux 2.6 - Fedora" for the OS.
> >
> > You will then be offered two choices, pick
> > SD-8686-LINUX26-SYSKT-9.70.3.p24-26409.P45-GPL. Extract (and then
> > extract the tar image contained within) and look in the FWImage
> > directory. Copy both .bin files to your omap system's /lib/firmware
> > directory and rename helper_sd.bin to sd8686.bin.
>
> Or, for the record, add them to your kernel "firmware" directory
> and using Kconfig set
>
> CONFIG_FIRMWARE_IN_KERNEL=y
> CONFIG_EXTRA_FIRMWARE="sd8686_helper.bin sd8686.bin"
> CONFIG_EXTRA_FIRMWARE_DIR="firmware"
>
> It adds some bloat to the kernel (128+ KBytes) but is painless
> in terms of rootfs configuration.
OK, I've pushed the hsmmc init patches. They still need work though.
Please everybody check your board MMC configuration and send patches
as needed.
Also the write protect interrupts are not handled, and gpio handling
is twl specific. Hopefully a better base for the code anyways.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-06 3:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 2:04 [PATCH 0/4] Init updates for hsmmc, also second controller Tony Lindgren
2008-10-31 2:04 ` [PATCH 1/4] HSMMC: Make hsmmc use omap_ctrl_read/write and existing defines Tony Lindgren
2008-10-31 2:04 ` [PATCH 2/4] HSMMC: Fix voltage defines, make card detect gpio controller specific Tony Lindgren
2008-10-31 2:04 ` [PATCH 3/4] HSMMC: Add support for the second controller Tony Lindgren
2008-10-31 2:04 ` [PATCH 4/4] HSMMC: Misc clean-up for hsmmc init Tony Lindgren
2008-10-31 3:12 ` [PATCH 3/4] HSMMC: Add support for the second controller David Brownell
2008-10-31 3:39 ` Tony Lindgren
2008-10-31 6:41 ` David Brownell
2008-10-31 16:35 ` Tony Lindgren
2008-10-31 4:05 ` Steve Sakoman
2008-10-31 10:00 ` David Brownell
2008-10-31 23:35 ` Steve Sakoman
2008-11-01 0:36 ` David Brownell
2008-11-01 2:31 ` Felipe Balbi
2008-11-01 2:50 ` Steve Sakoman
2008-11-01 3:02 ` David Brownell
2008-11-01 3:11 ` Steve Sakoman
2008-11-03 22:54 ` Steve Sakoman
2008-11-03 23:22 ` Tony Lindgren
2008-11-03 23:36 ` Steve Sakoman
2008-11-05 23:54 ` David Brownell
2008-11-06 3:32 ` Tony Lindgren [this message]
2008-11-06 7:09 ` David Brownell
2008-11-06 17:04 ` Tony Lindgren
2008-11-06 20:19 ` Grazvydas Ignotas
2008-11-07 5:54 ` David Brownell
2008-11-07 9:36 ` Grazvydas Ignotas
2008-11-10 10:36 ` Grazvydas Ignotas
2008-11-12 22:11 ` Tony Lindgren
2008-11-06 20:52 ` David Brownell
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=20081106033210.GP21736@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.com \
/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